2025-11-30 18:45:00.034 UTC postmaster[43401] LOG: starting PostgreSQL 19devel on x86_64-freebsd, compiled by clang-19.1.7, 64-bit 2025-11-30 18:45:00.034 UTC postmaster[43401] LOG: listening on IPv6 address "::1", port 5432 2025-11-30 18:45:00.034 UTC postmaster[43401] LOG: listening on IPv4 address "127.0.0.1", port 5432 2025-11-30 18:45:00.034 UTC postmaster[43401] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" 2025-11-30 18:45:00.036 UTC startup[43407] LOG: database system was shut down at 2025-11-30 18:45:00 UTC 2025-11-30 18:45:00.038 UTC postmaster[43401] LOG: database system is ready to accept connections 2025-11-30 18:45:00.465 UTC unrecognized[43420] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.465 UTC client backend[43420] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.465 UTC client backend[43420] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.470 UTC client backend[43420] pg_regress LOG: connection ready: setup total=6.235 ms, fork=0.560 ms, authentication=0.150 ms 2025-11-30 18:45:00.471 UTC client backend[43420] pg_regress LOG: disconnection: session time: 0:00:00.006 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.477 UTC unrecognized[43428] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.477 UTC client backend[43428] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.477 UTC client backend[43428] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.478 UTC unrecognized[43430] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.478 UTC client backend[43428] pg_regress LOG: connection ready: setup total=3.674 ms, fork=2.352 ms, authentication=0.149 ms 2025-11-30 18:45:00.478 UTC unrecognized[43429] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.478 UTC unrecognized[43431] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.479 UTC client backend[43429] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.479 UTC client backend[43428] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.479 UTC client backend[43429] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.479 UTC client backend[43431] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.479 UTC client backend[43431] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.479 UTC client backend[43429] pg_regress LOG: connection ready: setup total=4.394 ms, fork=3.250 ms, authentication=0.086 ms 2025-11-30 18:45:00.479 UTC client backend[43431] pg_regress LOG: connection ready: setup total=1.507 ms, fork=0.371 ms, authentication=0.082 ms 2025-11-30 18:45:00.480 UTC client backend[43429] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.481 UTC client backend[43430] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.481 UTC client backend[43430] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.481 UTC client backend[43430] pg_regress LOG: connection ready: setup total=3.865 ms, fork=0.369 ms, authentication=0.082 ms 2025-11-30 18:45:00.482 UTC client backend[43430] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.497 UTC client backend[43431] pg_regress LOG: disconnection: session time: 0:00:00.018 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.500 UTC unrecognized[43435] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.500 UTC client backend[43435] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.500 UTC client backend[43435] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.501 UTC client backend[43435] pg_regress LOG: connection ready: setup total=15.558 ms, fork=14.087 ms, authentication=0.136 ms 2025-11-30 18:45:00.502 UTC unrecognized[43440] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.503 UTC client backend[43440] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.503 UTC client backend[43440] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.504 UTC client backend[43440] pg_regress LOG: connection ready: setup total=2.998 ms, fork=1.575 ms, authentication=0.112 ms 2025-11-30 18:45:00.504 UTC unrecognized[43442] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.505 UTC client backend[43442] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.505 UTC client backend[43442] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.505 UTC client backend[43442] pg_regress LOG: connection ready: setup total=1.801 ms, fork=0.394 ms, authentication=0.098 ms 2025-11-30 18:45:00.509 UTC unrecognized[43444] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.510 UTC client backend[43444] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.510 UTC client backend[43444] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.511 UTC client backend[43444] pg_regress LOG: connection ready: setup total=3.233 ms, fork=0.966 ms, authentication=0.126 ms 2025-11-30 18:45:00.511 UTC unrecognized[43445] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.512 UTC unrecognized[43447] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.512 UTC client backend[43445] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.512 UTC client backend[43445] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.513 UTC client backend[43445] pg_regress LOG: connection ready: setup total=4.271 ms, fork=2.965 ms, authentication=0.122 ms 2025-11-30 18:45:00.513 UTC client backend[43445] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.514 UTC client backend[43444] pg_regress LOG: disconnection: session time: 0:00:00.004 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.514 UTC client backend[43447] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.514 UTC client backend[43447] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/test_setup 2025-11-30 18:45:00.519 UTC client backend[43447] pg_regress/test_setup LOG: connection ready: setup total=8.074 ms, fork=0.742 ms, authentication=0.107 ms 2025-11-30 18:45:00.521 UTC client backend[43440] pg_regress LOG: disconnection: session time: 0:00:00.018 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.526 UTC unrecognized[43452] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.526 UTC client backend[43452] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.526 UTC client backend[43452] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.527 UTC unrecognized[43454] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.527 UTC client backend[43452] pg_regress LOG: connection ready: setup total=4.164 ms, fork=2.843 ms, authentication=0.111 ms 2025-11-30 18:45:00.527 UTC client backend[43454] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.527 UTC client backend[43454] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.527 UTC unrecognized[43455] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.527 UTC client backend[43452] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.528 UTC client backend[43455] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.528 UTC client backend[43455] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.528 UTC client backend[43454] pg_regress LOG: connection ready: setup total=2.825 ms, fork=1.603 ms, authentication=0.097 ms 2025-11-30 18:45:00.528 UTC client backend[43455] pg_regress LOG: connection ready: setup total=1.987 ms, fork=0.752 ms, authentication=0.095 ms 2025-11-30 18:45:00.528 UTC unrecognized[43456] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.529 UTC client backend[43456] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.529 UTC client backend[43456] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_setup 2025-11-30 18:45:00.530 UTC client backend[43435] pg_regress LOG: disconnection: session time: 0:00:00.030 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.533 UTC client backend[43456] pg_regress/plperl_setup LOG: connection ready: setup total=6.715 ms, fork=0.409 ms, authentication=0.096 ms 2025-11-30 18:45:00.535 UTC unrecognized[43459] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.535 UTC client backend[43459] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.535 UTC client backend[43459] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.536 UTC client backend[43459] pg_regress LOG: connection ready: setup total=3.581 ms, fork=2.374 ms, authentication=0.097 ms 2025-11-30 18:45:00.536 UTC unrecognized[43460] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.537 UTC client backend[43460] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.537 UTC client backend[43460] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_array 2025-11-30 18:45:00.543 UTC client backend[43460] pg_regress/plpgsql_array LOG: connection ready: setup total=7.716 ms, fork=0.868 ms, authentication=0.110 ms 2025-11-30 18:45:00.545 UTC client backend[43456] pg_regress/plperl_setup ERROR: permission denied to create extension "plperl" 2025-11-30 18:45:00.545 UTC client backend[43456] pg_regress/plperl_setup HINT: Must have CREATE privilege on current database to create this extension. 2025-11-30 18:45:00.545 UTC client backend[43456] pg_regress/plperl_setup STATEMENT: CREATE EXTENSION plperl; 2025-11-30 18:45:00.546 UTC client backend[43456] pg_regress/plperl_setup ERROR: permission denied to create extension "plperlu" 2025-11-30 18:45:00.546 UTC client backend[43456] pg_regress/plperl_setup HINT: Must be superuser to create this extension. 2025-11-30 18:45:00.546 UTC client backend[43456] pg_regress/plperl_setup STATEMENT: CREATE EXTENSION plperlu; 2025-11-30 18:45:00.550 UTC client backend[43454] pg_regress LOG: disconnection: session time: 0:00:00.023 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.555 UTC client backend[43455] pg_regress LOG: disconnection: session time: 0:00:00.027 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.555 UTC client backend[43442] pg_regress LOG: disconnection: session time: 0:00:00.051 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.555 UTC client backend[43459] pg_regress LOG: disconnection: session time: 0:00:00.020 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.557 UTC client backend[43460] pg_regress/plpgsql_array ERROR: malformed array literal: "4" 2025-11-30 18:45:00.557 UTC client backend[43460] pg_regress/plpgsql_array DETAIL: Array value must start with "{" or dimension information. 2025-11-30 18:45:00.557 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment 2025-11-30 18:45:00.557 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[]; begin a[1:2] := 4; raise notice 'a = %', a; end$$; 2025-11-30 18:45:00.558 UTC client backend[43456] pg_regress/plperl_setup ERROR: permission denied to create extension "plperlu" 2025-11-30 18:45:00.558 UTC client backend[43456] pg_regress/plperl_setup HINT: Must be superuser to create this extension. 2025-11-30 18:45:00.558 UTC client backend[43456] pg_regress/plperl_setup STATEMENT: CREATE EXTENSION plperlu; 2025-11-30 18:45:00.558 UTC client backend[43460] pg_regress/plpgsql_array ERROR: cannot assign to field "i" of column "a" because its type complex[] is not a composite type at character 1 2025-11-30 18:45:00.558 UTC client backend[43460] pg_regress/plpgsql_array QUERY: a[1:2].i := array[11,12] 2025-11-30 18:45:00.558 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment 2025-11-30 18:45:00.558 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare a complex[]; begin a[1:2].i := array[11,12]; raise notice 'a = %', a; end$$; 2025-11-30 18:45:00.558 UTC unrecognized[43468] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.559 UTC client backend[43468] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.559 UTC client backend[43468] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_schema 2025-11-30 18:45:00.560 UTC unrecognized[43467] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.561 UTC client backend[43467] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.561 UTC client backend[43467] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.561 UTC unrecognized[43469] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.562 UTC client backend[43467] pg_regress LOG: connection ready: setup total=4.753 ms, fork=3.485 ms, authentication=0.101 ms 2025-11-30 18:45:00.562 UTC client backend[43469] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.562 UTC client backend[43469] [unknown] LOG: connection authorized: user=postgres database=regression_amcheck application_name=pg_regress/check 2025-11-30 18:45:00.564 UTC client backend[43468] pg_regress/plpython_schema LOG: connection ready: setup total=6.791 ms, fork=0.680 ms, authentication=0.106 ms 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array ERROR: assignment source returned 0 columns 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: PL/pgSQL assignment "a := from onecol" PL/pgSQL function inline_code_block line 2 at assignment 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[]; begin a := from onecol; raise notice 'a = %', a; end$$; 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array ERROR: assignment source returned 2 columns 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: PL/pgSQL assignment "a := f1, f1 from onecol" PL/pgSQL function inline_code_block line 2 at assignment 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[]; begin a := f1, f1 from onecol; raise notice 'a = %', a; end$$; 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array ERROR: query returned more than one row 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: query: a := f1 from onecol PL/pgSQL function inline_code_block line 2 at assignment 2025-11-30 18:45:00.565 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare a int[]; begin a := f1 from onecol; raise notice 'a = %', a; end$$; 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array ERROR: cannot subscript type real because it does not support subscripting at character 1 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array QUERY: a[1] := 2 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare a real; begin a[1] := 2; raise notice 'a = %', a; end$$; 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array ERROR: cannot subscript type double precision because it does not support subscripting at character 1 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array QUERY: a.r[1] := 2 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: PL/pgSQL function inline_code_block line 2 at assignment 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare a complex; begin a.r[1] := 2; raise notice 'a = %', a; end$$; 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array ERROR: could not find array type for data type pg_node_tree 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 4 2025-11-30 18:45:00.566 UTC client backend[43460] pg_regress/plpgsql_array STATEMENT: do $$ declare v pg_node_tree; v1 v%type[]; begin end; $$; 2025-11-30 18:45:00.567 UTC client backend[43469] pg_regress/check LOG: connection ready: setup total=6.518 ms, fork=0.559 ms, authentication=0.091 ms 2025-11-30 18:45:00.567 UTC client backend[43467] pg_regress LOG: disconnection: session time: 0:00:00.006 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.570 UTC client backend[43460] pg_regress/plpgsql_array LOG: disconnection: session time: 0:00:00.034 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:00.570 UTC unrecognized[43473] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.571 UTC client backend[43473] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.571 UTC client backend[43473] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly 2025-11-30 18:45:00.571 UTC unrecognized[43470] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.571 UTC client backend[43470] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.571 UTC client backend[43470] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress 2025-11-30 18:45:00.575 UTC client backend[43473] isolation/read-only-anomaly LOG: connection ready: setup total=6.728 ms, fork=1.728 ms, authentication=0.100 ms 2025-11-30 18:45:00.576 UTC client backend[43469] pg_regress/check LOG: disconnection: session time: 0:00:00.014 user=postgres database=regression_amcheck host=[local] 2025-11-30 18:45:00.576 UTC client backend[43470] pg_regress LOG: connection ready: setup total=11.675 ms, fork=4.980 ms, authentication=0.097 ms 2025-11-30 18:45:00.580 UTC unrecognized[43479] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.580 UTC client backend[43479] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.580 UTC client backend[43479] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.581 UTC unrecognized[43475] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.582 UTC client backend[43475] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.582 UTC client backend[43475] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly 2025-11-30 18:45:00.582 UTC client backend[43479] pg_regress LOG: connection ready: setup total=2.036 ms, fork=0.309 ms, authentication=0.106 ms 2025-11-30 18:45:00.583 UTC client backend[43475] isolation/read-only-anomaly LOG: connection ready: setup total=6.230 ms, fork=2.209 ms, authentication=0.125 ms 2025-11-30 18:45:00.584 UTC client backend[43470] pg_regress LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:00.585 UTC unrecognized[43482] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.585 UTC client backend[43482] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.585 UTC client backend[43482] [unknown] LOG: connection authorized: user=postgres database=regression_amcheck application_name=pg_regress/check_btree 2025-11-30 18:45:00.586 UTC unrecognized[43480] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.586 UTC client backend[43482] pg_regress/check_btree LOG: connection ready: setup total=2.127 ms, fork=0.395 ms, authentication=0.099 ms 2025-11-30 18:45:00.589 UTC client backend[43480] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.589 UTC client backend[43480] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly 2025-11-30 18:45:00.590 UTC client backend[43480] isolation/read-only-anomaly LOG: connection ready: setup total=5.862 ms, fork=1.852 ms, authentication=0.109 ms 2025-11-30 18:45:00.591 UTC unrecognized[43483] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.592 UTC client backend[43483] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.592 UTC client backend[43483] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly 2025-11-30 18:45:00.592 UTC unrecognized[43484] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.592 UTC client backend[43484] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.592 UTC client backend[43484] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_setup 2025-11-30 18:45:00.593 UTC client backend[43483] isolation/read-only-anomaly LOG: connection ready: setup total=2.430 ms, fork=0.808 ms, authentication=0.119 ms 2025-11-30 18:45:00.593 UTC client backend[43484] pg_regress/plperl_setup LOG: connection ready: setup total=1.897 ms, fork=0.442 ms, authentication=0.122 ms 2025-11-30 18:45:00.593 UTC client backend[43456] pg_regress/plperl_setup LOG: disconnection: session time: 0:00:00.066 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:00.598 UTC unrecognized[43485] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.599 UTC client backend[43485] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.599 UTC client backend[43485] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_setup 2025-11-30 18:45:00.599 UTC client backend[43485] pg_regress/pltcl_setup LOG: connection ready: setup total=2.235 ms, fork=0.823 ms, authentication=0.104 ms 2025-11-30 18:45:00.600 UTC unrecognized[43486] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.601 UTC client backend[43486] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.601 UTC client backend[43486] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_cache 2025-11-30 18:45:00.602 UTC client backend[43486] pg_regress/plpgsql_cache LOG: connection ready: setup total=3.828 ms, fork=2.492 ms, authentication=0.093 ms 2025-11-30 18:45:00.603 UTC client backend[43484] pg_regress/plperl_setup ERROR: permission denied for language plperl 2025-11-30 18:45:00.603 UTC client backend[43484] pg_regress/plperl_setup STATEMENT: CREATE FUNCTION foo2() returns int language plperl as '2;'; 2025-11-30 18:45:00.612 UTC client backend[43486] pg_regress/plpgsql_cache ERROR: type of parameter 4 (double precision) does not match that when preparing the plan (integer) 2025-11-30 18:45:00.612 UTC client backend[43486] pg_regress/plpgsql_cache CONTEXT: PL/pgSQL function c_sillyaddone(integer) line 1 at RETURN 2025-11-30 18:45:00.612 UTC client backend[43486] pg_regress/plpgsql_cache STATEMENT: select c_sillyaddone(42); 2025-11-30 18:45:00.613 UTC client backend[43479] pg_regress LOG: disconnection: session time: 0:00:00.032 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.616 UTC unrecognized[43488] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.616 UTC client backend[43488] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.616 UTC client backend[43488] [unknown] LOG: connection authorized: user=postgres database=regression_auto_explain application_name=pg_regress/alter_reset 2025-11-30 18:45:00.618 UTC client backend[43486] pg_regress/plpgsql_cache ERROR: type of parameter 5 (numeric) does not match that when preparing the plan (integer) 2025-11-30 18:45:00.618 UTC client backend[43486] pg_regress/plpgsql_cache CONTEXT: SQL statement "select pg_typeof(r.a)" PL/pgSQL function show_result_type(text) line 7 at SQL statement 2025-11-30 18:45:00.618 UTC client backend[43486] pg_regress/plpgsql_cache STATEMENT: select show_result_type('select 2.0 as a'); 2025-11-30 18:45:00.618 UTC client backend[43486] pg_regress/plpgsql_cache LOG: disconnection: session time: 0:00:00.017 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:00.621 UTC client backend[43484] pg_regress/plperl_setup ERROR: cannot drop language plperl because extension plperl requires it 2025-11-30 18:45:00.621 UTC client backend[43484] pg_regress/plperl_setup HINT: You can drop extension plperl instead. 2025-11-30 18:45:00.621 UTC client backend[43484] pg_regress/plperl_setup STATEMENT: DROP LANGUAGE plperl CASCADE; 2025-11-30 18:45:00.621 UTC client backend[43488] pg_regress/alter_reset LOG: connection ready: setup total=5.345 ms, fork=0.393 ms, authentication=0.117 ms 2025-11-30 18:45:00.623 UTC client backend[43488] pg_regress/alter_reset WARNING: invalid configuration parameter name "auto_explain.bogus", removing it 2025-11-30 18:45:00.623 UTC client backend[43488] pg_regress/alter_reset DETAIL: "auto_explain" is now a reserved prefix. 2025-11-30 18:45:00.623 UTC client backend[43475] isolation/read-only-anomaly/s1 LOG: disconnection: session time: 0:00:00.044 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.625 UTC client backend[43473] isolation/read-only-anomaly/control connection LOG: disconnection: session time: 0:00:00.054 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.626 UTC client backend[43480] isolation/read-only-anomaly/s2 LOG: disconnection: session time: 0:00:00.040 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.627 UTC client backend[43483] isolation/read-only-anomaly/s3 LOG: disconnection: session time: 0:00:00.035 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.628 UTC client backend[43488] pg_regress/alter_reset LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_auto_explain host=[local] 2025-11-30 18:45:00.628 UTC unrecognized[43491] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.629 UTC client backend[43491] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.629 UTC client backend[43491] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_call 2025-11-30 18:45:00.630 UTC client backend[43491] pg_regress/plpgsql_call LOG: connection ready: setup total=5.049 ms, fork=2.411 ms, authentication=0.122 ms 2025-11-30 18:45:00.632 UTC client backend[43468] pg_regress/plpython_schema LOG: disconnection: session time: 0:00:00.074 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.634 UTC client backend[43491] pg_regress/plpgsql_call ERROR: RETURN cannot have a parameter in a procedure at character 71 2025-11-30 18:45:00.634 UTC client backend[43491] pg_regress/plpgsql_call STATEMENT: CREATE PROCEDURE test_proc2() LANGUAGE plpgsql AS $$ BEGIN RETURN 5; END; $$; 2025-11-30 18:45:00.639 UTC unrecognized[43497] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.639 UTC client backend[43497] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.639 UTC client backend[43497] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_populate 2025-11-30 18:45:00.640 UTC client backend[43484] pg_regress/plperl_setup LOG: disconnection: session time: 0:00:00.047 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:00.641 UTC unrecognized[43500] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.642 UTC client backend[43497] pg_regress/plpython_populate LOG: connection ready: setup total=3.554 ms, fork=0.777 ms, authentication=0.113 ms 2025-11-30 18:45:00.644 UTC client backend[43500] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.644 UTC client backend[43500] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-2 2025-11-30 18:45:00.645 UTC client backend[43500] isolation/read-only-anomaly-2 LOG: connection ready: setup total=3.814 ms, fork=0.454 ms, authentication=0.113 ms 2025-11-30 18:45:00.656 UTC unrecognized[43501] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.656 UTC client backend[43501] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.656 UTC client backend[43501] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-2 2025-11-30 18:45:00.657 UTC client backend[43501] isolation/read-only-anomaly-2 LOG: connection ready: setup total=11.695 ms, fork=10.135 ms, authentication=0.117 ms 2025-11-30 18:45:00.666 UTC client backend[43497] pg_regress/plpython_populate LOG: disconnection: session time: 0:00:00.027 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.670 UTC client backend[43491] pg_regress/plpgsql_call ERROR: procedure parameter "b" is an output parameter but corresponding argument is not writable 2025-11-30 18:45:00.670 UTC client backend[43491] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 6 at CALL 2025-11-30 18:45:00.670 UTC client backend[43491] pg_regress/plpgsql_call STATEMENT: DO LANGUAGE plpgsql $$ DECLARE x int := 3; y int := 4; BEGIN CALL test_proc6(2, x + 1, y); -- error RAISE INFO 'x = %, y = %', x, y; END; $$; 2025-11-30 18:45:00.671 UTC client backend[43491] pg_regress/plpgsql_call ERROR: variable "x" is declared CONSTANT 2025-11-30 18:45:00.671 UTC client backend[43491] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 6 at CALL 2025-11-30 18:45:00.671 UTC client backend[43491] pg_regress/plpgsql_call STATEMENT: DO LANGUAGE plpgsql $$ DECLARE x constant int := 3; y int := 4; BEGIN CALL test_proc6(2, x, y); -- error because x is constant END; $$; 2025-11-30 18:45:00.671 UTC client backend[43485] pg_regress/pltcl_setup LOG: disconnection: session time: 0:00:00.073 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:00.672 UTC unrecognized[43505] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.673 UTC client backend[43505] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.673 UTC client backend[43505] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl 2025-11-30 18:45:00.674 UTC client backend[43505] pg_regress/plperl LOG: connection ready: setup total=6.511 ms, fork=4.333 ms, authentication=0.113 ms 2025-11-30 18:45:00.677 UTC unrecognized[43510] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.677 UTC client backend[43510] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.677 UTC client backend[43510] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_test 2025-11-30 18:45:00.678 UTC client backend[43510] pg_regress/plpython_test LOG: connection ready: setup total=2.303 ms, fork=0.911 ms, authentication=0.101 ms 2025-11-30 18:45:00.680 UTC unrecognized[43511] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.680 UTC client backend[43511] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.680 UTC client backend[43511] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.681 UTC client backend[43511] pg_regress LOG: connection ready: setup total=1.630 ms, fork=0.447 ms, authentication=0.096 ms 2025-11-30 18:45:00.681 UTC client backend[43511] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.685 UTC unrecognized[43513] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.686 UTC client backend[43513] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.686 UTC client backend[43513] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:00.686 UTC client backend[43513] pg_regress LOG: connection ready: setup total=1.454 ms, fork=0.277 ms, authentication=0.105 ms 2025-11-30 18:45:00.687 UTC unrecognized[43503] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.688 UTC client backend[43503] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.688 UTC client backend[43503] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-2 2025-11-30 18:45:00.689 UTC client backend[43503] isolation/read-only-anomaly-2 LOG: connection ready: setup total=30.591 ms, fork=8.930 ms, authentication=0.129 ms 2025-11-30 18:45:00.694 UTC client backend[43491] pg_regress/plpgsql_call ERROR: procedure parameter "c" is an output parameter but corresponding argument is not writable 2025-11-30 18:45:00.694 UTC client backend[43491] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 5 at CALL 2025-11-30 18:45:00.694 UTC client backend[43491] pg_regress/plpgsql_call STATEMENT: DO $$ DECLARE _a int; _b int; _c int; BEGIN _a := 10; _b := 30; _c := 50; CALL test_proc8c(_a, _b); -- fail, no output argument for c RAISE NOTICE '_a: %, _b: %, _c: %', _a, _b, _c; END $$; 2025-11-30 18:45:00.694 UTC unrecognized[43515] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.694 UTC client backend[43491] pg_regress/plpgsql_call ERROR: procedure parameter "c" is an output parameter but corresponding argument is not writable 2025-11-30 18:45:00.694 UTC client backend[43491] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 5 at CALL 2025-11-30 18:45:00.694 UTC client backend[43491] pg_regress/plpgsql_call STATEMENT: DO $$ DECLARE _a int; _b int; _c int; BEGIN _a := 10; _b := 30; _c := 50; CALL test_proc8c(_a, b => _b); -- fail, no output argument for c RAISE NOTICE '_a: %, _b: %, _c: %', _a, _b, _c; END $$; 2025-11-30 18:45:00.694 UTC unrecognized[43516] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.694 UTC client backend[43515] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.694 UTC client backend[43515] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-2 2025-11-30 18:45:00.694 UTC client backend[43516] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.694 UTC client backend[43516] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_queries 2025-11-30 18:45:00.695 UTC client backend[43516] pg_regress/pltcl_queries LOG: connection ready: setup total=2.232 ms, fork=0.789 ms, authentication=0.093 ms 2025-11-30 18:45:00.696 UTC client backend[43515] isolation/read-only-anomaly-2 LOG: connection ready: setup total=3.033 ms, fork=0.669 ms, authentication=0.490 ms 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test LOG: log 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test CONTEXT: PL/Python function "elog_test_basic" 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test STATEMENT: SELECT elog_test_basic(); 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test WARNING: warning 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test CONTEXT: PL/Python function "elog_test_basic" 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test ERROR: plpy.Error: error 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test CONTEXT: Traceback (most recent call last): PL/Python function "elog_test_basic", line 10, in plpy.error('error') PL/Python function "elog_test_basic" 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test STATEMENT: SELECT elog_test_basic(); 2025-11-30 18:45:00.702 UTC client backend[43510] pg_regress/plpython_test LOG: disconnection: session time: 0:00:00.025 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.708 UTC client backend[43513] pg_regress LOG: disconnection: session time: 0:00:00.023 user=postgres database=postgres host=[local] 2025-11-30 18:45:00.710 UTC unrecognized[43520] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.710 UTC client backend[43520] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.710 UTC client backend[43520] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_do 2025-11-30 18:45:00.711 UTC client backend[43520] pg_regress/plpython_do LOG: connection ready: setup total=1.700 ms, fork=0.310 ms, authentication=0.099 ms 2025-11-30 18:45:00.722 UTC client backend[43503] isolation/read-only-anomaly-2/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:00.722 UTC client backend[43503] isolation/read-only-anomaly-2/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:00.722 UTC client backend[43503] isolation/read-only-anomaly-2/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:00.722 UTC client backend[43503] isolation/read-only-anomaly-2/s2 STATEMENT: UPDATE bank_account SET balance = -11 WHERE id = 'X'; 2025-11-30 18:45:00.724 UTC client backend[43500] isolation/read-only-anomaly-2/control connection LOG: disconnection: session time: 0:00:00.083 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.725 UTC client backend[43520] pg_regress/plpython_do ERROR: Exception: error test 2025-11-30 18:45:00.725 UTC client backend[43520] pg_regress/plpython_do CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in raise Exception("error test") PL/Python anonymous code block 2025-11-30 18:45:00.725 UTC client backend[43520] pg_regress/plpython_do STATEMENT: DO $$ raise Exception("error test") $$ LANGUAGE plpython3u; 2025-11-30 18:45:00.726 UTC client backend[43520] pg_regress/plpython_do LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.726 UTC client backend[43501] isolation/read-only-anomaly-2/s1 LOG: disconnection: session time: 0:00:00.069 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.727 UTC client backend[43503] isolation/read-only-anomaly-2/s2 LOG: disconnection: session time: 0:00:00.059 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.727 UTC client backend[43515] isolation/read-only-anomaly-2/s3 LOG: disconnection: session time: 0:00:00.034 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.728 UTC client backend[43516] pg_regress/pltcl_queries ERROR: value for domain d_comp1 violates check constraint "d_comp1_check" 2025-11-30 18:45:00.728 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_cdomain_arg(row('tkey', -1, 'ref2')); 2025-11-30 18:45:00.735 UTC unrecognized[43526] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.735 UTC client backend[43526] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.735 UTC client backend[43526] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-3 2025-11-30 18:45:00.735 UTC client backend[43516] pg_regress/pltcl_queries ERROR: invalid command name "returm" 2025-11-30 18:45:00.735 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "returm 1" (procedure "__PLTcl_proc_tcl_error" line 2) invoked from within "__PLTcl_proc_tcl_error" in PL/Tcl function tcl_error() 2025-11-30 18:45:00.735 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_error(); 2025-11-30 18:45:00.736 UTC unrecognized[43527] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.736 UTC client backend[43526] isolation/read-only-anomaly-3 LOG: connection ready: setup total=2.079 ms, fork=0.552 ms, authentication=0.110 ms 2025-11-30 18:45:00.736 UTC client backend[43527] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.736 UTC client backend[43527] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_global 2025-11-30 18:45:00.737 UTC client backend[43516] pg_regress/pltcl_queries ERROR: column name/value list must have even number of elements 2025-11-30 18:45:00.737 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select bad_record(); 2025-11-30 18:45:00.737 UTC client backend[43527] pg_regress/plpython_global LOG: connection ready: setup total=2.850 ms, fork=1.332 ms, authentication=0.091 ms 2025-11-30 18:45:00.737 UTC client backend[43491] pg_regress/plpgsql_call ERROR: procedure test_proc12(integer, integer, text[]) does not exist at character 6 2025-11-30 18:45:00.737 UTC client backend[43491] pg_regress/plpgsql_call DETAIL: No procedure of that name accepts the given argument types. 2025-11-30 18:45:00.737 UTC client backend[43491] pg_regress/plpgsql_call HINT: You might need to add explicit type casts. 2025-11-30 18:45:00.737 UTC client backend[43491] pg_regress/plpgsql_call QUERY: CALL test_proc12(_a, _b, _c) 2025-11-30 18:45:00.737 UTC client backend[43491] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 5 at CALL 2025-11-30 18:45:00.737 UTC client backend[43491] pg_regress/plpgsql_call STATEMENT: DO $$ DECLARE _a int; _b int; _c text[]; BEGIN _a := 10; CALL test_proc12(_a, _b, _c); -- error RAISE NOTICE '_a: %, _b: %, _c: %', _a, _b, _c; END $$; 2025-11-30 18:45:00.738 UTC unrecognized[43525] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.738 UTC client backend[43525] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.738 UTC client backend[43525] [unknown] LOG: connection authorized: user=postgres database=regression_bloom application_name=pg_regress/bloom 2025-11-30 18:45:00.743 UTC client backend[43525] pg_regress/bloom LOG: connection ready: setup total=10.290 ms, fork=1.108 ms, authentication=0.122 ms 2025-11-30 18:45:00.746 UTC client backend[43516] pg_regress/pltcl_queries ERROR: column name/value list contains nonexistent column name "cow" 2025-11-30 18:45:00.746 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select bad_field(); 2025-11-30 18:45:00.747 UTC unrecognized[43528] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.748 UTC client backend[43528] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.748 UTC client backend[43528] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-3 2025-11-30 18:45:00.748 UTC client backend[43491] pg_regress/plpgsql_call ERROR: procedure parameter "v_text" is an output parameter but corresponding argument is not writable 2025-11-30 18:45:00.748 UTC client backend[43491] pg_regress/plpgsql_call CONTEXT: PL/pgSQL function inline_code_block line 6 at CALL 2025-11-30 18:45:00.748 UTC client backend[43491] pg_regress/plpgsql_call STATEMENT: DO $$ DECLARE v_Text text; v_cnt integer := 42; BEGIN CALL p1(v_cnt := v_cnt); -- error, must supply something for v_Text RAISE NOTICE '%', v_Text; END; $$; 2025-11-30 18:45:00.749 UTC client backend[43528] isolation/read-only-anomaly-3 LOG: connection ready: setup total=11.337 ms, fork=5.811 ms, authentication=0.099 ms 2025-11-30 18:45:00.750 UTC client backend[43516] pg_regress/pltcl_queries ERROR: return_next cannot be used in non-set-returning functions 2025-11-30 18:45:00.750 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "return_next 1" (procedure "__PLTcl_proc_non_srf" line 2) invoked from within "__PLTcl_proc_non_srf" in PL/Tcl function non_srf() 2025-11-30 18:45:00.750 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select non_srf(); 2025-11-30 18:45:00.750 UTC unrecognized[43529] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.751 UTC client backend[43505] pg_regress/plperl ERROR: SETOF-composite-returning PL/Perl function must call return_next with reference to hash 2025-11-30 18:45:00.751 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "perl_set" 2025-11-30 18:45:00.751 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT perl_set(); 2025-11-30 18:45:00.751 UTC client backend[43505] pg_regress/plperl ERROR: SETOF-composite-returning PL/Perl function must call return_next with reference to hash 2025-11-30 18:45:00.751 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "perl_set" 2025-11-30 18:45:00.751 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM perl_set(); 2025-11-30 18:45:00.751 UTC client backend[43529] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.751 UTC client backend[43529] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-3 2025-11-30 18:45:00.752 UTC client backend[43529] isolation/read-only-anomaly-3 LOG: connection ready: setup total=2.456 ms, fork=0.810 ms, authentication=0.119 ms 2025-11-30 18:45:00.754 UTC client backend[43516] pg_regress/pltcl_queries ERROR: column name/value list must have even number of elements 2025-11-30 18:45:00.754 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "return_next [list a]" (procedure "__PLTcl_proc_bad_record_srf" line 3) invoked from within "__PLTcl_proc_bad_record_srf" in PL/Tcl function bad_record_srf() 2025-11-30 18:45:00.754 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select bad_record_srf(); 2025-11-30 18:45:00.754 UTC unrecognized[43530] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.754 UTC client backend[43516] pg_regress/pltcl_queries ERROR: column name/value list contains nonexistent column name "cow" 2025-11-30 18:45:00.754 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "return_next [list a 1 b 2 cow 3]" (procedure "__PLTcl_proc_bad_field_srf" line 3) invoked from within "__PLTcl_proc_bad_field_srf" in PL/Tcl function bad_field_srf() 2025-11-30 18:45:00.754 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select bad_field_srf(); 2025-11-30 18:45:00.755 UTC client backend[43505] pg_regress/plperl ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:00.755 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM perl_record(); 2025-11-30 18:45:00.755 UTC client backend[43516] pg_regress/pltcl_queries ERROR: value for domain d_comp1 violates check constraint "d_comp1_check" 2025-11-30 18:45:00.755 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select * from tcl_dcomposite_result(-1); 2025-11-30 18:45:00.756 UTC client backend[43505] pg_regress/plperl ERROR: function returning record called in context that cannot accept type record 2025-11-30 18:45:00.756 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "perl_record" 2025-11-30 18:45:00.756 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT perl_record(); 2025-11-30 18:45:00.756 UTC client backend[43530] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.756 UTC client backend[43530] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-only-anomaly-3 2025-11-30 18:45:00.756 UTC client backend[43505] pg_regress/plperl ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:00.756 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM perl_record(); 2025-11-30 18:45:00.756 UTC client backend[43516] pg_regress/pltcl_queries ERROR: function returning record called in context that cannot accept type record 2025-11-30 18:45:00.756 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_record_result(42); 2025-11-30 18:45:00.756 UTC client backend[43527] pg_regress/plpython_global LOG: disconnection: session time: 0:00:00.020 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.757 UTC client backend[43530] isolation/read-only-anomaly-3 LOG: connection ready: setup total=3.859 ms, fork=0.514 ms, authentication=0.103 ms 2025-11-30 18:45:00.757 UTC client backend[43516] pg_regress/pltcl_queries ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:00.757 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select * from tcl_record_result(42); 2025-11-30 18:45:00.762 UTC client backend[43516] pg_regress/pltcl_queries ERROR: column name/value list contains nonexistent column name "q3" 2025-11-30 18:45:00.762 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select * from tcl_record_result(42) as (q1 text, q2 int, q4 int); 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries ERROR: wrong # args: should be "quote string" 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "quote foo bar" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {quote foo bar}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('quote foo bar'); 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries ERROR: wrong # args: should be "argisnull argno" 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "argisnull" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text argisnull" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('argisnull'); 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries ERROR: argno out of range 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "argisnull 14" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {argisnull 14}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('argisnull 14'); 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries ERROR: expected integer but got "abc" 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "argisnull abc" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {argisnull abc}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('argisnull abc'); 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries ERROR: wrong # args: should be "return_null " 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "return_null 14" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {return_null 14}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.763 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('return_null 14'); 2025-11-30 18:45:00.763 UTC unrecognized[43533] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.764 UTC client backend[43516] pg_regress/pltcl_queries ERROR: wrong # args: should be "spi_exec ?-count n? ?-array name? query ?loop body?" 2025-11-30 18:45:00.764 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_exec" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text spi_exec" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.764 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_exec'); 2025-11-30 18:45:00.764 UTC client backend[43505] pg_regress/plperl ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:00.764 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM perl_record_set(); 2025-11-30 18:45:00.764 UTC client backend[43533] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.764 UTC client backend[43533] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_import 2025-11-30 18:45:00.765 UTC client backend[43533] pg_regress/plpython_import LOG: connection ready: setup total=1.829 ms, fork=0.426 ms, authentication=0.101 ms 2025-11-30 18:45:00.765 UTC client backend[43516] pg_regress/pltcl_queries ERROR: missing argument to -count or -array 2025-11-30 18:45:00.765 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_exec -count" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {spi_exec -count}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.765 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_exec -count'); 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl ERROR: function returning record called in context that cannot accept type record 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "perl_record_set" 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT perl_record_set(); 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM perl_record_set(); 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl ERROR: SETOF-composite-returning PL/Perl function must call return_next with reference to hash 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "perl_record_set" 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM perl_record_set() AS (f1 integer, f2 text, f3 text); 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl ERROR: function returning record called in context that cannot accept type record 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "perl_record_set" 2025-11-30 18:45:00.768 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT perl_record_set(); 2025-11-30 18:45:00.769 UTC client backend[43505] pg_regress/plperl ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:00.769 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM perl_record_set(); 2025-11-30 18:45:00.772 UTC client backend[43505] pg_regress/plperl ERROR: Perl hash contains nonexistent column "z" 2025-11-30 18:45:00.772 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_bad" 2025-11-30 18:45:00.772 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_bad(); 2025-11-30 18:45:00.772 UTC client backend[43505] pg_regress/plperl ERROR: malformed record literal: "42" 2025-11-30 18:45:00.772 UTC client backend[43505] pg_regress/plperl DETAIL: Missing left parenthesis. 2025-11-30 18:45:00.772 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_bad" 2025-11-30 18:45:00.772 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_bad(); 2025-11-30 18:45:00.773 UTC client backend[43505] pg_regress/plperl ERROR: cannot convert Perl array to non-array type footype 2025-11-30 18:45:00.773 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_bad" 2025-11-30 18:45:00.773 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_bad(); 2025-11-30 18:45:00.774 UTC client backend[43516] pg_regress/pltcl_queries ERROR: missing argument to -count or -array 2025-11-30 18:45:00.774 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_exec -array" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {spi_exec -array}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.774 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_exec -array'); 2025-11-30 18:45:00.776 UTC client backend[43505] pg_regress/plperl ERROR: set-returning PL/Perl function must return reference to array or use return_next 2025-11-30 18:45:00.776 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_set_bad" 2025-11-30 18:45:00.776 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_set_bad(); 2025-11-30 18:45:00.776 UTC client backend[43505] pg_regress/plperl ERROR: set-returning PL/Perl function must return reference to array or use return_next 2025-11-30 18:45:00.776 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_set_bad" 2025-11-30 18:45:00.776 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_set_bad(); 2025-11-30 18:45:00.777 UTC client backend[43505] pg_regress/plperl ERROR: SETOF-composite-returning PL/Perl function must call return_next with reference to hash 2025-11-30 18:45:00.777 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_set_bad" 2025-11-30 18:45:00.777 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_set_bad(); 2025-11-30 18:45:00.777 UTC client backend[43505] pg_regress/plperl ERROR: Perl hash contains nonexistent column "z" 2025-11-30 18:45:00.777 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_set_bad" 2025-11-30 18:45:00.777 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_set_bad(); 2025-11-30 18:45:00.779 UTC client backend[43505] pg_regress/plperl ERROR: value for domain orderedfootype violates check constraint "orderedfootype_check" 2025-11-30 18:45:00.779 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_ordered" 2025-11-30 18:45:00.779 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_ordered(); 2025-11-30 18:45:00.780 UTC client backend[43505] pg_regress/plperl ERROR: value for domain orderedfootype violates check constraint "orderedfootype_check" 2025-11-30 18:45:00.780 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "foo_ordered_set" 2025-11-30 18:45:00.780 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT * FROM foo_ordered_set(); 2025-11-30 18:45:00.781 UTC client backend[43505] pg_regress/plperl ERROR: value for domain orderedfootype violates check constraint "orderedfootype_check" 2025-11-30 18:45:00.781 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT perl_get_cfield((12,11), 'x'); 2025-11-30 18:45:00.783 UTC client backend[43505] pg_regress/plperl ERROR: value for domain orderedfootype violates check constraint "orderedfootype_check" 2025-11-30 18:45:00.783 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT perl_get_rfield((12,11)::orderedfootype, 'x'); 2025-11-30 18:45:00.791 UTC client backend[43505] pg_regress/plperl ERROR: type "does_not_exist" does not exist at line 2. 2025-11-30 18:45:00.791 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "perl_spi_prepared_bad" 2025-11-30 18:45:00.791 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT perl_spi_prepared_bad(4.35) as "double precision"; 2025-11-30 18:45:00.791 UTC client backend[43516] pg_regress/pltcl_queries ERROR: expected integer but got "abc" 2025-11-30 18:45:00.791 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_exec -count abc" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {spi_exec -count abc}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.791 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_exec -count abc'); 2025-11-30 18:45:00.794 UTC client backend[43505] pg_regress/plperl ERROR: 'system' trapped by operation mask at line 1. 2025-11-30 18:45:00.794 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:00.794 UTC client backend[43505] pg_regress/plperl STATEMENT: DO $$ system("/nonesuch"); $$ LANGUAGE plperl; 2025-11-30 18:45:00.794 UTC client backend[43533] pg_regress/plpython_import LOG: disconnection: session time: 0:00:00.030 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.794 UTC client backend[43505] pg_regress/plperl ERROR: 'quoted execution (``, qx)' trapped by operation mask at line 1. 2025-11-30 18:45:00.794 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:00.794 UTC client backend[43505] pg_regress/plperl STATEMENT: DO $$ qx("/nonesuch"); $$ LANGUAGE plperl; 2025-11-30 18:45:00.795 UTC client backend[43505] pg_regress/plperl ERROR: 'open' trapped by operation mask at line 1. 2025-11-30 18:45:00.795 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:00.795 UTC client backend[43505] pg_regress/plperl STATEMENT: DO $$ open my $fh, " qw(void) ; my @y; sort @y; 1; $do$ LANGUAGE plperl; 2025-11-30 18:45:00.799 UTC client backend[43505] pg_regress/plperl ERROR: cannot convert Perl array to non-array type text 2025-11-30 18:45:00.799 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "text_arrayref" 2025-11-30 18:45:00.799 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT text_arrayref(); 2025-11-30 18:45:00.800 UTC client backend[43505] pg_regress/plperl ERROR: cannot convert Perl hash to non-composite type text 2025-11-30 18:45:00.800 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "text_hashref" 2025-11-30 18:45:00.800 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT text_hashref(); 2025-11-30 18:45:00.800 UTC client backend[43505] pg_regress/plperl ERROR: cannot convert Perl hash to non-composite type text 2025-11-30 18:45:00.800 UTC client backend[43505] pg_regress/plperl CONTEXT: PL/Perl function "text_obj" 2025-11-30 18:45:00.800 UTC client backend[43505] pg_regress/plperl STATEMENT: SELECT text_obj(); 2025-11-30 18:45:00.802 UTC unrecognized[43537] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.803 UTC client backend[43537] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.803 UTC client backend[43537] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_control 2025-11-30 18:45:00.804 UTC client backend[43537] pg_regress/plpgsql_control LOG: connection ready: setup total=2.784 ms, fork=0.728 ms, authentication=0.132 ms 2025-11-30 18:45:00.804 UTC client backend[43505] pg_regress/plperl LOG: disconnection: session time: 0:00:00.132 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:00.807 UTC client backend[43537] pg_regress/plpgsql_control ERROR: BY value of FOR loop must be greater than zero 2025-11-30 18:45:00.807 UTC client backend[43537] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function inline_code_block line 3 at FOR with integer loop variable 2025-11-30 18:45:00.807 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: do $$ begin for i in 1..3 by 0 loop raise notice '1..3 by 0: i = %', i; end loop; end$$; 2025-11-30 18:45:00.807 UTC client backend[43537] pg_regress/plpgsql_control ERROR: BY value of FOR loop must be greater than zero 2025-11-30 18:45:00.807 UTC client backend[43537] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function inline_code_block line 3 at FOR with integer loop variable 2025-11-30 18:45:00.807 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: do $$ begin for i in 1..3 by -1 loop raise notice '1..3 by -1: i = %', i; end loop; end$$; 2025-11-30 18:45:00.807 UTC client backend[43516] pg_regress/pltcl_queries ERROR: missing argument to -array, -count or -nulls 2025-11-30 18:45:00.807 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_execp -nulls" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {spi_execp -nulls}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.807 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_execp -nulls'); 2025-11-30 18:45:00.808 UTC unrecognized[43541] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.808 UTC client backend[43541] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.808 UTC client backend[43541] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_lc 2025-11-30 18:45:00.809 UTC client backend[43516] pg_regress/pltcl_queries ERROR: invalid queryid '' 2025-11-30 18:45:00.809 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_execp """ ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {spi_execp ""}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.809 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_execp ""'); 2025-11-30 18:45:00.809 UTC client backend[43516] pg_regress/pltcl_queries ERROR: wrong # args: should be "spi_prepare query argtypes" 2025-11-30 18:45:00.809 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_prepare" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text spi_prepare" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.809 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_prepare'); 2025-11-30 18:45:00.810 UTC client backend[43537] pg_regress/plpgsql_control ERROR: BY value of FOR loop must be greater than zero 2025-11-30 18:45:00.810 UTC client backend[43537] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function inline_code_block line 3 at FOR with integer loop variable 2025-11-30 18:45:00.810 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: do $$ begin for i in reverse 1..3 by -1 loop raise notice 'reverse 1..3 by -1: i = %', i; end loop; end$$; 2025-11-30 18:45:00.810 UTC client backend[43541] pg_regress/plperl_lc LOG: connection ready: setup total=2.849 ms, fork=0.499 ms, authentication=0.102 ms 2025-11-30 18:45:00.810 UTC client backend[43516] pg_regress/pltcl_queries ERROR: type "b" does not exist 2025-11-30 18:45:00.810 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_prepare a b" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {spi_prepare a b}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.810 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_prepare a b'); 2025-11-30 18:45:00.811 UTC client backend[43516] pg_regress/pltcl_queries ERROR: unmatched open brace in list 2025-11-30 18:45:00.811 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "spi_prepare a "b {"" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text spi_prepare\ a\ \"b\ \{\"" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.811 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('spi_prepare a "b {"'); 2025-11-30 18:45:00.814 UTC client backend[43516] pg_regress/pltcl_queries ERROR: wrong # args: should be "elog level msg" 2025-11-30 18:45:00.814 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "elog" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text elog" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.814 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('elog'); 2025-11-30 18:45:00.814 UTC client backend[43516] pg_regress/pltcl_queries ERROR: bad priority "foo": must be DEBUG, LOG, INFO, NOTICE, WARNING, ERROR, or FATAL 2025-11-30 18:45:00.814 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "elog foo bar" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {elog foo bar}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.814 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('elog foo bar'); 2025-11-30 18:45:00.816 UTC client backend[43516] pg_regress/pltcl_queries ERROR: forced error 2025-11-30 18:45:00.816 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "error "forced error"" ("eval" body line 1) invoked from within "eval $1" (procedure "__PLTcl_proc_tcl_eval_text" line 3) invoked from within "__PLTcl_proc_tcl_eval_text {error "forced error"}" in PL/Tcl function tcl_eval(text) 2025-11-30 18:45:00.816 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_eval('error "forced error"'); 2025-11-30 18:45:00.818 UTC client backend[43529] isolation/read-only-anomaly-3/s2 LOG: disconnection: session time: 0:00:00.067 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.818 UTC client backend[43528] isolation/read-only-anomaly-3/s1 LOG: disconnection: session time: 0:00:00.074 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.818 UTC client backend[43526] isolation/read-only-anomaly-3/control connection LOG: disconnection: session time: 0:00:00.083 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.820 UTC client backend[43516] pg_regress/pltcl_queries ERROR: error message 2025-11-30 18:45:00.820 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "error "error message"" invoked from within "spi_execp -array A $prep { elog NOTICE "col1 $A(col1), col2 $A(col2)" switch $A(col1) { 2 { elog NOTICE "..." (procedure "__PLTcl_proc_tcl_spi_exec_boolean_text" line 6) invoked from within "__PLTcl_proc_tcl_spi_exec_boolean_text t error" in PL/Tcl function tcl_spi_exec(boolean,text) 2025-11-30 18:45:00.820 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_spi_exec(true, 'error'); 2025-11-30 18:45:00.820 UTC unrecognized[43542] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.821 UTC client backend[43542] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.821 UTC client backend[43542] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_spi 2025-11-30 18:45:00.821 UTC client backend[43516] pg_regress/pltcl_queries ERROR: error message 2025-11-30 18:45:00.821 UTC client backend[43516] pg_regress/pltcl_queries CONTEXT: while executing "error "error message"" invoked from within "spi_exec -array A $query { elog NOTICE "col1 $A(col1), col2 $A(col2)" switch $A(col1) { 2 { elog NOTICE "..." (procedure "__PLTcl_proc_tcl_spi_exec_boolean_text" line 31) invoked from within "__PLTcl_proc_tcl_spi_exec_boolean_text f error" in PL/Tcl function tcl_spi_exec(boolean,text) 2025-11-30 18:45:00.821 UTC client backend[43516] pg_regress/pltcl_queries STATEMENT: select tcl_spi_exec(false, 'error'); 2025-11-30 18:45:00.822 UTC client backend[43542] pg_regress/plpython_spi LOG: connection ready: setup total=8.143 ms, fork=6.629 ms, authentication=0.110 ms 2025-11-30 18:45:00.823 UTC client backend[43530] isolation/read-only-anomaly-3/s3 LOG: disconnection: session time: 0:00:00.069 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:00.826 UTC client backend[43541] pg_regress/plperl_lc ERROR: invalid byte sequence for encoding "UTF8": 0x00 2025-11-30 18:45:00.826 UTC client backend[43541] pg_regress/plperl_lc CONTEXT: PL/Perl function "perl_zerob" 2025-11-30 18:45:00.826 UTC client backend[43541] pg_regress/plperl_lc STATEMENT: SELECT perl_zerob(); 2025-11-30 18:45:00.827 UTC client backend[43541] pg_regress/plperl_lc LOG: disconnection: session time: 0:00:00.018 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:00.837 UTC unrecognized[43548] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.838 UTC client backend[43548] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.838 UTC client backend[43548] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_trigger 2025-11-30 18:45:00.839 UTC client backend[43548] pg_regress/plperl_trigger LOG: connection ready: setup total=2.108 ms, fork=0.483 ms, authentication=0.122 ms 2025-11-30 18:45:00.852 UTC client backend[43542] pg_regress/plpython_spi ERROR: plpy.Error: command did not produce a result set 2025-11-30 18:45:00.852 UTC client backend[43542] pg_regress/plpython_spi CONTEXT: Traceback (most recent call last): PL/Python function "result_metadata_test", line 6, in plpy.info(result.colnames()) PL/Python function "result_metadata_test" 2025-11-30 18:45:00.852 UTC client backend[43542] pg_regress/plpython_spi STATEMENT: SELECT result_metadata_test($$CREATE TEMPORARY TABLE foo1 (a int, b text)$$); 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control ERROR: CONTINUE cannot be used outside a loop at character 78 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function continue_error1() returns void as $$ begin begin continue; end; end; $$ language plpgsql; 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control ERROR: EXIT cannot be used outside a loop, unless it has a label at character 74 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function exit_error1() returns void as $$ begin begin exit; end; end; $$ language plpgsql; 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control ERROR: there is no label "no_such_label" attached to any block or loop enclosing this statement at character 104 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function continue_error2() returns void as $$ begin begin loop continue no_such_label; end loop; end; end; $$ language plpgsql; 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control ERROR: there is no label "no_such_label" attached to any block or loop enclosing this statement at character 96 2025-11-30 18:45:00.860 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function exit_error2() returns void as $$ begin begin loop exit no_such_label; end loop; end; end; $$ language plpgsql; 2025-11-30 18:45:00.861 UTC client backend[43537] pg_regress/plpgsql_control ERROR: block label "begin_block1" cannot be used in CONTINUE at character 125 2025-11-30 18:45:00.861 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function continue_error3() returns void as $$ begin <> begin loop continue begin_block1; end loop; end; end; $$ language plpgsql; 2025-11-30 18:45:00.861 UTC unrecognized[43547] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.862 UTC client backend[43547] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.862 UTC client backend[43547] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique 2025-11-30 18:45:00.863 UTC client backend[43547] isolation/read-write-unique LOG: connection ready: setup total=30.429 ms, fork=28.711 ms, authentication=0.129 ms 2025-11-30 18:45:00.870 UTC client backend[43537] pg_regress/plpgsql_control ERROR: end label "flbl1" specified for unlabeled block at character 101 2025-11-30 18:45:00.870 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function end_label2() returns void as $$ begin for _i in 1 .. 10 loop exit; end loop flbl1; end; $$ language plpgsql; 2025-11-30 18:45:00.870 UTC client backend[43537] pg_regress/plpgsql_control ERROR: end label "outer_label" differs from block's label "inner_label" at character 135 2025-11-30 18:45:00.870 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function end_label3() returns void as $$ <> begin <> for _i in 1 .. 10 loop exit; end loop outer_label; end; $$ language plpgsql; 2025-11-30 18:45:00.870 UTC client backend[43537] pg_regress/plpgsql_control ERROR: end label "outer_label" specified for unlabeled block at character 117 2025-11-30 18:45:00.870 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: create function end_label4() returns void as $$ <> begin for _i in 1 .. 10 loop exit; end loop outer_label; end; $$ language plpgsql; 2025-11-30 18:45:00.874 UTC client backend[43537] pg_regress/plpgsql_control ERROR: case not found 2025-11-30 18:45:00.874 UTC client backend[43537] pg_regress/plpgsql_control HINT: CASE statement is missing ELSE part. 2025-11-30 18:45:00.874 UTC client backend[43537] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function case_test(bigint) line 5 at CASE 2025-11-30 18:45:00.874 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: select case_test(5); 2025-11-30 18:45:00.875 UTC client backend[43537] pg_regress/plpgsql_control ERROR: case not found 2025-11-30 18:45:00.875 UTC client backend[43537] pg_regress/plpgsql_control HINT: CASE statement is missing ELSE part. 2025-11-30 18:45:00.875 UTC client backend[43537] pg_regress/plpgsql_control CONTEXT: PL/pgSQL function case_test(bigint) line 5 at CASE 2025-11-30 18:45:00.875 UTC client backend[43537] pg_regress/plpgsql_control STATEMENT: select case_test(13); 2025-11-30 18:45:00.881 UTC client backend[43537] pg_regress/plpgsql_control LOG: disconnection: session time: 0:00:00.079 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:00.893 UTC unrecognized[43552] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.893 UTC client backend[43552] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.893 UTC client backend[43552] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_copy 2025-11-30 18:45:00.894 UTC client backend[43552] pg_regress/plpgsql_copy LOG: connection ready: setup total=2.021 ms, fork=0.445 ms, authentication=0.117 ms 2025-11-30 18:45:00.897 UTC client backend[43552] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL 2025-11-30 18:45:00.897 UTC client backend[43552] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at SQL statement 2025-11-30 18:45:00.897 UTC client backend[43552] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$ BEGIN COPY copy1 TO stdout; END; $$; 2025-11-30 18:45:00.897 UTC client backend[43447] pg_regress/test_setup LOG: disconnection: session time: 0:00:00.385 user=postgres database=regression host=[local] 2025-11-30 18:45:00.899 UTC client backend[43552] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL 2025-11-30 18:45:00.899 UTC client backend[43552] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at SQL statement 2025-11-30 18:45:00.899 UTC client backend[43552] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$ BEGIN COPY copy1 FROM stdin; END; $$; 2025-11-30 18:45:00.899 UTC client backend[43552] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL 2025-11-30 18:45:00.899 UTC client backend[43552] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at EXECUTE 2025-11-30 18:45:00.899 UTC client backend[43552] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$ BEGIN EXECUTE 'COPY copy1 TO stdout'; END; $$; 2025-11-30 18:45:00.900 UTC client backend[43552] pg_regress/plpgsql_copy ERROR: cannot COPY to/from client in PL/pgSQL 2025-11-30 18:45:00.900 UTC client backend[43552] pg_regress/plpgsql_copy CONTEXT: PL/pgSQL function inline_code_block line 3 at EXECUTE 2025-11-30 18:45:00.900 UTC client backend[43552] pg_regress/plpgsql_copy STATEMENT: DO LANGUAGE plpgsql $$ BEGIN EXECUTE 'COPY copy1 FROM stdin'; END; $$; 2025-11-30 18:45:00.905 UTC client backend[43542] pg_regress/plpython_spi ERROR: TypeError: Expected sequence of 1 argument, got 2: ['a', 'b'] 2025-11-30 18:45:00.905 UTC client backend[43542] pg_regress/plpython_spi CONTEXT: Traceback (most recent call last): PL/Python function "cursor_plan_wrong_args", line 4, in c = plpy.cursor(plan, ["a", "b"]) PL/Python function "cursor_plan_wrong_args" 2025-11-30 18:45:00.905 UTC client backend[43542] pg_regress/plpython_spi STATEMENT: SELECT cursor_plan_wrong_args(); 2025-11-30 18:45:00.908 UTC unrecognized[43549] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.908 UTC client backend[43549] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.908 UTC client backend[43549] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique 2025-11-30 18:45:00.909 UTC client backend[43549] isolation/read-write-unique LOG: connection ready: setup total=45.143 ms, fork=4.167 ms, authentication=0.148 ms 2025-11-30 18:45:00.923 UTC unrecognized[43575] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.924 UTC client backend[43542] pg_regress/plpython_spi LOG: disconnection: session time: 0:00:00.103 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.924 UTC client backend[43575] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.924 UTC client backend[43575] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/varchar 2025-11-30 18:45:00.924 UTC unrecognized[43576] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.925 UTC client backend[43576] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.925 UTC client backend[43576] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int8 2025-11-30 18:45:00.925 UTC client backend[43575] pg_regress/varchar LOG: connection ready: setup total=13.865 ms, fork=11.051 ms, authentication=0.115 ms 2025-11-30 18:45:00.925 UTC client backend[43576] pg_regress/int8 LOG: connection ready: setup total=11.628 ms, fork=1.671 ms, authentication=0.112 ms 2025-11-30 18:45:00.928 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: " " at character 34 2025-11-30 18:45:00.928 UTC client backend[43576] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' '); 2025-11-30 18:45:00.928 UTC unrecognized[43577] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.928 UTC client backend[43577] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.928 UTC client backend[43577] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/money 2025-11-30 18:45:00.929 UTC client backend[43577] pg_regress/money LOG: connection ready: setup total=10.983 ms, fork=7.435 ms, authentication=0.116 ms 2025-11-30 18:45:00.930 UTC unrecognized[43578] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.930 UTC client backend[43578] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.930 UTC client backend[43578] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int2 2025-11-30 18:45:00.931 UTC client backend[43578] pg_regress/int2 LOG: connection ready: setup total=12.295 ms, fork=7.196 ms, authentication=0.102 ms 2025-11-30 18:45:00.931 UTC unrecognized[43580] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.931 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "34.5" at character 34 2025-11-30 18:45:00.931 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('34.5'); 2025-11-30 18:45:00.931 UTC client backend[43580] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.931 UTC client backend[43580] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/regproc 2025-11-30 18:45:00.932 UTC unrecognized[43582] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.932 UTC client backend[43582] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.932 UTC client backend[43582] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/txid 2025-11-30 18:45:00.932 UTC client backend[43580] pg_regress/regproc LOG: connection ready: setup total=10.821 ms, fork=4.404 ms, authentication=0.103 ms 2025-11-30 18:45:00.933 UTC client backend[43582] pg_regress/txid LOG: connection ready: setup total=8.471 ms, fork=5.404 ms, authentication=0.101 ms 2025-11-30 18:45:00.933 UTC unrecognized[43581] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.934 UTC client backend[43581] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.934 UTC client backend[43581] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/boolean 2025-11-30 18:45:00.934 UTC client backend[43578] pg_regress/int2 ERROR: value "100000" is out of range for type smallint at character 34 2025-11-30 18:45:00.934 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('100000'); 2025-11-30 18:45:00.935 UTC client backend[43581] pg_regress/boolean LOG: connection ready: setup total=12.353 ms, fork=3.545 ms, authentication=0.130 ms 2025-11-30 18:45:00.936 UTC unrecognized[43584] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.937 UTC client backend[43584] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.937 UTC client backend[43584] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/bit 2025-11-30 18:45:00.937 UTC client backend[43582] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2025-11-30 18:45:00.937 UTC client backend[43582] pg_regress/txid STATEMENT: select '31:12:'::txid_snapshot; 2025-11-30 18:45:00.938 UTC client backend[43584] pg_regress/bit LOG: connection ready: setup total=11.076 ms, fork=6.318 ms, authentication=0.114 ms 2025-11-30 18:45:00.938 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "xxx" at character 34 2025-11-30 18:45:00.938 UTC client backend[43576] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('xxx'); 2025-11-30 18:45:00.938 UTC client backend[43575] pg_regress/varchar ERROR: value too long for type character varying(1) 2025-11-30 18:45:00.938 UTC client backend[43575] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('cd'); 2025-11-30 18:45:00.938 UTC client backend[43582] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2025-11-30 18:45:00.938 UTC client backend[43582] pg_regress/txid STATEMENT: select '0:1:'::txid_snapshot; 2025-11-30 18:45:00.938 UTC client backend[43582] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2025-11-30 18:45:00.938 UTC client backend[43582] pg_regress/txid STATEMENT: select '12:13:0'::txid_snapshot; 2025-11-30 18:45:00.939 UTC client backend[43582] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2025-11-30 18:45:00.939 UTC client backend[43582] pg_regress/txid STATEMENT: select '12:16:14,13'::txid_snapshot; 2025-11-30 18:45:00.939 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "asdf" at character 34 2025-11-30 18:45:00.939 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('asdf'); 2025-11-30 18:45:00.940 UTC unrecognized[43589] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.941 UTC client backend[43589] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.941 UTC client backend[43589] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/name 2025-11-30 18:45:00.942 UTC client backend[43589] pg_regress/name LOG: connection ready: setup total=8.816 ms, fork=5.040 ms, authentication=0.109 ms 2025-11-30 18:45:00.943 UTC client backend[43584] pg_regress/bit ERROR: bit string length 2 does not match type bit(11) 2025-11-30 18:45:00.943 UTC client backend[43584] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'10'); 2025-11-30 18:45:00.943 UTC client backend[43576] pg_regress/int8 ERROR: value "3908203590239580293850293850329485" is out of range for type bigint at character 34 2025-11-30 18:45:00.943 UTC client backend[43576] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('3908203590239580293850293850329485'); 2025-11-30 18:45:00.944 UTC unrecognized[43579] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.945 UTC client backend[43579] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.945 UTC client backend[43579] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/float8 2025-11-30 18:45:00.946 UTC client backend[43579] pg_regress/float8 LOG: connection ready: setup total=24.699 ms, fork=18.906 ms, authentication=0.102 ms 2025-11-30 18:45:00.946 UTC unrecognized[43583] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.947 UTC client backend[43583] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.947 UTC client backend[43583] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique 2025-11-30 18:45:00.948 UTC client backend[43516] pg_regress/pltcl_queries LOG: disconnection: session time: 0:00:00.253 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:00.948 UTC client backend[43583] isolation/read-write-unique LOG: connection ready: setup total=22.911 ms, fork=17.004 ms, authentication=0.104 ms 2025-11-30 18:45:00.948 UTC unrecognized[43585] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.948 UTC client backend[43585] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.948 UTC client backend[43585] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/char 2025-11-30 18:45:00.949 UTC unrecognized[43587] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.949 UTC client backend[43585] pg_regress/char LOG: connection ready: setup total=20.123 ms, fork=12.940 ms, authentication=0.109 ms 2025-11-30 18:45:00.949 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: " " at character 34 2025-11-30 18:45:00.949 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (' '); 2025-11-30 18:45:00.949 UTC unrecognized[43586] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.949 UTC client backend[43587] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.949 UTC client backend[43587] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/text 2025-11-30 18:45:00.950 UTC client backend[43575] pg_regress/varchar ERROR: value too long for type character varying(4) 2025-11-30 18:45:00.950 UTC client backend[43575] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('abcde'); 2025-11-30 18:45:00.950 UTC client backend[43586] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.950 UTC client backend[43586] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int4 2025-11-30 18:45:00.950 UTC unrecognized[43596] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.950 UTC client backend[43587] pg_regress/text LOG: connection ready: setup total=20.195 ms, fork=15.311 ms, authentication=0.127 ms 2025-11-30 18:45:00.951 UTC client backend[43596] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.951 UTC client backend[43596] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/numeric 2025-11-30 18:45:00.951 UTC client backend[43586] pg_regress/int4 LOG: connection ready: setup total=21.267 ms, fork=12.627 ms, authentication=0.106 ms 2025-11-30 18:45:00.951 UTC unrecognized[43588] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.951 UTC client backend[43588] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.951 UTC client backend[43588] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/oid 2025-11-30 18:45:00.951 UTC client backend[43596] pg_regress/numeric LOG: connection ready: setup total=4.469 ms, fork=2.396 ms, authentication=0.105 ms 2025-11-30 18:45:00.952 UTC unrecognized[43592] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.952 UTC client backend[43588] pg_regress/oid LOG: connection ready: setup total=19.821 ms, fork=12.004 ms, authentication=0.119 ms 2025-11-30 18:45:00.952 UTC client backend[43592] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.952 UTC client backend[43592] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/uuid 2025-11-30 18:45:00.953 UTC client backend[43592] pg_regress/uuid LOG: connection ready: setup total=7.550 ms, fork=4.987 ms, authentication=0.112 ms 2025-11-30 18:45:00.953 UTC unrecognized[43593] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.953 UTC client backend[43576] pg_regress/int8 ERROR: value "-1204982019841029840928340329840934" is out of range for type bigint at character 34 2025-11-30 18:45:00.953 UTC client backend[43576] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('-1204982019841029840928340329840934'); 2025-11-30 18:45:00.954 UTC client backend[43593] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.954 UTC client backend[43593] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/enum 2025-11-30 18:45:00.955 UTC client backend[43593] pg_regress/enum LOG: connection ready: setup total=8.680 ms, fork=4.694 ms, authentication=0.105 ms 2025-11-30 18:45:00.955 UTC unrecognized[43597] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.955 UTC client backend[43597] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.955 UTC client backend[43597] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rangetypes 2025-11-30 18:45:00.955 UTC unrecognized[43595] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.956 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "34.5" at character 34 2025-11-30 18:45:00.956 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('34.5'); 2025-11-30 18:45:00.956 UTC client backend[43595] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.956 UTC client backend[43595] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/pg_lsn 2025-11-30 18:45:00.956 UTC client backend[43597] pg_regress/rangetypes LOG: connection ready: setup total=8.962 ms, fork=3.791 ms, authentication=0.103 ms 2025-11-30 18:45:00.957 UTC client backend[43595] pg_regress/pg_lsn LOG: connection ready: setup total=10.123 ms, fork=7.834 ms, authentication=0.107 ms 2025-11-30 18:45:00.957 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "- 123" at character 34 2025-11-30 18:45:00.957 UTC client backend[43576] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('- 123'); 2025-11-30 18:45:00.958 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "- 1234" at character 34 2025-11-30 18:45:00.958 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('- 1234'); 2025-11-30 18:45:00.958 UTC unrecognized[43594] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.958 UTC client backend[43594] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.958 UTC client backend[43594] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/float4 2025-11-30 18:45:00.959 UTC client backend[43594] pg_regress/float4 LOG: connection ready: setup total=12.514 ms, fork=7.627 ms, authentication=0.108 ms 2025-11-30 18:45:00.961 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "" at character 8 2025-11-30 18:45:00.961 UTC client backend[43597] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2025-11-30 18:45:00.961 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select ''::textrange; 2025-11-30 18:45:00.963 UTC client backend[43582] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 22 2025-11-30 18:45:00.963 UTC client backend[43582] pg_regress/txid STATEMENT: SELECT txid_snapshot '1:9223372036854775808:3'; 2025-11-30 18:45:00.963 UTC client backend[43587] pg_regress/text ERROR: function length(integer) does not exist at character 8 2025-11-30 18:45:00.963 UTC client backend[43587] pg_regress/text DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:00.963 UTC client backend[43587] pg_regress/text HINT: You might need to add explicit type casts. 2025-11-30 18:45:00.963 UTC client backend[43587] pg_regress/text STATEMENT: select length(42); 2025-11-30 18:45:00.963 UTC client backend[43575] pg_regress/varchar LOG: disconnection: session time: 0:00:00.040 user=postgres database=regression host=[local] 2025-11-30 18:45:00.964 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "-[a,z)" at character 8 2025-11-30 18:45:00.964 UTC client backend[43597] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2025-11-30 18:45:00.964 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '-[a,z)'::textrange; 2025-11-30 18:45:00.964 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "4 444" at character 34 2025-11-30 18:45:00.964 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('4 444'); 2025-11-30 18:45:00.964 UTC client backend[43586] pg_regress/int4 ERROR: value "1000000000000" is out of range for type integer at character 34 2025-11-30 18:45:00.964 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('1000000000000'); 2025-11-30 18:45:00.964 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "123 dt" at character 34 2025-11-30 18:45:00.964 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('123 dt'); 2025-11-30 18:45:00.964 UTC client backend[43552] pg_regress/plpgsql_copy LOG: disconnection: session time: 0:00:00.071 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:00.964 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: " 345 5" at character 34 2025-11-30 18:45:00.964 UTC client backend[43576] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' 345 5'); 2025-11-30 18:45:00.966 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "" at character 34 2025-11-30 18:45:00.966 UTC client backend[43578] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (''); 2025-11-30 18:45:00.967 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "test" at character 13 2025-11-30 18:45:00.967 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool 'test' AS error; 2025-11-30 18:45:00.967 UTC unrecognized[43598] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.967 UTC client backend[43598] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.967 UTC client backend[43598] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_newline 2025-11-30 18:45:00.968 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "" at character 34 2025-11-30 18:45:00.968 UTC client backend[43576] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (''); 2025-11-30 18:45:00.968 UTC client backend[43598] pg_regress/plpython_newline LOG: connection ready: setup total=7.058 ms, fork=3.523 ms, authentication=0.107 ms 2025-11-30 18:45:00.969 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "asdf" at character 34 2025-11-30 18:45:00.969 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('asdf'); 2025-11-30 18:45:00.969 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: " " at character 34 2025-11-30 18:45:00.969 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' '); 2025-11-30 18:45:00.971 UTC client backend[43584] pg_regress/bit ERROR: bit string length 12 does not match type bit(11) 2025-11-30 18:45:00.971 UTC client backend[43584] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'101011111010'); 2025-11-30 18:45:00.972 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "foo" at character 13 2025-11-30 18:45:00.972 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool 'foo' AS error; 2025-11-30 18:45:00.973 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: " asdf " at character 34 2025-11-30 18:45:00.973 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' asdf '); 2025-11-30 18:45:00.973 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "- 1234" at character 34 2025-11-30 18:45:00.973 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('- 1234'); 2025-11-30 18:45:00.974 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "123 5" at character 34 2025-11-30 18:45:00.974 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('123 5'); 2025-11-30 18:45:00.974 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "yeah" at character 13 2025-11-30 18:45:00.974 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool 'yeah' AS error; 2025-11-30 18:45:00.975 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "" at character 34 2025-11-30 18:45:00.975 UTC client backend[43586] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (''); 2025-11-30 18:45:00.975 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "[a,z) - " at character 8 2025-11-30 18:45:00.975 UTC client backend[43597] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-11-30 18:45:00.975 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '[a,z) - '::textrange; 2025-11-30 18:45:00.977 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "nay" at character 13 2025-11-30 18:45:00.977 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool 'nay' AS error; 2025-11-30 18:45:00.977 UTC client backend[43578] pg_regress/int2 ERROR: table "f" has 1 columns available but 2 columns specified 2025-11-30 18:45:00.977 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT * FROM INT2_TBL AS f(a, b); 2025-11-30 18:45:00.978 UTC client backend[43578] pg_regress/int2 ERROR: table "s" has 1 columns available but 2 columns specified 2025-11-30 18:45:00.978 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT * FROM (TABLE int2_tbl) AS s (a, b); 2025-11-30 18:45:00.978 UTC client backend[43587] pg_regress/text ERROR: operator does not exist: integer || numeric at character 10 2025-11-30 18:45:00.978 UTC client backend[43587] pg_regress/text DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:00.978 UTC client backend[43587] pg_regress/text HINT: You might need to add explicit type casts. 2025-11-30 18:45:00.978 UTC client backend[43587] pg_regress/text STATEMENT: select 3 || 4.0; 2025-11-30 18:45:00.979 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "(",a)" at character 8 2025-11-30 18:45:00.979 UTC client backend[43597] pg_regress/rangetypes DETAIL: Unexpected end of input. 2025-11-30 18:45:00.979 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '(",a)'::textrange; 2025-11-30 18:45:00.979 UTC client backend[43593] pg_regress/enum ERROR: invalid input value for enum rainbow: "mauve" at character 8 2025-11-30 18:45:00.979 UTC client backend[43593] pg_regress/enum STATEMENT: SELECT 'mauve'::rainbow; 2025-11-30 18:45:00.980 UTC client backend[43595] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "G/0" at character 32 2025-11-30 18:45:00.980 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('G/0'); 2025-11-30 18:45:00.980 UTC client backend[43594] pg_regress/float4 ERROR: "10e70" is out of range for type real at character 36 2025-11-30 18:45:00.980 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'); 2025-11-30 18:45:00.980 UTC client backend[43595] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "-1/0" at character 32 2025-11-30 18:45:00.980 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('-1/0'); 2025-11-30 18:45:00.980 UTC client backend[43594] pg_regress/float4 ERROR: "-10e70" is out of range for type real at character 36 2025-11-30 18:45:00.980 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'); 2025-11-30 18:45:00.980 UTC client backend[43595] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: " 0/12345678" at character 32 2025-11-30 18:45:00.980 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES (' 0/12345678'); 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 ERROR: "10e-70" is out of range for type real at character 36 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'); 2025-11-30 18:45:00.981 UTC client backend[43595] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "ABCD/" at character 32 2025-11-30 18:45:00.981 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('ABCD/'); 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 ERROR: "-10e-70" is out of range for type real at character 36 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'); 2025-11-30 18:45:00.981 UTC client backend[43595] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "/ABCD" at character 32 2025-11-30 18:45:00.981 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('/ABCD'); 2025-11-30 18:45:00.981 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "(,,a)" at character 8 2025-11-30 18:45:00.981 UTC client backend[43597] pg_regress/rangetypes DETAIL: Too many commas. 2025-11-30 18:45:00.981 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '(,,a)'::textrange; 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 ERROR: value out of range: overflow 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'::float8); 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 ERROR: value out of range: overflow 2025-11-30 18:45:00.981 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'::float8); 2025-11-30 18:45:00.982 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "(),a)" at character 8 2025-11-30 18:45:00.982 UTC client backend[43597] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2025-11-30 18:45:00.982 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '(),a)'::textrange; 2025-11-30 18:45:00.983 UTC client backend[43594] pg_regress/float4 ERROR: value out of range: underflow 2025-11-30 18:45:00.983 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'::float8); 2025-11-30 18:45:00.984 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "(a,))" at character 8 2025-11-30 18:45:00.984 UTC client backend[43597] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-11-30 18:45:00.984 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '(a,))'::textrange; 2025-11-30 18:45:00.984 UTC client backend[43594] pg_regress/float4 ERROR: value out of range: underflow 2025-11-30 18:45:00.984 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'::float8); 2025-11-30 18:45:00.984 UTC client backend[43594] pg_regress/float4 ERROR: "10e400" is out of range for type real at character 36 2025-11-30 18:45:00.984 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e400'); 2025-11-30 18:45:00.985 UTC client backend[43594] pg_regress/float4 ERROR: "-10e400" is out of range for type real at character 36 2025-11-30 18:45:00.985 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e400'); 2025-11-30 18:45:00.985 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "(],a)" at character 8 2025-11-30 18:45:00.985 UTC client backend[43597] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2025-11-30 18:45:00.985 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '(],a)'::textrange; 2025-11-30 18:45:00.985 UTC client backend[43594] pg_regress/float4 ERROR: "10e-400" is out of range for type real at character 36 2025-11-30 18:45:00.985 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-400'); 2025-11-30 18:45:00.985 UTC client backend[43594] pg_regress/float4 ERROR: "-10e-400" is out of range for type real at character 36 2025-11-30 18:45:00.985 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-400'); 2025-11-30 18:45:00.985 UTC client backend[43595] pg_regress/pg_lsn ERROR: pg_lsn out of range 2025-11-30 18:45:00.985 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: SELECT 'FFFFFFFF/FFFFFFFE'::pg_lsn + 2::numeric; 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "" at character 36 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (''); 2025-11-30 18:45:00.986 UTC client backend[43595] pg_regress/pg_lsn ERROR: pg_lsn out of range 2025-11-30 18:45:00.986 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: SELECT '0/1'::pg_lsn - 2::numeric; 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: " " at character 36 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' '); 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "xyz" at character 36 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('xyz'); 2025-11-30 18:45:00.986 UTC client backend[43595] pg_regress/pg_lsn ERROR: cannot add NaN to pg_lsn 2025-11-30 18:45:00.986 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn + 'NaN'::numeric; 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "5.0.0" at character 36 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5.0.0'); 2025-11-30 18:45:00.986 UTC client backend[43595] pg_regress/pg_lsn ERROR: cannot subtract NaN from pg_lsn 2025-11-30 18:45:00.986 UTC client backend[43595] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn - 'NaN'::numeric; 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "5 . 0" at character 36 2025-11-30 18:45:00.986 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5 . 0'); 2025-11-30 18:45:00.987 UTC client backend[43597] pg_regress/rangetypes ERROR: malformed range literal: "(a,])" at character 8 2025-11-30 18:45:00.987 UTC client backend[43597] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-11-30 18:45:00.987 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '(a,])'::textrange; 2025-11-30 18:45:00.988 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "5. 0" at character 36 2025-11-30 18:45:00.988 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5. 0'); 2025-11-30 18:45:00.989 UTC unrecognized[43601] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:00.989 UTC client backend[43597] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-11-30 18:45:00.989 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '[z,a]'::textrange; 2025-11-30 18:45:00.990 UTC client backend[43601] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:00.990 UTC client backend[43601] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_trigger 2025-11-30 18:45:00.990 UTC client backend[43595] pg_regress/pg_lsn LOG: disconnection: session time: 0:00:00.035 user=postgres database=regression host=[local] 2025-11-30 18:45:00.991 UTC client backend[43601] pg_regress/pltcl_trigger LOG: connection ready: setup total=18.656 ms, fork=15.430 ms, authentication=0.117 ms 2025-11-30 18:45:00.991 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: " - 3.0" at character 36 2025-11-30 18:45:00.991 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' - 3.0'); 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "123 5" at character 36 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('123 5'); 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "N A N" at character 8 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT 'N A N'::float4; 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: "NaN x" at character 8 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT 'NaN x'::float4; 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 ERROR: invalid input syntax for type real: " INFINITY x" at character 8 2025-11-30 18:45:00.992 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT ' INFINITY x'::float4; 2025-11-30 18:45:00.995 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "o" at character 13 2025-11-30 18:45:00.995 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool 'o' AS error; 2025-11-30 18:45:00.995 UTC client backend[43578] pg_regress/int2 ERROR: smallint out of range 2025-11-30 18:45:00.995 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT2_TBL i; 2025-11-30 18:45:00.996 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "on_" at character 13 2025-11-30 18:45:00.996 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool 'on_' AS error; 2025-11-30 18:45:00.996 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "off_" at character 13 2025-11-30 18:45:00.996 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool 'off_' AS error; 2025-11-30 18:45:00.997 UTC client backend[43598] pg_regress/plpython_newline LOG: disconnection: session time: 0:00:00.031 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:00.998 UTC client backend[43525] pg_regress/bloom ERROR: value 0 out of bounds for option "length" 2025-11-30 18:45:00.998 UTC client backend[43525] pg_regress/bloom DETAIL: Valid values are between "1" and "4096". 2025-11-30 18:45:00.998 UTC client backend[43525] pg_regress/bloom STATEMENT: CREATE INDEX bloomidx2 ON tst USING bloom (i, t) WITH (length=0); 2025-11-30 18:45:00.998 UTC client backend[43587] pg_regress/text ERROR: VARIADIC argument must be an array at character 32 2025-11-30 18:45:00.998 UTC client backend[43587] pg_regress/text STATEMENT: select concat_ws(',', variadic 10); 2025-11-30 18:45:00.998 UTC client backend[43525] pg_regress/bloom ERROR: value 0 out of bounds for option "col1" 2025-11-30 18:45:00.998 UTC client backend[43525] pg_regress/bloom DETAIL: Valid values are between "1" and "4095". 2025-11-30 18:45:00.998 UTC client backend[43525] pg_regress/bloom STATEMENT: CREATE INDEX bloomidx2 ON tst USING bloom (i, t) WITH (col1=0); 2025-11-30 18:45:00.998 UTC client backend[43579] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 8 2025-11-30 18:45:00.998 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '10e400'::float8; 2025-11-30 18:45:00.998 UTC client backend[43579] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 8 2025-11-30 18:45:00.998 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '-10e400'::float8; 2025-11-30 18:45:00.998 UTC client backend[43579] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 8 2025-11-30 18:45:00.998 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '10e-400'::float8; 2025-11-30 18:45:00.998 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "11" at character 13 2025-11-30 18:45:00.998 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool '11' AS error; 2025-11-30 18:45:00.999 UTC client backend[43579] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 8 2025-11-30 18:45:00.999 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '-10e-400'::float8; 2025-11-30 18:45:00.999 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "000" at character 13 2025-11-30 18:45:00.999 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool '000' AS error; 2025-11-30 18:45:00.999 UTC client backend[43525] pg_regress/bloom LOG: disconnection: session time: 0:00:00.265 user=postgres database=regression_bloom host=[local] 2025-11-30 18:45:01.000 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" at character 13 2025-11-30 18:45:01.000 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT bool '' AS error; 2025-11-30 18:45:01.007 UTC unrecognized[43605] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.007 UTC client backend[43605] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.007 UTC client backend[43605] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_void 2025-11-30 18:45:01.008 UTC client backend[43605] pg_regress/plpython_void LOG: connection ready: setup total=3.578 ms, fork=2.068 ms, authentication=0.124 ms 2025-11-30 18:45:01.009 UTC client backend[43548] pg_regress/plperl_trigger ERROR: trigger functions can only be called as triggers 2025-11-30 18:45:01.009 UTC client backend[43548] pg_regress/plperl_trigger CONTEXT: compilation of PL/Perl function "direct_trigger" 2025-11-30 18:45:01.009 UTC client backend[43548] pg_regress/plperl_trigger STATEMENT: SELECT direct_trigger(); 2025-11-30 18:45:01.010 UTC client backend[43592] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-1111-111111111111F" at character 38 2025-11-30 18:45:01.010 UTC client backend[43592] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111F'); 2025-11-30 18:45:01.011 UTC client backend[43578] pg_regress/int2 ERROR: smallint out of range 2025-11-30 18:45:01.011 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT2_TBL i; 2025-11-30 18:45:01.011 UTC client backend[43592] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{11111111-1111-1111-1111-11111111111}" at character 38 2025-11-30 18:45:01.011 UTC client backend[43592] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{11111111-1111-1111-1111-11111111111}'); 2025-11-30 18:45:01.011 UTC client backend[43585] pg_regress/char ERROR: value too long for type character(1) 2025-11-30 18:45:01.011 UTC client backend[43585] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('cd'); 2025-11-30 18:45:01.012 UTC client backend[43592] pg_regress/uuid ERROR: invalid input syntax for type uuid: "111-11111-1111-1111-1111-111111111111" at character 38 2025-11-30 18:45:01.012 UTC client backend[43592] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('111-11111-1111-1111-1111-111111111111'); 2025-11-30 18:45:01.012 UTC client backend[43578] pg_regress/int2 ERROR: smallint out of range 2025-11-30 18:45:01.012 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT2_TBL i; 2025-11-30 18:45:01.013 UTC client backend[43592] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{22222222-2222-2222-2222-222222222222 " at character 38 2025-11-30 18:45:01.013 UTC client backend[43592] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{22222222-2222-2222-2222-222222222222 '); 2025-11-30 18:45:01.014 UTC client backend[43593] pg_regress/enum ERROR: enum label "foo" used more than once 2025-11-30 18:45:01.014 UTC client backend[43593] pg_regress/enum STATEMENT: CREATE TYPE dup_enum AS ENUM ('foo','bar','foo'); 2025-11-30 18:45:01.016 UTC client backend[43592] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-G111-111111111111" at character 38 2025-11-30 18:45:01.016 UTC client backend[43592] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-G111-111111111111'); 2025-11-30 18:45:01.017 UTC client backend[43592] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11+11111-1111-1111-1111-111111111111" at character 38 2025-11-30 18:45:01.017 UTC client backend[43592] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11+11111-1111-1111-1111-111111111111'); 2025-11-30 18:45:01.017 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "" at character 36 2025-11-30 18:45:01.017 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (''); 2025-11-30 18:45:01.017 UTC client backend[43578] pg_regress/int2 ERROR: smallint out of range 2025-11-30 18:45:01.017 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 * (-1)::int2; 2025-11-30 18:45:01.018 UTC client backend[43587] pg_regress/text ERROR: too few arguments for format() 2025-11-30 18:45:01.018 UTC client backend[43587] pg_regress/text STATEMENT: select format('Hello %s %s', 'World'); 2025-11-30 18:45:01.019 UTC client backend[43582] pg_regress/txid LOG: disconnection: session time: 0:00:00.089 user=postgres database=regression host=[local] 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: " " at character 36 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' '); 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "xyz" at character 36 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('xyz'); 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5.0.0" at character 36 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5.0.0'); 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5 . 0" at character 36 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5 . 0'); 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5. 0" at character 36 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5. 0'); 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: " - 3" at character 36 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' - 3'); 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "123 5" at character 36 2025-11-30 18:45:01.019 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('123 5'); 2025-11-30 18:45:01.020 UTC client backend[43585] pg_regress/char ERROR: value too long for type character(4) 2025-11-30 18:45:01.020 UTC client backend[43585] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('abcde'); 2025-11-30 18:45:01.020 UTC client backend[43587] pg_regress/text ERROR: too few arguments for format() 2025-11-30 18:45:01.020 UTC client backend[43587] pg_regress/text STATEMENT: select format('Hello %s'); 2025-11-30 18:45:01.020 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "N A N" at character 8 2025-11-30 18:45:01.020 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT 'N A N'::float8; 2025-11-30 18:45:01.020 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: "NaN x" at character 8 2025-11-30 18:45:01.020 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT 'NaN x'::float8; 2025-11-30 18:45:01.020 UTC unrecognized[43608] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.020 UTC client backend[43579] pg_regress/float8 ERROR: invalid input syntax for type double precision: " INFINITY x" at character 8 2025-11-30 18:45:01.020 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT ' INFINITY x'::float8; 2025-11-30 18:45:01.021 UTC client backend[43578] pg_regress/int2 ERROR: smallint out of range 2025-11-30 18:45:01.021 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 / (-1)::int2; 2025-11-30 18:45:01.021 UTC client backend[43608] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.021 UTC client backend[43608] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_domain 2025-11-30 18:45:01.022 UTC client backend[43608] pg_regress/plpgsql_domain LOG: connection ready: setup total=3.951 ms, fork=0.936 ms, authentication=0.114 ms 2025-11-30 18:45:01.024 UTC client backend[43587] pg_regress/text ERROR: unrecognized format() type specifier "x" 2025-11-30 18:45:01.024 UTC client backend[43587] pg_regress/text HINT: For a single "%" use "%%". 2025-11-30 18:45:01.024 UTC client backend[43587] pg_regress/text STATEMENT: select format('Hello %x', 20); 2025-11-30 18:45:01.025 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.025 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT4_TBL i; 2025-11-30 18:45:01.027 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-11-30 18:45:01.027 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_booltrue(false, true); 2025-11-30 18:45:01.028 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.028 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int4 '2' AS x FROM INT4_TBL i; 2025-11-30 18:45:01.029 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-11-30 18:45:01.029 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_booltrue(booltrue,boolean) while casting return value to function's return type 2025-11-30 18:45:01.029 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_booltrue(true, false); 2025-11-30 18:45:01.030 UTC client backend[43587] pg_regress/text ERROR: null values cannot be formatted as an SQL identifier 2025-11-30 18:45:01.030 UTC client backend[43587] pg_regress/text STATEMENT: select format('INSERT INTO %I VALUES(%L,%L)', NULL, 10, 'Hello'); 2025-11-30 18:45:01.030 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0b" at character 13 2025-11-30 18:45:01.030 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '0b'; 2025-11-30 18:45:01.030 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.030 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT4_TBL i; 2025-11-30 18:45:01.031 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0o" at character 13 2025-11-30 18:45:01.031 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '0o'; 2025-11-30 18:45:01.031 UTC client backend[43605] pg_regress/plpython_void ERROR: PL/Python function with return type "void" did not return None 2025-11-30 18:45:01.031 UTC client backend[43605] pg_regress/plpython_void CONTEXT: while creating return value PL/Python function "test_void_func2" 2025-11-30 18:45:01.031 UTC client backend[43605] pg_regress/plpython_void STATEMENT: SELECT test_void_func2(); 2025-11-30 18:45:01.032 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-11-30 18:45:01.032 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_booltrue(boolean,boolean) line 2 during statement block local variable initialization 2025-11-30 18:45:01.032 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_booltrue(false, true); 2025-11-30 18:45:01.032 UTC client backend[43584] pg_regress/bit ERROR: bit string too long for type bit varying(11) 2025-11-30 18:45:01.032 UTC client backend[43584] pg_regress/bit STATEMENT: INSERT INTO VARBIT_TABLE VALUES (B'101011111010'); 2025-11-30 18:45:01.032 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: " tru e " 2025-11-30 18:45:01.032 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT ' tru e '::text::boolean AS invalid; 2025-11-30 18:45:01.033 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" 2025-11-30 18:45:01.033 UTC client backend[43581] pg_regress/boolean STATEMENT: SELECT ''::text::boolean AS invalid; 2025-11-30 18:45:01.033 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0x" at character 13 2025-11-30 18:45:01.033 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '0x'; 2025-11-30 18:45:01.033 UTC client backend[43587] pg_regress/text ERROR: too few arguments for format() 2025-11-30 18:45:01.033 UTC client backend[43587] pg_regress/text STATEMENT: select format('%1$s %4$s', 1, 2, 3); 2025-11-30 18:45:01.033 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-11-30 18:45:01.033 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_booltrue(boolean,boolean) line 4 at assignment 2025-11-30 18:45:01.033 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_booltrue(true, false); 2025-11-30 18:45:01.033 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.033 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int4 '2' AS x FROM INT4_TBL i; 2025-11-30 18:45:01.034 UTC client backend[43605] pg_regress/plpython_void LOG: disconnection: session time: 0:00:00.026 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.034 UTC client backend[43587] pg_regress/text ERROR: too few arguments for format() 2025-11-30 18:45:01.034 UTC client backend[43587] pg_regress/text STATEMENT: select format('%1$s %13$s', 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12); 2025-11-30 18:45:01.035 UTC client backend[43578] pg_regress/int2 ERROR: value "0b1000000000000000" is out of range for type smallint at character 13 2025-11-30 18:45:01.035 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '0b1000000000000000'; 2025-11-30 18:45:01.035 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.035 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT4_TBL i; 2025-11-30 18:45:01.035 UTC client backend[43594] pg_regress/float4 ERROR: division by zero 2025-11-30 18:45:01.035 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT f.f1 / '0.0' from FLOAT4_TBL f; 2025-11-30 18:45:01.035 UTC client backend[43584] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2025-11-30 18:45:01.035 UTC client backend[43584] pg_regress/bit STATEMENT: SELECT b' 0'; 2025-11-30 18:45:01.036 UTC client backend[43583] isolation/read-write-unique/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.036 UTC client backend[43583] isolation/read-write-unique/s2 DETAIL: Reason code: Canceled on identification as a pivot, during conflict in checking. 2025-11-30 18:45:01.036 UTC client backend[43583] isolation/read-write-unique/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.036 UTC client backend[43583] isolation/read-write-unique/s2 STATEMENT: INSERT INTO test VALUES (42); 2025-11-30 18:45:01.036 UTC client backend[43585] pg_regress/char LOG: disconnection: session time: 0:00:00.093 user=postgres database=regression host=[local] 2025-11-30 18:45:01.036 UTC client backend[43587] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2025-11-30 18:45:01.036 UTC client backend[43587] pg_regress/text STATEMENT: select format('%0$s', 'Hello'); 2025-11-30 18:45:01.037 UTC client backend[43578] pg_regress/int2 ERROR: value "0o100000" is out of range for type smallint at character 13 2025-11-30 18:45:01.037 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '0o100000'; 2025-11-30 18:45:01.037 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-11-30 18:45:01.037 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_uint2(uint2,integer) while casting return value to function's return type 2025-11-30 18:45:01.037 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_uint2(100::uint2, -50); 2025-11-30 18:45:01.038 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.038 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int4 '2' AS x FROM INT4_TBL i; 2025-11-30 18:45:01.038 UTC client backend[43587] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2025-11-30 18:45:01.038 UTC client backend[43587] pg_regress/text STATEMENT: select format('%*0$s', 'Hello'); 2025-11-30 18:45:01.039 UTC client backend[43578] pg_regress/int2 ERROR: value "0x8000" is out of range for type smallint at character 13 2025-11-30 18:45:01.039 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '0x8000'; 2025-11-30 18:45:01.039 UTC client backend[43587] pg_regress/text ERROR: unterminated format() type specifier 2025-11-30 18:45:01.039 UTC client backend[43587] pg_regress/text HINT: For a single "%" use "%%". 2025-11-30 18:45:01.039 UTC client backend[43587] pg_regress/text STATEMENT: select format('%1$', 1); 2025-11-30 18:45:01.041 UTC client backend[43587] pg_regress/text ERROR: unterminated format() type specifier 2025-11-30 18:45:01.041 UTC client backend[43587] pg_regress/text HINT: For a single "%" use "%%". 2025-11-30 18:45:01.041 UTC client backend[43587] pg_regress/text STATEMENT: select format('%1$1', 1); 2025-11-30 18:45:01.041 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-11-30 18:45:01.041 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_uint2(integer,integer) line 4 at assignment 2025-11-30 18:45:01.041 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_uint2(100, -50); 2025-11-30 18:45:01.041 UTC client backend[43578] pg_regress/int2 ERROR: value "-0b1000000000000001" is out of range for type smallint at character 13 2025-11-30 18:45:01.041 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '-0b1000000000000001'; 2025-11-30 18:45:01.042 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-11-30 18:45:01.042 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_uint2(integer,integer) line 2 during statement block local variable initialization 2025-11-30 18:45:01.042 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_uint2(-100, 50); 2025-11-30 18:45:01.042 UTC client backend[43578] pg_regress/int2 ERROR: value "-0o100001" is out of range for type smallint at character 13 2025-11-30 18:45:01.042 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '-0o100001'; 2025-11-30 18:45:01.042 UTC client backend[43584] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2025-11-30 18:45:01.042 UTC client backend[43584] pg_regress/bit STATEMENT: SELECT b'0 '; 2025-11-30 18:45:01.043 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: "" at character 33 2025-11-30 18:45:01.043 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (''); 2025-11-30 18:45:01.043 UTC client backend[43584] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2025-11-30 18:45:01.043 UTC client backend[43584] pg_regress/bit STATEMENT: SELECT x' 0'; 2025-11-30 18:45:01.044 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: " " at character 33 2025-11-30 18:45:01.044 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' '); 2025-11-30 18:45:01.044 UTC client backend[43584] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2025-11-30 18:45:01.044 UTC client backend[43584] pg_regress/bit STATEMENT: SELECT x'0 '; 2025-11-30 18:45:01.044 UTC client backend[43578] pg_regress/int2 ERROR: value "-0x8001" is out of range for type smallint at character 13 2025-11-30 18:45:01.044 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '-0x8001'; 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 ERROR: smallint out of range 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT '32767.6'::float4::int2; 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: "asdfasd" at character 33 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('asdfasd'); 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: "99asdfasd" at character 33 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('99asdfasd'); 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 ERROR: smallint out of range 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT '-32768.6'::float4::int2; 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: "5 d" at character 33 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 d'); 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 ERROR: integer out of range 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT '2147483647'::float4::int4; 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: " 5d" at character 33 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' 5d'); 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: "5 5" at character 33 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 5'); 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 ERROR: integer out of range 2025-11-30 18:45:01.045 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT '-2147483900'::float4::int4; 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid ERROR: invalid input syntax for type oid: " - 500" at character 33 2025-11-30 18:45:01.045 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' - 500'); 2025-11-30 18:45:01.046 UTC client backend[43594] pg_regress/float4 ERROR: bigint out of range 2025-11-30 18:45:01.046 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT '9223372036854775807'::float4::int8; 2025-11-30 18:45:01.046 UTC client backend[43588] pg_regress/oid ERROR: value "32958209582039852935" is out of range for type oid at character 33 2025-11-30 18:45:01.046 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('32958209582039852935'); 2025-11-30 18:45:01.046 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.046 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_nnint(null, 20); 2025-11-30 18:45:01.046 UTC client backend[43588] pg_regress/oid ERROR: value "-23582358720398502385" is out of range for type oid at character 33 2025-11-30 18:45:01.046 UTC client backend[43588] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('-23582358720398502385'); 2025-11-30 18:45:01.046 UTC client backend[43594] pg_regress/float4 ERROR: bigint out of range 2025-11-30 18:45:01.046 UTC client backend[43594] pg_regress/float4 STATEMENT: SELECT '-9223380000000000000'::float4::int8; 2025-11-30 18:45:01.047 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.047 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_nnint(nnint,integer) while casting return value to function's return type 2025-11-30 18:45:01.047 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_nnint(10, null); 2025-11-30 18:45:01.048 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "_100" at character 13 2025-11-30 18:45:01.048 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '_100'; 2025-11-30 18:45:01.048 UTC client backend[43592] pg_regress/uuid ERROR: duplicate key value violates unique constraint "guid1_unique_btree" 2025-11-30 18:45:01.048 UTC client backend[43592] pg_regress/uuid DETAIL: Key (guid_field)=(11111111-1111-1111-1111-111111111111) already exists. 2025-11-30 18:45:01.048 UTC client backend[43592] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111'); 2025-11-30 18:45:01.048 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.048 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint(integer,integer) line 2 during statement block local variable initialization 2025-11-30 18:45:01.048 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint(null, 20); 2025-11-30 18:45:01.048 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "100_" at character 13 2025-11-30 18:45:01.048 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '100_'; 2025-11-30 18:45:01.049 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.049 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint(integer,integer) line 4 at assignment 2025-11-30 18:45:01.049 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint(10, null); 2025-11-30 18:45:01.049 UTC client backend[43578] pg_regress/int2 ERROR: invalid input syntax for type smallint: "10__000" at character 13 2025-11-30 18:45:01.049 UTC client backend[43578] pg_regress/int2 STATEMENT: SELECT int2 '10__000'; 2025-11-30 18:45:01.051 UTC client backend[43578] pg_regress/int2 LOG: disconnection: session time: 0:00:00.125 user=postgres database=regression host=[local] 2025-11-30 18:45:01.052 UTC client backend[43583] isolation/read-write-unique/s2 ERROR: duplicate key value violates unique constraint "test_pkey" 2025-11-30 18:45:01.052 UTC client backend[43583] isolation/read-write-unique/s2 DETAIL: Key (i)=(42) already exists. 2025-11-30 18:45:01.052 UTC client backend[43583] isolation/read-write-unique/s2 STATEMENT: INSERT INTO test VALUES (42); 2025-11-30 18:45:01.053 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.053 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT q1, q2, q1 * q2 AS multiply FROM INT8_TBL; 2025-11-30 18:45:01.055 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-11-30 18:45:01.055 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_array_domain_check_violation() while casting return value to function's return type 2025-11-30 18:45:01.055 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_argresult_array_domain_check_violation(); 2025-11-30 18:45:01.056 UTC client backend[43581] pg_regress/boolean ERROR: invalid input syntax for type boolean: "XXX" at character 43 2025-11-30 18:45:01.056 UTC client backend[43581] pg_regress/boolean STATEMENT: INSERT INTO BOOLTBL2 (f1) VALUES (bool 'XXX'); 2025-11-30 18:45:01.056 UTC client backend[43584] pg_regress/bit ERROR: negative substring length not allowed 2025-11-30 18:45:01.056 UTC client backend[43584] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::bit(8) FROM -10 FOR -2147483646) AS "error"; 2025-11-30 18:45:01.056 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-11-30 18:45:01.056 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_pair_domain(integer,integer,integer) line 4 at assignment 2025-11-30 18:45:01.056 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_pair_domain(1,2,0); 2025-11-30 18:45:01.056 UTC client backend[43547] isolation/read-write-unique/control connection LOG: disconnection: session time: 0:00:00.195 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.057 UTC client backend[43587] pg_regress/text LOG: disconnection: session time: 0:00:00.111 user=postgres database=regression host=[local] 2025-11-30 18:45:01.059 UTC client backend[43577] pg_regress/money ERROR: value "123456789012345678" is out of range for type money at character 8 2025-11-30 18:45:01.059 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '123456789012345678'::money; 2025-11-30 18:45:01.059 UTC client backend[43549] isolation/read-write-unique/s1 LOG: disconnection: session time: 0:00:00.190 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.060 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-11-30 18:45:01.060 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_pair_domain(integer,integer,integer) line 2 during statement block local variable initialization 2025-11-30 18:45:01.060 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_pair_domain(2,1,3); 2025-11-30 18:45:01.060 UTC client backend[43577] pg_regress/money ERROR: value "9223372036854775807" is out of range for type money at character 8 2025-11-30 18:45:01.060 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '9223372036854775807'::money; 2025-11-30 18:45:01.060 UTC client backend[43584] pg_regress/bit ERROR: negative substring length not allowed 2025-11-30 18:45:01.060 UTC client backend[43584] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::varbit FROM -10 FOR -2147483646) AS "error"; 2025-11-30 18:45:01.062 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-11-30 18:45:01.062 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_build_uint2_array(smallint) while casting return value to function's return type 2025-11-30 18:45:01.062 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: select test_build_uint2_array(-1::int2); 2025-11-30 18:45:01.062 UTC client backend[43583] isolation/read-write-unique/s2 LOG: disconnection: session time: 0:00:00.120 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.063 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-11-30 18:45:01.063 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_argresult_domain_array(integer[]) line 3 at RETURN 2025-11-30 18:45:01.063 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: select test_argresult_domain_array(array[4,2]); 2025-11-30 18:45:01.064 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-11-30 18:45:01.064 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: select test_argresult_domain_array2(array[4,2]); 2025-11-30 18:45:01.065 UTC client backend[43593] pg_regress/enum ERROR: invalid enum label "plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto" 2025-11-30 18:45:01.065 UTC client backend[43593] pg_regress/enum DETAIL: Labels must be 63 bytes or less. 2025-11-30 18:45:01.065 UTC client backend[43593] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto'; 2025-11-30 18:45:01.066 UTC client backend[43577] pg_regress/money ERROR: value "-123456789012345678" is out of range for type money at character 8 2025-11-30 18:45:01.066 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '-123456789012345678'::money; 2025-11-30 18:45:01.066 UTC client backend[43597] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-30 18:45:01.066 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select numrange(2.0, 1.0); 2025-11-30 18:45:01.067 UTC client backend[43577] pg_regress/money ERROR: value "-9223372036854775808" is out of range for type money at character 8 2025-11-30 18:45:01.067 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '-9223372036854775808'::money; 2025-11-30 18:45:01.067 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.067 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_result_nnint_container(integer,integer) line 3 at RETURN 2025-11-30 18:45:01.067 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT test_result_nnint_container(3, null); 2025-11-30 18:45:01.068 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.068 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int4; 2025-11-30 18:45:01.069 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.069 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint_container(integer,integer,integer) line 4 at assignment 2025-11-30 18:45:01.069 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint_container(1,2,null); 2025-11-30 18:45:01.069 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.069 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int4; 2025-11-30 18:45:01.070 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.070 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint_container(integer,integer,integer) line 2 during statement block local variable initialization 2025-11-30 18:45:01.070 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint_container(1,null,3); 2025-11-30 18:45:01.071 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: domain nnint does not allow null values 2025-11-30 18:45:01.071 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_nnint_container2(integer,integer,integer) line 4 at assignment 2025-11-30 18:45:01.071 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_nnint_container2(1,2,null); 2025-11-30 18:45:01.072 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.072 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int2; 2025-11-30 18:45:01.073 UTC unrecognized[43612] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.073 UTC client backend[43580] pg_regress/regproc ERROR: constant of the type regrole cannot be used here 2025-11-30 18:45:01.073 UTC client backend[43580] pg_regress/regproc STATEMENT: CREATE TABLE regrole_test (rolid OID DEFAULT 'regress_regrole_test'::regrole); 2025-11-30 18:45:01.073 UTC client backend[43593] pg_regress/enum ERROR: "zeus" is not an existing enum label 2025-11-30 18:45:01.073 UTC client backend[43593] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'pluto' AFTER 'zeus'; 2025-11-30 18:45:01.074 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.074 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int2; 2025-11-30 18:45:01.075 UTC client backend[43612] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.075 UTC client backend[43612] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_call 2025-11-30 18:45:01.076 UTC client backend[43612] pg_regress/plpython_call LOG: connection ready: setup total=3.988 ms, fork=0.676 ms, authentication=0.125 ms 2025-11-30 18:45:01.077 UTC client backend[43579] pg_regress/float8 ERROR: zero raised to a negative power is undefined 2025-11-30 18:45:01.077 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT power(float8 '0', float8 '-inf'); 2025-11-30 18:45:01.078 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.078 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT read_ordered_named_pair(row(2, 1)); 2025-11-30 18:45:01.078 UTC client backend[43580] pg_regress/regproc ERROR: constant of the type regdatabase cannot be used here 2025-11-30 18:45:01.078 UTC client backend[43580] pg_regress/regproc STATEMENT: CREATE TABLE regdatabase_test (datid OID DEFAULT 'template1'::regdatabase); 2025-11-30 18:45:01.079 UTC client backend[43579] pg_regress/float8 ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-30 18:45:01.079 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT power(float8 '-inf', float8 '3.5'); 2025-11-30 18:45:01.080 UTC client backend[43588] pg_regress/oid LOG: disconnection: session time: 0:00:00.135 user=postgres database=regression host=[local] 2025-11-30 18:45:01.080 UTC client backend[43577] pg_regress/money ERROR: value "-92233720368547758.09" is out of range for type money at character 8 2025-11-30 18:45:01.080 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '-92233720368547758.09'::money; 2025-11-30 18:45:01.080 UTC client backend[43580] pg_regress/regproc ERROR: operator does not exist: ||// at character 16 2025-11-30 18:45:01.080 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regoper('||//'); 2025-11-30 18:45:01.080 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.080 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT f.f1 * '1e200' from FLOAT8_TBL f; 2025-11-30 18:45:01.080 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.080 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT f.f1 ^ '1e200' from FLOAT8_TBL f; 2025-11-30 18:45:01.081 UTC client backend[43579] pg_regress/float8 ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.081 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ; 2025-11-30 18:45:01.082 UTC client backend[43577] pg_regress/money ERROR: value "92233720368547758.08" is out of range for type money at character 8 2025-11-30 18:45:01.082 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '92233720368547758.08'::money; 2025-11-30 18:45:01.082 UTC client backend[43580] pg_regress/regproc ERROR: operator does not exist: ++(int4,int4) at character 20 2025-11-30 18:45:01.082 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regoperator('++(int4,int4)'); 2025-11-30 18:45:01.082 UTC client backend[43593] pg_regress/enum ERROR: enum label "mercury" already exists 2025-11-30 18:45:01.082 UTC client backend[43593] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'mercury'; 2025-11-30 18:45:01.082 UTC client backend[43579] pg_regress/float8 ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.082 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 < '0.0' ; 2025-11-30 18:45:01.082 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: underflow 2025-11-30 18:45:01.082 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT exp(f.f1) from FLOAT8_TBL f; 2025-11-30 18:45:01.083 UTC client backend[43579] pg_regress/float8 ERROR: division by zero 2025-11-30 18:45:01.083 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT f.f1 / '0.0' from FLOAT8_TBL f; 2025-11-30 18:45:01.083 UTC client backend[43577] pg_regress/money ERROR: value "-92233720368547758.085" is out of range for type money at character 8 2025-11-30 18:45:01.083 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '-92233720368547758.085'::money; 2025-11-30 18:45:01.084 UTC client backend[43577] pg_regress/money ERROR: value "92233720368547758.075" is out of range for type money at character 8 2025-11-30 18:45:01.084 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '92233720368547758.075'::money; 2025-11-30 18:45:01.084 UTC client backend[43584] pg_regress/bit ERROR: cannot AND bit strings of different sizes 2025-11-30 18:45:01.084 UTC client backend[43584] pg_regress/bit STATEMENT: select B'001' & B'10'; 2025-11-30 18:45:01.085 UTC client backend[43579] pg_regress/float8 ERROR: input is out of range 2025-11-30 18:45:01.085 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT acosh(float8 '-infinity'); 2025-11-30 18:45:01.085 UTC client backend[43584] pg_regress/bit ERROR: cannot OR bit strings of different sizes 2025-11-30 18:45:01.085 UTC client backend[43584] pg_regress/bit STATEMENT: select B'0111' | B'011'; 2025-11-30 18:45:01.085 UTC client backend[43579] pg_regress/float8 ERROR: input is out of range 2025-11-30 18:45:01.085 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT atanh(float8 'infinity'); 2025-11-30 18:45:01.085 UTC client backend[43579] pg_regress/float8 ERROR: input is out of range 2025-11-30 18:45:01.085 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT atanh(float8 '-infinity'); 2025-11-30 18:45:01.086 UTC client backend[43584] pg_regress/bit ERROR: cannot XOR bit strings of different sizes 2025-11-30 18:45:01.086 UTC client backend[43584] pg_regress/bit STATEMENT: select B'0010' # B'011101'; 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-infinity'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: underflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-1000.5'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-1'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '-1'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT gamma(float8 '0'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '0'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT gamma(float8 '1000'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: value out of range: overflow 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '1e308'); 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 36 2025-11-30 18:45:01.086 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e400'); 2025-11-30 18:45:01.087 UTC client backend[43579] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 36 2025-11-30 18:45:01.087 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400'); 2025-11-30 18:45:01.087 UTC client backend[43579] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 36 2025-11-30 18:45:01.087 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e-400'); 2025-11-30 18:45:01.087 UTC client backend[43579] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 36 2025-11-30 18:45:01.087 UTC client backend[43579] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400'); 2025-11-30 18:45:01.087 UTC client backend[43580] pg_regress/regproc ERROR: function "know" does not exist at character 16 2025-11-30 18:45:01.087 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regproc('know'); 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 ERROR: smallint out of range 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '32767.6'::float8::int2; 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 ERROR: smallint out of range 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '-32768.6'::float8::int2; 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 ERROR: integer out of range 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '2147483647.6'::float8::int4; 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 ERROR: integer out of range 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '-2147483648.6'::float8::int4; 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 ERROR: bigint out of range 2025-11-30 18:45:01.088 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '9223372036854775807'::float8::int8; 2025-11-30 18:45:01.089 UTC client backend[43579] pg_regress/float8 ERROR: bigint out of range 2025-11-30 18:45:01.089 UTC client backend[43579] pg_regress/float8 STATEMENT: SELECT '-9223372036854780000'::float8::int8; 2025-11-30 18:45:01.094 UTC client backend[43579] pg_regress/float8 ERROR: type "no_such_type" does not exist at character 69 2025-11-30 18:45:01.094 UTC client backend[43579] pg_regress/float8 STATEMENT: create type xfloat8 (input = xfloat8in, output = xfloat8out, like = no_such_type); 2025-11-30 18:45:01.097 UTC client backend[43594] pg_regress/float4 LOG: disconnection: session time: 0:00:00.143 user=postgres database=regression host=[local] 2025-11-30 18:45:01.097 UTC client backend[43576] pg_regress/int8 ERROR: value "-9223372036854775809" is out of range for type bigint at character 8 2025-11-30 18:45:01.097 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-9223372036854775809'::int8; 2025-11-30 18:45:01.099 UTC client backend[43581] pg_regress/boolean LOG: disconnection: session time: 0:00:00.172 user=postgres database=regression host=[local] 2025-11-30 18:45:01.099 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.099 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function build_ordered_named_pair(integer,integer) while casting return value to function's return type 2025-11-30 18:45:01.099 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT build_ordered_named_pair(2,1); 2025-11-30 18:45:01.100 UTC client backend[43576] pg_regress/int8 ERROR: value "9223372036854775808" is out of range for type bigint at character 8 2025-11-30 18:45:01.100 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775808'::int8; 2025-11-30 18:45:01.101 UTC client backend[43597] pg_regress/rangetypes ERROR: result of range union would not be contiguous 2025-11-30 18:45:01.101 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select numrange(1.0, 2.0) + numrange(2.5, 3.0); 2025-11-30 18:45:01.101 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.101 UTC client backend[43576] pg_regress/int8 STATEMENT: select -('-9223372036854775808'::int8); 2025-11-30 18:45:01.102 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.102 UTC client backend[43576] pg_regress/int8 STATEMENT: select 0::int8 - '-9223372036854775808'::int8; 2025-11-30 18:45:01.102 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.102 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '9223372036854775800'::int8; 2025-11-30 18:45:01.102 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.102 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money + '0.01'::money; 2025-11-30 18:45:01.102 UTC client backend[43579] pg_regress/float8 LOG: disconnection: session time: 0:00:00.162 user=postgres database=regression host=[local] 2025-11-30 18:45:01.102 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.102 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 + '-9223372036854775800'::int8; 2025-11-30 18:45:01.102 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.102 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '-92233720368547758.08'::money - '0.01'::money; 2025-11-30 18:45:01.103 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.103 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 - '-9223372036854775800'::int8; 2025-11-30 18:45:01.103 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.103 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money * 2::float8; 2025-11-30 18:45:01.103 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.103 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '9223372036854775800'::int8; 2025-11-30 18:45:01.103 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.103 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '-1'::money / 1.175494e-38::float4; 2025-11-30 18:45:01.104 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.104 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '9223372036854775800'::int8; 2025-11-30 18:45:01.104 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.104 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money * 2::int4; 2025-11-30 18:45:01.104 UTC client backend[43576] pg_regress/int8 ERROR: division by zero 2025-11-30 18:45:01.104 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 / '0'::int8; 2025-11-30 18:45:01.104 UTC client backend[43577] pg_regress/money ERROR: division by zero 2025-11-30 18:45:01.104 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '1'::money / 0::int2; 2025-11-30 18:45:01.104 UTC client backend[43576] pg_regress/int8 ERROR: division by zero 2025-11-30 18:45:01.104 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 % '0'::int8; 2025-11-30 18:45:01.105 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.105 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '42'::money * 'inf'::float8; 2025-11-30 18:45:01.105 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.105 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, 0::int4); 2025-11-30 18:45:01.105 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.105 UTC client backend[43576] pg_regress/int8 STATEMENT: select abs('-9223372036854775808'::int8); 2025-11-30 18:45:01.105 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.105 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '42'::money * '-inf'::float8; 2025-11-30 18:45:01.106 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.106 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, (-2147483648)::int4); 2025-11-30 18:45:01.107 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.107 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int4; 2025-11-30 18:45:01.107 UTC client backend[43577] pg_regress/money ERROR: money out of range 2025-11-30 18:45:01.107 UTC client backend[43577] pg_regress/money STATEMENT: SELECT '42'::money * 'nan'::float4; 2025-11-30 18:45:01.107 UTC unrecognized[43615] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.108 UTC client backend[43615] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.108 UTC client backend[43615] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-2 2025-11-30 18:45:01.108 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.108 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int4; 2025-11-30 18:45:01.108 UTC client backend[43577] pg_regress/money LOG: disconnection: session time: 0:00:00.181 user=postgres database=regression host=[local] 2025-11-30 18:45:01.108 UTC client backend[43615] isolation/read-write-unique-2 LOG: connection ready: setup total=1.960 ms, fork=0.466 ms, authentication=0.125 ms 2025-11-30 18:45:01.110 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.110 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int4; 2025-11-30 18:45:01.110 UTC unrecognized[43616] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.110 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.110 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_named_pair(integer,integer,integer) line 4 at assignment 2025-11-30 18:45:01.110 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_named_pair(1,2,0); 2025-11-30 18:45:01.111 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.111 UTC client backend[43576] pg_regress/int8 STATEMENT: select '100'::int4 + '9223372036854775800'::int8; 2025-11-30 18:45:01.111 UTC client backend[43616] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.111 UTC client backend[43616] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-2 2025-11-30 18:45:01.111 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.111 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-100'::int4 - '9223372036854775800'::int8; 2025-11-30 18:45:01.111 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.111 UTC client backend[43576] pg_regress/int8 STATEMENT: select '100'::int4 * '9223372036854775800'::int8; 2025-11-30 18:45:01.112 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.112 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int2; 2025-11-30 18:45:01.112 UTC client backend[43616] isolation/read-write-unique-2 LOG: connection ready: setup total=2.405 ms, fork=0.716 ms, authentication=0.106 ms 2025-11-30 18:45:01.112 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.112 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT lcm((-2147483648)::int4, 1::int4); 2025-11-30 18:45:01.112 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.112 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int2; 2025-11-30 18:45:01.112 UTC client backend[43580] pg_regress/regproc ERROR: function "absinthe(numeric)" does not exist at character 21 2025-11-30 18:45:01.112 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regprocedure('absinthe(numeric)'); 2025-11-30 18:45:01.113 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.113 UTC client backend[43576] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int2; 2025-11-30 18:45:01.113 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.113 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_named_pair(integer,integer,integer) line 2 during statement block local variable initialization 2025-11-30 18:45:01.113 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_named_pair(2,1,3); 2025-11-30 18:45:01.113 UTC client backend[43580] pg_regress/regproc ERROR: relation "pg_classes" does not exist at character 17 2025-11-30 18:45:01.113 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regclass('pg_classes'); 2025-11-30 18:45:01.114 UTC client backend[43612] pg_regress/plpython_call ERROR: PL/Python procedure did not return None 2025-11-30 18:45:01.114 UTC client backend[43612] pg_regress/plpython_call CONTEXT: PL/Python procedure "test_proc2" 2025-11-30 18:45:01.114 UTC client backend[43612] pg_regress/plpython_call STATEMENT: CALL test_proc2(); 2025-11-30 18:45:01.114 UTC client backend[43586] pg_regress/int4 ERROR: integer out of range 2025-11-30 18:45:01.114 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT lcm(2147483647::int4, 2147483646::int4); 2025-11-30 18:45:01.114 UTC client backend[43580] pg_regress/regproc ERROR: type "int3" does not exist at character 16 2025-11-30 18:45:01.114 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regtype('int3'); 2025-11-30 18:45:01.114 UTC client backend[43580] pg_regress/regproc ERROR: operator does not exist: ng_catalog.||/ at character 16 2025-11-30 18:45:01.114 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regoper('ng_catalog.||/'); 2025-11-30 18:45:01.115 UTC client backend[43580] pg_regress/regproc ERROR: operator does not exist: ng_catalog.+(int4,int4) at character 20 2025-11-30 18:45:01.115 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regoperator('ng_catalog.+(int4,int4)'); 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 ERROR: division by zero 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-9223372036854775808'::int8 / '0'::int2; 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 STATEMENT: select '100'::int2 + '9223372036854775800'::int8; 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 STATEMENT: select '-100'::int2 - '9223372036854775800'::int8; 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 STATEMENT: select '100'::int2 * '9223372036854775800'::int8; 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 ERROR: division by zero 2025-11-30 18:45:01.116 UTC client backend[43576] pg_regress/int8 STATEMENT: select '100'::int2 / '0'::int8; 2025-11-30 18:45:01.116 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: "foo.boo[]" 2025-11-30 18:45:01.116 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident('foo.boo[]'); 2025-11-30 18:45:01.117 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.117 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function build_ordered_named_pairs(integer,integer) while casting return value to function's return type 2025-11-30 18:45:01.117 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT build_ordered_named_pairs(2,1); 2025-11-30 18:45:01.117 UTC client backend[43576] pg_regress/int8 ERROR: integer out of range 2025-11-30 18:45:01.117 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int4) FROM int8_tbl WHERE q2 <> 456; 2025-11-30 18:45:01.117 UTC client backend[43576] pg_regress/int8 ERROR: smallint out of range 2025-11-30 18:45:01.117 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int2) FROM int8_tbl WHERE q2 <> 456; 2025-11-30 18:45:01.118 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "0b" at character 13 2025-11-30 18:45:01.118 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '0b'; 2025-11-30 18:45:01.118 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.118 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT CAST('922337203685477580700.0'::float8 AS int8); 2025-11-30 18:45:01.118 UTC client backend[43576] pg_regress/int8 ERROR: OID out of range 2025-11-30 18:45:01.118 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS oid) FROM INT8_TBL; 2025-11-30 18:45:01.118 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: " " 2025-11-30 18:45:01.118 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident(' '); 2025-11-30 18:45:01.119 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "0o" at character 13 2025-11-30 18:45:01.119 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '0o'; 2025-11-30 18:45:01.119 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: " .aaa" 2025-11-30 18:45:01.119 UTC client backend[43589] pg_regress/name DETAIL: No valid identifier before ".". 2025-11-30 18:45:01.119 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident(' .aaa'); 2025-11-30 18:45:01.119 UTC client backend[43580] pg_regress/regproc ERROR: function "ng_catalog.now" does not exist at character 16 2025-11-30 18:45:01.119 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regproc('ng_catalog.now'); 2025-11-30 18:45:01.119 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: " aaa . " 2025-11-30 18:45:01.119 UTC client backend[43589] pg_regress/name DETAIL: No valid identifier after ".". 2025-11-30 18:45:01.119 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident(' aaa . '); 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 ERROR: step size cannot equal zero 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT * FROM generate_series('+4567890123456789'::int8, '+4567890123456799'::int8, 0); 2025-11-30 18:45:01.120 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: "aaa.a%b" 2025-11-30 18:45:01.120 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident('aaa.a%b'); 2025-11-30 18:45:01.120 UTC client backend[43608] pg_regress/plpgsql_domain ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.120 UTC client backend[43608] pg_regress/plpgsql_domain CONTEXT: PL/pgSQL function test_assign_ordered_named_pairs(integer,integer,integer) line 2 during statement block local variable initialization 2025-11-30 18:45:01.120 UTC client backend[43608] pg_regress/plpgsql_domain STATEMENT: SELECT * FROM test_assign_ordered_named_pairs(2,1,3); 2025-11-30 18:45:01.120 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "0x" at character 13 2025-11-30 18:45:01.120 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '0x'; 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int8; 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int8; 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.120 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int4; 2025-11-30 18:45:01.120 UTC unrecognized[43617] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.120 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: "X XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" 2025-11-30 18:45:01.120 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident(E'X\rXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'); 2025-11-30 18:45:01.121 UTC client backend[43617] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.121 UTC client backend[43617] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-2 2025-11-30 18:45:01.121 UTC client backend[43608] pg_regress/plpgsql_domain LOG: disconnection: session time: 0:00:00.102 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:01.122 UTC client backend[43617] isolation/read-write-unique-2 LOG: connection ready: setup total=6.420 ms, fork=4.209 ms, authentication=0.118 ms 2025-11-30 18:45:01.122 UTC client backend[43592] pg_regress/uuid LOG: disconnection: session time: 0:00:00.171 user=postgres database=regression host=[local] 2025-11-30 18:45:01.122 UTC client backend[43586] pg_regress/int4 ERROR: value "0b10000000000000000000000000000000" is out of range for type integer at character 13 2025-11-30 18:45:01.122 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '0b10000000000000000000000000000000'; 2025-11-30 18:45:01.123 UTC client backend[43612] pg_regress/plpython_call LOG: disconnection: session time: 0:00:00.050 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.123 UTC client backend[43580] pg_regress/regproc ERROR: function "ng_catalog.abs(numeric)" does not exist at character 21 2025-11-30 18:45:01.123 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regprocedure('ng_catalog.abs(numeric)'); 2025-11-30 18:45:01.124 UTC client backend[43586] pg_regress/int4 ERROR: value "0o20000000000" is out of range for type integer at character 13 2025-11-30 18:45:01.124 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '0o20000000000'; 2025-11-30 18:45:01.124 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: ""c".X XXXXXXXXXX" 2025-11-30 18:45:01.124 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident(E'"c".X XXXX\002XXXXXX'); 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: "1020" 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident('1020'); 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: "10.20" 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident('10.20'); 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: "." 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name DETAIL: No valid identifier before ".". 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident('.'); 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: ".1020" 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name DETAIL: No valid identifier before ".". 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident('.1020'); 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name ERROR: string is not a valid identifier: "xxx.1020" 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name DETAIL: No valid identifier after ".". 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name STATEMENT: SELECT parse_ident('xxx.1020'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: relation "ng_catalog.pg_class" does not exist at character 17 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regclass('ng_catalog.pg_class'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: schema "ng_catalog" does not exist at character 16 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regtype('ng_catalog.int4'); 2025-11-30 18:45:01.125 UTC client backend[43548] pg_regress/plperl_trigger ERROR: cannot set generated column "j" 2025-11-30 18:45:01.125 UTC client backend[43548] pg_regress/plperl_trigger CONTEXT: PL/Perl function "generated_test_func1" 2025-11-30 18:45:01.125 UTC client backend[43548] pg_regress/plperl_trigger STATEMENT: INSERT INTO trigger_test_generated (i) VALUES (1); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: collation "ng_catalog.POSIX" for encoding "UTF8" does not exist at character 21 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regcollation('ng_catalog."POSIX"'); 2025-11-30 18:45:01.125 UTC client backend[43589] pg_regress/name LOG: disconnection: session time: 0:00:00.187 user=postgres database=regression host=[local] 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regrole('regress_regrole_test'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regrole('"regress_regrole_test"'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: role "nonexistent" does not exist at character 16 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regrole('Nonexistent'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: role "Nonexistent" does not exist at character 16 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regrole('"Nonexistent"'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: invalid name syntax at character 16 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regrole('foo.bar'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: schema "nonexistent" does not exist at character 21 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regnamespace('Nonexistent'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: schema "Nonexistent" does not exist at character 21 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regnamespace('"Nonexistent"'); 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc ERROR: invalid name syntax at character 21 2025-11-30 18:45:01.125 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regnamespace('foo.bar'); 2025-11-30 18:45:01.126 UTC client backend[43580] pg_regress/regproc ERROR: database "nonexistent" does not exist at character 20 2025-11-30 18:45:01.126 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regdatabase('Nonexistent'); 2025-11-30 18:45:01.126 UTC client backend[43580] pg_regress/regproc ERROR: database "Nonexistent" does not exist at character 20 2025-11-30 18:45:01.126 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regdatabase('"Nonexistent"'); 2025-11-30 18:45:01.126 UTC client backend[43580] pg_regress/regproc ERROR: invalid name syntax at character 20 2025-11-30 18:45:01.126 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT regdatabase('foo.bar'); 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 ERROR: value "0x80000000" is out of range for type integer at character 13 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '0x80000000'; 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 ERROR: value "-0b10000000000000000000000000000001" is out of range for type integer at character 13 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '-0b10000000000000000000000000000001'; 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 ERROR: value "-0o20000000001" is out of range for type integer at character 13 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '-0o20000000001'; 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 ERROR: value "-0x80000001" is out of range for type integer at character 13 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '-0x80000001'; 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "_100" at character 13 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '_100'; 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "100_" at character 13 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '100_'; 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 ERROR: invalid input syntax for type integer: "100__000" at character 13 2025-11-30 18:45:01.127 UTC client backend[43586] pg_regress/int4 STATEMENT: SELECT int4 '100__000'; 2025-11-30 18:45:01.127 UTC client backend[43548] pg_regress/plperl_trigger LOG: disconnection: session time: 0:00:00.290 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.128 UTC client backend[43586] pg_regress/int4 LOG: disconnection: session time: 0:00:00.185 user=postgres database=regression host=[local] 2025-11-30 18:45:01.131 UTC client backend[43580] pg_regress/regproc ERROR: syntax error at or near "type" at character 11 2025-11-30 18:45:01.131 UTC client backend[43580] pg_regress/regproc CONTEXT: invalid type name "incorrect type name syntax" 2025-11-30 18:45:01.131 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('incorrect type name syntax', 'regtype'); 2025-11-30 18:45:01.131 UTC client backend[43580] pg_regress/regproc ERROR: invalid NUMERIC type modifier 2025-11-30 18:45:01.131 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('numeric(1,2,3)', 'regtype'); 2025-11-30 18:45:01.131 UTC client backend[43580] pg_regress/regproc ERROR: improper qualified name (too many dotted names): way.too.many.names 2025-11-30 18:45:01.131 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('way.too.many.names', 'regtype'); 2025-11-30 18:45:01.132 UTC client backend[43580] pg_regress/regproc ERROR: cross-database references are not implemented: no_such_catalog.schema.name 2025-11-30 18:45:01.132 UTC client backend[43580] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('no_such_catalog.schema.name', 'regtype'); 2025-11-30 18:45:01.132 UTC client backend[43580] pg_regress/regproc LOG: disconnection: session time: 0:00:00.206 user=postgres database=regression host=[local] 2025-11-30 18:45:01.136 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.136 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int4; 2025-11-30 18:45:01.136 UTC unrecognized[43623] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.137 UTC client backend[43623] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.137 UTC client backend[43623] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_misc 2025-11-30 18:45:01.138 UTC client backend[43623] pg_regress/plpgsql_misc LOG: connection ready: setup total=3.668 ms, fork=2.093 ms, authentication=0.108 ms 2025-11-30 18:45:01.140 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.140 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int2; 2025-11-30 18:45:01.140 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.140 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int2; 2025-11-30 18:45:01.141 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.141 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, 0::int8); 2025-11-30 18:45:01.141 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.141 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, (-9223372036854775808)::int8); 2025-11-30 18:45:01.141 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.141 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT lcm((-9223372036854775808)::int8, 1::int8); 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: bigint out of range 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT lcm(9223372036854775807::int8, 9223372036854775806::int8); 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0b" at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '0b'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0o" at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '0o'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0x" at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '0x'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: value "0b1000000000000000000000000000000000000000000000000000000000000000" is out of range for type bigint at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '0b1000000000000000000000000000000000000000000000000000000000000000'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: value "0o1000000000000000000000" is out of range for type bigint at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '0o1000000000000000000000'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: value "0x8000000000000000" is out of range for type bigint at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '0x8000000000000000'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: value "-0b1000000000000000000000000000000000000000000000000000000000000001" is out of range for type bigint at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '-0b1000000000000000000000000000000000000000000000000000000000000001'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: value "-0o1000000000000000000001" is out of range for type bigint at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '-0o1000000000000000000001'; 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 ERROR: value "-0x8000000000000001" is out of range for type bigint at character 13 2025-11-30 18:45:01.142 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '-0x8000000000000001'; 2025-11-30 18:45:01.143 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "_100" at character 13 2025-11-30 18:45:01.143 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '_100'; 2025-11-30 18:45:01.143 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100_" at character 13 2025-11-30 18:45:01.143 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '100_'; 2025-11-30 18:45:01.143 UTC client backend[43576] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100__000" at character 13 2025-11-30 18:45:01.143 UTC client backend[43576] pg_regress/int8 STATEMENT: SELECT int8 '100__000'; 2025-11-30 18:45:01.143 UTC client backend[43576] pg_regress/int8 LOG: disconnection: session time: 0:00:00.227 user=postgres database=regression host=[local] 2025-11-30 18:45:01.144 UTC unrecognized[43626] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.144 UTC client backend[43626] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.144 UTC client backend[43626] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: variable "foo" does not exist 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo%type; begin end $$; 2025-11-30 18:45:01.145 UTC client backend[43626] pg_regress LOG: connection ready: setup total=1.623 ms, fork=0.432 ms, authentication=0.096 ms 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: variable "notice" does not exist 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x notice%type; begin end $$; 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: relation "foo" does not exist 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.145 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar%type; begin end $$; 2025-11-30 18:45:01.145 UTC unrecognized[43625] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.146 UTC client backend[43626] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.146 UTC client backend[43625] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.146 UTC client backend[43625] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_shared 2025-11-30 18:45:01.147 UTC client backend[43625] pg_regress/plperl_shared LOG: connection ready: setup total=8.473 ms, fork=6.536 ms, authentication=0.093 ms 2025-11-30 18:45:01.147 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: schema "foo" does not exist 2025-11-30 18:45:01.147 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.147 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar.baz%type; begin end $$; 2025-11-30 18:45:01.150 UTC client backend[43617] isolation/read-write-unique-2/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.150 UTC client backend[43617] isolation/read-write-unique-2/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:01.150 UTC client backend[43617] isolation/read-write-unique-2/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.150 UTC client backend[43617] isolation/read-write-unique-2/s2 STATEMENT: INSERT INTO test VALUES (42); 2025-11-30 18:45:01.153 UTC client backend[43584] pg_regress/bit ERROR: bit index 16 out of valid range (0..15) 2025-11-30 18:45:01.153 UTC client backend[43584] pg_regress/bit STATEMENT: SELECT set_bit(B'0101011000100100', 16, 1); 2025-11-30 18:45:01.153 UTC unrecognized[43628] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.154 UTC client backend[43628] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.154 UTC client backend[43628] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.154 UTC client backend[43628] pg_regress LOG: connection ready: setup total=4.026 ms, fork=2.857 ms, authentication=0.097 ms 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: relation "public.foo" does not exist 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x public.foo.bar%type; begin end $$; 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: column "zed" of relation "misc_table" does not exist 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x public.misc_table.zed%type; begin end $$; 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: relation "foo" does not exist 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo%rowtype; begin end $$; 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: relation "notice" does not exist 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.160 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x notice%rowtype; begin end $$; 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: schema "foo" does not exist 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar%rowtype; begin end $$; 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: cross-database references are not implemented: "foo.bar.baz" 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x foo.bar.baz%rowtype; begin end $$; 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: relation "public.foo" does not exist 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 1 2025-11-30 18:45:01.161 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare x public.foo%rowtype; begin end $$; 2025-11-30 18:45:01.162 UTC client backend[43623] pg_regress/plpgsql_misc ERROR: field name "foreach" is a reserved key word at character 1 2025-11-30 18:45:01.162 UTC client backend[43623] pg_regress/plpgsql_misc HINT: Use double quotes to quote it. 2025-11-30 18:45:01.162 UTC client backend[43623] pg_regress/plpgsql_misc QUERY: r.foreach 2025-11-30 18:45:01.162 UTC client backend[43623] pg_regress/plpgsql_misc CONTEXT: PL/pgSQL function inline_code_block line 5 at RAISE 2025-11-30 18:45:01.162 UTC client backend[43623] pg_regress/plpgsql_misc STATEMENT: do $$ declare r record; begin select 1 as x, 2 as foreach into r; raise notice 'r.x = %', r.x; raise notice 'r.foreach = %', r.foreach; -- fails end $$; 2025-11-30 18:45:01.162 UTC unrecognized[43630] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.162 UTC client backend[43623] pg_regress/plpgsql_misc LOG: disconnection: session time: 0:00:00.025 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:01.162 UTC client backend[43630] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.162 UTC client backend[43630] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_params 2025-11-30 18:45:01.163 UTC client backend[43630] pg_regress/plpython_params LOG: connection ready: setup total=2.193 ms, fork=0.652 ms, authentication=0.112 ms 2025-11-30 18:45:01.170 UTC client backend[43625] pg_regress/plperl_shared LOG: disconnection: session time: 0:00:00.025 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.176 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: duplicate key '1', 'KEY1-3' for T_pkey2 2025-11-30 18:45:01.176 UTC client backend[43601] pg_regress/pltcl_trigger CONTEXT: while executing "elog ERROR "duplicate key '$NEW(key1)', '$NEW(key2)' for T_pkey2"" invoked from within "if {$n > 0} { elog ERROR \ "duplicate key '$NEW(key1)', '$NEW(key2)' for T_pkey2" }" (procedure "__PLTcl_trigger_trig_pkey2_before" line 32) invoked from within "__PLTcl_trigger_trig_pkey2_before pkey2_before 17111 t_pkey2 public {{} key1 key2 txt} BEFORE ROW INSERT {key1 1 key2 {KEY1-3 } txt {shou..." in PL/Tcl function trig_pkey2_before() 2025-11-30 18:45:01.176 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: insert into T_pkey2 values (1, 'KEY1-3', 'should fail'); 2025-11-30 18:45:01.185 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: key for t_dta1 not in t_pkey1 2025-11-30 18:45:01.185 UTC client backend[43601] pg_regress/pltcl_trigger CONTEXT: while executing "elog ERROR "key for $GD($planrel) not in $keyrel"" (procedure "__PLTcl_trigger_check_primkey" line 92) invoked from within "__PLTcl_trigger_check_primkey dta1_before 17119 t_dta1 public {{} tkey ref1 ref2} BEFORE ROW INSERT {tkey {trec 4 } ref1 1 ref2 {key1-4 ..." in PL/Tcl function check_primkey() 2025-11-30 18:45:01.185 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: insert into T_dta1 values ('trec 4', 1, 'key1-4'); 2025-11-30 18:45:01.188 UTC client backend[43630] pg_regress/plpython_params LOG: disconnection: session time: 0:00:00.026 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.188 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: key for t_dta2 not in t_pkey2 2025-11-30 18:45:01.188 UTC client backend[43601] pg_regress/pltcl_trigger CONTEXT: while executing "elog ERROR "key for $GD($planrel) not in $keyrel"" (procedure "__PLTcl_trigger_check_primkey" line 92) invoked from within "__PLTcl_trigger_check_primkey dta2_before 17122 t_dta2 public {{} tkey ref1 ref2} BEFORE ROW INSERT {tkey {trec 4 } ref1 1 ref2 {KEY1-4 ..." in PL/Tcl function check_primkey() 2025-11-30 18:45:01.188 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: insert into T_dta2 values ('trec 4', 1, 'KEY1-4'); 2025-11-30 18:45:01.191 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: key '1', 'key1-1 ' referenced by T_dta1 2025-11-30 18:45:01.191 UTC client backend[43601] pg_regress/pltcl_trigger CONTEXT: while executing "elog ERROR "key '$OLD(key1)', '$OLD(key2)' referenced by T_dta1"" invoked from within "if {$check_old_ref} { # # Check for references to OLD # set n [spi_execp -count 1 $GD(plan_dta1) [list $OLD(key1) $OLD(key2)]] if {$n > 0}..." (procedure "__PLTcl_trigger_trig_pkey1_before" line 79) invoked from within "__PLTcl_trigger_trig_pkey1_before pkey1_before 17102 t_pkey1 public {{} key1 key2 txt} BEFORE ROW UPDATE {key1 1 key2 {key1-9 } txt {test..." in PL/Tcl function trig_pkey1_before() 2025-11-30 18:45:01.191 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: update T_pkey1 set key2 = 'key1-9' where key1 = 1 and key2 = 'key1-1'; 2025-11-30 18:45:01.192 UTC client backend[43628] pg_regress LOG: disconnection: session time: 0:00:00.038 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.192 UTC unrecognized[43634] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.193 UTC client backend[43634] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.193 UTC client backend[43634] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_elog 2025-11-30 18:45:01.193 UTC client backend[43634] pg_regress/plperl_elog LOG: connection ready: setup total=10.822 ms, fork=9.376 ms, authentication=0.106 ms 2025-11-30 18:45:01.194 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: key '1', 'key1-2 ' referenced by T_dta1 2025-11-30 18:45:01.194 UTC client backend[43601] pg_regress/pltcl_trigger CONTEXT: while executing "elog ERROR "key '$OLD(key1)', '$OLD(key2)' referenced by T_dta1"" invoked from within "if {$check_old_ref} { # # Check for references to OLD # set n [spi_execp -count 1 $GD(plan_dta1) [list $OLD(key1) $OLD(key2)]] if {$n > 0}..." (procedure "__PLTcl_trigger_trig_pkey1_before" line 79) invoked from within "__PLTcl_trigger_trig_pkey1_before pkey1_before 17102 t_pkey1 public {{} key1 key2 txt} BEFORE ROW DELETE {} {key1 1 key2 {key1-2 } txt {t..." in PL/Tcl function trig_pkey1_before() 2025-11-30 18:45:01.194 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: delete from T_pkey1 where key1 = 1 and key2 = 'key1-2'; 2025-11-30 18:45:01.206 UTC client backend[43584] pg_regress/bit LOG: disconnection: session time: 0:00:00.272 user=postgres database=regression host=[local] 2025-11-30 18:45:01.208 UTC client backend[43617] isolation/read-write-unique-2/s2 ERROR: duplicate key value violates unique constraint "test_pkey" 2025-11-30 18:45:01.208 UTC client backend[43617] isolation/read-write-unique-2/s2 DETAIL: Key (i)=(42) already exists. 2025-11-30 18:45:01.208 UTC client backend[43617] isolation/read-write-unique-2/s2 STATEMENT: INSERT INTO test VALUES (42); 2025-11-30 18:45:01.212 UTC client backend[43593] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2025-11-30 18:45:01.212 UTC client backend[43593] pg_regress/enum STATEMENT: SELECT 'purple'::rgb; 2025-11-30 18:45:01.212 UTC client backend[43593] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2025-11-30 18:45:01.212 UTC client backend[43593] pg_regress/enum STATEMENT: SELECT 'purple'::rainbow::rgb; 2025-11-30 18:45:01.214 UTC unrecognized[43640] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.214 UTC client backend[43640] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.214 UTC client backend[43640] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_setof 2025-11-30 18:45:01.215 UTC client backend[43640] pg_regress/plpython_setof LOG: connection ready: setup total=2.015 ms, fork=0.512 ms, authentication=0.113 ms 2025-11-30 18:45:01.222 UTC unrecognized[43639] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.222 UTC client backend[43639] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.222 UTC client backend[43639] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_record 2025-11-30 18:45:01.223 UTC client backend[43639] pg_regress/plpgsql_record LOG: connection ready: setup total=13.346 ms, fork=11.383 ms, authentication=0.126 ms 2025-11-30 18:45:01.224 UTC client backend[43634] pg_regress/plperl_elog WARNING: implicit elog via warn at line 4. 2025-11-30 18:45:01.224 UTC client backend[43634] pg_regress/plperl_elog CONTEXT: PL/Perl function "perl_warn" 2025-11-30 18:45:01.225 UTC client backend[43593] pg_regress/enum ERROR: insert or update on table "enumtest_child" violates foreign key constraint "enumtest_child_parent_fkey" 2025-11-30 18:45:01.225 UTC client backend[43593] pg_regress/enum DETAIL: Key (parent)=(blue) is not present in table "enumtest_parent". 2025-11-30 18:45:01.225 UTC client backend[43593] pg_regress/enum STATEMENT: INSERT INTO enumtest_child VALUES ('blue'); 2025-11-30 18:45:01.227 UTC client backend[43615] isolation/read-write-unique-2/control connection LOG: disconnection: session time: 0:00:00.119 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.228 UTC client backend[43593] pg_regress/enum ERROR: update or delete on table "enumtest_parent" violates foreign key constraint "enumtest_child_parent_fkey" on table "enumtest_child" 2025-11-30 18:45:01.228 UTC client backend[43593] pg_regress/enum DETAIL: Key (id)=(red) is still referenced from table "enumtest_child". 2025-11-30 18:45:01.228 UTC client backend[43593] pg_regress/enum STATEMENT: DELETE FROM enumtest_parent; 2025-11-30 18:45:01.228 UTC unrecognized[43642] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.229 UTC client backend[43634] pg_regress/plperl_elog ERROR: Global symbol "$global" requires explicit package name (did you forget to declare "my $global"?) at line 3. Global symbol "$other_global" requires explicit package name (did you forget to declare "my $other_global"?) at line 4. 2025-11-30 18:45:01.229 UTC client backend[43634] pg_regress/plperl_elog CONTEXT: compilation of PL/Perl function "uses_global" 2025-11-30 18:45:01.229 UTC client backend[43634] pg_regress/plperl_elog STATEMENT: create or replace function uses_global() returns text language plperl as $$ $global = 1; $other_global = 2; return 'uses_global worked'; $$; 2025-11-30 18:45:01.229 UTC client backend[43634] pg_regress/plperl_elog ERROR: function uses_global() does not exist at character 8 2025-11-30 18:45:01.229 UTC client backend[43634] pg_regress/plperl_elog DETAIL: There is no function of that name. 2025-11-30 18:45:01.229 UTC client backend[43634] pg_regress/plperl_elog STATEMENT: select uses_global(); 2025-11-30 18:45:01.230 UTC client backend[43616] isolation/read-write-unique-2/s1 LOG: disconnection: session time: 0:00:00.119 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.230 UTC client backend[43593] pg_regress/enum ERROR: foreign key constraint "enumtest_bogus_child_parent_fkey" cannot be implemented 2025-11-30 18:45:01.230 UTC client backend[43593] pg_regress/enum DETAIL: Key columns "parent" of the referencing table and "id" of the referenced table are of incompatible types: bogus and rainbow. 2025-11-30 18:45:01.230 UTC client backend[43593] pg_regress/enum STATEMENT: CREATE TABLE enumtest_bogus_child(parent bogus REFERENCES enumtest_parent); 2025-11-30 18:45:01.231 UTC client backend[43617] isolation/read-write-unique-2/s2 LOG: disconnection: session time: 0:00:00.111 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.231 UTC client backend[43642] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.231 UTC client backend[43642] [unknown] LOG: connection authorized: user=postgres database=regression_bool_plperl application_name=pg_regress/bool_plperl 2025-11-30 18:45:01.232 UTC client backend[43593] pg_regress/enum ERROR: "red" is not an existing enum label 2025-11-30 18:45:01.232 UTC client backend[43593] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'red' TO 'crimson'; 2025-11-30 18:45:01.232 UTC client backend[43593] pg_regress/enum ERROR: enum label "green" already exists 2025-11-30 18:45:01.232 UTC client backend[43593] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'blue' TO 'green'; 2025-11-30 18:45:01.232 UTC client backend[43640] pg_regress/plpython_setof ERROR: returned object cannot be iterated 2025-11-30 18:45:01.232 UTC client backend[43640] pg_regress/plpython_setof DETAIL: PL/Python set-returning functions must return an iterable object. 2025-11-30 18:45:01.232 UTC client backend[43640] pg_regress/plpython_setof CONTEXT: PL/Python function "test_setof_error" 2025-11-30 18:45:01.232 UTC client backend[43640] pg_regress/plpython_setof STATEMENT: SELECT test_setof_error(); 2025-11-30 18:45:01.233 UTC unrecognized[43644] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.234 UTC client backend[43593] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus at character 8 2025-11-30 18:45:01.234 UTC client backend[43593] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-30 18:45:01.234 UTC client backend[43593] pg_regress/enum STATEMENT: SELECT 'new'::bogus; 2025-11-30 18:45:01.234 UTC client backend[43593] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2025-11-30 18:45:01.234 UTC client backend[43593] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-30 18:45:01.234 UTC client backend[43593] pg_regress/enum STATEMENT: SELECT enum_last(null::bogus); 2025-11-30 18:45:01.235 UTC client backend[43593] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2025-11-30 18:45:01.235 UTC client backend[43593] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-30 18:45:01.235 UTC client backend[43593] pg_regress/enum STATEMENT: SELECT enum_range(null::bogus); 2025-11-30 18:45:01.236 UTC client backend[43642] pg_regress/bool_plperl LOG: connection ready: setup total=8.486 ms, fork=0.997 ms, authentication=0.104 ms 2025-11-30 18:45:01.236 UTC client backend[43644] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.236 UTC client backend[43644] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-3 2025-11-30 18:45:01.236 UTC client backend[43634] pg_regress/plperl_elog ERROR: just die at line 2. 2025-11-30 18:45:01.236 UTC client backend[43634] pg_regress/plperl_elog CONTEXT: PL/Perl function "just_die" 2025-11-30 18:45:01.236 UTC client backend[43634] pg_regress/plperl_elog STATEMENT: select just_die(); 2025-11-30 18:45:01.236 UTC client backend[43644] isolation/read-write-unique-3 LOG: connection ready: setup total=3.753 ms, fork=0.386 ms, authentication=0.103 ms 2025-11-30 18:45:01.237 UTC client backend[43593] pg_regress/enum ERROR: unsafe use of new value "bad" of enum type bogon at character 8 2025-11-30 18:45:01.237 UTC client backend[43593] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-30 18:45:01.237 UTC client backend[43593] pg_regress/enum STATEMENT: SELECT 'bad'::bogon; 2025-11-30 18:45:01.238 UTC client backend[43634] pg_regress/plperl_elog ERROR: this message contains a no-break space at line 2. 2025-11-30 18:45:01.238 UTC client backend[43634] pg_regress/plperl_elog CONTEXT: PL/Perl function "error_with_nbsp" 2025-11-30 18:45:01.238 UTC client backend[43634] pg_regress/plperl_elog STATEMENT: select error_with_nbsp(); 2025-11-30 18:45:01.238 UTC client backend[43634] pg_regress/plperl_elog LOG: disconnection: session time: 0:00:00.046 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.240 UTC client backend[43482] pg_regress/check_btree ERROR: permission denied for function bt_index_check 2025-11-30 18:45:01.240 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_check('bttest_a_idx'::regclass); 2025-11-30 18:45:01.243 UTC client backend[43640] pg_regress/plpython_setof LOG: disconnection: session time: 0:00:00.029 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.245 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: argisnull cannot be used in triggers 2025-11-30 18:45:01.245 UTC client backend[43601] pg_regress/pltcl_trigger CONTEXT: while executing "argisnull 1" (procedure "__PLTcl_trigger_trigger_data" line 19) invoked from within "__PLTcl_trigger_trigger_data show_trigger_data_trig 17126 trigger_test public {{} i v {} test_skip test_return_null test_argisnull} BEFORE ROW INSERT ..." in PL/Tcl function trigger_data() 2025-11-30 18:45:01.245 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: insert into trigger_test(test_argisnull) values(true); 2025-11-30 18:45:01.245 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: return_null cannot be used in triggers 2025-11-30 18:45:01.245 UTC client backend[43601] pg_regress/pltcl_trigger CONTEXT: while executing "return_null" (procedure "__PLTcl_trigger_trigger_data" line 16) invoked from within "__PLTcl_trigger_trigger_data show_trigger_data_trig 17126 trigger_test public {{} i v {} test_skip test_return_null test_argisnull} BEFORE ROW INSERT ..." in PL/Tcl function trigger_data() 2025-11-30 18:45:01.245 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: insert into trigger_test(test_return_null) values(true); 2025-11-30 18:45:01.247 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.247 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column "q1" (position 1). 2025-11-30 18:45:01.247 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type 2025-11-30 18:45:01.247 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select retc(42); 2025-11-30 18:45:01.250 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.250 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Number of returned columns (3) does not match expected column count (2). 2025-11-30 18:45:01.250 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type 2025-11-30 18:45:01.250 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select retc(42); 2025-11-30 18:45:01.251 UTC client backend[43593] pg_regress/enum LOG: disconnection: session time: 0:00:00.300 user=postgres database=regression host=[local] 2025-11-30 18:45:01.256 UTC unrecognized[43646] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.256 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.256 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column "q1" (position 1). 2025-11-30 18:45:01.256 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type 2025-11-30 18:45:01.256 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select retc(42); 2025-11-30 18:45:01.256 UTC client backend[43646] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.256 UTC client backend[43646] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-3 2025-11-30 18:45:01.256 UTC unrecognized[43651] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.257 UTC client backend[43651] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.257 UTC client backend[43651] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_record 2025-11-30 18:45:01.257 UTC client backend[43646] isolation/read-write-unique-3 LOG: connection ready: setup total=15.617 ms, fork=9.092 ms, authentication=0.118 ms 2025-11-30 18:45:01.257 UTC client backend[43482] pg_regress/check_btree ERROR: permission denied for function bt_index_parent_check 2025-11-30 18:45:01.257 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_parent_check('bttest_a_idx'::regclass); 2025-11-30 18:45:01.258 UTC client backend[43651] pg_regress/plpython_record LOG: connection ready: setup total=2.411 ms, fork=0.813 ms, authentication=0.121 ms 2025-11-30 18:45:01.259 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.259 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Number of returned columns (3) does not match expected column count (2). 2025-11-30 18:45:01.259 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function retc(integer) while casting return value to function's return type 2025-11-30 18:45:01.259 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select retc(42); 2025-11-30 18:45:01.264 UTC unrecognized[43653] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.264 UTC client backend[43653] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.264 UTC client backend[43653] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_util 2025-11-30 18:45:01.265 UTC client backend[43653] pg_regress/plperl_util LOG: connection ready: setup total=3.245 ms, fork=1.808 ms, authentication=0.108 ms 2025-11-30 18:45:01.268 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "c" has no field "x" 2025-11-30 18:45:01.268 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "c.x = 1" PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.268 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare c two_int8s; begin c.x = 1; end $$; 2025-11-30 18:45:01.270 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "c" has no field "x" 2025-11-30 18:45:01.270 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "c.x = 1" PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.270 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin c.x = 1; end $$; 2025-11-30 18:45:01.271 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "c" has no field "x" 2025-11-30 18:45:01.271 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "c.x.q1 = 1" PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.271 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin c.x.q1 = 1; end $$; 2025-11-30 18:45:01.271 UTC client backend[43639] pg_regress/plpgsql_record ERROR: cannot assign to field "x" of column "c" because there is no such column in data type two_int8s at character 1 2025-11-30 18:45:01.271 UTC client backend[43639] pg_regress/plpgsql_record QUERY: c.c2.x = 1 2025-11-30 18:45:01.271 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.271 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin c.c2.x = 1; end $$; 2025-11-30 18:45:01.272 UTC client backend[43639] pg_regress/plpgsql_record ERROR: "d.c2.x" is not a known variable at character 37 2025-11-30 18:45:01.272 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare c nested_int8s; begin d.c2.x = 1; end $$; 2025-11-30 18:45:01.272 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "c" has no field "x" 2025-11-30 18:45:01.272 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "b.c.x = 1" PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.272 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ <> declare c two_int8s; begin b.c.x = 1; end $$; 2025-11-30 18:45:01.273 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "c" has no field "x" 2025-11-30 18:45:01.273 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "b.c.x = 1" PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.273 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ <> declare c nested_int8s; begin b.c.x = 1; end $$; 2025-11-30 18:45:01.273 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "c" has no field "x" 2025-11-30 18:45:01.273 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL assignment "b.c.x.q1 = 1" PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.273 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ <> declare c nested_int8s; begin b.c.x.q1 = 1; end $$; 2025-11-30 18:45:01.274 UTC unrecognized[43652] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.275 UTC client backend[43652] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.275 UTC client backend[43652] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-3 2025-11-30 18:45:01.275 UTC client backend[43639] pg_regress/plpgsql_record ERROR: cannot assign to field "x" of column "b" because there is no such column in data type two_int8s at character 1 2025-11-30 18:45:01.275 UTC client backend[43639] pg_regress/plpgsql_record QUERY: b.c.c2.x = 1 2025-11-30 18:45:01.275 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 1 at assignment 2025-11-30 18:45:01.275 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ <> declare c nested_int8s; begin b.c.c2.x = 1; end $$; 2025-11-30 18:45:01.276 UTC client backend[43652] isolation/read-write-unique-3 LOG: connection ready: setup total=14.188 ms, fork=12.617 ms, authentication=0.118 ms 2025-11-30 18:45:01.276 UTC client backend[43639] pg_regress/plpgsql_record ERROR: "b.d.c2" is not a known variable at character 43 2025-11-30 18:45:01.276 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ <> declare c nested_int8s; begin b.d.c2.x = 1; end $$; 2025-11-30 18:45:01.285 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "r1" has no field "nosuchfield" 2025-11-30 18:45:01.285 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "r1.nosuchfield" PL/pgSQL function inline_code_block line 7 at RAISE 2025-11-30 18:45:01.285 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r1 two_int8s; begin raise notice 'r1.q1 = %', r1.q1; raise notice 'r1.q2 = %', r1.q2; raise notice 'r1 = %', r1; raise notice 'r1.nosuchfield = %', r1.nosuchfield; end$$; 2025-11-30 18:45:01.287 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "r1" is not assigned yet 2025-11-30 18:45:01.287 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: The tuple structure of a not-yet-assigned record is indeterminate. 2025-11-30 18:45:01.287 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "r1.f1" PL/pgSQL function inline_code_block line 5 at RAISE 2025-11-30 18:45:01.287 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r1 record; begin raise notice 'r1 = %', r1; raise notice 'r1.f1 = %', r1.f1; raise notice 'r1.f2 = %', r1.f2; raise notice 'r1 = %', r1; end$$; 2025-11-30 18:45:01.288 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "r1" has no field "nosuchfield" 2025-11-30 18:45:01.288 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "r1.nosuchfield" PL/pgSQL function inline_code_block line 9 at RAISE 2025-11-30 18:45:01.288 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r1 record; begin raise notice 'r1 = %', r1; r1 := row(1,2); raise notice 'r1.f1 = %', r1.f1; raise notice 'r1.f2 = %', r1.f2; raise notice 'r1 = %', r1; raise notice 'r1.nosuchfield = %', r1.nosuchfield; end$$; 2025-11-30 18:45:01.292 UTC client backend[43639] pg_regress/plpgsql_record ERROR: variable "r1" has pseudo-type record[] 2025-11-30 18:45:01.292 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 2 2025-11-30 18:45:01.292 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r1 record[]; begin end$$; 2025-11-30 18:45:01.292 UTC client backend[43651] pg_regress/plpython_record ERROR: key "second" not found in mapping 2025-11-30 18:45:01.292 UTC client backend[43651] pg_regress/plpython_record HINT: To return null in a column, add the value None to the mapping with the key named after the column. 2025-11-30 18:45:01.292 UTC client backend[43651] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error1" 2025-11-30 18:45:01.292 UTC client backend[43651] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error1(); 2025-11-30 18:45:01.292 UTC client backend[43653] pg_regress/plperl_util ERROR: value for domain perl_foo_pos violates check constraint "perl_foo_pos_check" 2025-11-30 18:45:01.292 UTC client backend[43653] pg_regress/plperl_util CONTEXT: PL/Perl function "perl_encode_typed_literal" 2025-11-30 18:45:01.292 UTC client backend[43653] pg_regress/plperl_util STATEMENT: select perl_encode_typed_literal(); 2025-11-30 18:45:01.293 UTC client backend[43653] pg_regress/plperl_util LOG: disconnection: session time: 0:00:00.028 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.293 UTC client backend[43651] pg_regress/plpython_record ERROR: length of returned sequence did not match number of columns in row 2025-11-30 18:45:01.293 UTC client backend[43651] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error2" 2025-11-30 18:45:01.293 UTC client backend[43651] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error2(); 2025-11-30 18:45:01.294 UTC client backend[43639] pg_regress/plpgsql_record ERROR: variable "r2" has pseudo-type record[] 2025-11-30 18:45:01.294 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: compilation of PL/pgSQL function "inline_code_block" near line 3 2025-11-30 18:45:01.294 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r1 record; r2 r1%type[]; begin end$$; 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record ERROR: attribute "second" does not exist in Python object 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record HINT: To return null in a column, let the returned object have an attribute named after column with value None. 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error3" 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error3(); 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record ERROR: malformed record literal: "foo" 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record DETAIL: Missing left parenthesis. 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record CONTEXT: while creating return value PL/Python function "test_type_record_error4" 2025-11-30 18:45:01.294 UTC client backend[43651] pg_regress/plpython_record STATEMENT: SELECT * FROM test_type_record_error4(); 2025-11-30 18:45:01.295 UTC client backend[43651] pg_regress/plpython_record LOG: disconnection: session time: 0:00:00.038 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.295 UTC client backend[43601] pg_regress/pltcl_trigger ERROR: cannot set generated column "j" 2025-11-30 18:45:01.295 UTC client backend[43601] pg_regress/pltcl_trigger STATEMENT: INSERT INTO trigger_test_generated (i) VALUES (1); 2025-11-30 18:45:01.297 UTC client backend[43482] pg_regress/check_btree ERROR: "bttest_a" is not an index 2025-11-30 18:45:01.297 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_check('bttest_a'); 2025-11-30 18:45:01.297 UTC client backend[43601] pg_regress/pltcl_trigger LOG: disconnection: session time: 0:00:00.309 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:01.299 UTC client backend[43482] pg_regress/check_btree ERROR: "bttest_a" is not an index 2025-11-30 18:45:01.299 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_parent_check('bttest_a'); 2025-11-30 18:45:01.299 UTC client backend[43642] pg_regress/bool_plperl LOG: disconnection: session time: 0:00:00.071 user=postgres database=regression_bool_plperl host=[local] 2025-11-30 18:45:01.301 UTC client backend[43482] pg_regress/check_btree ERROR: could not open relation with OID 17 2025-11-30 18:45:01.301 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_check(17); 2025-11-30 18:45:01.302 UTC client backend[43482] pg_regress/check_btree ERROR: could not open relation with OID 17 2025-11-30 18:45:01.302 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_parent_check(17); 2025-11-30 18:45:01.307 UTC unrecognized[43660] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.307 UTC client backend[43660] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.307 UTC client backend[43660] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_call 2025-11-30 18:45:01.309 UTC client backend[43660] pg_regress/pltcl_call LOG: connection ready: setup total=5.125 ms, fork=3.373 ms, authentication=0.135 ms 2025-11-30 18:45:01.309 UTC client backend[43652] isolation/read-write-unique-3/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.309 UTC client backend[43652] isolation/read-write-unique-3/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:01.309 UTC client backend[43652] isolation/read-write-unique-3/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.309 UTC client backend[43652] isolation/read-write-unique-3/s2 CONTEXT: SQL function "insert_unique" statement 1 2025-11-30 18:45:01.309 UTC client backend[43652] isolation/read-write-unique-3/s2 STATEMENT: SELECT insert_unique(1, '2'); 2025-11-30 18:45:01.310 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.310 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3). 2025-11-30 18:45:01.310 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.310 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int); 2025-11-30 18:45:01.312 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.312 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column "y" (position 2). 2025-11-30 18:45:01.312 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.312 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint); 2025-11-30 18:45:01.313 UTC client backend[43644] isolation/read-write-unique-3/control connection LOG: disconnection: session time: 0:00:00.079 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.314 UTC client backend[43646] isolation/read-write-unique-3/s1 LOG: disconnection: session time: 0:00:00.063 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.315 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.315 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3). 2025-11-30 18:45:01.315 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.315 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int); 2025-11-30 18:45:01.316 UTC client backend[43652] isolation/read-write-unique-3/s2 LOG: disconnection: session time: 0:00:00.041 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.317 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.317 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column "y" (position 2). 2025-11-30 18:45:01.317 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.317 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint); 2025-11-30 18:45:01.318 UTC unrecognized[43663] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.318 UTC unrecognized[43665] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.318 UTC client backend[43663] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.318 UTC client backend[43663] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_trigger 2025-11-30 18:45:01.318 UTC client backend[43665] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.318 UTC client backend[43665] [unknown] LOG: connection authorized: user=postgres database=regression_bool_plperl application_name=pg_regress/bool_plperlu 2025-11-30 18:45:01.319 UTC client backend[43663] pg_regress/plpython_trigger LOG: connection ready: setup total=5.911 ms, fork=4.271 ms, authentication=0.124 ms 2025-11-30 18:45:01.319 UTC client backend[43665] pg_regress/bool_plperlu LOG: connection ready: setup total=2.348 ms, fork=0.945 ms, authentication=0.102 ms 2025-11-30 18:45:01.329 UTC client backend[43482] pg_regress/check_btree ERROR: expected "btree" index as targets for verification 2025-11-30 18:45:01.329 UTC client backend[43482] pg_regress/check_btree DETAIL: Relation "bttest_a_brin_idx" is a brin index. 2025-11-30 18:45:01.329 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_parent_check('bttest_a_brin_idx'); 2025-11-30 18:45:01.329 UTC unrecognized[43667] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.332 UTC client backend[43667] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.332 UTC client backend[43667] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_init 2025-11-30 18:45:01.333 UTC client backend[43667] pg_regress/plperl_init LOG: connection ready: setup total=4.933 ms, fork=0.629 ms, authentication=0.140 ms 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3). 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int); 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column "y" (position 2). 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.335 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint); 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Number of returned columns (2) does not match expected column count (3). 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y int, z int); 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Returned type integer does not match expected type bigint in column "y" (position 2). 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnsrecord(integer) while casting return value to function's return type 2025-11-30 18:45:01.337 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select * from returnsrecord(42) as r(x int, y bigint); 2025-11-30 18:45:01.339 UTC client backend[43639] pg_regress/plpgsql_record ERROR: function getf1(integer) does not exist at character 8 2025-11-30 18:45:01.339 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:01.339 UTC client backend[43639] pg_regress/plpgsql_record HINT: You might need to add explicit type casts. 2025-11-30 18:45:01.339 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select getf1(1); 2025-11-30 18:45:01.341 UTC client backend[43665] pg_regress/bool_plperlu LOG: disconnection: session time: 0:00:00.023 user=postgres database=regression_bool_plperl host=[local] 2025-11-30 18:45:01.344 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "x" has no field "f1" 2025-11-30 18:45:01.344 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "x.f1" PL/pgSQL function getf1(record) line 1 at RETURN 2025-11-30 18:45:01.344 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select getf1(row(1,2)::two_int8s); 2025-11-30 18:45:01.344 UTC client backend[43639] pg_regress/plpgsql_record ERROR: could not identify column "f2" in record data type at character 1 2025-11-30 18:45:01.344 UTC client backend[43639] pg_regress/plpgsql_record QUERY: $1.f2 2025-11-30 18:45:01.344 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function getf2(record) line 1 at RETURN 2025-11-30 18:45:01.344 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select getf2(row(1,2)); 2025-11-30 18:45:01.346 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "r" is not assigned yet 2025-11-30 18:45:01.346 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: The tuple structure of a not-yet-assigned record is indeterminate. 2025-11-30 18:45:01.346 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnssetofholes() line 4 at RETURN NEXT 2025-11-30 18:45:01.346 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select returnssetofholes(); 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record ERROR: returned record type does not match expected record type 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Number of returned columns (3) does not match expected column count (2). 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function returnssetofholes() line 3 at RETURN NEXT 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select returnssetofholes(); 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record ERROR: structure of query does not match function result type 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record DETAIL: Returned type numeric does not match expected type integer in column "f3" (position 2). 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: SQL statement "select 1, 2.0" PL/pgSQL function returnssetofholes() line 3 at RETURN QUERY 2025-11-30 18:45:01.347 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select returnssetofholes(); 2025-11-30 18:45:01.348 UTC client backend[43667] pg_regress/plperl_init ERROR: 'system' trapped by operation mask at line 1. 2025-11-30 18:45:01.348 UTC client backend[43667] pg_regress/plperl_init CONTEXT: while executing plperl.on_plperl_init PL/Perl anonymous code block 2025-11-30 18:45:01.348 UTC client backend[43667] pg_regress/plperl_init STATEMENT: DO $$ warn 42 $$ language plperl; 2025-11-30 18:45:01.349 UTC unrecognized[43670] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.349 UTC unrecognized[43669] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.350 UTC client backend[43669] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.350 UTC client backend[43669] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-4 2025-11-30 18:45:01.350 UTC client backend[43670] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.350 UTC client backend[43670] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_init 2025-11-30 18:45:01.350 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "r" has no field "f1" 2025-11-30 18:45:01.350 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function sillyaddone(integer) line 1 at assignment 2025-11-30 18:45:01.350 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select sillyaddone(42); 2025-11-30 18:45:01.351 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "x" has no field "f3" 2025-11-30 18:45:01.351 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL expression "x.f3" PL/pgSQL function getf3(mutable) line 1 at RETURN 2025-11-30 18:45:01.351 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select getf3(null::mutable); 2025-11-30 18:45:01.351 UTC client backend[43669] isolation/read-write-unique-4 LOG: connection ready: setup total=6.518 ms, fork=4.788 ms, authentication=0.120 ms 2025-11-30 18:45:01.351 UTC client backend[43670] pg_regress/plperl_init LOG: connection ready: setup total=2.625 ms, fork=0.555 ms, authentication=0.131 ms 2025-11-30 18:45:01.351 UTC client backend[43482] pg_regress/check_btree ERROR: expected index as targets for verification 2025-11-30 18:45:01.351 UTC client backend[43482] pg_regress/check_btree DETAIL: This operation is not supported for partitioned indexes. 2025-11-30 18:45:01.351 UTC client backend[43482] pg_regress/check_btree STATEMENT: SELECT bt_index_parent_check('bttest_btree_partitioned_idx'); 2025-11-30 18:45:01.351 UTC client backend[43667] pg_regress/plperl_init LOG: disconnection: session time: 0:00:00.022 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.351 UTC client backend[43639] pg_regress/plpgsql_record ERROR: record "x" has no field "f3" 2025-11-30 18:45:01.351 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function getf3(mutable) line 1 at RETURN 2025-11-30 18:45:01.351 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select getf3(null::mutable); 2025-11-30 18:45:01.352 UTC client backend[43639] pg_regress/plpgsql_record ERROR: type "mutable2" does not exist at character 12 2025-11-30 18:45:01.352 UTC client backend[43639] pg_regress/plpgsql_record QUERY: declare r mutable2; begin r.f1 := $1; return r.f1 + 2; end 2025-11-30 18:45:01.352 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: compilation of PL/pgSQL function "sillyaddtwo" near line 1 2025-11-30 18:45:01.352 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select sillyaddtwo(42); 2025-11-30 18:45:01.354 UTC client backend[43660] pg_regress/pltcl_call ERROR: could not parse function return value: list element in braces followed by ")" instead of space 2025-11-30 18:45:01.354 UTC client backend[43660] pg_regress/pltcl_call STATEMENT: CALL test_proc10('abc'); 2025-11-30 18:45:01.354 UTC unrecognized[43671] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.354 UTC client backend[43671] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.354 UTC client backend[43671] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-4 2025-11-30 18:45:01.355 UTC client backend[43671] isolation/read-write-unique-4 LOG: connection ready: setup total=3.699 ms, fork=1.789 ms, authentication=0.127 ms 2025-11-30 18:45:01.356 UTC client backend[43660] pg_regress/pltcl_call LOG: disconnection: session time: 0:00:00.048 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:01.358 UTC client backend[43639] pg_regress/plpgsql_record ERROR: type "mutable2" does not exist 2025-11-30 18:45:01.358 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function sillyaddtwo(integer) line 1 at assignment 2025-11-30 18:45:01.358 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select sillyaddtwo(42); 2025-11-30 18:45:01.360 UTC unrecognized[43673] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.360 UTC client backend[43673] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.360 UTC client backend[43673] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/read-write-unique-4 2025-11-30 18:45:01.362 UTC client backend[43673] isolation/read-write-unique-4 LOG: connection ready: setup total=3.256 ms, fork=1.542 ms, authentication=0.131 ms 2025-11-30 18:45:01.365 UTC unrecognized[43675] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.366 UTC client backend[43675] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.366 UTC client backend[43675] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_start_proc 2025-11-30 18:45:01.367 UTC client backend[43675] pg_regress/pltcl_start_proc LOG: connection ready: setup total=3.331 ms, fork=0.861 ms, authentication=0.116 ms 2025-11-30 18:45:01.368 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.368 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select read_ordered_int8s(row(2, 1)); 2025-11-30 18:45:01.369 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.369 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s(bigint,bigint) while casting return value to function's return type 2025-11-30 18:45:01.369 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s(2,1); 2025-11-30 18:45:01.369 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.369 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_2(bigint,bigint) while casting return value to function's return type 2025-11-30 18:45:01.369 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_2(2,1); 2025-11-30 18:45:01.370 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.370 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_3(bigint,bigint) while casting return value to function's return type 2025-11-30 18:45:01.370 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_3(2,1); 2025-11-30 18:45:01.370 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.370 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_4(bigint,bigint) line 2 at assignment 2025-11-30 18:45:01.370 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_4(2,1); 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function build_ordered_int8s_a(bigint,bigint) while casting return value to function's return type 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: select build_ordered_int8s_a(2,1); 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r ordered_int8s; begin r.q1 := null; r.q2 := 43; r.q1 := 42; r.q2 := 41; -- fail end$$; 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment 2025-11-30 18:45:01.371 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r ordered_int8s; begin r := null; r := row(null,null); r := row(1,2); r := row(2,1); -- fail end$$; 2025-11-30 18:45:01.372 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_int8s violates check constraint "ordered_int8s_check" 2025-11-30 18:45:01.372 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 4 at FOR over SELECT rows 2025-11-30 18:45:01.372 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r ordered_int8s; begin for r in values (1,2),(3,4),(6,5) loop raise notice 'r = %', r; end loop; end$$; 2025-11-30 18:45:01.377 UTC client backend[43675] pg_regress/pltcl_start_proc ERROR: function no_such_function() does not exist 2025-11-30 18:45:01.377 UTC client backend[43675] pg_regress/pltcl_start_proc CONTEXT: processing pltcl.start_proc parameter 2025-11-30 18:45:01.377 UTC client backend[43675] pg_regress/pltcl_start_proc STATEMENT: select tcl_int4add(1, 2); 2025-11-30 18:45:01.378 UTC client backend[43675] pg_regress/pltcl_start_proc ERROR: function no_such_function() does not exist 2025-11-30 18:45:01.378 UTC client backend[43675] pg_regress/pltcl_start_proc CONTEXT: processing pltcl.start_proc parameter 2025-11-30 18:45:01.378 UTC client backend[43675] pg_regress/pltcl_start_proc STATEMENT: select tcl_int4add(1, 2); 2025-11-30 18:45:01.379 UTC client backend[43675] pg_regress/pltcl_start_proc ERROR: function "public.tcl_initialize" must not be SECURITY DEFINER 2025-11-30 18:45:01.379 UTC client backend[43675] pg_regress/pltcl_start_proc CONTEXT: processing pltcl.start_proc parameter 2025-11-30 18:45:01.379 UTC client backend[43675] pg_regress/pltcl_start_proc STATEMENT: select tcl_int4add(1, 2); 2025-11-30 18:45:01.381 UTC client backend[43675] pg_regress/pltcl_start_proc LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:01.384 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_texts violates check constraint "ordered_texts_check" 2025-11-30 18:45:01.384 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 4 at FOR over SELECT rows 2025-11-30 18:45:01.384 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare d ordered_texts; begin for d in select a, b from sometable loop raise notice 'succeeded at "%"', d.f1; end loop; end$$; 2025-11-30 18:45:01.386 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_texts violates check constraint "ordered_texts_check" 2025-11-30 18:45:01.386 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 6 at assignment 2025-11-30 18:45:01.386 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r record; d ordered_texts; begin for r in select * from sometable loop raise notice 'processing row %', r.id; d := row(r.a, r.b); end loop; end$$; 2025-11-30 18:45:01.387 UTC client backend[43639] pg_regress/plpgsql_record ERROR: value for domain ordered_texts violates check constraint "ordered_texts_check" 2025-11-30 18:45:01.387 UTC client backend[43639] pg_regress/plpgsql_record CONTEXT: PL/pgSQL function inline_code_block line 8 at assignment 2025-11-30 18:45:01.387 UTC client backend[43639] pg_regress/plpgsql_record STATEMENT: do $$ declare r record; d ordered_texts; begin for r in select * from sometable loop raise notice 'processing row %', r.id; d := null; d.f1 := r.a; d.f2 := r.b; end loop; end$$; 2025-11-30 18:45:01.390 UTC client backend[43663] pg_regress/plpython_trigger ERROR: unexpected return value from trigger procedure 2025-11-30 18:45:01.390 UTC client backend[43663] pg_regress/plpython_trigger DETAIL: Expected None or a string. 2025-11-30 18:45:01.390 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid1" 2025-11-30 18:45:01.390 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: INSERT INTO trigger_test VALUES (1, 'one'); 2025-11-30 18:45:01.391 UTC client backend[43663] pg_regress/plpython_trigger WARNING: PL/Python trigger function returned "MODIFY" in a DELETE trigger -- ignored 2025-11-30 18:45:01.391 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid2" 2025-11-30 18:45:01.392 UTC client backend[43670] pg_regress/plperl_init WARNING: permission denied to set parameter "plperl.on_plperl_init" 2025-11-30 18:45:01.393 UTC client backend[43663] pg_regress/plpython_trigger ERROR: unexpected return value from trigger procedure 2025-11-30 18:45:01.393 UTC client backend[43663] pg_regress/plpython_trigger DETAIL: Expected None, "OK", "SKIP", or "MODIFY". 2025-11-30 18:45:01.393 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid3" 2025-11-30 18:45:01.393 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-11-30 18:45:01.394 UTC client backend[43663] pg_regress/plpython_trigger ERROR: unexpected return value from trigger procedure 2025-11-30 18:45:01.394 UTC client backend[43663] pg_regress/plpython_trigger DETAIL: Expected None, "OK", "SKIP", or "MODIFY". 2025-11-30 18:45:01.394 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: PL/Python function "stupid3u" 2025-11-30 18:45:01.394 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-11-30 18:45:01.395 UTC client backend[43673] isolation/read-write-unique-4/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.395 UTC client backend[43673] isolation/read-write-unique-4/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:01.395 UTC client backend[43673] isolation/read-write-unique-4/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.395 UTC client backend[43673] isolation/read-write-unique-4/s2 STATEMENT: INSERT INTO invoice VALUES (2016, 3); 2025-11-30 18:45:01.396 UTC client backend[43663] pg_regress/plpython_trigger ERROR: TD["new"] deleted, cannot modify row 2025-11-30 18:45:01.396 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid4" 2025-11-30 18:45:01.396 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-11-30 18:45:01.398 UTC client backend[43663] pg_regress/plpython_trigger ERROR: TD["new"] is not a dictionary 2025-11-30 18:45:01.398 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid5" 2025-11-30 18:45:01.398 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-11-30 18:45:01.399 UTC unrecognized[43678] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.399 UTC client backend[43678] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.399 UTC client backend[43678] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_subxact 2025-11-30 18:45:01.399 UTC client backend[43663] pg_regress/plpython_trigger ERROR: TD["new"] dictionary key at ordinal position 0 is not a string 2025-11-30 18:45:01.399 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid6" 2025-11-30 18:45:01.399 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-11-30 18:45:01.400 UTC client backend[43678] pg_regress/pltcl_subxact LOG: connection ready: setup total=8.319 ms, fork=6.671 ms, authentication=0.121 ms 2025-11-30 18:45:01.401 UTC client backend[43663] pg_regress/plpython_trigger ERROR: key "a" found in TD["new"] does not exist as a column in the triggering row 2025-11-30 18:45:01.401 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid7" 2025-11-30 18:45:01.401 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-11-30 18:45:01.402 UTC client backend[43663] pg_regress/plpython_trigger ERROR: key "a" found in TD["new"] does not exist as a column in the triggering row 2025-11-30 18:45:01.402 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "stupid7u" 2025-11-30 18:45:01.402 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: UPDATE trigger_test SET v = 'null' WHERE i = 0; 2025-11-30 18:45:01.402 UTC client backend[43663] pg_regress/plpython_trigger ERROR: trigger functions can only be called as triggers 2025-11-30 18:45:01.402 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: SELECT stupid7(); 2025-11-30 18:45:01.404 UTC client backend[43670] pg_regress/plperl_init WARNING: 42 at line 1. 2025-11-30 18:45:01.404 UTC client backend[43670] pg_regress/plperl_init CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:01.407 UTC client backend[43670] pg_regress/plperl_init ERROR: permission denied to set parameter "plperl.on_plperl_init" 2025-11-30 18:45:01.407 UTC client backend[43670] pg_regress/plperl_init STATEMENT: SET SESSION plperl.on_plperl_init = 'test'; 2025-11-30 18:45:01.408 UTC unrecognized[43680] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.408 UTC client backend[43680] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.408 UTC client backend[43680] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_record 2025-11-30 18:45:01.409 UTC client backend[43680] pg_regress/plpgsql_record LOG: connection ready: setup total=1.920 ms, fork=0.435 ms, authentication=0.111 ms 2025-11-30 18:45:01.409 UTC client backend[43639] pg_regress/plpgsql_record LOG: disconnection: session time: 0:00:00.187 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:01.412 UTC client backend[43680] pg_regress/plpgsql_record LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:01.412 UTC client backend[43670] pg_regress/plperl_init LOG: disconnection: session time: 0:00:00.063 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.415 UTC client backend[43678] pg_regress/pltcl_subxact LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:01.419 UTC client backend[43673] isolation/read-write-unique-4/s2 ERROR: duplicate key value violates unique constraint "invoice_pkey" 2025-11-30 18:45:01.419 UTC client backend[43673] isolation/read-write-unique-4/s2 DETAIL: Key (year, invoice_number)=(2016, 3) already exists. 2025-11-30 18:45:01.419 UTC client backend[43673] isolation/read-write-unique-4/s2 STATEMENT: INSERT INTO invoice VALUES (2016, 3); 2025-11-30 18:45:01.425 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.425 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric / '0'; 2025-11-30 18:45:01.425 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.425 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric / '0'; 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT '0'::numeric / '0'; 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric % '0'; 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric % '0'; 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT '0'::numeric % '0'; 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT div('inf'::numeric, '0'); 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT div('-inf'::numeric, '0'); 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.427 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT div('0'::numeric, '0'); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take square root of a negative number 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT sqrt('-1'::numeric); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take square root of a negative number 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT sqrt('-inf'::numeric); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT ln('0'::numeric); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT ln('-1'::numeric); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT ln('-inf'::numeric); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT log('0'::numeric, '10'); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '0'); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, '10'); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '-inf'); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '0'); 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.429 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '-inf'); 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, 'inf'); 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-1'); 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-inf'); 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '3.3'); 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-30 18:45:01.430 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '-1.5'); 2025-11-30 18:45:01.431 UTC client backend[43596] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-30 18:45:01.431 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT power('-inf'::numeric, '4.5'); 2025-11-30 18:45:01.434 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.434 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2025-11-30 18:45:01.434 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (3, '1.0'); 2025-11-30 18:45:01.434 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.434 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2025-11-30 18:45:01.434 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (6, '0.99995'); 2025-11-30 18:45:01.435 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.435 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2025-11-30 18:45:01.435 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (10, 'Inf'); 2025-11-30 18:45:01.435 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.435 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2025-11-30 18:45:01.435 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (11, '-Inf'); 2025-11-30 18:45:01.436 UTC client backend[43596] pg_regress/numeric ERROR: bigint out of range 2025-11-30 18:45:01.436 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT (-9223372036854775808.5)::int8; 2025-11-30 18:45:01.436 UTC client backend[43596] pg_regress/numeric ERROR: bigint out of range 2025-11-30 18:45:01.436 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 9223372036854775807.5::int8; 2025-11-30 18:45:01.436 UTC client backend[43596] pg_regress/numeric ERROR: integer out of range 2025-11-30 18:45:01.436 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT (-2147483648.5)::int4; 2025-11-30 18:45:01.437 UTC client backend[43596] pg_regress/numeric ERROR: integer out of range 2025-11-30 18:45:01.437 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 2147483647.5::int4; 2025-11-30 18:45:01.437 UTC client backend[43596] pg_regress/numeric ERROR: smallint out of range 2025-11-30 18:45:01.437 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT (-32768.5)::int2; 2025-11-30 18:45:01.437 UTC client backend[43596] pg_regress/numeric ERROR: smallint out of range 2025-11-30 18:45:01.437 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 32767.5::int2; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert NaN to smallint 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int2; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert infinity to smallint 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int2; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert infinity to smallint 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int2; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert NaN to integer 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int4; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert infinity to integer 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int4; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert infinity to integer 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int4; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert NaN to bigint 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int8; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert infinity to bigint 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int8; 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert infinity to bigint 2025-11-30 18:45:01.438 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int8; 2025-11-30 18:45:01.440 UTC client backend[43673] isolation/read-write-unique-4/s2 ERROR: duplicate key value violates unique constraint "invoice_pkey" 2025-11-30 18:45:01.440 UTC client backend[43673] isolation/read-write-unique-4/s2 DETAIL: Key (year, invoice_number)=(2016, 3) already exists. 2025-11-30 18:45:01.440 UTC client backend[43673] isolation/read-write-unique-4/s2 STATEMENT: INSERT INTO invoice VALUES (2016, 3); 2025-11-30 18:45:01.441 UTC client backend[43663] pg_regress/plpython_trigger ERROR: cannot set generated column "j" 2025-11-30 18:45:01.441 UTC client backend[43663] pg_regress/plpython_trigger CONTEXT: while modifying trigger row PL/Python function "generated_test_func1" 2025-11-30 18:45:01.441 UTC client backend[43663] pg_regress/plpython_trigger STATEMENT: INSERT INTO trigger_test_generated (i) VALUES (1); 2025-11-30 18:45:01.442 UTC client backend[43669] isolation/read-write-unique-4/control connection LOG: disconnection: session time: 0:00:00.092 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.443 UTC unrecognized[43686] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.443 UTC client backend[43686] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.443 UTC client backend[43686] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_unicode 2025-11-30 18:45:01.443 UTC client backend[43671] isolation/read-write-unique-4/s1 LOG: disconnection: session time: 0:00:00.089 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.444 UTC client backend[43686] pg_regress/pltcl_unicode LOG: connection ready: setup total=19.691 ms, fork=14.493 ms, authentication=0.123 ms 2025-11-30 18:45:01.445 UTC client backend[43673] isolation/read-write-unique-4/s2 LOG: disconnection: session time: 0:00:00.084 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.456 UTC client backend[43596] pg_regress/numeric ERROR: value overflows numeric format 2025-11-30 18:45:01.456 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT round(5.5e131071, -131072); 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric ERROR: count must be greater than zero 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, 0); 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric ERROR: count must be greater than zero 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, -5); 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5, 3.0, 3.0, 888); 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric ERROR: count must be greater than zero 2025-11-30 18:45:01.457 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, 0); 2025-11-30 18:45:01.458 UTC client backend[43596] pg_regress/numeric ERROR: count must be greater than zero 2025-11-30 18:45:01.458 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, -5); 2025-11-30 18:45:01.458 UTC client backend[43663] pg_regress/plpython_trigger LOG: disconnection: session time: 0:00:00.140 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.458 UTC client backend[43596] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2025-11-30 18:45:01.458 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5::float8, 3.0::float8, 3.0::float8, 888); 2025-11-30 18:45:01.459 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds cannot be NaN 2025-11-30 18:45:01.459 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0, 'NaN', 4.0, 888); 2025-11-30 18:45:01.459 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds cannot be NaN 2025-11-30 18:45:01.459 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 'NaN', 4.0::float8, 888); 2025-11-30 18:45:01.460 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-30 18:45:01.460 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(2.0, 3.0, '-inf', 888); 2025-11-30 18:45:01.460 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-30 18:45:01.460 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, '-inf', 4.0::float8, 888); 2025-11-30 18:45:01.461 UTC client backend[43686] pg_regress/pltcl_unicode LOG: disconnection: session time: 0:00:00.022 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:01.463 UTC unrecognized[43693] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.463 UTC client backend[43693] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.463 UTC client backend[43693] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_types 2025-11-30 18:45:01.464 UTC client backend[43693] pg_regress/plpython_types LOG: connection ready: setup total=1.998 ms, fork=0.404 ms, authentication=0.120 ms 2025-11-30 18:45:01.466 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-30 18:45:01.466 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 'Infinity'::numeric, 5, 10); 2025-11-30 18:45:01.468 UTC unrecognized[43687] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.469 UTC client backend[43687] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.469 UTC client backend[43687] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperlu 2025-11-30 18:45:01.470 UTC unrecognized[43696] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.470 UTC client backend[43687] pg_regress/plperlu LOG: connection ready: setup total=27.450 ms, fork=24.532 ms, authentication=0.115 ms 2025-11-30 18:45:01.470 UTC client backend[43696] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.470 UTC client backend[43696] [unknown] LOG: connection authorized: user=postgres database=regression_pltcl application_name=pg_regress/pltcl_transaction 2025-11-30 18:45:01.471 UTC client backend[43696] pg_regress/pltcl_transaction LOG: connection ready: setup total=3.193 ms, fork=1.658 ms, authentication=0.114 ms 2025-11-30 18:45:01.471 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-30 18:45:01.471 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 5, '-Infinity'::numeric, 20); 2025-11-30 18:45:01.472 UTC unrecognized[43697] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.472 UTC client backend[43697] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.472 UTC client backend[43697] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.473 UTC client backend[43697] pg_regress LOG: connection ready: setup total=1.747 ms, fork=0.514 ms, authentication=0.105 ms 2025-11-30 18:45:01.473 UTC client backend[43697] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.474 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-30 18:45:01.474 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 'Infinity'::float8, 5, 10); 2025-11-30 18:45:01.474 UTC client backend[43596] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-30 18:45:01.474 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 5, '-Infinity'::float8, 20); 2025-11-30 18:45:01.475 UTC client backend[43597] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_room_during_excl" 2025-11-30 18:45:01.475 UTC client backend[43597] pg_regress/rangetypes DETAIL: Key (room, during)=([123,124), ["Sat Jan 02 10:10:00 2010","Sat Jan 02 11:00:00 2010")) conflicts with existing key (room, during)=([123,124), ["Sat Jan 02 10:00:00 2010","Sat Jan 02 11:00:00 2010")). 2025-11-30 18:45:01.475 UTC client backend[43597] pg_regress/rangetypes STATEMENT: insert into test_range_excl values(int4range(123, 123, '[]'), int4range(3, 3, '[]'), '[2010-01-02 10:10, 2010-01-02 11:00)'); 2025-11-30 18:45:01.477 UTC client backend[43687] pg_regress/plperlu WARNING: 42 at line 1. 2025-11-30 18:45:01.477 UTC client backend[43687] pg_regress/plperlu CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:01.478 UTC client backend[43596] pg_regress/numeric ERROR: integer out of range 2025-11-30 18:45:01.478 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(1::float8, 0, 1, 2147483647); 2025-11-30 18:45:01.478 UTC client backend[43596] pg_regress/numeric ERROR: integer out of range 2025-11-30 18:45:01.478 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 1, 0, 2147483647); 2025-11-30 18:45:01.479 UTC client backend[43687] pg_regress/plperlu LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.479 UTC unrecognized[43700] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.480 UTC client backend[43597] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_speaker_during_excl" 2025-11-30 18:45:01.480 UTC client backend[43597] pg_regress/rangetypes DETAIL: Key (speaker, during)=([1,2), ["Sat Jan 02 10:10:00 2010","Sat Jan 02 11:00:00 2010")) conflicts with existing key (speaker, during)=([1,2), ["Sat Jan 02 10:00:00 2010","Sat Jan 02 11:00:00 2010")). 2025-11-30 18:45:01.480 UTC client backend[43597] pg_regress/rangetypes STATEMENT: insert into test_range_excl values(int4range(125, 125, '[]'), int4range(1, 1, '[]'), '[2010-01-02 10:10, 2010-01-02 11:00)'); 2025-11-30 18:45:01.480 UTC client backend[43700] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.480 UTC client backend[43700] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.481 UTC client backend[43700] pg_regress LOG: connection ready: setup total=2.089 ms, fork=0.419 ms, authentication=0.109 ms 2025-11-30 18:45:01.491 UTC client backend[43700] pg_regress LOG: disconnection: session time: 0:00:00.011 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.492 UTC client backend[43597] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-11-30 18:45:01.492 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '[2010-01-01 01:00:00 -08, 2010-01-01 02:00:00 -05)'::tstzrange; 2025-11-30 18:45:01.493 UTC client backend[43597] pg_regress/rangetypes ERROR: function float4mi(double precision, double precision) does not exist 2025-11-30 18:45:01.493 UTC client backend[43597] pg_regress/rangetypes STATEMENT: create type bogus_float8range as range (subtype=float8, subtype_diff=float4mi); 2025-11-30 18:45:01.494 UTC client backend[43696] pg_regress/pltcl_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.494 UTC client backend[43696] pg_regress/pltcl_transaction CONTEXT: while executing "commit" (procedure "__PLTcl_proc_transaction_test2" line 6) invoked from within "__PLTcl_proc_transaction_test2" in PL/Tcl function transaction_test2() 2025-11-30 18:45:01.494 UTC client backend[43696] pg_regress/pltcl_transaction STATEMENT: SELECT transaction_test2(); 2025-11-30 18:45:01.494 UTC client backend[43696] pg_regress/pltcl_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.494 UTC client backend[43696] pg_regress/pltcl_transaction CONTEXT: while executing "commit" (procedure "__PLTcl_proc_transaction_test1" line 6) invoked from within "__PLTcl_proc_transaction_test1" invoked from within "spi_exec "CALL transaction_test1()"" (procedure "__PLTcl_proc_transaction_test3" line 3) invoked from within "__PLTcl_proc_transaction_test3" in PL/Tcl function transaction_test3() 2025-11-30 18:45:01.494 UTC client backend[43696] pg_regress/pltcl_transaction STATEMENT: SELECT transaction_test3(); 2025-11-30 18:45:01.497 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-11-30 18:45:01.497 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_booltrue(false, true); 2025-11-30 18:45:01.498 UTC client backend[43696] pg_regress/pltcl_transaction ERROR: cannot commit while a subtransaction is active 2025-11-30 18:45:01.498 UTC client backend[43696] pg_regress/pltcl_transaction CONTEXT: while executing "commit" invoked from within "spi_exec -array row "SELECT * FROM test2 ORDER BY x" { spi_exec "INSERT INTO test1 (a) VALUES ($row(x))" commit }" (procedure "__PLTcl_proc_transaction_test4a" line 3) invoked from within "__PLTcl_proc_transaction_test4a" in PL/Tcl function transaction_test4a() 2025-11-30 18:45:01.498 UTC client backend[43696] pg_regress/pltcl_transaction STATEMENT: CALL transaction_test4a(); 2025-11-30 18:45:01.498 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain booltrue violates check constraint "booltrue_check" 2025-11-30 18:45:01.498 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_booltrue" 2025-11-30 18:45:01.498 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_booltrue(true, false); 2025-11-30 18:45:01.499 UTC client backend[43696] pg_regress/pltcl_transaction ERROR: cannot roll back while a subtransaction is active 2025-11-30 18:45:01.499 UTC client backend[43696] pg_regress/pltcl_transaction CONTEXT: while executing "rollback" invoked from within "spi_exec -array row "SELECT * FROM test2 ORDER BY x" { spi_exec "INSERT INTO test1 (a) VALUES ($row(x))" rollback }" (procedure "__PLTcl_proc_transaction_test4b" line 3) invoked from within "__PLTcl_proc_transaction_test4b" in PL/Tcl function transaction_test4b() 2025-11-30 18:45:01.499 UTC client backend[43696] pg_regress/pltcl_transaction STATEMENT: CALL transaction_test4b(); 2025-11-30 18:45:01.499 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-11-30 18:45:01.499 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_uint2" 2025-11-30 18:45:01.499 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_uint2(100::uint2, -50); 2025-11-30 18:45:01.501 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain nnint violates check constraint "nnint_check" 2025-11-30 18:45:01.501 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_nnint(null, 20); 2025-11-30 18:45:01.501 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain nnint violates check constraint "nnint_check" 2025-11-30 18:45:01.501 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_nnint" 2025-11-30 18:45:01.501 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_nnint(10, null); 2025-11-30 18:45:01.502 UTC unrecognized[43705] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.502 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-11-30 18:45:01.502 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10('hello world', 'hello wold'); 2025-11-30 18:45:01.502 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-11-30 18:45:01.502 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_bytea10" 2025-11-30 18:45:01.502 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10('hello word', 'hello world'); 2025-11-30 18:45:01.503 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-11-30 18:45:01.503 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10(null, 'hello word'); 2025-11-30 18:45:01.503 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain bytea10 violates check constraint "bytea10_check" 2025-11-30 18:45:01.503 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_bytea10" 2025-11-30 18:45:01.503 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_bytea10('hello word', null); 2025-11-30 18:45:01.503 UTC unrecognized[43704] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.503 UTC client backend[43705] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.503 UTC client backend[43704] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.503 UTC client backend[43705] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_array 2025-11-30 18:45:01.503 UTC client backend[43704] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/install_btree_gin 2025-11-30 18:45:01.504 UTC client backend[43696] pg_regress/pltcl_transaction ERROR: insert or update on table "testfk" violates foreign key constraint "testfk_f1_fkey" 2025-11-30 18:45:01.504 UTC client backend[43696] pg_regress/pltcl_transaction CONTEXT: while executing "commit" (procedure "__PLTcl_proc_transaction_testfk" line 5) invoked from within "__PLTcl_proc_transaction_testfk" in PL/Tcl function transaction_testfk() 2025-11-30 18:45:01.504 UTC client backend[43696] pg_regress/pltcl_transaction STATEMENT: CALL transaction_testfk(); 2025-11-30 18:45:01.507 UTC unrecognized[43707] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.507 UTC client backend[43707] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.507 UTC client backend[43707] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_simple 2025-11-30 18:45:01.508 UTC client backend[43704] pg_regress/install_btree_gin LOG: connection ready: setup total=11.572 ms, fork=6.445 ms, authentication=0.097 ms 2025-11-30 18:45:01.508 UTC client backend[43707] pg_regress/plpgsql_simple LOG: connection ready: setup total=2.091 ms, fork=0.652 ms, authentication=0.092 ms 2025-11-30 18:45:01.509 UTC client backend[43705] pg_regress/plperl_array LOG: connection ready: setup total=8.162 ms, fork=0.987 ms, authentication=0.118 ms 2025-11-30 18:45:01.512 UTC unrecognized[43708] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.513 UTC client backend[43708] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.513 UTC client backend[43708] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/simple-write-skew 2025-11-30 18:45:01.514 UTC client backend[43708] isolation/simple-write-skew LOG: connection ready: setup total=2.781 ms, fork=0.805 ms, authentication=0.098 ms 2025-11-30 18:45:01.516 UTC client backend[43597] pg_regress/rangetypes ERROR: cannot drop type mydomain because other objects depend on it 2025-11-30 18:45:01.516 UTC client backend[43597] pg_regress/rangetypes DETAIL: type mydomainrange depends on type mydomain 2025-11-30 18:45:01.516 UTC client backend[43597] pg_regress/rangetypes HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:01.516 UTC client backend[43597] pg_regress/rangetypes STATEMENT: drop domain mydomain; 2025-11-30 18:45:01.518 UTC unrecognized[43709] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.518 UTC client backend[43709] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.518 UTC client backend[43709] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/simple-write-skew 2025-11-30 18:45:01.519 UTC client backend[43709] isolation/simple-write-skew LOG: connection ready: setup total=2.735 ms, fork=1.272 ms, authentication=0.098 ms 2025-11-30 18:45:01.521 UTC client backend[43597] pg_regress/rangetypes ERROR: value for domain restrictedrange violates check constraint "restrictedrange_check" 2025-11-30 18:45:01.521 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select '[4,50)'::restrictedrange @> 7; 2025-11-30 18:45:01.523 UTC client backend[43696] pg_regress/pltcl_transaction LOG: disconnection: session time: 0:00:00.053 user=postgres database=regression_pltcl host=[local] 2025-11-30 18:45:01.528 UTC client backend[43597] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-30 18:45:01.528 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select textrange1('a','Z') @> 'b'::text; 2025-11-30 18:45:01.528 UTC client backend[43693] pg_regress/plpython_types ERROR: invalid input syntax for type integer: "abc" 2025-11-30 18:45:01.528 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_array_mixed2" 2025-11-30 18:45:01.528 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_array_mixed2(); 2025-11-30 18:45:01.529 UTC client backend[43705] pg_regress/plperl_array ERROR: number of array dimensions exceeds the maximum allowed (6) at character 25 2025-11-30 18:45:01.529 UTC client backend[43705] pg_regress/plperl_array STATEMENT: select plperl_sum_array('{{{{{{{1,2},{3,4}},{{5,6},{7,8}}},{{{9,10},{11,12}}, {{13,14},{15,16}}}}, {{{{17,18},{19,20}},{{21,22},{23,24}}},{{{25,26},{27,28}},{{29,30},{31,32}}}}}, {{{{{1,2},{3,4}},{{5,6},{7,8}}},{{{9,10},{11,12}},{{13,14},{15,16}}}}, {{{{17,18},{19,20}},{{21,22},{23,24}}},{{{25,26},{27,28}},{{29,30},{31,32}}}}}}, {{{{{{1,2},{3,4}},{{5,6},{7,8}}},{{{9,10},{11,12}},{{13,14},{15,16}}}}, {{{{17,18},{19,20}},{{21,22},{23,24}}},{{{25,26},{27,28}},{{29,30},{31,32}}}}}, {{{{{1,2},{3,4}},{{5,6},{7,8}}},{{{9,10},{11,12}},{{13,14},{15,16}}}}, {{{{17,18},{19,20}},{{21,22},{23,24}}},{{{25,26},{27,28}},{{29,30},{31,32}}}}}}}' ); 2025-11-30 18:45:01.530 UTC client backend[43705] pg_regress/plperl_array ERROR: malformed array literal: "{{{1,2,3}, {4,5,6,7}}, {{7,8,9}, {10, 11, 12}}}" at character 25 2025-11-30 18:45:01.530 UTC client backend[43705] pg_regress/plperl_array DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:01.530 UTC client backend[43705] pg_regress/plperl_array STATEMENT: select plperl_sum_array('{{{1,2,3}, {4,5,6,7}}, {{7,8,9}, {10, 11, 12}}}'); 2025-11-30 18:45:01.533 UTC client backend[43597] pg_regress/rangetypes ERROR: function anyarray_anyrange_func(integer[], numrange) does not exist at character 8 2025-11-30 18:45:01.533 UTC client backend[43597] pg_regress/rangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:01.533 UTC client backend[43597] pg_regress/rangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:01.533 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select anyarray_anyrange_func(ARRAY[1,2], numrange(10,20)); 2025-11-30 18:45:01.535 UTC client backend[43597] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-30 18:45:01.535 UTC client backend[43597] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:01.535 UTC client backend[43597] pg_regress/rangetypes STATEMENT: create function bogus_func(anyelement) returns anyrange as 'select int4range(1,10)' language sql; 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-11-30 18:45:01.536 UTC client backend[43597] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-30 18:45:01.536 UTC client backend[43597] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:01.536 UTC client backend[43597] pg_regress/rangetypes STATEMENT: create function bogus_func(int) returns anyrange as 'select int4range(1,10)' language sql; 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-11-30 18:45:01.536 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-11-30 18:45:01.537 UTC unrecognized[43710] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.537 UTC client backend[43710] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.537 UTC client backend[43710] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/simple-write-skew 2025-11-30 18:45:01.537 UTC unrecognized[43712] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.538 UTC client backend[43712] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.538 UTC client backend[43712] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_simple 2025-11-30 18:45:01.538 UTC client backend[43710] isolation/simple-write-skew LOG: connection ready: setup total=18.310 ms, fork=14.254 ms, authentication=0.113 ms 2025-11-30 18:45:01.539 UTC client backend[43712] pg_regress/plpgsql_simple LOG: connection ready: setup total=1.748 ms, fork=0.411 ms, authentication=0.095 ms 2025-11-30 18:45:01.539 UTC client backend[43707] pg_regress/plpgsql_simple LOG: disconnection: session time: 0:00:00.031 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:01.540 UTC client backend[43597] pg_regress/rangetypes ERROR: function rangetypes_sql(numrange, integer[]) does not exist at character 8 2025-11-30 18:45:01.540 UTC client backend[43597] pg_regress/rangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:01.540 UTC client backend[43597] pg_regress/rangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:01.540 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select rangetypes_sql(numrange(1,10), ARRAY[2,20]); 2025-11-30 18:45:01.540 UTC client backend[43693] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.540 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_md_array_out" 2025-11-30 18:45:01.540 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_type_conversion_md_array_out(); 2025-11-30 18:45:01.542 UTC client backend[43597] pg_regress/rangetypes ERROR: function anycompatiblearray_anycompatiblerange_func(numeric[], int4range) does not exist at character 8 2025-11-30 18:45:01.542 UTC client backend[43597] pg_regress/rangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:01.542 UTC client backend[43597] pg_regress/rangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:01.542 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select anycompatiblearray_anycompatiblerange_func(ARRAY[1.1,2], int4range(10,20)); 2025-11-30 18:45:01.543 UTC client backend[43597] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-30 18:45:01.543 UTC client backend[43597] pg_regress/rangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-30 18:45:01.543 UTC client backend[43597] pg_regress/rangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2025-11-30 18:45:01.543 UTC client backend[43693] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.543 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_malformed" 2025-11-30 18:45:01.543 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_malformed(); 2025-11-30 18:45:01.543 UTC client backend[43705] pg_regress/plperl_array ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.543 UTC client backend[43705] pg_regress/plperl_array CONTEXT: PL/Perl function "plperl_md_array_out" 2025-11-30 18:45:01.543 UTC client backend[43705] pg_regress/plperl_array STATEMENT: select plperl_md_array_out(); 2025-11-30 18:45:01.544 UTC client backend[43712] pg_regress/plpgsql_simple ERROR: division by zero 2025-11-30 18:45:01.544 UTC client backend[43712] pg_regress/plpgsql_simple CONTEXT: SQL function "simplesql" during inlining SQL statement "select simplesql()" PL/pgSQL function simplecaller() line 4 at SQL statement 2025-11-30 18:45:01.544 UTC client backend[43712] pg_regress/plpgsql_simple STATEMENT: select simplecaller(); 2025-11-30 18:45:01.544 UTC client backend[43693] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.544 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_malformed2" 2025-11-30 18:45:01.544 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_malformed2(); 2025-11-30 18:45:01.545 UTC client backend[43693] pg_regress/plpython_types ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.545 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_malformed3" 2025-11-30 18:45:01.545 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_malformed3(); 2025-11-30 18:45:01.545 UTC client backend[43705] pg_regress/plperl_array ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.545 UTC client backend[43705] pg_regress/plperl_array CONTEXT: PL/Perl function "plperl_md_array_out" 2025-11-30 18:45:01.545 UTC client backend[43705] pg_regress/plperl_array STATEMENT: select plperl_md_array_out(); 2025-11-30 18:45:01.546 UTC client backend[43693] pg_regress/plpython_types ERROR: number of array dimensions exceeds the maximum allowed (6) 2025-11-30 18:45:01.546 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_mdarray_toodeep" 2025-11-30 18:45:01.546 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_mdarray_toodeep(); 2025-11-30 18:45:01.546 UTC client backend[43705] pg_regress/plperl_array ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.546 UTC client backend[43705] pg_regress/plperl_array CONTEXT: PL/Perl function "plperl_md_array_out" 2025-11-30 18:45:01.546 UTC client backend[43705] pg_regress/plperl_array STATEMENT: select plperl_md_array_out(); 2025-11-30 18:45:01.547 UTC client backend[43705] pg_regress/plperl_array ERROR: multidimensional arrays must have array expressions with matching dimensions 2025-11-30 18:45:01.547 UTC client backend[43705] pg_regress/plperl_array CONTEXT: PL/Perl function "plperl_md_array_out" 2025-11-30 18:45:01.547 UTC client backend[43705] pg_regress/plperl_array STATEMENT: select plperl_md_array_out(); 2025-11-30 18:45:01.548 UTC client backend[43705] pg_regress/plperl_array LOG: disconnection: session time: 0:00:00.046 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.552 UTC client backend[43712] pg_regress/plpgsql_simple LOG: disconnection: session time: 0:00:00.014 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:01.554 UTC client backend[43693] pg_regress/plpython_types ERROR: return value of function with array return type is not a Python sequence 2025-11-30 18:45:01.554 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_array_error" 2025-11-30 18:45:01.554 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_array_error(); 2025-11-30 18:45:01.557 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-11-30 18:45:01.557 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_array_domain_check_violation" 2025-11-30 18:45:01.557 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT * FROM test_type_conversion_array_domain_check_violation(); 2025-11-30 18:45:01.558 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain uint2 violates check constraint "uint2_check" 2025-11-30 18:45:01.558 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_build_uint2_array" 2025-11-30 18:45:01.558 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_build_uint2_array(-1::int2); 2025-11-30 18:45:01.559 UTC client backend[43693] pg_regress/plpython_types ERROR: return value of function with array return type is not a Python sequence 2025-11-30 18:45:01.559 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_domain_array" 2025-11-30 18:45:01.559 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_type_conversion_domain_array(array[2,4]); 2025-11-30 18:45:01.559 UTC client backend[43693] pg_regress/plpython_types ERROR: return value of function with array return type is not a Python sequence 2025-11-30 18:45:01.559 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "test_type_conversion_domain_array" 2025-11-30 18:45:01.559 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_type_conversion_domain_array(array[4,2]); 2025-11-30 18:45:01.560 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain ordered_pair_domain violates check constraint "ordered_pair_domain_check" 2025-11-30 18:45:01.560 UTC client backend[43693] pg_regress/plpython_types STATEMENT: select test_type_conversion_domain_array2(array[4,2]); 2025-11-30 18:45:01.560 UTC unrecognized[43716] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.561 UTC client backend[43716] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.561 UTC client backend[43716] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_transaction 2025-11-30 18:45:01.561 UTC client backend[43597] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-30 18:45:01.561 UTC client backend[43597] pg_regress/rangetypes STATEMENT: select arrayrange(ARRAY[2,1], ARRAY[1,2]); 2025-11-30 18:45:01.562 UTC client backend[43716] pg_regress/plpgsql_transaction LOG: connection ready: setup total=1.929 ms, fork=0.384 ms, authentication=0.113 ms 2025-11-30 18:45:01.562 UTC client backend[43710] isolation/simple-write-skew/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.562 UTC client backend[43710] isolation/simple-write-skew/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:01.562 UTC client backend[43710] isolation/simple-write-skew/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.562 UTC client backend[43710] isolation/simple-write-skew/s2 STATEMENT: COMMIT; 2025-11-30 18:45:01.564 UTC client backend[43693] pg_regress/plpython_types ERROR: KeyError: 'bonus' 2025-11-30 18:45:01.564 UTC client backend[43693] pg_regress/plpython_types CONTEXT: Traceback (most recent call last): PL/Python function "test_composite_table_input", line 2, in return e['basesalary'] + e['bonus'] PL/Python function "test_composite_table_input" 2025-11-30 18:45:01.564 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT name, test_composite_table_input(employee.*) FROM employee; 2025-11-30 18:45:01.568 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain nnint violates check constraint "nnint_check" 2025-11-30 18:45:01.568 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "nnint_test" 2025-11-30 18:45:01.568 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT nnint_test(3, null); 2025-11-30 18:45:01.571 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.571 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT read_ordered_named_pair(row(2, 1)); 2025-11-30 18:45:01.572 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.572 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "build_ordered_named_pair" 2025-11-30 18:45:01.572 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT build_ordered_named_pair(2,1); 2025-11-30 18:45:01.573 UTC client backend[43693] pg_regress/plpython_types ERROR: value for domain ordered_named_pair violates check constraint "ordered_named_pair_check" 2025-11-30 18:45:01.573 UTC client backend[43693] pg_regress/plpython_types CONTEXT: while creating return value PL/Python function "build_ordered_named_pairs" 2025-11-30 18:45:01.573 UTC client backend[43693] pg_regress/plpython_types STATEMENT: SELECT build_ordered_named_pairs(2,1); 2025-11-30 18:45:01.575 UTC client backend[43709] isolation/simple-write-skew/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.575 UTC client backend[43709] isolation/simple-write-skew/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:01.575 UTC client backend[43709] isolation/simple-write-skew/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.575 UTC client backend[43709] isolation/simple-write-skew/s1 STATEMENT: COMMIT; 2025-11-30 18:45:01.575 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.575 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test1(integer,text) line 6 at COMMIT 2025-11-30 18:45:01.575 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test1(9, 'error'); 2025-11-30 18:45:01.575 UTC client backend[43693] pg_regress/plpython_types LOG: disconnection: session time: 0:00:00.112 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.580 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.580 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 1 at COMMIT 2025-11-30 18:45:01.580 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN COMMIT; END $$; 2025-11-30 18:45:01.582 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.582 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test2() line 6 at COMMIT 2025-11-30 18:45:01.582 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: SELECT transaction_test2(); 2025-11-30 18:45:01.582 UTC client backend[43710] isolation/simple-write-skew/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.582 UTC client backend[43710] isolation/simple-write-skew/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:01.582 UTC client backend[43710] isolation/simple-write-skew/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.582 UTC client backend[43710] isolation/simple-write-skew/s2 STATEMENT: COMMIT; 2025-11-30 18:45:01.588 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.588 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test1(integer,text) line 6 at COMMIT SQL statement "CALL transaction_test1(9, 'error')" PL/pgSQL function transaction_test3() line 3 at CALL 2025-11-30 18:45:01.588 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: SELECT transaction_test3(); 2025-11-30 18:45:01.589 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.589 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 1 at COMMIT SQL statement "DO LANGUAGE plpgsql $x$ BEGIN COMMIT; END $x$" PL/pgSQL function transaction_test4() line 3 at EXECUTE 2025-11-30 18:45:01.589 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: SELECT transaction_test4(); 2025-11-30 18:45:01.590 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.590 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test5() line 3 at COMMIT 2025-11-30 18:45:01.590 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test5(); 2025-11-30 18:45:01.590 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.590 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test5b() line 3 at COMMIT 2025-11-30 18:45:01.590 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test5b(); 2025-11-30 18:45:01.595 UTC unrecognized[43720] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.595 UTC client backend[43720] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.595 UTC client backend[43720] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_error 2025-11-30 18:45:01.596 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: invalid transaction termination 2025-11-30 18:45:01.596 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function transaction_test1(integer,text) line 6 at COMMIT SQL statement "CALL transaction_test1(10, $x$baz$x$)" PL/pgSQL function transaction_test8() line 3 at EXECUTE 2025-11-30 18:45:01.596 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: CALL transaction_test8(); 2025-11-30 18:45:01.596 UTC client backend[43720] pg_regress/plpython_error LOG: connection ready: setup total=3.041 ms, fork=0.998 ms, authentication=0.117 ms 2025-11-30 18:45:01.597 UTC client backend[43597] pg_regress/rangetypes ERROR: composite type two_ints cannot be made a member of itself 2025-11-30 18:45:01.597 UTC client backend[43597] pg_regress/rangetypes STATEMENT: alter type two_ints add attribute c two_ints_range; 2025-11-30 18:45:01.598 UTC client backend[43709] isolation/simple-write-skew/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:01.598 UTC client backend[43709] isolation/simple-write-skew/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:01.598 UTC client backend[43709] isolation/simple-write-skew/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:01.598 UTC client backend[43709] isolation/simple-write-skew/s1 STATEMENT: COMMIT; 2025-11-30 18:45:01.601 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: division by zero 2025-11-30 18:45:01.601 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: SQL statement "INSERT INTO test1 (a) VALUES (12/(r.x-2))" PL/pgSQL function inline_code_block line 6 at SQL statement 2025-11-30 18:45:01.601 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ DECLARE r RECORD; BEGIN FOR r IN SELECT * FROM test2 ORDER BY x LOOP INSERT INTO test1 (a) VALUES (12/(r.x-2)); COMMIT; END LOOP; END; $$; 2025-11-30 18:45:01.610 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: cannot perform transaction commands inside a cursor loop that is not read-only 2025-11-30 18:45:01.610 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 7 at ROLLBACK 2025-11-30 18:45:01.610 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ DECLARE r RECORD; BEGIN FOR r IN UPDATE test2 SET x = x * 2 RETURNING x LOOP INSERT INTO test1 (a) VALUES (r.x); ROLLBACK; END LOOP; END; $$; 2025-11-30 18:45:01.612 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.612 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('viv', 'RN'); 2025-11-30 18:45:01.613 UTC client backend[43708] isolation/simple-write-skew/control connection LOG: disconnection: session time: 0:00:00.100 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.613 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.613 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('DCCCD', 'RN'); 2025-11-30 18:45:01.614 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.614 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('XIXL', 'RN'); 2025-11-30 18:45:01.614 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.614 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('MCCM', 'RN'); 2025-11-30 18:45:01.614 UTC client backend[43709] isolation/simple-write-skew/s1 LOG: disconnection: session time: 0:00:00.096 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.614 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.614 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('MMMM', 'RN'); 2025-11-30 18:45:01.615 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.615 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('VV', 'RN'); 2025-11-30 18:45:01.616 UTC client backend[43710] isolation/simple-write-skew/s2 LOG: disconnection: session time: 0:00:00.081 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:01.616 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.616 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('IL', 'RN'); 2025-11-30 18:45:01.616 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.616 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('VIX', 'RN'); 2025-11-30 18:45:01.616 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.616 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('LXC', 'RN'); 2025-11-30 18:45:01.617 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.617 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('DCM', 'RN'); 2025-11-30 18:45:01.617 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: cannot commit while a subtransaction is active 2025-11-30 18:45:01.617 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 5 at COMMIT 2025-11-30 18:45:01.617 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN BEGIN INSERT INTO test1 (a) VALUES (1); COMMIT; INSERT INTO test1 (a) VALUES (1/0); COMMIT; EXCEPTION WHEN division_by_zero THEN RAISE NOTICE 'caught division_by_zero'; END; END; $$; 2025-11-30 18:45:01.617 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.617 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('MMMDCM', 'RN'); 2025-11-30 18:45:01.617 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.617 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('CLXC', 'RN'); 2025-11-30 18:45:01.618 UTC client backend[43596] pg_regress/numeric ERROR: "RN" is incompatible with other formats 2025-11-30 18:45:01.618 UTC client backend[43596] pg_regress/numeric DETAIL: "RN" may only be used together with "FM". 2025-11-30 18:45:01.618 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('CM', 'MIRN'); 2025-11-30 18:45:01.618 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: cannot roll back while a subtransaction is active 2025-11-30 18:45:01.618 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 5 at ROLLBACK 2025-11-30 18:45:01.618 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN BEGIN INSERT INTO test1 (a) VALUES (1); ROLLBACK; INSERT INTO test1 (a) VALUES (1/0); ROLLBACK; EXCEPTION WHEN division_by_zero THEN RAISE NOTICE 'caught division_by_zero'; END; END; $$; 2025-11-30 18:45:01.618 UTC client backend[43596] pg_regress/numeric ERROR: cannot use "RN" twice 2025-11-30 18:45:01.618 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('CM', 'RNRN'); 2025-11-30 18:45:01.619 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.619 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('qiv', 'RN'); 2025-11-30 18:45:01.619 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: " " 2025-11-30 18:45:01.619 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number('', 'RN'); 2025-11-30 18:45:01.620 UTC client backend[43597] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-30 18:45:01.620 UTC client backend[43597] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:01.620 UTC client backend[43597] pg_regress/rangetypes STATEMENT: create function outparam_fail(i anyelement, out r anyrange, out t text) as $$ select '[1,10]', 'foo' $$ language sql; 2025-11-30 18:45:01.621 UTC client backend[43596] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-30 18:45:01.621 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT to_number(' ', 'RN'); 2025-11-30 18:45:01.623 UTC unrecognized[43725] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.623 UTC client backend[43597] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-30 18:45:01.623 UTC client backend[43597] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:01.623 UTC client backend[43597] pg_regress/rangetypes STATEMENT: create function inoutparam_fail(inout i anyelement, out r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-30 18:45:01.623 UTC client backend[43725] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.623 UTC client backend[43725] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/receipt-report 2025-11-30 18:45:01.625 UTC client backend[43725] isolation/receipt-report LOG: connection ready: setup total=2.134 ms, fork=0.344 ms, authentication=0.104 ms 2025-11-30 18:45:01.626 UTC client backend[43597] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-30 18:45:01.626 UTC client backend[43597] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:01.626 UTC client backend[43597] pg_regress/rangetypes STATEMENT: create function table_fail(i anyelement) returns table(i anyelement, r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-30 18:45:01.629 UTC client backend[43704] pg_regress/install_btree_gin LOG: disconnection: session time: 0:00:00.126 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:01.630 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: duplicate key value violates unique constraint "test3_y_key" 2025-11-30 18:45:01.630 UTC client backend[43716] pg_regress/plpgsql_transaction DETAIL: Key (y)=(1) already exists. 2025-11-30 18:45:01.630 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 9 at COMMIT 2025-11-30 18:45:01.630 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN CREATE TABLE test3 (y int UNIQUE DEFERRABLE INITIALLY DEFERRED); COMMIT; INSERT INTO test3 (y) VALUES (1); COMMIT; INSERT INTO test3 (y) VALUES (1); INSERT INTO test3 (y) VALUES (2); COMMIT; INSERT INTO test3 (y) VALUES (3); -- won't get here END; $$; 2025-11-30 18:45:01.630 UTC unrecognized[43726] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.631 UTC client backend[43726] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.631 UTC client backend[43726] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/receipt-report 2025-11-30 18:45:01.632 UTC client backend[43726] isolation/receipt-report LOG: connection ready: setup total=6.362 ms, fork=3.827 ms, authentication=0.105 ms 2025-11-30 18:45:01.632 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: division by zero 2025-11-30 18:45:01.632 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function cursor_fail_during_commit() line 6 at COMMIT 2025-11-30 18:45:01.632 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: CALL cursor_fail_during_commit(); 2025-11-30 18:45:01.633 UTC unrecognized[43728] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.635 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: division by zero 2025-11-30 18:45:01.635 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function cursor_fail_during_rollback() line 6 at ROLLBACK 2025-11-30 18:45:01.635 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: CALL cursor_fail_during_rollback(); 2025-11-30 18:45:01.636 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query 2025-11-30 18:45:01.636 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: SQL statement "SET TRANSACTION ISOLATION LEVEL REPEATABLE READ" PL/pgSQL function inline_code_block line 3 at SQL statement 2025-11-30 18:45:01.636 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN SET TRANSACTION ISOLATION LEVEL REPEATABLE READ; END; $$; 2025-11-30 18:45:01.636 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: unsupported transaction command in PL/pgSQL 2025-11-30 18:45:01.636 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 3 at SQL statement 2025-11-30 18:45:01.636 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN SAVEPOINT foo; END; $$; 2025-11-30 18:45:01.637 UTC client backend[43716] pg_regress/plpgsql_transaction ERROR: EXECUTE of transaction commands is not implemented 2025-11-30 18:45:01.637 UTC client backend[43716] pg_regress/plpgsql_transaction CONTEXT: PL/pgSQL function inline_code_block line 3 at EXECUTE 2025-11-30 18:45:01.637 UTC client backend[43716] pg_regress/plpgsql_transaction STATEMENT: DO LANGUAGE plpgsql $$ BEGIN EXECUTE 'COMMIT'; END; $$; 2025-11-30 18:45:01.637 UTC client backend[43728] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.637 UTC client backend[43728] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/receipt-report 2025-11-30 18:45:01.637 UTC unrecognized[43730] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.637 UTC client backend[43720] pg_regress/plpython_error ERROR: could not compile PL/Python function "python_syntax_error" 2025-11-30 18:45:01.637 UTC client backend[43720] pg_regress/plpython_error DETAIL: SyntaxError: invalid syntax (, line 2) 2025-11-30 18:45:01.637 UTC client backend[43720] pg_regress/plpython_error STATEMENT: /* Flat out Python syntax error */ CREATE FUNCTION python_syntax_error() RETURNS text AS '.syntaxerror' LANGUAGE plpython3u; 2025-11-30 18:45:01.638 UTC client backend[43728] isolation/receipt-report LOG: connection ready: setup total=4.977 ms, fork=0.451 ms, authentication=0.108 ms 2025-11-30 18:45:01.638 UTC client backend[43730] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.638 UTC client backend[43730] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.638 UTC client backend[43720] pg_regress/plpython_error ERROR: could not compile PL/Python function "python_syntax_error" 2025-11-30 18:45:01.638 UTC client backend[43720] pg_regress/plpython_error DETAIL: SyntaxError: invalid syntax (, line 2) 2025-11-30 18:45:01.638 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT python_syntax_error(); 2025-11-30 18:45:01.638 UTC client backend[43720] pg_regress/plpython_error ERROR: could not compile PL/Python function "python_syntax_error" 2025-11-30 18:45:01.638 UTC client backend[43720] pg_regress/plpython_error DETAIL: SyntaxError: invalid syntax (, line 2) 2025-11-30 18:45:01.638 UTC client backend[43720] pg_regress/plpython_error STATEMENT: /* Run the function twice to check if the hashtable entry gets cleaned up */ SELECT python_syntax_error(); 2025-11-30 18:45:01.639 UTC client backend[43730] pg_regress LOG: connection ready: setup total=2.685 ms, fork=0.825 ms, authentication=0.092 ms 2025-11-30 18:45:01.639 UTC client backend[43720] pg_regress/plpython_error ERROR: spiexceptions.SyntaxError: syntax error at or near "syntax" at character 1 2025-11-30 18:45:01.639 UTC client backend[43720] pg_regress/plpython_error QUERY: syntax error 2025-11-30 18:45:01.639 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "sql_syntax_error", line 1, in plpy.execute("syntax error") PL/Python function "sql_syntax_error" 2025-11-30 18:45:01.639 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT sql_syntax_error(); 2025-11-30 18:45:01.639 UTC client backend[43720] pg_regress/plpython_error ERROR: IndexError: list index out of range 2025-11-30 18:45:01.639 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "exception_index_invalid", line 1, in return args[1] PL/Python function "exception_index_invalid" 2025-11-30 18:45:01.639 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT exception_index_invalid('test'); 2025-11-30 18:45:01.639 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: " " at character 40 2025-11-30 18:45:01.639 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' '); 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error ERROR: spiexceptions.UndefinedFunction: function test5(unknown) does not exist at character 8 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error DETAIL: There is no function of that name. 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error QUERY: SELECT test5('foo') 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "exception_index_invalid_nested", line 1, in rv = plpy.execute("SELECT test5('foo')") PL/Python function "exception_index_invalid_nested" 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT exception_index_invalid_nested(); 2025-11-30 18:45:01.640 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: " 1234 %" at character 40 2025-11-30 18:45:01.640 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' 1234 %'); 2025-11-30 18:45:01.640 UTC unrecognized[43731] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.640 UTC client backend[43597] pg_regress/rangetypes LOG: disconnection: session time: 0:00:00.688 user=postgres database=regression host=[local] 2025-11-30 18:45:01.640 UTC client backend[43731] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.640 UTC client backend[43731] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/receipt-report 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error ERROR: spiexceptions.UndefinedObject: type "test" does not exist 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "invalid_type_uncaught", line 3, in SD["plan"] = plpy.prepare(q, [ "test" ]) PL/Python function "invalid_type_uncaught" 2025-11-30 18:45:01.640 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT invalid_type_uncaught('rick'); 2025-11-30 18:45:01.641 UTC client backend[43731] isolation/receipt-report LOG: connection ready: setup total=1.743 ms, fork=0.389 ms, authentication=0.090 ms 2025-11-30 18:45:01.641 UTC client backend[43730] pg_regress LOG: disconnection: session time: 0:00:00.004 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.642 UTC client backend[43720] pg_regress/plpython_error ERROR: plpy.Error: type "test" does not exist 2025-11-30 18:45:01.642 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "invalid_type_reraised", line 6, in plpy.error(str(ex)) PL/Python function "invalid_type_reraised" 2025-11-30 18:45:01.642 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT invalid_type_reraised('rick'); 2025-11-30 18:45:01.644 UTC client backend[43720] pg_regress/plpython_error ERROR: plpy.Error: boom 2025-11-30 18:45:01.644 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "nested_error", line 10, in fun3() PL/Python function "nested_error", line 8, in fun3 fun2() PL/Python function "nested_error", line 5, in fun2 fun1() PL/Python function "nested_error", line 2, in fun1 plpy.error("boom") PL/Python function "nested_error" 2025-11-30 18:45:01.644 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT nested_error(); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "xyz" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('xyz'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "- 1234" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('- 1234'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5 . 0" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5 . 0'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5. 0 " at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5. 0 '); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (''); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: " N aN " at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' N aN '); 2025-11-30 18:45:01.645 UTC client backend[43720] pg_regress/plpython_error ERROR: plpy.Error: boom 2025-11-30 18:45:01.645 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "nested_error_raise", line 10, in fun3() PL/Python function "nested_error_raise", line 8, in fun3 fun2() PL/Python function "nested_error_raise", line 5, in fun2 fun1() PL/Python function "nested_error_raise", line 2, in fun1 raise plpy.Error("boom") PL/Python function "nested_error_raise" 2025-11-30 18:45:01.645 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT nested_error_raise(); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+NaN" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+NaN'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "-NaN" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('-NaN'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+ infinity" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+ infinity'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "_123" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('_123'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "12__34" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('12__34'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_.456" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_.456'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123._456" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123._456'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e_34" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e_34'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e34_" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e34_'); 2025-11-30 18:45:01.645 UTC client backend[43720] pg_regress/plpython_error WARNING: boom 2025-11-30 18:45:01.645 UTC client backend[43720] pg_regress/plpython_error CONTEXT: PL/Python function "nested_warning" 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e3__4" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e3__4'); 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0b1112" at character 40 2025-11-30 18:45:01.645 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0b1112'); 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0c1112" at character 40 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0c1112'); 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0o12345678" at character 40 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0o12345678'); 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1eg" at character 40 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1eg'); 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12.34" at character 40 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12.34'); 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x__1234" at character 40 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x__1234'); 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1234_" at character 40 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1234_'); 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12__34" at character 40 2025-11-30 18:45:01.646 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12__34'); 2025-11-30 18:45:01.646 UTC client backend[43720] pg_regress/plpython_error ERROR: AttributeError: module 'plpy' has no attribute 'nonexistent' 2025-11-30 18:45:01.646 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "toplevel_attribute_error", line 2, in plpy.nonexistent PL/Python function "toplevel_attribute_error" 2025-11-30 18:45:01.646 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT toplevel_attribute_error(); 2025-11-30 18:45:01.648 UTC client backend[43720] pg_regress/plpython_error ERROR: spiexceptions.DivisionByZero: division by zero 2025-11-30 18:45:01.648 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "python_traceback", line 11, in first() PL/Python function "python_traceback", line 3, in first second() PL/Python function "python_traceback", line 6, in second third() PL/Python function "python_traceback", line 9, in third plpy.execute("select sql_error()") PL/Python function "python_traceback" 2025-11-30 18:45:01.648 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT python_traceback(); 2025-11-30 18:45:01.649 UTC client backend[43720] pg_regress/plpython_error ERROR: division by zero 2025-11-30 18:45:01.649 UTC client backend[43720] pg_regress/plpython_error CONTEXT: SQL statement "select 1/0" PL/pgSQL function sql_error() line 3 at SQL statement 2025-11-30 18:45:01.649 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT sql_error(); 2025-11-30 18:45:01.649 UTC client backend[43720] pg_regress/plpython_error ERROR: spiexceptions.DivisionByZero: division by zero 2025-11-30 18:45:01.649 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "python_traceback", line 11, in first() PL/Python function "python_traceback", line 3, in first second() PL/Python function "python_traceback", line 6, in second third() PL/Python function "python_traceback", line 9, in third plpy.execute("select sql_error()") PL/Python function "python_traceback" SQL statement "select python_traceback()" PL/pgSQL function python_from_sql_error() line 3 at SQL statement 2025-11-30 18:45:01.649 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT python_from_sql_error(); 2025-11-30 18:45:01.650 UTC client backend[43720] pg_regress/plpython_error ERROR: spiexceptions.DivisionByZero: division by zero 2025-11-30 18:45:01.650 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "sql_from_python_error", line 2, in plpy.execute("select sql_error()") PL/Python function "sql_from_python_error" 2025-11-30 18:45:01.650 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT sql_from_python_error(); 2025-11-30 18:45:01.656 UTC client backend[43720] pg_regress/plpython_error ERROR: plpy.SPIError: SPI_execute failed: SPI_ERROR_TRANSACTION 2025-11-30 18:45:01.656 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "manual_subxact", line 2, in plpy.execute("savepoint save") PL/Python function "manual_subxact" 2025-11-30 18:45:01.656 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT manual_subxact(); 2025-11-30 18:45:01.657 UTC client backend[43720] pg_regress/plpython_error ERROR: plpy.SPIError: SPI_execute_plan failed: SPI_ERROR_TRANSACTION 2025-11-30 18:45:01.657 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "manual_subxact_prepared", line 4, in plpy.execute(save) PL/Python function "manual_subxact_prepared" 2025-11-30 18:45:01.657 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT manual_subxact_prepared(); 2025-11-30 18:45:01.660 UTC client backend[43720] pg_regress/plpython_error ERROR: error fetching next item from iterator 2025-11-30 18:45:01.660 UTC client backend[43720] pg_regress/plpython_error DETAIL: spiexceptions.InvalidDatetimeFormat: invalid value "xy" for "DD" 2025-11-30 18:45:01.660 UTC client backend[43720] pg_regress/plpython_error CONTEXT: Traceback (most recent call last): PL/Python function "python_error_detail" 2025-11-30 18:45:01.660 UTC client backend[43720] pg_regress/plpython_error STATEMENT: SELECT python_error_detail(); 2025-11-30 18:45:01.660 UTC client backend[43720] pg_regress/plpython_error LOG: disconnection: session time: 0:00:00.065 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.665 UTC unrecognized[43737] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.665 UTC unrecognized[43736] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.666 UTC client backend[43737] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.666 UTC client backend[43737] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.666 UTC client backend[43737] pg_regress LOG: connection ready: setup total=1.930 ms, fork=0.449 ms, authentication=0.106 ms 2025-11-30 18:45:01.667 UTC client backend[43736] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.667 UTC client backend[43736] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_call 2025-11-30 18:45:01.668 UTC client backend[43736] pg_regress/plperl_call LOG: connection ready: setup total=4.399 ms, fork=0.828 ms, authentication=0.106 ms 2025-11-30 18:45:01.675 UTC unrecognized[43739] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.676 UTC client backend[43739] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.676 UTC client backend[43739] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_ereport 2025-11-30 18:45:01.677 UTC client backend[43739] pg_regress/plpython_ereport LOG: connection ready: setup total=6.943 ms, fork=4.398 ms, authentication=0.111 ms 2025-11-30 18:45:01.688 UTC unrecognized[43732] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.688 UTC client backend[43732] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.688 UTC client backend[43732] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/int2 2025-11-30 18:45:01.689 UTC client backend[43732] pg_regress/int2 LOG: connection ready: setup total=44.992 ms, fork=42.964 ms, authentication=0.128 ms 2025-11-30 18:45:01.691 UTC client backend[43737] pg_regress LOG: disconnection: session time: 0:00:00.025 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.692 UTC client backend[43736] pg_regress/plperl_call LOG: disconnection: session time: 0:00:00.026 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport LOG: log 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport DETAIL: some detail 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: PL/Python function "elog_test" 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: SELECT elog_test(); 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport WARNING: warning 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport DETAIL: some detail 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: PL/Python function "elog_test" 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport ERROR: plpy.Error: stop on error 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport DETAIL: some detail 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport HINT: some hint 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "elog_test", line 18, in plpy.error('stop on error', detail='some detail', hint='some hint') PL/Python function "elog_test" 2025-11-30 18:45:01.692 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: SELECT elog_test(); 2025-11-30 18:45:01.694 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.694 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 3, scale -6 cannot hold an infinite value. 2025-11-30 18:45:01.694 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES ('inf'); 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 3, scale -6 must round to an absolute value less than 10^9. 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES (999500000); 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 3, scale -3 must round to an absolute value less than 10^6. 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousands) VALUES (999500); 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 3, scale 0 must round to an absolute value less than 10^3. 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (units) VALUES (999.5); 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 3, scale 3 must round to an absolute value less than 1. 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousandths) VALUES (0.9995); 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric ERROR: numeric field overflow 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric DETAIL: A field with precision 3, scale 6 must round to an absolute value less than 10^-3. 2025-11-30 18:45:01.695 UTC client backend[43596] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millionths) VALUES (0.0009995); 2025-11-30 18:45:01.701 UTC client backend[43596] pg_regress/numeric ERROR: value overflows numeric format 2025-11-30 18:45:01.701 UTC client backend[43596] pg_regress/numeric STATEMENT: select 10.0 ^ 2147483647 as overflows; 2025-11-30 18:45:01.701 UTC client backend[43596] pg_regress/numeric ERROR: value overflows numeric format 2025-11-30 18:45:01.701 UTC client backend[43596] pg_regress/numeric STATEMENT: select 117743296169.0 ^ 1000000000 as overflows; 2025-11-30 18:45:01.702 UTC client backend[43716] pg_regress/plpgsql_transaction LOG: disconnection: session time: 0:00:00.141 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:01.706 UTC unrecognized[43743] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.706 UTC client backend[43743] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.706 UTC client backend[43743] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_transaction 2025-11-30 18:45:01.707 UTC client backend[43743] pg_regress/plperl_transaction LOG: connection ready: setup total=7.619 ms, fork=5.680 ms, authentication=0.108 ms 2025-11-30 18:45:01.709 UTC unrecognized[43746] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.709 UTC unrecognized[43747] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.709 UTC client backend[43746] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.709 UTC client backend[43746] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/init 2025-11-30 18:45:01.709 UTC client backend[43747] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.709 UTC client backend[43747] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_trap 2025-11-30 18:45:01.710 UTC client backend[43596] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-11-30 18:45:01.710 UTC client backend[43596] pg_regress/numeric STATEMENT: select 0.0 ^ (-12.34); 2025-11-30 18:45:01.710 UTC client backend[43596] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-30 18:45:01.710 UTC client backend[43596] pg_regress/numeric STATEMENT: select (-12.34) ^ 1.2; 2025-11-30 18:45:01.710 UTC client backend[43747] pg_regress/plpgsql_trap LOG: connection ready: setup total=1.690 ms, fork=0.328 ms, authentication=0.097 ms 2025-11-30 18:45:01.713 UTC client backend[43747] pg_regress/plpgsql_trap ERROR: -100 is less than zero 2025-11-30 18:45:01.713 UTC client backend[43747] pg_regress/plpgsql_trap CONTEXT: PL/pgSQL function trap_zero_divide(integer) line 12 at RAISE 2025-11-30 18:45:01.713 UTC client backend[43747] pg_regress/plpgsql_trap STATEMENT: select trap_zero_divide(-100); 2025-11-30 18:45:01.715 UTC client backend[43746] pg_regress/init LOG: connection ready: setup total=6.653 ms, fork=0.372 ms, authentication=0.104 ms 2025-11-30 18:45:01.728 UTC client backend[43743] pg_regress/plperl_transaction ERROR: invalid transaction termination at line 5. 2025-11-30 18:45:01.728 UTC client backend[43743] pg_regress/plperl_transaction CONTEXT: PL/Perl function "transaction_test2" 2025-11-30 18:45:01.728 UTC client backend[43743] pg_regress/plperl_transaction STATEMENT: SELECT transaction_test2(); 2025-11-30 18:45:01.729 UTC client backend[43743] pg_regress/plperl_transaction ERROR: invalid transaction termination at line 5. at line 2. 2025-11-30 18:45:01.729 UTC client backend[43743] pg_regress/plperl_transaction CONTEXT: PL/Perl function "transaction_test3" 2025-11-30 18:45:01.729 UTC client backend[43743] pg_regress/plperl_transaction STATEMENT: SELECT transaction_test3(); 2025-11-30 18:45:01.730 UTC client backend[43743] pg_regress/plperl_transaction ERROR: invalid transaction termination at line 1. at line 2. 2025-11-30 18:45:01.730 UTC client backend[43743] pg_regress/plperl_transaction CONTEXT: PL/Perl function "transaction_test4" 2025-11-30 18:45:01.730 UTC client backend[43743] pg_regress/plperl_transaction STATEMENT: SELECT transaction_test4(); 2025-11-30 18:45:01.731 UTC client backend[43596] pg_regress/numeric ERROR: step size cannot equal zero 2025-11-30 18:45:01.731 UTC client backend[43596] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 0::numeric); 2025-11-30 18:45:01.734 UTC client backend[43596] pg_regress/numeric ERROR: step size cannot be NaN 2025-11-30 18:45:01.734 UTC client backend[43596] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 'nan'::numeric); 2025-11-30 18:45:01.734 UTC client backend[43596] pg_regress/numeric ERROR: start value cannot be NaN 2025-11-30 18:45:01.734 UTC client backend[43596] pg_regress/numeric STATEMENT: select * from generate_series('nan'::numeric, 100::numeric, 10::numeric); 2025-11-30 18:45:01.736 UTC client backend[43743] pg_regress/plperl_transaction ERROR: division by zero at line 5. 2025-11-30 18:45:01.736 UTC client backend[43743] pg_regress/plperl_transaction CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:01.736 UTC client backend[43743] pg_regress/plperl_transaction STATEMENT: DO LANGUAGE plperl $$ my $sth = spi_query("SELECT * FROM test2 ORDER BY x"); my $row; while (defined($row = spi_fetchrow($sth))) { spi_exec_query("INSERT INTO test1 (a) VALUES (12/(" . $row->{x} . "-2))"); spi_commit(); } $$; 2025-11-30 18:45:01.736 UTC client backend[43596] pg_regress/numeric ERROR: stop value cannot be NaN 2025-11-30 18:45:01.736 UTC client backend[43596] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'nan'::numeric, 10::numeric); 2025-11-30 18:45:01.736 UTC client backend[43596] pg_regress/numeric ERROR: start value cannot be infinity 2025-11-30 18:45:01.736 UTC client backend[43596] pg_regress/numeric STATEMENT: select * from generate_series('inf'::numeric, 'inf'::numeric, 10::numeric); 2025-11-30 18:45:01.738 UTC client backend[43596] pg_regress/numeric ERROR: stop value cannot be infinity 2025-11-30 18:45:01.738 UTC client backend[43596] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'inf'::numeric, 10::numeric); 2025-11-30 18:45:01.738 UTC client backend[43596] pg_regress/numeric ERROR: step size cannot be infinity 2025-11-30 18:45:01.738 UTC client backend[43596] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, '42'::numeric, '-inf'::numeric); 2025-11-30 18:45:01.744 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.744 UTC client backend[43596] pg_regress/numeric STATEMENT: select ln(-12.34); 2025-11-30 18:45:01.745 UTC client backend[43743] pg_regress/plperl_transaction ERROR: insert or update on table "testfk" violates foreign key constraint "testfk_f1_fkey" at line 4. 2025-11-30 18:45:01.745 UTC client backend[43743] pg_regress/plperl_transaction CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:01.745 UTC client backend[43743] pg_regress/plperl_transaction STATEMENT: DO LANGUAGE plperl $$ # this insert will fail during commit: spi_exec_query("INSERT INTO testfk VALUES (0)"); spi_commit(); elog(WARNING, 'should not get here'); $$; 2025-11-30 18:45:01.746 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.746 UTC client backend[43596] pg_regress/numeric STATEMENT: select ln(0.0); 2025-11-30 18:45:01.751 UTC client backend[43743] pg_regress/plperl_transaction LOG: disconnection: session time: 0:00:00.044 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.753 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.753 UTC client backend[43596] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2025-11-30 18:45:01.753 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(-12.34); 2025-11-30 18:45:01.754 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.754 UTC client backend[43596] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2025-11-30 18:45:01.754 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(0.0); 2025-11-30 18:45:01.758 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.758 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(-12.34, 56.78); 2025-11-30 18:45:01.758 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.758 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(-12.34, -56.78); 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(12.34, -56.78); 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(0.0, 12.34); 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(12.34, 0.0); 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric ERROR: division by zero 2025-11-30 18:45:01.759 UTC client backend[43596] pg_regress/numeric STATEMENT: select log(1.0, 12.34); 2025-11-30 18:45:01.761 UTC unrecognized[43750] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.761 UTC client backend[43750] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.761 UTC client backend[43750] [unknown] LOG: connection authorized: user=postgres database=regression_plperl application_name=pg_regress/plperl_env 2025-11-30 18:45:01.762 UTC client backend[43750] pg_regress/plperl_env LOG: connection ready: setup total=4.565 ms, fork=2.997 ms, authentication=0.106 ms 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport ERROR: ValueError: invalid SQLSTATE code 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('wrong sqlstate', sqlstate='54444A') PL/Python anonymous code block 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('wrong sqlstate', sqlstate='54444A') $$ LANGUAGE plpython3u; 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport ERROR: TypeError: 'blabla' is an invalid keyword argument for this function 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('unsupported argument', blabla='fooboo') PL/Python anonymous code block 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('unsupported argument', blabla='fooboo') $$ LANGUAGE plpython3u; 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport ERROR: TypeError: argument 'message' given by name and position 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('first message', message='second message') PL/Python anonymous code block 2025-11-30 18:45:01.762 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('first message', message='second message') $$ LANGUAGE plpython3u; 2025-11-30 18:45:01.763 UTC client backend[43739] pg_regress/plpython_ereport ERROR: TypeError: argument 'message' given by name and position 2025-11-30 18:45:01.763 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 1, in plpy.info('first message', 'second message', message='third message') PL/Python anonymous code block 2025-11-30 18:45:01.763 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: DO $$ plpy.info('first message', 'second message', message='third message') $$ LANGUAGE plpython3u; 2025-11-30 18:45:01.763 UTC client backend[43739] pg_regress/plpython_ereport ERROR: plpy.Error: hello 2025-11-30 18:45:01.763 UTC client backend[43739] pg_regress/plpython_ereport DETAIL: world 2025-11-30 18:45:01.763 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-11-30 18:45:01.763 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception('hello', 'world'); 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport ERROR: plpy.Error: message text 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport DETAIL: detail text 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception('message text', 'detail text', _sqlstate => 'YY333'); 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport ERROR: plpy.Error: message text 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport DETAIL: detail text 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport HINT: hint text 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception(_message => 'message text', _detail => 'detail text', _hint => 'hint text', _sqlstate => 'XX555', _schema_name => 'schema text', _table_name => 'table text', _column_name => 'column text', _datatype_name => 'datatype text', _constraint_name => 'constraint text'); 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport ERROR: plpy.Error: message text 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport HINT: hint text 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python function "raise_exception", line 9, in plpy.error(**dict((k, v) for k, v in iter(kwargs.items()) if v)) PL/Python function "raise_exception" 2025-11-30 18:45:01.764 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: SELECT raise_exception(_message => 'message text', _hint => 'hint text', _schema_name => 'schema text', _column_name => 'column text', _constraint_name => 'constraint text'); 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport ERROR: plpy.SPIError: plpy.Error: my message 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport HINT: some hint 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 6, in raise e PL/Python anonymous code block, line 3, in __plpython_inline_block plpy.execute("select raise_exception(_message => 'my message', _sqlstate => 'XX987', _hint => 'some hint', _table_name => 'users_tab', _datatype_name => 'user_type')") PL/Python anonymous code block 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: DO $$ try: plpy.execute("select raise_exception(_message => 'my message', _sqlstate => 'XX987', _hint => 'some hint', _table_name => 'users_tab', _datatype_name => 'user_type')") except Exception as e: plpy.info(e.spidata) raise e $$ LANGUAGE plpython3u; 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport ERROR: plpy.Error: my message 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport HINT: some hint 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 6, in raise e PL/Python anonymous code block, line 3, in __plpython_inline_block plpy.error(message = 'my message', sqlstate = 'XX987', hint = 'some hint', table_name = 'users_tab', datatype_name = 'user_type') PL/Python anonymous code block 2025-11-30 18:45:01.765 UTC client backend[43739] pg_regress/plpython_ereport STATEMENT: DO $$ try: plpy.error(message = 'my message', sqlstate = 'XX987', hint = 'some hint', table_name = 'users_tab', datatype_name = 'user_type') except Exception as e: plpy.info('sqlstate: %s, hint: %s, table_name: %s, datatype_name: %s' % (e.sqlstate, e.hint, e.table_name, e.datatype_name)) raise e $$ LANGUAGE plpython3u; 2025-11-30 18:45:01.766 UTC client backend[43739] pg_regress/plpython_ereport LOG: disconnection: session time: 0:00:00.090 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:01.792 UTC client backend[43750] pg_regress/plperl_env WARNING: attempted alteration of $ENV{TEST_PLPERL_ENV_FOO} at line 12. 2025-11-30 18:45:01.792 UTC client backend[43750] pg_regress/plperl_env CONTEXT: PL/Perl anonymous code block 2025-11-30 18:45:01.795 UTC client backend[43750] pg_regress/plperl_env LOG: disconnection: session time: 0:00:00.034 user=postgres database=regression_plperl host=[local] 2025-11-30 18:45:01.854 UTC unrecognized[43760] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.855 UTC client backend[43760] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.855 UTC client backend[43760] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.855 UTC client backend[43760] pg_regress LOG: connection ready: setup total=5.313 ms, fork=4.000 ms, authentication=0.102 ms 2025-11-30 18:45:01.856 UTC client backend[43760] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.859 UTC client backend[43732] pg_regress/int2 LOG: disconnection: session time: 0:00:00.171 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:01.892 UTC client backend[43746] pg_regress/init LOG: disconnection: session time: 0:00:00.183 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:01.898 UTC unrecognized[43766] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.898 UTC unrecognized[43765] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.898 UTC client backend[43765] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.898 UTC client backend[43765] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:01.899 UTC client backend[43765] pg_regress LOG: connection ready: setup total=2.204 ms, fork=0.961 ms, authentication=0.108 ms 2025-11-30 18:45:01.900 UTC client backend[43766] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.900 UTC client backend[43766] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_unicode 2025-11-30 18:45:01.900 UTC unrecognized[43767] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.901 UTC client backend[43767] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.901 UTC client backend[43767] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/int4 2025-11-30 18:45:01.902 UTC client backend[43767] pg_regress/int4 LOG: connection ready: setup total=3.878 ms, fork=2.602 ms, authentication=0.090 ms 2025-11-30 18:45:01.902 UTC client backend[43766] pg_regress/plpython_unicode LOG: connection ready: setup total=4.665 ms, fork=0.290 ms, authentication=0.088 ms 2025-11-30 18:45:01.919 UTC unrecognized[43774] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.919 UTC client backend[43774] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.919 UTC client backend[43774] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/int2 2025-11-30 18:45:01.920 UTC client backend[43774] pg_regress/int2 LOG: connection ready: setup total=5.267 ms, fork=0.674 ms, authentication=0.113 ms 2025-11-30 18:45:01.924 UTC client backend[43596] pg_regress/numeric ERROR: value overflows numeric format 2025-11-30 18:45:01.924 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT lcm(9999 * (10::numeric)^131068 + (10::numeric^131068 - 1), 2); 2025-11-30 18:45:01.926 UTC client backend[43596] pg_regress/numeric ERROR: value overflows numeric format 2025-11-30 18:45:01.926 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT factorial(100000); 2025-11-30 18:45:01.932 UTC client backend[43596] pg_regress/numeric ERROR: factorial of a negative number is undefined 2025-11-30 18:45:01.932 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT factorial(-4); 2025-11-30 18:45:01.938 UTC client backend[43596] pg_regress/numeric ERROR: pg_lsn out of range 2025-11-30 18:45:01.938 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT pg_lsn(-1::numeric); 2025-11-30 18:45:01.938 UTC client backend[43596] pg_regress/numeric ERROR: pg_lsn out of range 2025-11-30 18:45:01.938 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT pg_lsn(18446744073709551616::numeric); 2025-11-30 18:45:01.939 UTC client backend[43767] pg_regress/int4 LOG: disconnection: session time: 0:00:00.038 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:01.939 UTC client backend[43596] pg_regress/numeric ERROR: cannot convert NaN to pg_lsn 2025-11-30 18:45:01.939 UTC client backend[43596] pg_regress/numeric STATEMENT: SELECT pg_lsn('NaN'::numeric); 2025-11-30 18:45:01.941 UTC client backend[43774] pg_regress/int2 LOG: disconnection: session time: 0:00:00.025 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:01.943 UTC client backend[43596] pg_regress/numeric LOG: disconnection: session time: 0:00:00.993 user=postgres database=regression host=[local] 2025-11-30 18:45:01.948 UTC unrecognized[43778] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.948 UTC client backend[43778] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.948 UTC client backend[43778] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/int4 2025-11-30 18:45:01.949 UTC client backend[43778] pg_regress/int4 LOG: connection ready: setup total=1.967 ms, fork=0.413 ms, authentication=0.110 ms 2025-11-30 18:45:01.954 UTC client backend[43765] pg_regress LOG: disconnection: session time: 0:00:00.055 user=postgres database=postgres host=[local] 2025-11-30 18:45:01.959 UTC unrecognized[43783] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.959 UTC client backend[43783] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.959 UTC client backend[43783] [unknown] LOG: connection authorized: user=postgres database=regression_citext application_name=pg_regress/create_index_acl 2025-11-30 18:45:01.964 UTC client backend[43783] pg_regress/create_index_acl LOG: connection ready: setup total=6.056 ms, fork=0.868 ms, authentication=0.110 ms 2025-11-30 18:45:01.973 UTC unrecognized[43785] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:01.973 UTC client backend[43785] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:01.974 UTC client backend[43785] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/int8 2025-11-30 18:45:01.974 UTC client backend[43785] pg_regress/int8 LOG: connection ready: setup total=6.630 ms, fork=5.097 ms, authentication=0.111 ms 2025-11-30 18:45:01.979 UTC client backend[43778] pg_regress/int4 LOG: disconnection: session time: 0:00:00.030 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:01.986 UTC client backend[43785] pg_regress/int8 LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.006 UTC unrecognized[43789] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.007 UTC client backend[43789] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.007 UTC client backend[43789] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/int8 2025-11-30 18:45:02.008 UTC client backend[43789] pg_regress/int8 LOG: connection ready: setup total=1.906 ms, fork=0.396 ms, authentication=0.106 ms 2025-11-30 18:45:02.009 UTC client backend[43766] pg_regress/plpython_unicode LOG: disconnection: session time: 0:00:00.111 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:02.021 UTC unrecognized[43799] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.021 UTC client backend[43799] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.021 UTC client backend[43799] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_quote 2025-11-30 18:45:02.022 UTC client backend[43799] pg_regress/plpython_quote LOG: connection ready: setup total=2.585 ms, fork=1.133 ms, authentication=0.106 ms 2025-11-30 18:45:02.030 UTC client backend[43783] pg_regress/create_index_acl ERROR: collation "coll" for encoding "UTF8" does not exist 2025-11-30 18:45:02.030 UTC client backend[43783] pg_regress/create_index_acl STATEMENT: ALTER TABLE s.x ADD CONSTRAINT underqualified EXCLUDE USING btree ((s.index_this_expr(y, s.const())) COLLATE coll WITH s.=) USING INDEX TABLESPACE regress_create_idx_tblspace WHERE (s.index_row_if(y)); 2025-11-30 18:45:02.031 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:02.031 UTC unrecognized[43797] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.031 UTC client backend[43797] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.031 UTC client backend[43797] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/float4 2025-11-30 18:45:02.032 UTC client backend[43797] pg_regress/float4 LOG: connection ready: setup total=12.971 ms, fork=11.508 ms, authentication=0.105 ms 2025-11-30 18:45:02.049 UTC client backend[43797] pg_regress/float4 LOG: disconnection: session time: 0:00:00.017 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.059 UTC client backend[43799] pg_regress/plpython_quote LOG: disconnection: session time: 0:00:00.038 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:02.066 UTC unrecognized[43802] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.066 UTC client backend[43802] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.066 UTC client backend[43802] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/float8 2025-11-30 18:45:02.067 UTC client backend[43802] pg_regress/float8 LOG: connection ready: setup total=11.653 ms, fork=10.042 ms, authentication=0.118 ms 2025-11-30 18:45:02.076 UTC client backend[43802] pg_regress/float8 LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.081 UTC unrecognized[43805] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.081 UTC client backend[43805] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.081 UTC client backend[43805] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_composite 2025-11-30 18:45:02.082 UTC client backend[43805] pg_regress/plpython_composite LOG: connection ready: setup total=17.492 ms, fork=15.971 ms, authentication=0.114 ms 2025-11-30 18:45:02.083 UTC unrecognized[43809] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.083 UTC client backend[43809] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.083 UTC client backend[43809] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/money 2025-11-30 18:45:02.083 UTC checkpointer[43405] LOG: checkpoint complete: wrote 14810 buffers (90.4%), wrote 4 SLRU buffers; 0 WAL file(s) added, 0 removed, 7 recycled; write=0.052 s, sync=0.001 s, total=0.053 s; sync files=0, longest=0.000 s, average=0.000 s; distance=111197 kB, estimate=111197 kB; lsn=0/087491E8, redo lsn=0/08424C78 2025-11-30 18:45:02.084 UTC client backend[43809] pg_regress/money LOG: connection ready: setup total=2.135 ms, fork=0.876 ms, authentication=0.089 ms 2025-11-30 18:45:02.090 UTC client backend[43809] pg_regress/money LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.097 UTC client backend[43783] pg_regress/create_index_acl LOG: disconnection: session time: 0:00:00.138 user=postgres database=regression_citext host=[local] 2025-11-30 18:45:02.099 UTC client backend[43731] isolation/receipt-report/s3 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:02.099 UTC client backend[43731] isolation/receipt-report/s3 DETAIL: Reason code: Canceled on conflict out to pivot 2853, during read. 2025-11-30 18:45:02.099 UTC client backend[43731] isolation/receipt-report/s3 HINT: The transaction might succeed if retried. 2025-11-30 18:45:02.099 UTC client backend[43731] isolation/receipt-report/s3 STATEMENT: SELECT * FROM receipt WHERE deposit_date = DATE '2008-12-22'; 2025-11-30 18:45:02.113 UTC client backend[43805] pg_regress/plpython_composite ERROR: length of returned sequence did not match number of columns in row 2025-11-30 18:45:02.113 UTC client backend[43805] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "changing_test" 2025-11-30 18:45:02.113 UTC client backend[43805] pg_regress/plpython_composite STATEMENT: SELECT * FROM changing_test(); 2025-11-30 18:45:02.114 UTC client backend[43805] pg_regress/plpython_composite ERROR: length of returned sequence did not match number of columns in row 2025-11-30 18:45:02.114 UTC client backend[43805] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "changing_test" 2025-11-30 18:45:02.114 UTC client backend[43805] pg_regress/plpython_composite STATEMENT: SELECT * FROM changing_test(); 2025-11-30 18:45:02.114 UTC client backend[43726] isolation/receipt-report/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:02.114 UTC client backend[43726] isolation/receipt-report/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:02.114 UTC client backend[43726] isolation/receipt-report/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:02.114 UTC client backend[43726] isolation/receipt-report/s1 STATEMENT: COMMIT; 2025-11-30 18:45:02.118 UTC unrecognized[43819] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.118 UTC client backend[43819] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.118 UTC client backend[43819] [unknown] LOG: connection authorized: user=postgres database=regression_citext application_name=pg_regress/citext 2025-11-30 18:45:02.119 UTC client backend[43819] pg_regress/citext LOG: connection ready: setup total=2.727 ms, fork=1.287 ms, authentication=0.114 ms 2025-11-30 18:45:02.120 UTC client backend[43805] pg_regress/plpython_composite ERROR: key "v3" not found in mapping 2025-11-30 18:45:02.120 UTC client backend[43805] pg_regress/plpython_composite HINT: To return null in a column, add the value None to the mapping with the key named after the column. 2025-11-30 18:45:02.120 UTC client backend[43805] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "return_record_2" 2025-11-30 18:45:02.120 UTC client backend[43805] pg_regress/plpython_composite STATEMENT: SELECT * FROM return_record_2('v4') AS (v1 int, v3 int, v2 int); 2025-11-30 18:45:02.122 UTC client backend[43805] pg_regress/plpython_composite ERROR: malformed record literal: "first" 2025-11-30 18:45:02.122 UTC client backend[43805] pg_regress/plpython_composite DETAIL: Missing left parenthesis. 2025-11-30 18:45:02.122 UTC client backend[43805] pg_regress/plpython_composite HINT: To return a composite type in an array, return the composite type as a Python tuple, e.g., "[('foo',)]". 2025-11-30 18:45:02.122 UTC client backend[43805] pg_regress/plpython_composite CONTEXT: while creating return value PL/Python function "composite_type_as_list_broken" 2025-11-30 18:45:02.122 UTC client backend[43805] pg_regress/plpython_composite STATEMENT: SELECT * FROM composite_type_as_list_broken(); 2025-11-30 18:45:02.122 UTC client backend[43805] pg_regress/plpython_composite LOG: disconnection: session time: 0:00:00.040 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:02.136 UTC client backend[43726] isolation/receipt-report/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:02.136 UTC client backend[43726] isolation/receipt-report/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:02.136 UTC client backend[43726] isolation/receipt-report/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:02.136 UTC client backend[43726] isolation/receipt-report/s1 STATEMENT: COMMIT; 2025-11-30 18:45:02.160 UTC unrecognized[43817] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.160 UTC client backend[43817] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.160 UTC client backend[43817] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/oid 2025-11-30 18:45:02.161 UTC client backend[43817] pg_regress/oid LOG: connection ready: setup total=48.450 ms, fork=46.808 ms, authentication=0.126 ms 2025-11-30 18:45:02.165 UTC client backend[43789] pg_regress/int8 LOG: disconnection: session time: 0:00:00.158 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.168 UTC client backend[43817] pg_regress/oid LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.168 UTC unrecognized[43826] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.168 UTC client backend[43826] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.168 UTC client backend[43826] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_subtransaction 2025-11-30 18:45:02.169 UTC client backend[43826] pg_regress/plpython_subtransaction LOG: connection ready: setup total=41.283 ms, fork=39.750 ms, authentication=0.099 ms 2025-11-30 18:45:02.173 UTC unrecognized[43829] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.173 UTC client backend[43829] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.173 UTC client backend[43829] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/float4 2025-11-30 18:45:02.174 UTC client backend[43829] pg_regress/float4 LOG: connection ready: setup total=2.093 ms, fork=0.684 ms, authentication=0.097 ms 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext ERROR: duplicate key value violates unique constraint "try_pkey" 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext DETAIL: Key (name)=(a) already exists. 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO try (name) VALUES ('a'); 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext ERROR: duplicate key value violates unique constraint "try_pkey" 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext DETAIL: Key (name)=(A) already exists. 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO try (name) VALUES ('A'); 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext ERROR: duplicate key value violates unique constraint "try_pkey" 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext DETAIL: Key (name)=(aB) already exists. 2025-11-30 18:45:02.182 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO try (name) VALUES ('aB'); 2025-11-30 18:45:02.186 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: spiexceptions.InvalidTextRepresentation: invalid input syntax for type integer: "oops" at character 40 2025-11-30 18:45:02.186 UTC client backend[43826] pg_regress/plpython_subtransaction QUERY: INSERT INTO subtransaction_tbl VALUES ('oops') 2025-11-30 18:45:02.186 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_ctx_test", line 6, in plpy.execute("INSERT INTO subtransaction_tbl VALUES ('oops')") PL/Python function "subtransaction_ctx_test" 2025-11-30 18:45:02.186 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_ctx_test('SPI'); 2025-11-30 18:45:02.186 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: Exception: Python exception 2025-11-30 18:45:02.186 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_ctx_test", line 8, in raise Exception("Python exception") PL/Python function "subtransaction_ctx_test" 2025-11-30 18:45:02.186 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_ctx_test('Python'); 2025-11-30 18:45:02.187 UTC unrecognized[43832] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.188 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: spiexceptions.SyntaxError: syntax error at or near "error" at character 1 2025-11-30 18:45:02.188 UTC client backend[43826] pg_regress/plpython_subtransaction QUERY: error 2025-11-30 18:45:02.188 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_nested_test", line 8, in plpy.execute("error") PL/Python function "subtransaction_nested_test" 2025-11-30 18:45:02.188 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_nested_test(); 2025-11-30 18:45:02.190 UTC client backend[43832] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.190 UTC client backend[43832] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/timestamp 2025-11-30 18:45:02.191 UTC client backend[43829] pg_regress/float4 LOG: disconnection: session time: 0:00:00.018 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.191 UTC client backend[43832] pg_regress/timestamp LOG: connection ready: setup total=4.397 ms, fork=0.659 ms, authentication=0.109 ms 2025-11-30 18:45:02.211 UTC client backend[43832] pg_regress/timestamp LOG: disconnection: session time: 0:00:00.023 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.223 UTC client backend[43819] pg_regress/citext ERROR: column "chr" is of type "char" but expression is of type citext at character 44 2025-11-30 18:45:02.223 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.223 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (chr) VALUES ('f'::citext); 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext ERROR: column "bytea" is of type bytea but expression is of type text at character 44 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (bytea) VALUES ('foo'::text); 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext ERROR: column "bytea" is of type bytea but expression is of type citext at character 44 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (bytea) VALUES ('foo'::citext); 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext ERROR: column "boolean" is of type boolean but expression is of type text at character 44 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.225 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (boolean) VALUES ('t'::text); 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext ERROR: column "boolean" is of type boolean but expression is of type citext at character 44 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (boolean) VALUES ('t'::citext); 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext ERROR: column "float8" is of type double precision but expression is of type text at character 44 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (float8) VALUES ('12.42'::text); 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext ERROR: column "float8" is of type double precision but expression is of type citext at character 44 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.226 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (float8) VALUES ('12.42'::citext); 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext ERROR: column "float4" is of type real but expression is of type text at character 44 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (float4) VALUES ('12.42'::text); 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext ERROR: column "float4" is of type real but expression is of type citext at character 44 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (float4) VALUES ('12.42'::citext); 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext ERROR: column "numeric" is of type numeric but expression is of type text at character 44 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (numeric) VALUES ('12.42'::text); 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext ERROR: column "numeric" is of type numeric but expression is of type citext at character 44 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.227 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (numeric) VALUES ('12.42'::citext); 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext ERROR: column "int8" is of type bigint but expression is of type text at character 44 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (int8) VALUES ('12'::text); 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext ERROR: column "int8" is of type bigint but expression is of type citext at character 44 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (int8) VALUES ('12'::citext); 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext ERROR: column "int4" is of type integer but expression is of type text at character 44 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.228 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (int4) VALUES ('12'::text); 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext ERROR: column "int4" is of type integer but expression is of type citext at character 44 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (int4) VALUES ('12'::citext); 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext ERROR: column "int2" is of type smallint but expression is of type text at character 44 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (int2) VALUES ('12'::text); 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext ERROR: column "int2" is of type smallint but expression is of type citext at character 44 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.229 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (int2) VALUES ('12'::citext); 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext ERROR: column "cidr" is of type cidr but expression is of type text at character 44 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (cidr) VALUES ('192.168.100.128/25'::text); 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext ERROR: column "cidr" is of type cidr but expression is of type citext at character 44 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (cidr) VALUES ('192.168.100.128/25'::citext); 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext ERROR: column "inet" is of type inet but expression is of type text at character 44 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.230 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (inet) VALUES ('192.168.100.128'::text); 2025-11-30 18:45:02.232 UTC client backend[43819] pg_regress/citext ERROR: column "inet" is of type inet but expression is of type citext at character 44 2025-11-30 18:45:02.232 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.232 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (inet) VALUES ('192.168.100.128'::citext); 2025-11-30 18:45:02.232 UTC client backend[43819] pg_regress/citext ERROR: column "macaddr" is of type macaddr but expression is of type text at character 44 2025-11-30 18:45:02.232 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.232 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (macaddr) VALUES ('08:00:2b:01:02:03'::text); 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext ERROR: column "macaddr" is of type macaddr but expression is of type citext at character 44 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (macaddr) VALUES ('08:00:2b:01:02:03'::citext); 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext ERROR: column "money" is of type money but expression is of type text at character 44 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (money) VALUES ('12'::text); 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext ERROR: column "money" is of type money but expression is of type citext at character 44 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.233 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (money) VALUES ('12'::citext); 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext ERROR: column "timestamp" is of type timestamp without time zone but expression is of type text at character 44 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (timestamp) VALUES ('1999-01-08 04:05:06'::text); 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext ERROR: column "timestamp" is of type timestamp without time zone but expression is of type citext at character 44 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (timestamp) VALUES ('1999-01-08 04:05:06'::citext); 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext ERROR: column "timestamptz" is of type timestamp with time zone but expression is of type text at character 44 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.234 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (timestamptz) VALUES ('1999-01-08 04:05:06'::text); 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext ERROR: column "timestamptz" is of type timestamp with time zone but expression is of type citext at character 44 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (timestamptz) VALUES ('1999-01-08 04:05:06'::citext); 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext ERROR: column "interval" is of type interval but expression is of type text at character 44 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (interval) VALUES ('1 hour'::text); 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext ERROR: column "interval" is of type interval but expression is of type citext at character 44 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (interval) VALUES ('1 hour'::citext); 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext ERROR: column "date" is of type date but expression is of type text at character 44 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.235 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (date) VALUES ('1999-01-08'::text); 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext ERROR: column "date" is of type date but expression is of type citext at character 44 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (date) VALUES ('1999-01-08'::citext); 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext ERROR: column "time" is of type time without time zone but expression is of type text at character 44 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (time) VALUES ('04:05:06'::text); 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext ERROR: column "time" is of type time without time zone but expression is of type citext at character 44 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.236 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (time) VALUES ('04:05:06'::citext); 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext ERROR: column "timetz" is of type time with time zone but expression is of type text at character 44 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (timetz) VALUES ('04:05:06'::text); 2025-11-30 18:45:02.237 UTC unrecognized[43836] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext ERROR: column "timetz" is of type time with time zone but expression is of type citext at character 44 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (timetz) VALUES ('04:05:06'::citext); 2025-11-30 18:45:02.237 UTC client backend[43836] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.237 UTC client backend[43836] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/timestamptz 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext ERROR: column "point" is of type point but expression is of type text at character 44 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.237 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (point) VALUES ('( 1 , 1)'::text); 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext ERROR: column "point" is of type point but expression is of type citext at character 44 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (point) VALUES ('( 1 , 1)'::citext); 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext ERROR: column "lseg" is of type lseg but expression is of type text at character 44 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (lseg) VALUES ('( 1 , 1 ) , ( 2 , 2 )'::text); 2025-11-30 18:45:02.238 UTC client backend[43836] pg_regress/timestamptz LOG: connection ready: setup total=1.876 ms, fork=0.407 ms, authentication=0.102 ms 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext ERROR: column "lseg" is of type lseg but expression is of type citext at character 44 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.238 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (lseg) VALUES ('( 1 , 1 ) , ( 2 , 2 )'::citext); 2025-11-30 18:45:02.239 UTC client backend[43819] pg_regress/citext ERROR: column "box" is of type box but expression is of type text at character 44 2025-11-30 18:45:02.239 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.239 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (box) VALUES ('(0,0),(1,1)'::text); 2025-11-30 18:45:02.240 UTC client backend[43819] pg_regress/citext ERROR: column "box" is of type box but expression is of type citext at character 44 2025-11-30 18:45:02.240 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.240 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (box) VALUES ('(0,0),(1,1)'::citext); 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has not been entered 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_without_enter", line 2, in plpy.subtransaction().__exit__(None, None, None) PL/Python function "subtransaction_exit_without_enter" 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_without_enter(); 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_without_exit" 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_exit_twice" 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has not been entered 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_twice", line 3, in plpy.subtransaction().__exit__(None, None, None) PL/Python function "subtransaction_exit_twice" 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_twice(); 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_twice" 2025-11-30 18:45:02.241 UTC client backend[43819] pg_regress/citext ERROR: column "path" is of type path but expression is of type text at character 44 2025-11-30 18:45:02.241 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.241 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (path) VALUES ('((0,0),(1,1),(2,0))'::text); 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_twice" 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been exited 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_same_subtransaction_twice", line 5, in s.__exit__(None, None, None) PL/Python function "subtransaction_exit_same_subtransaction_twice" 2025-11-30 18:45:02.241 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_same_subtransaction_twice(); 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_enter_same_subtransaction_twice" 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been entered 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_enter_same_subtransaction_twice", line 4, in s.__enter__() PL/Python function "subtransaction_enter_same_subtransaction_twice" 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_enter_same_subtransaction_twice(); 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been entered 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_enter_subtransaction_in_with", line 3, in s.__enter__() PL/Python function "subtransaction_enter_subtransaction_in_with" 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_enter_subtransaction_in_with(); 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: this subtransaction has already been exited 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "subtransaction_exit_subtransaction_in_with", line 6, in raise ValueError(e) PL/Python function "subtransaction_exit_subtransaction_in_with" 2025-11-30 18:45:02.242 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT subtransaction_exit_subtransaction_in_with(); 2025-11-30 18:45:02.243 UTC client backend[43826] pg_regress/plpython_subtransaction WARNING: Caught a SPI error from an explicit subtransaction 2025-11-30 18:45:02.243 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_mix_explicit_and_implicit" 2025-11-30 18:45:02.243 UTC client backend[43826] pg_regress/plpython_subtransaction WARNING: Caught a SPI error 2025-11-30 18:45:02.243 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: PL/Python function "subtransaction_mix_explicit_and_implicit" 2025-11-30 18:45:02.244 UTC client backend[43819] pg_regress/citext ERROR: column "path" is of type path but expression is of type citext at character 44 2025-11-30 18:45:02.244 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.244 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (path) VALUES ('((0,0),(1,1),(2,0))'::citext); 2025-11-30 18:45:02.244 UTC client backend[43819] pg_regress/citext ERROR: column "polygon" is of type polygon but expression is of type text at character 44 2025-11-30 18:45:02.244 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.244 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (polygon) VALUES ('((0,0),(1,1))'::text); 2025-11-30 18:45:02.248 UTC client backend[43836] pg_regress/timestamptz LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.251 UTC unrecognized[43840] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.251 UTC client backend[43840] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.251 UTC client backend[43840] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/float8 2025-11-30 18:45:02.252 UTC client backend[43840] pg_regress/float8 LOG: connection ready: setup total=2.615 ms, fork=1.133 ms, authentication=0.103 ms 2025-11-30 18:45:02.253 UTC client backend[43819] pg_regress/citext ERROR: column "polygon" is of type polygon but expression is of type citext at character 44 2025-11-30 18:45:02.253 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.253 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (polygon) VALUES ('((0,0),(1,1))'::citext); 2025-11-30 18:45:02.253 UTC client backend[43819] pg_regress/citext ERROR: column "circle" is of type circle but expression is of type text at character 44 2025-11-30 18:45:02.253 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.253 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (circle) VALUES ('((0,0),2)'::text); 2025-11-30 18:45:02.255 UTC client backend[43819] pg_regress/citext ERROR: column "circle" is of type circle but expression is of type citext at character 44 2025-11-30 18:45:02.255 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.255 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (circle) VALUES ('((0,0),2)'::citext); 2025-11-30 18:45:02.256 UTC client backend[43819] pg_regress/citext ERROR: column "bit" is of type bit but expression is of type text at character 44 2025-11-30 18:45:02.256 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.256 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (bit) VALUES ('101'::text); 2025-11-30 18:45:02.257 UTC client backend[43819] pg_regress/citext ERROR: column "bit" is of type bit but expression is of type citext at character 44 2025-11-30 18:45:02.257 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.257 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (bit) VALUES ('101'::citext); 2025-11-30 18:45:02.257 UTC client backend[43819] pg_regress/citext ERROR: column "bitv" is of type bit varying but expression is of type text at character 44 2025-11-30 18:45:02.257 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.257 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (bitv) VALUES ('101'::text); 2025-11-30 18:45:02.264 UTC client backend[43840] pg_regress/float8 LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.265 UTC client backend[43819] pg_regress/citext ERROR: column "bitv" is of type bit varying but expression is of type citext at character 44 2025-11-30 18:45:02.265 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.265 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (bitv) VALUES ('101'::citext); 2025-11-30 18:45:02.266 UTC client backend[43819] pg_regress/citext ERROR: column "tsvector" is of type tsvector but expression is of type text at character 44 2025-11-30 18:45:02.266 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.266 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (tsvector) VALUES ('the fat cat'::text); 2025-11-30 18:45:02.267 UTC client backend[43819] pg_regress/citext ERROR: column "tsvector" is of type tsvector but expression is of type citext at character 44 2025-11-30 18:45:02.267 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.267 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (tsvector) VALUES ('the fat cat'::citext); 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext ERROR: column "tsquery" is of type tsquery but expression is of type text at character 44 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (tsquery) VALUES ('fat & rat'::text); 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext ERROR: column "tsquery" is of type tsquery but expression is of type citext at character 44 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (tsquery) VALUES ('fat & rat'::citext); 2025-11-30 18:45:02.269 UTC unrecognized[43843] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext ERROR: column "uuid" is of type uuid but expression is of type text at character 44 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.269 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (uuid) VALUES ('a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'::text); 2025-11-30 18:45:02.270 UTC client backend[43843] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.270 UTC client backend[43843] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/time 2025-11-30 18:45:02.270 UTC client backend[43819] pg_regress/citext ERROR: column "uuid" is of type uuid but expression is of type citext at character 44 2025-11-30 18:45:02.270 UTC client backend[43819] pg_regress/citext HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:02.270 UTC client backend[43819] pg_regress/citext STATEMENT: INSERT INTO caster (uuid) VALUES ('a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'::citext); 2025-11-30 18:45:02.271 UTC client backend[43843] pg_regress/time LOG: connection ready: setup total=2.303 ms, fork=0.810 ms, authentication=0.108 ms 2025-11-30 18:45:02.277 UTC client backend[43843] pg_regress/time LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.284 UTC client backend[43819] pg_regress/citext ERROR: regexp_match() does not support the "global" option 2025-11-30 18:45:02.284 UTC client backend[43819] pg_regress/citext HINT: Use the regexp_matches function instead. 2025-11-30 18:45:02.284 UTC client backend[43819] pg_regress/citext CONTEXT: SQL function "regexp_match" statement 1 2025-11-30 18:45:02.284 UTC client backend[43819] pg_regress/citext STATEMENT: SELECT regexp_match('foobarbequebazmorebarbequetoo'::citext, '(BAR)(BEQUE)'::citext, 'g') AS "error"; 2025-11-30 18:45:02.288 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: iterating a cursor in an aborted subtransaction 2025-11-30 18:45:02.288 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "cursor_aborted_subxact", line 8, in fetched = cur.fetch(10) PL/Python function "cursor_aborted_subxact" 2025-11-30 18:45:02.288 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT cursor_aborted_subxact(); 2025-11-30 18:45:02.290 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: iterating a cursor in an aborted subtransaction 2025-11-30 18:45:02.290 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "cursor_plan_aborted_subxact", line 10, in fetched = cur.fetch(5) PL/Python function "cursor_plan_aborted_subxact" 2025-11-30 18:45:02.290 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT cursor_plan_aborted_subxact(); 2025-11-30 18:45:02.294 UTC client backend[43826] pg_regress/plpython_subtransaction ERROR: ValueError: closing a cursor in an aborted subtransaction 2025-11-30 18:45:02.294 UTC client backend[43826] pg_regress/plpython_subtransaction CONTEXT: Traceback (most recent call last): PL/Python function "cursor_close_aborted_subxact", line 7, in cur.close() PL/Python function "cursor_close_aborted_subxact" 2025-11-30 18:45:02.294 UTC client backend[43826] pg_regress/plpython_subtransaction STATEMENT: SELECT cursor_close_aborted_subxact(); 2025-11-30 18:45:02.294 UTC client backend[43826] pg_regress/plpython_subtransaction LOG: disconnection: session time: 0:00:00.126 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:02.295 UTC unrecognized[43850] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.295 UTC client backend[43850] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.295 UTC client backend[43850] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/timetz 2025-11-30 18:45:02.296 UTC client backend[43850] pg_regress/timetz LOG: connection ready: setup total=1.944 ms, fork=0.488 ms, authentication=0.105 ms 2025-11-30 18:45:02.305 UTC client backend[43850] pg_regress/timetz LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.306 UTC unrecognized[43874] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.317 UTC client backend[43874] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.318 UTC client backend[43874] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/point 2025-11-30 18:45:02.319 UTC client backend[43874] pg_regress/point LOG: connection ready: setup total=14.277 ms, fork=1.772 ms, authentication=0.140 ms 2025-11-30 18:45:02.323 UTC unrecognized[43876] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.323 UTC client backend[43876] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.323 UTC client backend[43876] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/path 2025-11-30 18:45:02.324 UTC unrecognized[43887] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.324 UTC client backend[43876] pg_regress/path LOG: connection ready: setup total=15.079 ms, fork=11.273 ms, authentication=0.132 ms 2025-11-30 18:45:02.325 UTC client backend[43887] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.325 UTC client backend[43887] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timestamptz 2025-11-30 18:45:02.326 UTC client backend[43887] pg_regress/timestamptz LOG: connection ready: setup total=5.515 ms, fork=3.564 ms, authentication=0.114 ms 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point ERROR: invalid input syntax for type point: "asdfasdf" at character 35 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('asdfasdf'); 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point ERROR: invalid input syntax for type point: "(10.0 10.0)" at character 35 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0 10.0)'); 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point ERROR: invalid input syntax for type point: "(10.0, 10.0) x" at character 35 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 10.0) x'); 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point ERROR: invalid input syntax for type point: "(10.0,10.0" at character 35 2025-11-30 18:45:02.328 UTC client backend[43874] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0,10.0'); 2025-11-30 18:45:02.329 UTC client backend[43876] pg_regress/path ERROR: invalid input syntax for type path: "[]" at character 30 2025-11-30 18:45:02.329 UTC client backend[43876] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[]'); 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path ERROR: invalid input syntax for type path: "[(,2),(3,4)]" at character 30 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(,2),(3,4)]'); 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path ERROR: invalid input syntax for type path: "[(1,2),(3,4)" at character 30 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(1,2),(3,4)'); 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path ERROR: invalid input syntax for type path: "(1,2,3,4" at character 30 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2,3,4'); 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path ERROR: invalid input syntax for type path: "(1,2),(3,4)]" at character 30 2025-11-30 18:45:02.330 UTC client backend[43876] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2),(3,4)]'); 2025-11-30 18:45:02.331 UTC client backend[43874] pg_regress/point ERROR: "1e+500" is out of range for type double precision at character 35 2025-11-30 18:45:02.331 UTC client backend[43874] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 1e+500)'); 2025-11-30 18:45:02.331 UTC client backend[43876] pg_regress/path LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression host=[local] 2025-11-30 18:45:02.333 UTC unrecognized[43885] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.333 UTC unrecognized[43884] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.333 UTC unrecognized[43881] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.334 UTC client backend[43885] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.334 UTC client backend[43885] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/strings 2025-11-30 18:45:02.334 UTC unrecognized[43895] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.334 UTC unrecognized[43890] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.334 UTC unrecognized[43880] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.334 UTC unrecognized[43891] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.334 UTC unrecognized[43893] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.334 UTC unrecognized[43883] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.335 UTC client backend[43885] pg_regress/strings LOG: connection ready: setup total=17.385 ms, fork=5.455 ms, authentication=0.128 ms 2025-11-30 18:45:02.335 UTC unrecognized[43879] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.335 UTC client backend[43884] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.335 UTC client backend[43884] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/line 2025-11-30 18:45:02.335 UTC client backend[43881] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.335 UTC client backend[43881] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/multirangetypes 2025-11-30 18:45:02.335 UTC client backend[43879] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.335 UTC client backend[43879] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/date 2025-11-30 18:45:02.336 UTC client backend[43884] pg_regress/line LOG: connection ready: setup total=18.877 ms, fork=5.619 ms, authentication=1.429 ms 2025-11-30 18:45:02.336 UTC client backend[43881] pg_regress/multirangetypes LOG: connection ready: setup total=19.710 ms, fork=4.709 ms, authentication=1.474 ms 2025-11-30 18:45:02.336 UTC client backend[43879] pg_regress/date LOG: connection ready: setup total=20.398 ms, fork=7.308 ms, authentication=0.107 ms 2025-11-30 18:45:02.336 UTC client backend[43880] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.336 UTC client backend[43880] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/cash 2025-11-30 18:45:02.336 UTC client backend[43890] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.336 UTC client backend[43890] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/interval 2025-11-30 18:45:02.336 UTC client backend[43895] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.336 UTC client backend[43895] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_transaction 2025-11-30 18:45:02.337 UTC client backend[43883] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.337 UTC client backend[43883] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timetz 2025-11-30 18:45:02.337 UTC client backend[43880] pg_regress/cash LOG: connection ready: setup total=21.160 ms, fork=2.847 ms, authentication=1.849 ms 2025-11-30 18:45:02.337 UTC client backend[43891] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.337 UTC client backend[43891] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/md5 2025-11-30 18:45:02.338 UTC client backend[43883] pg_regress/timetz LOG: connection ready: setup total=21.232 ms, fork=6.386 ms, authentication=2.321 ms 2025-11-30 18:45:02.338 UTC client backend[43893] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.338 UTC client backend[43893] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/inet 2025-11-30 18:45:02.338 UTC client backend[43891] pg_regress/md5 LOG: connection ready: setup total=13.388 ms, fork=3.411 ms, authentication=2.958 ms 2025-11-30 18:45:02.339 UTC unrecognized[43878] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.339 UTC client backend[43893] pg_regress/inet LOG: connection ready: setup total=13.617 ms, fork=3.019 ms, authentication=3.493 ms 2025-11-30 18:45:02.339 UTC unrecognized[43897] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.339 UTC client backend[43878] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.339 UTC client backend[43878] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/box 2025-11-30 18:45:02.339 UTC client backend[43897] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.339 UTC client backend[43897] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/date 2025-11-30 18:45:02.340 UTC client backend[43878] pg_regress/box LOG: connection ready: setup total=27.557 ms, fork=8.113 ms, authentication=0.110 ms 2025-11-30 18:45:02.340 UTC client backend[43897] pg_regress/date LOG: connection ready: setup total=8.681 ms, fork=3.290 ms, authentication=0.109 ms 2025-11-30 18:45:02.341 UTC unrecognized[43889] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.341 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "" at character 8 2025-11-30 18:45:02.341 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Missing left brace. 2025-11-30 18:45:02.341 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select ''::textmultirange; 2025-11-30 18:45:02.341 UTC unrecognized[43886] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.341 UTC unrecognized[43888] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.341 UTC client backend[43889] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.341 UTC client backend[43889] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timestamp 2025-11-30 18:45:02.341 UTC client backend[43886] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.341 UTC client backend[43886] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/macaddr8 2025-11-30 18:45:02.341 UTC client backend[43888] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.341 UTC client backend[43888] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/time 2025-11-30 18:45:02.342 UTC client backend[43889] pg_regress/timestamp LOG: connection ready: setup total=21.101 ms, fork=3.183 ms, authentication=0.096 ms 2025-11-30 18:45:02.342 UTC unrecognized[43894] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.342 UTC client backend[43886] pg_regress/macaddr8 LOG: connection ready: setup total=22.163 ms, fork=12.953 ms, authentication=0.101 ms 2025-11-30 18:45:02.342 UTC client backend[43888] pg_regress/time LOG: connection ready: setup total=21.616 ms, fork=3.360 ms, authentication=0.102 ms 2025-11-30 18:45:02.342 UTC unrecognized[43877] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.342 UTC client backend[43894] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.342 UTC client backend[43894] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/numerology 2025-11-30 18:45:02.343 UTC client backend[43890] pg_regress/interval LOG: connection ready: setup total=20.771 ms, fork=2.203 ms, authentication=0.104 ms 2025-11-30 18:45:02.343 UTC client backend[43877] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.343 UTC client backend[43877] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/lseg 2025-11-30 18:45:02.343 UTC client backend[43894] pg_regress/numerology LOG: connection ready: setup total=17.697 ms, fork=1.936 ms, authentication=0.098 ms 2025-11-30 18:45:02.343 UTC unrecognized[43892] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.343 UTC client backend[43877] pg_regress/lseg LOG: connection ready: setup total=31.282 ms, fork=8.355 ms, authentication=0.097 ms 2025-11-30 18:45:02.344 UTC client backend[43892] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.344 UTC client backend[43892] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/macaddr 2025-11-30 18:45:02.344 UTC client backend[43893] pg_regress/inet ERROR: table "inet_tbl" does not exist 2025-11-30 18:45:02.344 UTC client backend[43893] pg_regress/inet STATEMENT: DROP TABLE INET_TBL; 2025-11-30 18:45:02.344 UTC client backend[43885] pg_regress/strings ERROR: syntax error at or near "' - third line'" at character 75 2025-11-30 18:45:02.344 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT 'first line' ' - next line' /* this comment is not allowed here */ ' - third line' AS "Illegal comment within continuation"; 2025-11-30 18:45:02.345 UTC client backend[43892] pg_regress/macaddr LOG: connection ready: setup total=19.593 ms, fork=3.219 ms, authentication=0.093 ms 2025-11-30 18:45:02.345 UTC unrecognized[43882] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.345 UTC client backend[43882] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.345 UTC client backend[43882] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/polygon 2025-11-30 18:45:02.346 UTC client backend[43882] pg_regress/polygon LOG: connection ready: setup total=29.597 ms, fork=6.561 ms, authentication=0.093 ms 2025-11-30 18:45:02.347 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,}" at character 8 2025-11-30 18:45:02.347 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-30 18:45:02.347 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{,}'::textmultirange; 2025-11-30 18:45:02.350 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(,)}." at character 8 2025-11-30 18:45:02.350 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Junk after closing right brace. 2025-11-30 18:45:02.350 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{(,)}.'::textmultirange; 2025-11-30 18:45:02.353 UTC unrecognized[43898] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.356 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "{}" at character 30 2025-11-30 18:45:02.356 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{}'); 2025-11-30 18:45:02.356 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "{0" at character 30 2025-11-30 18:45:02.356 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0'); 2025-11-30 18:45:02.357 UTC client backend[43898] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.357 UTC client backend[43898] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/circle 2025-11-30 18:45:02.358 UTC client backend[43883] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 America/New_York" at character 32 2025-11-30 18:45:02.358 UTC client backend[43883] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York'); 2025-11-30 18:45:02.358 UTC client backend[43898] pg_regress/circle LOG: connection ready: setup total=17.719 ms, fork=7.517 ms, authentication=0.105 ms 2025-11-30 18:45:02.359 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "{0,0}" at character 30 2025-11-30 18:45:02.359 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0}'); 2025-11-30 18:45:02.359 UTC client backend[43878] pg_regress/box ERROR: invalid input syntax for type box: "(2.3, 4.5)" at character 34 2025-11-30 18:45:02.359 UTC client backend[43878] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(2.3, 4.5)'); 2025-11-30 18:45:02.359 UTC client backend[43883] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 m2" at character 32 2025-11-30 18:45:02.359 UTC client backend[43883] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2'); 2025-11-30 18:45:02.359 UTC client backend[43895] pg_regress/plpython_transaction LOG: connection ready: setup total=33.511 ms, fork=1.706 ms, authentication=2.277 ms 2025-11-30 18:45:02.360 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1" at character 30 2025-11-30 18:45:02.360 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1'); 2025-11-30 18:45:02.361 UTC client backend[43883] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 MSK m2" at character 32 2025-11-30 18:45:02.361 UTC client backend[43883] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2'); 2025-11-30 18:45:02.361 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,c),}" at character 8 2025-11-30 18:45:02.361 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-30 18:45:02.361 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{[a,c),}'::textmultirange; 2025-11-30 18:45:02.361 UTC client backend[43878] pg_regress/box ERROR: invalid input syntax for type box: "[1, 2, 3, 4)" at character 34 2025-11-30 18:45:02.361 UTC client backend[43878] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('[1, 2, 3, 4)'); 2025-11-30 18:45:02.361 UTC client backend[43884] pg_regress/line ERROR: invalid line specification: A and B cannot both be zero at character 30 2025-11-30 18:45:02.361 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1}'); 2025-11-30 18:45:02.362 UTC client backend[43892] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "0800:2b01:0203" at character 37 2025-11-30 18:45:02.362 UTC client backend[43892] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (8, '0800:2b01:0203'); 2025-11-30 18:45:02.362 UTC client backend[43882] pg_regress/polygon ERROR: invalid input syntax for type polygon: "0.0" at character 37 2025-11-30 18:45:02.362 UTC client backend[43882] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('0.0'); 2025-11-30 18:45:02.362 UTC client backend[43878] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4]" at character 34 2025-11-30 18:45:02.362 UTC client backend[43878] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4]'); 2025-11-30 18:45:02.362 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,[a,c)}" at character 8 2025-11-30 18:45:02.362 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-30 18:45:02.362 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{,[a,c)}'::textmultirange; 2025-11-30 18:45:02.362 UTC client backend[43892] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "not even close" at character 37 2025-11-30 18:45:02.362 UTC client backend[43892] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (9, 'not even close'); 2025-11-30 18:45:02.363 UTC client backend[43882] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0.0 0.0" at character 37 2025-11-30 18:45:02.363 UTC client backend[43882] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0.0 0.0'); 2025-11-30 18:45:02.363 UTC client backend[43878] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4) x" at character 34 2025-11-30 18:45:02.363 UTC client backend[43878] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4) x'); 2025-11-30 18:45:02.363 UTC client backend[43882] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2)" at character 37 2025-11-30 18:45:02.363 UTC client backend[43882] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2)'); 2025-11-30 18:45:02.363 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1} x" at character 30 2025-11-30 18:45:02.363 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1} x'); 2025-11-30 18:45:02.364 UTC client backend[43878] pg_regress/box ERROR: invalid input syntax for type box: "asdfasdf(ad" at character 34 2025-11-30 18:45:02.364 UTC client backend[43878] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('asdfasdf(ad'); 2025-11-30 18:45:02.364 UTC client backend[43882] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2,3" at character 37 2025-11-30 18:45:02.364 UTC client backend[43882] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2,3'); 2025-11-30 18:45:02.364 UTC client backend[43898] pg_regress/circle ERROR: invalid input syntax for type circle: "<(-100,0),-100>" at character 32 2025-11-30 18:45:02.364 UTC client backend[43898] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(-100,0),-100>'); 2025-11-30 18:45:02.365 UTC client backend[43893] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 37 2025-11-30 18:45:02.365 UTC client backend[43893] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-11-30 18:45:02.365 UTC client backend[43893] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226'); 2025-11-30 18:45:02.365 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "(3asdf,2 ,3,4r2)" at character 30 2025-11-30 18:45:02.365 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2025-11-30 18:45:02.365 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{-[a,z)}" at character 8 2025-11-30 18:45:02.365 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-30 18:45:02.365 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{-[a,z)}'::textmultirange; 2025-11-30 18:45:02.366 UTC client backend[43882] pg_regress/polygon ERROR: invalid input syntax for type polygon: "asdf" at character 37 2025-11-30 18:45:02.366 UTC client backend[43882] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('asdf'); 2025-11-30 18:45:02.366 UTC client backend[43898] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10" at character 32 2025-11-30 18:45:02.366 UTC client backend[43898] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10'); 2025-11-30 18:45:02.368 UTC client backend[43893] pg_regress/inet ERROR: invalid input syntax for type cidr: "1234::1234::1234" at character 37 2025-11-30 18:45:02.368 UTC client backend[43893] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4'); 2025-11-30 18:45:02.368 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "[1,2,3, 4" at character 30 2025-11-30 18:45:02.368 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[1,2,3, 4'); 2025-11-30 18:45:02.369 UTC client backend[43898] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10> x" at character 32 2025-11-30 18:45:02.369 UTC client backend[43898] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10> x'); 2025-11-30 18:45:02.370 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "badly formatted interval" at character 39 2025-11-30 18:45:02.370 UTC client backend[43890] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('badly formatted interval'); 2025-11-30 18:45:02.371 UTC client backend[43893] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 42 2025-11-30 18:45:02.371 UTC client backend[43893] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-11-30 18:45:02.371 UTC client backend[43893] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('192.168.1.2/30'), '192.168.1.226'); 2025-11-30 18:45:02.371 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "[(,2),(3,4)]" at character 30 2025-11-30 18:45:02.371 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(,2),(3,4)]'); 2025-11-30 18:45:02.371 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,z) - }" at character 8 2025-11-30 18:45:02.371 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-11-30 18:45:02.371 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{[a,z) - }'::textmultirange; 2025-11-30 18:45:02.372 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "@ 30 eons ago" at character 39 2025-11-30 18:45:02.372 UTC client backend[43890] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('@ 30 eons ago'); 2025-11-30 18:45:02.372 UTC client backend[43883] pg_regress/timetz ERROR: date/time field value out of range: "24:00:00.01 PDT" at character 8 2025-11-30 18:45:02.372 UTC client backend[43883] pg_regress/timetz STATEMENT: SELECT '24:00:00.01 PDT'::timetz; 2025-11-30 18:45:02.372 UTC client backend[43893] pg_regress/inet ERROR: invalid cidr value: "ffff:ffff:ffff:ffff::/24" at character 42 2025-11-30 18:45:02.372 UTC client backend[43893] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-11-30 18:45:02.372 UTC client backend[43893] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('ffff:ffff:ffff:ffff::/24'), '::192.168.1.226'); 2025-11-30 18:45:02.372 UTC client backend[43884] pg_regress/line ERROR: invalid input syntax for type line: "[(1,2),(3,4)" at character 30 2025-11-30 18:45:02.372 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(3,4)'); 2025-11-30 18:45:02.374 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(",a)}" at character 8 2025-11-30 18:45:02.374 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Unexpected end of input. 2025-11-30 18:45:02.374 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{(",a)}'::textmultirange; 2025-11-30 18:45:02.375 UTC client backend[43883] pg_regress/timetz ERROR: date/time field value out of range: "23:59:60.01 PDT" at character 8 2025-11-30 18:45:02.375 UTC client backend[43883] pg_regress/timetz STATEMENT: SELECT '23:59:60.01 PDT'::timetz; 2025-11-30 18:45:02.375 UTC client backend[43891] pg_regress/md5 LOG: disconnection: session time: 0:00:00.047 user=postgres database=regression host=[local] 2025-11-30 18:45:02.375 UTC client backend[43884] pg_regress/line ERROR: invalid line specification: must be two distinct points at character 30 2025-11-30 18:45:02.375 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(1,2)]'); 2025-11-30 18:45:02.377 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed range literal: "(,,a)" at character 8 2025-11-30 18:45:02.377 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Too many commas. 2025-11-30 18:45:02.377 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{(,,a)}'::textmultirange; 2025-11-30 18:45:02.377 UTC client backend[43883] pg_regress/timetz ERROR: date/time field value out of range: "24:01:00 PDT" at character 8 2025-11-30 18:45:02.377 UTC client backend[43883] pg_regress/timetz STATEMENT: SELECT '24:01:00 PDT'::timetz; 2025-11-30 18:45:02.378 UTC client backend[43884] pg_regress/line ERROR: invalid line specification: must be two distinct points 2025-11-30 18:45:02.378 UTC client backend[43884] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES (line(point '(1,0)', point '(1,0)')); 2025-11-30 18:45:02.379 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed range literal: "()" at character 8 2025-11-30 18:45:02.379 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2025-11-30 18:45:02.379 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{(),a)}'::textmultirange; 2025-11-30 18:45:02.379 UTC client backend[43883] pg_regress/timetz ERROR: date/time field value out of range: "25:00:00 PDT" at character 8 2025-11-30 18:45:02.379 UTC client backend[43883] pg_regress/timetz STATEMENT: SELECT '25:00:00 PDT'::timetz; 2025-11-30 18:45:02.380 UTC client backend[43880] pg_regress/cash LOG: disconnection: session time: 0:00:00.060 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.380 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,))}" at character 8 2025-11-30 18:45:02.380 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-11-30 18:45:02.380 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{(a,))}'::textmultirange; 2025-11-30 18:45:02.384 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed range literal: "(]" at character 8 2025-11-30 18:45:02.384 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2025-11-30 18:45:02.384 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{(],a)}'::textmultirange; 2025-11-30 18:45:02.384 UTC client backend[43881] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,])}" at character 8 2025-11-30 18:45:02.384 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-11-30 18:45:02.384 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{(a,])}'::textmultirange; 2025-11-30 18:45:02.385 UTC client backend[43881] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-11-30 18:45:02.385 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{[z,a]}'::textmultirange; 2025-11-30 18:45:02.387 UTC client backend[43883] pg_regress/timetz ERROR: operator does not exist: time with time zone + time with time zone at character 11 2025-11-30 18:45:02.387 UTC client backend[43883] pg_regress/timetz DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:02.387 UTC client backend[43883] pg_regress/timetz HINT: You might need to add explicit type casts. 2025-11-30 18:45:02.387 UTC client backend[43883] pg_regress/timetz STATEMENT: SELECT f1 + time with time zone '00:01' AS "Illegal" FROM TIMETZ_TBL; 2025-11-30 18:45:02.389 UTC client backend[43898] pg_regress/circle ERROR: invalid input syntax for type circle: "1abc,3,5" at character 32 2025-11-30 18:45:02.389 UTC client backend[43898] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('1abc,3,5'); 2025-11-30 18:45:02.389 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.389 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT -('-2147483648 months'::interval); 2025-11-30 18:45:02.391 UTC client backend[43884] pg_regress/line LOG: disconnection: session time: 0:00:00.068 user=postgres database=regression host=[local] 2025-11-30 18:45:02.392 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.392 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT -('-2147483648 days'::interval); 2025-11-30 18:45:02.392 UTC client backend[43883] pg_regress/timetz ERROR: unit "day" not supported for type time with time zone 2025-11-30 18:45:02.392 UTC client backend[43883] pg_regress/timetz STATEMENT: SELECT EXTRACT(DAY FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2025-11-30 18:45:02.393 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.393 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT -('-9223372036854775808 us'::interval); 2025-11-30 18:45:02.393 UTC client backend[43883] pg_regress/timetz ERROR: unit "fortnight" not recognized for type time with time zone 2025-11-30 18:45:02.393 UTC client backend[43883] pg_regress/timetz STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2025-11-30 18:45:02.393 UTC client backend[43898] pg_regress/circle ERROR: invalid input syntax for type circle: "(3,(1,2),3)" at character 32 2025-11-30 18:45:02.393 UTC client backend[43898] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('(3,(1,2),3)'); 2025-11-30 18:45:02.394 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.394 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT -('-2147483647 months -2147483647 days -9223372036854775807 us'::interval); 2025-11-30 18:45:02.396 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "123abc" at character 8 2025-11-30 18:45:02.396 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 123abc; 2025-11-30 18:45:02.398 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape at character 18 2025-11-30 18:45:02.398 UTC client backend[43885] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2025-11-30 18:45:02.398 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2025-11-30 18:45:02.398 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0o" at character 8 2025-11-30 18:45:02.398 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0x0o; 2025-11-30 18:45:02.401 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.a" at character 8 2025-11-30 18:45:02.401 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0.a; 2025-11-30 18:45:02.403 UTC client backend[43883] pg_regress/timetz LOG: disconnection: session time: 0:00:00.079 user=postgres database=regression host=[local] 2025-11-30 18:45:02.404 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape at character 18 2025-11-30 18:45:02.404 UTC client backend[43885] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2025-11-30 18:45:02.404 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 42 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483648 days'); 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 42 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483649 days'); 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval ERROR: interval out of range at character 42 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483647 years'); 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval ERROR: interval out of range at character 42 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483648 years'); 2025-11-30 18:45:02.405 UTC client backend[43898] pg_regress/circle LOG: disconnection: session time: 0:00:00.057 user=postgres database=regression host=[local] 2025-11-30 18:45:02.405 UTC client backend[43888] pg_regress/time ERROR: invalid input syntax for type time: "15:36:39 America/New_York" at character 30 2025-11-30 18:45:02.405 UTC client backend[43888] pg_regress/time STATEMENT: INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York'); 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.405 UTC client backend[43890] pg_regress/interval STATEMENT: select extract(epoch from '256 microseconds'::interval * (2^55)::float8); 2025-11-30 18:45:02.406 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0a" at character 8 2025-11-30 18:45:02.406 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0.0a; 2025-11-30 18:45:02.407 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near ".0a" at character 8 2025-11-30 18:45:02.407 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT .0a; 2025-11-30 18:45:02.407 UTC client backend[43874] pg_regress/point LOG: disconnection: session time: 0:00:00.101 user=postgres database=regression host=[local] 2025-11-30 18:45:02.407 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e1a" at character 8 2025-11-30 18:45:02.407 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0.0e1a; 2025-11-30 18:45:02.408 UTC client backend[43892] pg_regress/macaddr LOG: disconnection: session time: 0:00:00.079 user=postgres database=regression host=[local] 2025-11-30 18:45:02.408 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "1997-02-29" at character 30 2025-11-30 18:45:02.408 UTC client backend[43879] pg_regress/date STATEMENT: INSERT INTO DATE_TBL VALUES ('1997-02-29'); 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e" at character 8 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0.0e; 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e+" at character 8 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0.0e+a; 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after parameter at or near "$1a" at character 22 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $1a; 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology ERROR: parameter number too large at or near "$2147483648" at character 22 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $2147483648; 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology ERROR: invalid binary integer at or near "0b" at character 8 2025-11-30 18:45:02.408 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0b; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1b" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 1b; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0b0x" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0b0x; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: invalid octal integer at or near "0o" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0o; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1o" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 1o; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0o0x" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0o0x; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: invalid hexadecimal integer at or near "0x" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0x; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1x" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 1x; 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0y" at character 8 2025-11-30 18:45:02.409 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 0x0y; 2025-11-30 18:45:02.410 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03" at character 8 2025-11-30 18:45:02.410 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03'::macaddr8; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: column "_100" does not exist at character 8 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT _100; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100_" at character 8 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 100_; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100__000" at character 8 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 100__000; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: syntax error at or near ".5" at character 14 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT _1_000.5; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000_" at character 8 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 1_000_.5; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000._5" at character 8 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 1_000._5; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5_" at character 8 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 1_000.5_; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5e_1" at character 8 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: SELECT 1_000.5e_1; 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology ERROR: trailing junk after parameter at or near "$0_1" at character 22 2025-11-30 18:45:02.411 UTC client backend[43894] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $0_1; 2025-11-30 18:45:02.411 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.411 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval * 1000; 2025-11-30 18:45:02.411 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03 123" at character 8 2025-11-30 18:45:02.411 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03 123'::macaddr8; 2025-11-30 18:45:02.412 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.412 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval / 0.001; 2025-11-30 18:45:02.412 UTC client backend[43885] pg_regress/strings ERROR: UESCAPE must be followed by a simple string literal at or near "+" at character 33 2025-11-30 18:45:02.412 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE +; 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval * 1000; 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval / 0.001; 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '1 month 2146410 days'::interval * 1000.5002; 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.413 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '4611686018427387904 usec'::interval / 0.1; 2025-11-30 18:45:02.414 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.414 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT justify_hours(interval '2147483647 days 24 hrs'); 2025-11-30 18:45:02.414 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.414 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT justify_days(interval '2147483647 months 30 days'); 2025-11-30 18:45:02.414 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.414 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months 30 days'); 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months -30 days'); 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months -30 days 1440 hrs'); 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months 30 days -1440 hrs'); 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 second 2 seconds" at character 8 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '1 second 2 seconds'::interval; 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "10 milliseconds 20 milliseconds" at character 8 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '10 milliseconds 20 milliseconds'::interval; 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "5.5 seconds 3 milliseconds" at character 8 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '5.5 seconds 3 milliseconds'::interval; 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1:20:05 5 microseconds" at character 8 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '1:20:05 5 microseconds'::interval; 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 day 1 day" at character 8 2025-11-30 18:45:02.415 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '1 day 1 day'::interval; 2025-11-30 18:45:02.416 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-30 18:45:02.416 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2' day to minute; 2025-11-30 18:45:02.416 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-30 18:45:02.416 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2' day to second; 2025-11-30 18:45:02.416 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-30 18:45:02.416 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to minute; 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to second; 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2' minute to second; 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '123 11' day; 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '123 11'; 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "123 2:03 -2:04" at character 17 2025-11-30 18:45:02.417 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '123 2:03 -2:04'; 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2.345' day to second(2); 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2.345' hour to second(2); 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.3456" at character 17 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '1 2.3456' minute to second(2); 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval ERROR: interval out of range at character 17 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '2562047788:00:54.775807' second(2); 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval ERROR: interval out of range at character 17 2025-11-30 18:45:02.418 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-2562047788:00:54.775807' second(2); 2025-11-30 18:45:02.419 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "" at character 18 2025-11-30 18:45:02.419 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval ''; 2025-11-30 18:45:02.419 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape character at or near "'+'" at character 33 2025-11-30 18:45:02.419 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2025-11-30 18:45:02.420 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03:04:05" at character 8 2025-11-30 18:45:02.420 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03:04:05'::macaddr8; 2025-11-30 18:45:02.420 UTC client backend[43893] pg_regress/inet ERROR: invalid mask length: 33 2025-11-30 18:45:02.420 UTC client backend[43893] pg_regress/inet STATEMENT: SELECT set_masklen(inet(text(i)), 33) FROM INET_TBL; 2025-11-30 18:45:02.420 UTC client backend[43895] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: invalid transaction termination 2025-11-30 18:45:02.420 UTC client backend[43895] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python function "transaction_test2", line 5, in plpy.commit() PL/Python function "transaction_test2" 2025-11-30 18:45:02.420 UTC client backend[43895] pg_regress/plpython_transaction STATEMENT: SELECT transaction_test2(); 2025-11-30 18:45:02.420 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05 123" at character 8 2025-11-30 18:45:02.420 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05 123'::macaddr8; 2025-11-30 18:45:02.420 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "P.Y0M3DT4H5M6S" at character 17 2025-11-30 18:45:02.420 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P.Y0M3DT4H5M6S'; 2025-11-30 18:45:02.421 UTC client backend[43893] pg_regress/inet ERROR: invalid mask length: 33 2025-11-30 18:45:02.421 UTC client backend[43893] pg_regress/inet STATEMENT: SELECT set_masklen(cidr(text(c)), 33) FROM INET_TBL; 2025-11-30 18:45:02.421 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05:06:07" at character 8 2025-11-30 18:45:02.421 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05:06:07'::macaddr8; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483648 years" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483648 years'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483649 years" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483649 years'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483648 months" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483648 months'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483649 months" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483649 months'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483648 days'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483649 days'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2562047789 hours" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2562047789 hours'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2562047789 hours" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2562047789 hours'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "153722867281 minutes" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '153722867281 minutes'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-153722867281 minutes" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-153722867281 minutes'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "9223372036855 seconds" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '9223372036855 seconds'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-9223372036855 seconds" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-9223372036855 seconds'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "9223372036854777 millisecond" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '9223372036854777 millisecond'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-9223372036854777 millisecond" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-9223372036854777 millisecond'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "9223372036854775808 microsecond" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '9223372036854775808 microsecond'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775809 microsecond" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-9223372036854775809 microsecond'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P2147483648" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P2147483648'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-2147483649" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-2147483649'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval out of range at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P1-2147483647-2147483647'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT2562047789" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT2562047789'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT-2562047789" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT-2562047789'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 weeks" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 weeks'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 weeks" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 weeks'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 decades" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 decades'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 decades" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 decades'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 centuries" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 centuries'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 centuries" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 centuries'; 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 millennium" at character 17 2025-11-30 18:45:02.422 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 millennium'; 2025-11-30 18:45:02.423 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08-00-2b-01-02-03-04-05-06-07" at character 8 2025-11-30 18:45:02.423 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08-00-2b-01-02-03-04-05-06-07'::macaddr8; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 millennium" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 millennium'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "1 week 2147483647 days" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '1 week 2147483647 days'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-1 week -2147483648 days" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-1 week -2147483648 days'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 1 week" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 days 1 week'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -1 week" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 days -1 week'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P1W2147483647D" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P1W2147483647D'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-1W-2147483648D" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-1W-2147483648D'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P2147483647D1W" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P2147483647D1W'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-1W" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-2147483648D-1W'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "1 decade 2147483647 years" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '1 decade 2147483647 years'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "1 century 2147483647 years" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '1 century 2147483647 years'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "1 millennium 2147483647 years" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '1 millennium 2147483647 years'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-1 decade -2147483648 years" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-1 decade -2147483648 years'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-1 century -2147483648 years" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-1 century -2147483648 years'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-1 millennium -2147483648 years" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-1 millennium -2147483648 years'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 decade" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 years 1 decade'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 century" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 years 1 century'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 millennium" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 years 1 millennium'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 decade" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 decade'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 century" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 century'; 2025-11-30 18:45:02.423 UTC client backend[43895] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: spiexceptions.InvalidTransactionTermination: invalid transaction termination 2025-11-30 18:45:02.423 UTC client backend[43895] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python function "transaction_test3", line 2, in plpy.execute("CALL transaction_test1()") PL/Python function "transaction_test3" 2025-11-30 18:45:02.423 UTC client backend[43895] pg_regress/plpython_transaction STATEMENT: SELECT transaction_test3(); 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 millennium" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 millennium'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 millennium 2147483647 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 millennium 2147483647 months'; 2025-11-30 18:45:02.423 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b:01020304050607" at character 8 2025-11-30 18:45:02.423 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08002b:01020304050607'::macaddr8; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 centuries 2147483647 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 centuries 2147483647 months'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 decades 2147483647 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 decades 2147483647 months'; 2025-11-30 18:45:02.423 UTC client backend[43888] pg_regress/time ERROR: date/time field value out of range: "24:00:00.01" at character 8 2025-11-30 18:45:02.423 UTC client backend[43888] pg_regress/time STATEMENT: SELECT '24:00:00.01'::time; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 yrs 2147483647 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 yrs 2147483647 months'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.1 millennium -2147483648 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.1 millennium -2147483648 months'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.1 centuries -2147483648 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.1 centuries -2147483648 months'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.1 decades -2147483648 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.1 decades -2147483648 months'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.1 yrs -2147483648 months" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.1 yrs -2147483648 months'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 millennium" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 millennium'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 centuries" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 centuries'; 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 decades" at character 17 2025-11-30 18:45:02.423 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 decades'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 yrs" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 yrs'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 millennium" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 millennium'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 centuries" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 centuries'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 decades" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 decades'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 yrs" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 yrs'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 months 2147483647 days" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 months 2147483647 days'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.1 months -2147483648 days" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.1 months -2147483648 days'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.1 months" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 days 0.1 months'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.1 months" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.1 months'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.5 weeks 2147483647 days" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.5 weeks 2147483647 days'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.5 weeks -2147483648 days" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.5 weeks -2147483648 days'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.5 weeks" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2147483647 days 0.5 weeks'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.5 weeks" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.5 weeks'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.01 months 9223372036854775807 microseconds" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.01 months 9223372036854775807 microseconds'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.01 months -9223372036854775808 microseconds" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.01 months -9223372036854775808 microseconds'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.01 months" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.01 months'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.01 months" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.01 months'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 weeks 9223372036854775807 microseconds" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 weeks 9223372036854775807 microseconds'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.1 weeks -9223372036854775808 microseconds" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.1 weeks -9223372036854775808 microseconds'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 weeks" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 weeks'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 weeks" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 weeks'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 days 9223372036854775807 microseconds" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 days 9223372036854775807 microseconds'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-0.1 days -9223372036854775808 microseconds" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-0.1 days -9223372036854775808 microseconds'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 days" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 days'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 days" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 days'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P0.1Y2147483647M" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P0.1Y2147483647M'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-0.1Y-2147483648M" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-0.1Y-2147483648M'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P2147483647M0.1Y" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P2147483647M0.1Y'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-2147483648M-0.1Y" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-2147483648M-0.1Y'; 2025-11-30 18:45:02.424 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b01020304050607" at character 8 2025-11-30 18:45:02.424 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08002b01020304050607'::macaddr8; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P0.1M2147483647D" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P0.1M2147483647D'; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-0.1M-2147483648D" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-0.1M-2147483648D'; 2025-11-30 18:45:02.424 UTC client backend[43888] pg_regress/time ERROR: date/time field value out of range: "23:59:60.01" at character 8 2025-11-30 18:45:02.424 UTC client backend[43888] pg_regress/time STATEMENT: SELECT '23:59:60.01'::time; 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.1M" at character 17 2025-11-30 18:45:02.424 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P2147483647D0.1M'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.1M" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.1M'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P0.5W2147483647D" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P0.5W2147483647D'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-0.5W-2147483648D" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-0.5W-2147483648D'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.5W" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P2147483647D0.5W'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.5W" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.5W'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P0.01MT2562047788H54.775807S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P0.01MT2562047788H54.775807S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-0.01MT-2562047788H-54.775808S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-0.01MT-2562047788H-54.775808S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P0.1DT2562047788H54.775807S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P0.1DT2562047788H54.775807S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P-0.1DT-2562047788H-54.775808S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P-0.1DT-2562047788H-54.775808S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1H54.775807S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT2562047788.1H54.775807S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788.1H-54.775808S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT-2562047788.1H-54.775808S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT2562047788H0.1M54.775807S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT2562047788H0.1M54.775807S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788H-0.1M-54.775808S" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT-2562047788H-0.1M-54.775808S'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P0.1-2147483647-00" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P0.1-2147483647-00'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P00-0.1-2147483647" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P00-0.1-2147483647'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P00-0.01-00T2562047788:00:54.775807" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P00-0.01-00T2562047788:00:54.775807'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "P00-00-0.1T2562047788:00:54.775807" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'P00-00-0.1T2562047788:00:54.775807'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1:00:54.775807" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT2562047788.1:00:54.775807'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "PT2562047788:01.:54.775807" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval 'PT2562047788:01.:54.775807'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775807" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775807'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775808 ago" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775808 ago'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775807" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775807'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775808 ago" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775808 ago'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775807" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775807'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775808 ago" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775808 ago'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months ago" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 months ago'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days ago" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 days ago'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds ago" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds ago'; 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -2147483648 days -9223372036854775808 microseconds ago" at character 17 2025-11-30 18:45:02.425 UTC client backend[43890] pg_regress/interval STATEMENT: select interval '-2147483648 months -2147483648 days -9223372036854775808 microseconds ago'; 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(years := 178956971); 2025-11-30 18:45:02.426 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "0z002b0102030405" at character 8 2025-11-30 18:45:02.426 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '0z002b0102030405'::macaddr8; 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(years := -178956971); 2025-11-30 18:45:02.426 UTC client backend[43888] pg_regress/time ERROR: date/time field value out of range: "24:01:00" at character 8 2025-11-30 18:45:02.426 UTC client backend[43888] pg_regress/time STATEMENT: SELECT '24:01:00'::time; 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(years := 1, months := 2147483647); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(years := -1, months := -2147483648); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(weeks := 306783379); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(weeks := -306783379); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(weeks := 1, days := 2147483647); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(weeks := -1, days := -2147483648); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: value out of range: overflow 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(secs := 1e308); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(secs := 1e18); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(secs := -1e18); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(mins := 1, secs := 9223372036800.0); 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.426 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(mins := -1, secs := -9223372036800.0); 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: spiexceptions.InvalidTransactionTermination: invalid transaction termination 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python function "transaction_test4", line 2, in plpy.execute("DO LANGUAGE plpython3u $x$ plpy.commit() $x$") PL/Python function "transaction_test4" 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction STATEMENT: SELECT transaction_test4(); 2025-11-30 18:45:02.427 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b010203xyza" at character 8 2025-11-30 18:45:02.427 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08002b010203xyza'::macaddr8; 2025-11-30 18:45:02.427 UTC client backend[43888] pg_regress/time ERROR: date/time field value out of range: "25:00:00" at character 8 2025-11-30 18:45:02.427 UTC client backend[43888] pg_regress/time STATEMENT: SELECT '25:00:00'::time; 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction WARNING: forcibly aborting a subtransaction that has not been exited 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction CONTEXT: PL/Python anonymous code block 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction ERROR: spiexceptions.InvalidTransactionTermination: cannot commit while a subtransaction is active 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 4, in plpy.commit() PL/Python anonymous code block 2025-11-30 18:45:02.427 UTC client backend[43895] pg_regress/plpython_transaction STATEMENT: DO LANGUAGE plpython3u $$ s = plpy.subtransaction() s.enter() plpy.commit() $$; 2025-11-30 18:45:02.427 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2025-11-30 18:45:02.427 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2025-11-30 18:45:02.429 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2025-11-30 18:45:02.429 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2025-11-30 18:45:02.429 UTC client backend[43894] pg_regress/numerology LOG: disconnection: session time: 0:00:00.101 user=postgres database=regression host=[local] 2025-11-30 18:45:02.429 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2025-11-30 18:45:02.429 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2025-11-30 18:45:02.430 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-30 18:45:02.430 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99'; 2025-11-30 18:45:02.431 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2025-11-30 18:45:02.431 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99xy'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\\'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\0061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 26 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \+00db99\+000061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape value at character 18 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \+2FFFFF'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape at character 17 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \u061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape at character 17 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \U0061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "'" at character 23 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "x" at character 23 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99xy'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\" at character 23 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\\'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\u0061" at character 23 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\u0061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\U00000061" at character 27 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \U0000db99\U00000061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape value at or near "\U002FFFFF" at character 17 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'wrong: \U002FFFFF'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'d\0061t\+000061' AS U&"d\0061t\+000061"; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'d!0061t\+000061' UESCAPE '!' AS U&"d*0061t\+000061" UESCAPE '*'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&' \' UESCAPE '!' AS "tricky"; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-30 18:45:02.431 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2025-11-30 18:45:02.432 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal data: odd number of digits at character 8 2025-11-30 18:45:02.432 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeE'::bytea; 2025-11-30 18:45:02.432 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "x" at character 8 2025-11-30 18:45:02.432 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeEx'::bytea; 2025-11-30 18:45:02.432 UTC client backend[43885] pg_regress/strings ERROR: invalid input syntax for type bytea at character 8 2025-11-30 18:45:02.432 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT E'De\\678dBeEf'::bytea; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "!" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('!', 32))::bytea; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "/" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('/', 34))::bytea; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: ":" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat(':', 32))::bytea; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "@" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('@', 34))::bytea; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "G" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('G', 32))::bytea; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "`" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('`', 34))::bytea; 2025-11-30 18:45:02.433 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "1/8/1999" at character 13 2025-11-30 18:45:02.433 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.433 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '1/8/1999'; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "g" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('g', 32))::bytea; 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings ERROR: invalid hexadecimal digit: "~" 2025-11-30 18:45:02.433 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('~', 34))::bytea; 2025-11-30 18:45:02.436 UTC client backend[43888] pg_regress/time ERROR: operator is not unique: time without time zone + time without time zone at character 11 2025-11-30 18:45:02.436 UTC client backend[43888] pg_regress/time DETAIL: Could not choose a best candidate operator. 2025-11-30 18:45:02.436 UTC client backend[43888] pg_regress/time HINT: You might need to add explicit type casts. 2025-11-30 18:45:02.436 UTC client backend[43888] pg_regress/time STATEMENT: SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL; 2025-11-30 18:45:02.436 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2025-11-30 18:45:02.436 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.436 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2025-11-30 18:45:02.438 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2025-11-30 18:45:02.438 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.438 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2025-11-30 18:45:02.438 UTC client backend[43885] pg_regress/strings ERROR: negative substring length not allowed 2025-11-30 18:45:02.438 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT SUBSTRING('string' FROM -10 FOR -2147483646) AS "error"; 2025-11-30 18:45:02.439 UTC client backend[43895] pg_regress/plpython_transaction ERROR: spiexceptions.DivisionByZero: division by zero 2025-11-30 18:45:02.439 UTC client backend[43895] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 3, in plpy.execute("INSERT INTO test1 (a) VALUES (12/(%s-2))" % row['x']) PL/Python anonymous code block 2025-11-30 18:45:02.439 UTC client backend[43895] pg_regress/plpython_transaction STATEMENT: DO LANGUAGE plpython3u $$ for row in plpy.cursor("SELECT * FROM test2 ORDER BY x"): plpy.execute("INSERT INTO test1 (a) VALUES (12/(%s-2))" % row['x']) plpy.commit() $$; 2025-11-30 18:45:02.440 UTC client backend[43885] pg_regress/strings ERROR: SQL regular expression may not contain more than two escape-double-quote separators 2025-11-30 18:45:02.440 UTC client backend[43885] pg_regress/strings CONTEXT: SQL function "substring" statement 1 2025-11-30 18:45:02.440 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT SUBSTRING('abcdefg' SIMILAR 'a*#"%#"g*#"x' ESCAPE '#') AS "error"; 2025-11-30 18:45:02.441 UTC client backend[43885] pg_regress/strings ERROR: invalid escape string 2025-11-30 18:45:02.441 UTC client backend[43885] pg_regress/strings HINT: Escape string must be empty or one character. 2025-11-30 18:45:02.441 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT 'abcdefg' SIMILAR TO '_bcd#%' ESCAPE '##' AS error; 2025-11-30 18:45:02.443 UTC client backend[43888] pg_regress/time ERROR: unit "day" not supported for type time without time zone 2025-11-30 18:45:02.443 UTC client backend[43888] pg_regress/time STATEMENT: SELECT EXTRACT(DAY FROM TIME '2020-05-26 13:30:25.575401'); 2025-11-30 18:45:02.444 UTC client backend[43888] pg_regress/time ERROR: unit "fortnight" not recognized for type time without time zone 2025-11-30 18:45:02.444 UTC client backend[43888] pg_regress/time STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME '2020-05-26 13:30:25.575401'); 2025-11-30 18:45:02.444 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "January 8, 99 BC" at character 13 2025-11-30 18:45:02.444 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.444 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date 'January 8, 99 BC'; 2025-11-30 18:45:02.445 UTC client backend[43885] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-30 18:45:02.445 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_replace('AAA aaa', 'A+', 'Z', 'z'); 2025-11-30 18:45:02.445 UTC client backend[43888] pg_regress/time ERROR: unit "timezone" not supported for type time without time zone 2025-11-30 18:45:02.445 UTC client backend[43888] pg_regress/time STATEMENT: SELECT EXTRACT(TIMEZONE FROM TIME '2020-05-26 13:30:25.575401'); 2025-11-30 18:45:02.445 UTC client backend[43886] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "not even close" at character 38 2025-11-30 18:45:02.445 UTC client backend[43886] pg_regress/macaddr8 STATEMENT: INSERT INTO macaddr8_data VALUES (9, 'not even close'); 2025-11-30 18:45:02.445 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "start": -1 2025-11-30 18:45:02.445 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', -1, 0, 'i'); 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "n": -1 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', 1, -1, 'i'); 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings ERROR: invalid regular expression option: "1" 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings HINT: If you meant to use regexp_replace() with a start parameter, cast the fourth argument to integer explicitly. 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', '1'); 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', 0); 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "start": -3 2025-11-30 18:45:02.446 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', -3); 2025-11-30 18:45:02.447 UTC client backend[43885] pg_regress/strings ERROR: regexp_like() does not support the "global" option 2025-11-30 18:45:02.447 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_like('abc', 'a.c', 'g'); 2025-11-30 18:45:02.447 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "08-Jan-99" at character 13 2025-11-30 18:45:02.447 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.447 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '08-Jan-99'; 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 0, 1); 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "n": 0 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 0); 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "endoption": -1 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, -1); 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "endoption": 2 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 2); 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings ERROR: regexp_instr() does not support the "global" option 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, 'g'); 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2025-11-30 18:45:02.449 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, '', -1); 2025-11-30 18:45:02.449 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "Jan-08-99" at character 13 2025-11-30 18:45:02.449 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.449 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date 'Jan-08-99'; 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 0, 1); 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "n": 0 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 0); 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings ERROR: regexp_substr() does not support the "global" option 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, 'g'); 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2025-11-30 18:45:02.450 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, '', -1); 2025-11-30 18:45:02.451 UTC client backend[43888] pg_regress/time LOG: disconnection: session time: 0:00:00.127 user=postgres database=regression host=[local] 2025-11-30 18:45:02.452 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-11-30 18:45:02.452 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-11-30 18:45:02.452 UTC client backend[43885] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-30 18:45:02.452 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque)$re$, 'gz'); 2025-11-30 18:45:02.453 UTC client backend[43897] pg_regress/date LOG: disconnection: session time: 0:00:00.117 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval ERROR: integer out of range 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(years := 'inf'::float::int); 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval ERROR: integer out of range 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(months := 'NaN'::float::int); 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(secs := 'inf'); 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.453 UTC client backend[43890] pg_regress/interval STATEMENT: select make_interval(secs := 'NaN'); 2025-11-30 18:45:02.453 UTC client backend[43885] pg_regress/strings ERROR: invalid regular expression: parentheses () not balanced 2025-11-30 18:45:02.453 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(barbeque$re$); 2025-11-30 18:45:02.453 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-11-30 18:45:02.453 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-11-30 18:45:02.453 UTC client backend[43885] pg_regress/strings ERROR: invalid regular expression: invalid repetition count(s) 2025-11-30 18:45:02.453 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque){2,1}$re$); 2025-11-30 18:45:02.454 UTC client backend[43890] pg_regress/interval ERROR: unit "fortnight" not recognized for type interval 2025-11-30 18:45:02.454 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT EXTRACT(FORTNIGHT FROM INTERVAL '2 days'); 2025-11-30 18:45:02.454 UTC client backend[43890] pg_regress/interval ERROR: unit "timezone" not supported for type interval 2025-11-30 18:45:02.454 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT EXTRACT(TIMEZONE FROM INTERVAL '2 days'); 2025-11-30 18:45:02.454 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "08 Jan 99" at character 13 2025-11-30 18:45:02.454 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.454 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '08 Jan 99'; 2025-11-30 18:45:02.454 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "Jan 08 99" at character 13 2025-11-30 18:45:02.454 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.454 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date 'Jan 08 99'; 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "08-01-99" at character 13 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '08-01-99'; 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "08-01-1999" at character 13 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '08-01-1999'; 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "01-08-99" at character 13 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '01-08-99'; 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "01-08-1999" at character 13 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.456 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '01-08-1999'; 2025-11-30 18:45:02.456 UTC client backend[43885] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-30 18:45:02.456 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT foo, length(foo) FROM regexp_split_to_table('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'zippy') AS foo; 2025-11-30 18:45:02.457 UTC client backend[43885] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-30 18:45:02.457 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'iz'); 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "08 01 99" at character 13 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '08 01 99'; 2025-11-30 18:45:02.457 UTC client backend[43885] pg_regress/strings ERROR: regexp_split_to_table() does not support the "global" option 2025-11-30 18:45:02.457 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT foo, length(foo) FROM regexp_split_to_table('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g') AS foo; 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "08 01 1999" at character 13 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '08 01 1999'; 2025-11-30 18:45:02.457 UTC client backend[43885] pg_regress/strings ERROR: regexp_split_to_array() does not support the "global" option 2025-11-30 18:45:02.457 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g'); 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "01 08 99" at character 13 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '01 08 99'; 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "01 08 1999" at character 13 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.457 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '01 08 1999'; 2025-11-30 18:45:02.458 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2025-11-30 18:45:02.458 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.458 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' + interval '1 month 1 day 1 us'; 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' + interval '-1 month -1 day -1 us'; 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' - interval '-1 month -1 day -1 us'; 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.459 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' - interval '1 month 1 day 1 us'; 2025-11-30 18:45:02.460 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2025-11-30 18:45:02.460 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.460 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2025-11-30 18:45:02.460 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-11-30 18:45:02.460 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-11-30 18:45:02.460 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-11-30 18:45:02.460 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-11-30 18:45:02.461 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99 Jan 08" at character 13 2025-11-30 18:45:02.461 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.461 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2025-11-30 18:45:02.461 UTC client backend[43890] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-30 18:45:02.461 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval 'infinity'; 2025-11-30 18:45:02.461 UTC unrecognized[43903] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.461 UTC client backend[43903] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.461 UTC client backend[43903] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/interval 2025-11-30 18:45:02.462 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2025-11-30 18:45:02.462 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2025-11-30 18:45:02.462 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2025-11-30 18:45:02.462 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.462 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2025-11-30 18:45:02.462 UTC client backend[43903] pg_regress/interval LOG: connection ready: setup total=2.205 ms, fork=0.635 ms, authentication=0.110 ms 2025-11-30 18:45:02.462 UTC client backend[43890] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-30 18:45:02.462 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval '-infinity'; 2025-11-30 18:45:02.463 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2025-11-30 18:45:02.463 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.463 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2025-11-30 18:45:02.463 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2025-11-30 18:45:02.463 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.463 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2025-11-30 18:45:02.464 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2025-11-30 18:45:02.464 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.464 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2025-11-30 18:45:02.464 UTC client backend[43890] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-30 18:45:02.464 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval 'infinity'; 2025-11-30 18:45:02.465 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2025-11-30 18:45:02.465 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.465 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2025-11-30 18:45:02.466 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2025-11-30 18:45:02.466 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.466 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2025-11-30 18:45:02.467 UTC client backend[43890] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-30 18:45:02.467 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval '-infinity'; 2025-11-30 18:45:02.467 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-11-30 18:45:02.467 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-11-30 18:45:02.467 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-11-30 18:45:02.467 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-11-30 18:45:02.467 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "99 Jan 08" at character 13 2025-11-30 18:45:02.467 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2025-11-30 18:45:02.468 UTC client backend[43890] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-30 18:45:02.468 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval 'infinity'; 2025-11-30 18:45:02.469 UTC client backend[43890] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-30 18:45:02.469 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval '-infinity'; 2025-11-30 18:45:02.469 UTC client backend[43903] pg_regress/interval LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.470 UTC client backend[43890] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-30 18:45:02.470 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval 'infinity'; 2025-11-30 18:45:02.470 UTC client backend[43890] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-30 18:45:02.470 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval '-infinity'; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT -interval '-2147483647 months -2147483647 days -9223372036854775807 us'; 2025-11-30 18:45:02.471 UTC client backend[43879] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2025-11-30 18:45:02.471 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 'nan'; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 'nan'; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' * 2; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 0; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 0; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '0 days' * 'infinity'::float; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '0 days' * '-infinity'::float; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'infinity'; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval 'infinity' / '-infinity'; 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.471 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'nan'; 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'infinity'; 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-infinity' / '-infinity'; 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'nan'; 2025-11-30 18:45:02.472 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2025-11-30 18:45:02.472 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.472 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: interval out of range 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' / 0.5; 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT date_bin('infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT date_bin('-infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: unit "week" not supported for type interval 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval DETAIL: Months usually have fractional weeks. 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT i AS interval, date_trunc('week', i) FROM INFINITE_INTERVAL_TBL WHERE NOT isfinite(i); 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval ERROR: unit "ago" not recognized for type interval 2025-11-30 18:45:02.472 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT i AS interval, date_trunc('ago', i) FROM INFINITE_INTERVAL_TBL WHERE NOT isfinite(i); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::time); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::time); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::timetz); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::timetz); 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: cannot convert infinite interval to time 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT 'infinity'::interval::time; 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval ERROR: cannot convert infinite interval to time 2025-11-30 18:45:02.473 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT '-infinity'::interval::time; 2025-11-30 18:45:02.474 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2025-11-30 18:45:02.474 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.474 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "42 days 2 seconds ago ago" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL '42 days 2 seconds ago ago'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "2 minutes ago 5 days" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL '2 minutes ago 5 days'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "hour 5 months" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'hour 5 months'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "1 year months days 5 hours" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL '1 year months days 5 hours'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "now" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'now'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "today" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'today'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "tomorrow" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'tomorrow'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "allballs" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'allballs'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "epoch" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'epoch'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "yesterday" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'yesterday'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity years" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity years'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity ago" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity ago'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval ERROR: invalid input syntax for type interval: "+infinity -infinity" at character 17 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval STATEMENT: SELECT INTERVAL '+infinity -infinity'; 2025-11-30 18:45:02.474 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2025-11-30 18:45:02.474 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.474 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2025-11-30 18:45:02.474 UTC client backend[43890] pg_regress/interval LOG: disconnection: session time: 0:00:00.150 user=postgres database=regression host=[local] 2025-11-30 18:45:02.476 UTC client backend[43879] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2025-11-30 18:45:02.476 UTC client backend[43879] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:02.476 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2025-11-30 18:45:02.478 UTC client backend[43879] pg_regress/date ERROR: date out of range: "4714-11-23 BC" at character 13 2025-11-30 18:45:02.478 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '4714-11-23 BC'; 2025-11-30 18:45:02.478 UTC client backend[43879] pg_regress/date ERROR: date out of range: "5874898-01-01" at character 13 2025-11-30 18:45:02.478 UTC client backend[43879] pg_regress/date STATEMENT: SELECT date '5874898-01-01'; 2025-11-30 18:45:02.480 UTC client backend[43877] pg_regress/lseg ERROR: invalid input syntax for type lseg: "(3asdf,2 ,3,4r2)" at character 30 2025-11-30 18:45:02.480 UTC client backend[43877] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2025-11-30 18:45:02.480 UTC client backend[43877] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[1,2,3, 4" at character 30 2025-11-30 18:45:02.480 UTC client backend[43877] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[1,2,3, 4'); 2025-11-30 18:45:02.481 UTC client backend[43877] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(,2),(3,4)]" at character 30 2025-11-30 18:45:02.481 UTC client backend[43877] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(,2),(3,4)]'); 2025-11-30 18:45:02.481 UTC client backend[43877] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(1,2),(3,4)" at character 30 2025-11-30 18:45:02.481 UTC client backend[43877] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(1,2),(3,4)'); 2025-11-30 18:45:02.483 UTC client backend[43895] pg_regress/plpython_transaction ERROR: spiexceptions.ForeignKeyViolation: insert or update on table "testfk" violates foreign key constraint "testfk_f1_fkey" 2025-11-30 18:45:02.483 UTC client backend[43895] pg_regress/plpython_transaction DETAIL: Key (f1)=(0) is not present in table "testpk". 2025-11-30 18:45:02.483 UTC client backend[43895] pg_regress/plpython_transaction CONTEXT: Traceback (most recent call last): PL/Python anonymous code block, line 4, in plpy.commit() PL/Python anonymous code block 2025-11-30 18:45:02.483 UTC client backend[43895] pg_regress/plpython_transaction STATEMENT: DO LANGUAGE plpython3u $$ # this insert will fail during commit: plpy.execute("INSERT INTO testfk VALUES (0)") plpy.commit() plpy.warning('should not get here') $$; 2025-11-30 18:45:02.490 UTC client backend[43881] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-30 18:45:02.490 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select nummultirange(numrange(2.0, 1.0)); 2025-11-30 18:45:02.491 UTC unrecognized[43906] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.491 UTC client backend[43906] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.491 UTC client backend[43906] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/macaddr 2025-11-30 18:45:02.492 UTC client backend[43906] pg_regress/macaddr LOG: connection ready: setup total=5.857 ms, fork=3.772 ms, authentication=0.104 ms 2025-11-30 18:45:02.495 UTC unrecognized[43907] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.496 UTC client backend[43907] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.496 UTC client backend[43907] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/oid 2025-11-30 18:45:02.496 UTC client backend[43907] pg_regress/oid LOG: connection ready: setup total=5.146 ms, fork=3.681 ms, authentication=0.103 ms 2025-11-30 18:45:02.499 UTC client backend[43877] pg_regress/lseg LOG: disconnection: session time: 0:00:00.178 user=postgres database=regression host=[local] 2025-11-30 18:45:02.501 UTC client backend[43906] pg_regress/macaddr LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.503 UTC client backend[43886] pg_regress/macaddr8 LOG: disconnection: session time: 0:00:00.169 user=postgres database=regression host=[local] 2025-11-30 18:45:02.507 UTC client backend[43895] pg_regress/plpython_transaction LOG: disconnection: session time: 0:00:00.179 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:02.514 UTC client backend[43907] pg_regress/oid LOG: disconnection: session time: 0:00:00.018 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.515 UTC unrecognized[43913] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.515 UTC client backend[43893] pg_regress/inet ERROR: result is out of range 2025-11-30 18:45:02.515 UTC client backend[43893] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet + 10000000000; 2025-11-30 18:45:02.515 UTC client backend[43913] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.516 UTC client backend[43913] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/macaddr8 2025-11-30 18:45:02.516 UTC client backend[43893] pg_regress/inet ERROR: result is out of range 2025-11-30 18:45:02.516 UTC client backend[43893] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet - 10000000000; 2025-11-30 18:45:02.516 UTC client backend[43893] pg_regress/inet ERROR: result is out of range 2025-11-30 18:45:02.516 UTC client backend[43893] pg_regress/inet STATEMENT: SELECT '126::1'::inet - '127::2'::inet; 2025-11-30 18:45:02.516 UTC client backend[43913] pg_regress/macaddr8 LOG: connection ready: setup total=1.782 ms, fork=0.351 ms, authentication=0.102 ms 2025-11-30 18:45:02.517 UTC client backend[43893] pg_regress/inet ERROR: result is out of range 2025-11-30 18:45:02.517 UTC client backend[43893] pg_regress/inet STATEMENT: SELECT '127::1'::inet - '126::2'::inet; 2025-11-30 18:45:02.520 UTC client backend[43893] pg_regress/inet ERROR: cannot merge addresses from different families 2025-11-30 18:45:02.520 UTC client backend[43893] pg_regress/inet STATEMENT: SELECT inet_merge(c, i) FROM INET_TBL; 2025-11-30 18:45:02.527 UTC client backend[43913] pg_regress/macaddr8 LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.531 UTC unrecognized[43914] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.531 UTC client backend[43914] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.531 UTC client backend[43914] [unknown] LOG: connection authorized: user=postgres database=regression_plpython application_name=pg_regress/plpython_drop 2025-11-30 18:45:02.532 UTC client backend[43914] pg_regress/plpython_drop LOG: connection ready: setup total=6.130 ms, fork=4.407 ms, authentication=0.101 ms 2025-11-30 18:45:02.537 UTC unrecognized[43917] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.538 UTC client backend[43917] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.538 UTC client backend[43917] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/timestamp 2025-11-30 18:45:02.539 UTC client backend[43917] pg_regress/timestamp LOG: connection ready: setup total=2.835 ms, fork=1.408 ms, authentication=0.099 ms 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date ERROR: unit "microseconds" not supported for type date 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSECONDS FROM DATE '2020-08-11'); 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date ERROR: unit "milliseconds" not supported for type date 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(MILLISECONDS FROM DATE '2020-08-11'); 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date ERROR: unit "second" not supported for type date 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(SECOND FROM DATE '2020-08-11'); 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date ERROR: unit "minute" not supported for type date 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(MINUTE FROM DATE '2020-08-11'); 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date ERROR: unit "hour" not supported for type date 2025-11-30 18:45:02.552 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(HOUR FROM DATE '2020-08-11'); 2025-11-30 18:45:02.553 UTC unrecognized[43923] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.553 UTC client backend[43879] pg_regress/date ERROR: unit "timezone" not supported for type date 2025-11-30 18:45:02.553 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE FROM DATE '2020-08-11'); 2025-11-30 18:45:02.553 UTC client backend[43879] pg_regress/date ERROR: unit "timezone_m" not supported for type date 2025-11-30 18:45:02.553 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_M FROM DATE '2020-08-11'); 2025-11-30 18:45:02.553 UTC client backend[43879] pg_regress/date ERROR: unit "timezone_h" not supported for type date 2025-11-30 18:45:02.553 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_H FROM DATE '2020-08-11'); 2025-11-30 18:45:02.553 UTC client backend[43923] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.553 UTC client backend[43923] [unknown] LOG: connection authorized: user=postgres database=regression_citext application_name=pg_regress/citext_utf8 2025-11-30 18:45:02.554 UTC client backend[43923] pg_regress/citext_utf8 LOG: connection ready: setup total=1.809 ms, fork=0.356 ms, authentication=0.104 ms 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date ERROR: unit "microsec" not recognized for type date 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSEC FROM DATE 'infinity'); 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date ERROR: date field value out of range: 0-07-15 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date STATEMENT: select make_date(0, 7, 15); 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date ERROR: date field value out of range: 2013-02-30 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date STATEMENT: select make_date(2013, 2, 30); 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date ERROR: date field value out of range: 2013-13-01 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date STATEMENT: select make_date(2013, 13, 1); 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date ERROR: date field value out of range: 2013-11--1 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date STATEMENT: select make_date(2013, 11, -1); 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date ERROR: date field value out of range: -2147483648-01-01 2025-11-30 18:45:02.556 UTC client backend[43879] pg_regress/date STATEMENT: SELECT make_date(-2147483648, 1, 1); 2025-11-30 18:45:02.557 UTC client backend[43879] pg_regress/date ERROR: time field value out of range: 10:55:100.1 2025-11-30 18:45:02.557 UTC client backend[43879] pg_regress/date STATEMENT: select make_time(10, 55, 100.1); 2025-11-30 18:45:02.557 UTC client backend[43879] pg_regress/date ERROR: time field value out of range: 24:00:2.1 2025-11-30 18:45:02.557 UTC client backend[43879] pg_regress/date STATEMENT: select make_time(24, 0, 2.1); 2025-11-30 18:45:02.557 UTC client backend[43879] pg_regress/date LOG: disconnection: session time: 0:00:00.233 user=postgres database=regression host=[local] 2025-11-30 18:45:02.558 UTC unrecognized[43919] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.559 UTC client backend[43919] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.559 UTC client backend[43919] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/inet 2025-11-30 18:45:02.559 UTC client backend[43923] pg_regress/citext_utf8 LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_citext host=[local] 2025-11-30 18:45:02.559 UTC client backend[43919] pg_regress/inet LOG: connection ready: setup total=14.271 ms, fork=12.883 ms, authentication=0.099 ms 2025-11-30 18:45:02.560 UTC client backend[43819] pg_regress/citext LOG: disconnection: session time: 0:00:00.442 user=postgres database=regression_citext host=[local] 2025-11-30 18:45:02.568 UTC client backend[43914] pg_regress/plpython_drop LOG: disconnection: session time: 0:00:00.037 user=postgres database=regression_plpython host=[local] 2025-11-30 18:45:02.573 UTC client backend[43893] pg_regress/inet LOG: disconnection: session time: 0:00:00.244 user=postgres database=regression host=[local] 2025-11-30 18:45:02.594 UTC client backend[43882] pg_regress/polygon LOG: disconnection: session time: 0:00:00.271 user=postgres database=regression host=[local] 2025-11-30 18:45:02.607 UTC unrecognized[43929] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.607 UTC client backend[43929] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.607 UTC client backend[43929] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.608 UTC client backend[43929] pg_regress LOG: connection ready: setup total=1.783 ms, fork=0.408 ms, authentication=0.187 ms 2025-11-30 18:45:02.608 UTC client backend[43929] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.616 UTC unrecognized[43931] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.616 UTC client backend[43931] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.616 UTC client backend[43931] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.617 UTC client backend[43931] pg_regress LOG: connection ready: setup total=5.038 ms, fork=3.761 ms, authentication=0.127 ms 2025-11-30 18:45:02.623 UTC client backend[43885] pg_regress/strings ERROR: negative substring length not allowed 2025-11-30 18:45:02.623 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2025-11-30 18:45:02.630 UTC client backend[43917] pg_regress/timestamp LOG: disconnection: session time: 0:00:00.092 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.634 UTC client backend[43931] pg_regress LOG: disconnection: session time: 0:00:00.018 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.640 UTC client backend[43885] pg_regress/strings ERROR: negative substring length not allowed 2025-11-30 18:45:02.640 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2025-11-30 18:45:02.645 UTC client backend[43919] pg_regress/inet LOG: disconnection: session time: 0:00:00.086 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.653 UTC unrecognized[43938] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.653 UTC client backend[43938] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.653 UTC client backend[43938] [unknown] LOG: connection authorized: user=postgres database=regression_cube application_name=pg_regress/cube 2025-11-30 18:45:02.656 UTC client backend[43885] pg_regress/strings ERROR: field position must not be zero 2025-11-30 18:45:02.656 UTC client backend[43885] pg_regress/strings STATEMENT: select split_part('joeuser@mydatabase','@',0) AS "an error"; 2025-11-30 18:45:02.658 UTC client backend[43938] pg_regress/cube LOG: connection ready: setup total=5.442 ms, fork=0.340 ms, authentication=0.119 ms 2025-11-30 18:45:02.661 UTC client backend[43885] pg_regress/strings ERROR: unrecognized encoding: "invalid" 2025-11-30 18:45:02.661 UTC client backend[43885] pg_regress/strings HINT: Valid encodings are "base64", "base64url", "escape", and "hex". 2025-11-30 18:45:02.661 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT encode('\x01'::bytea, 'invalid'); 2025-11-30 18:45:02.661 UTC client backend[43885] pg_regress/strings ERROR: unrecognized encoding: "invalid" 2025-11-30 18:45:02.661 UTC client backend[43885] pg_regress/strings HINT: Valid encodings are "base64", "base64url", "escape", and "hex". 2025-11-30 18:45:02.661 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT decode('00', 'invalid'); 2025-11-30 18:45:02.662 UTC client backend[43885] pg_regress/strings ERROR: invalid symbol "@" found while decoding base64url sequence 2025-11-30 18:45:02.662 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT decode('QQ@=', 'base64url'); 2025-11-30 18:45:02.662 UTC client backend[43885] pg_regress/strings ERROR: invalid base64url end sequence 2025-11-30 18:45:02.662 UTC client backend[43885] pg_regress/strings HINT: Input data is missing padding, is truncated, or is otherwise corrupted. 2025-11-30 18:45:02.662 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT decode('QQIDQ', 'base64url'); 2025-11-30 18:45:02.662 UTC client backend[43885] pg_regress/strings ERROR: unexpected "=" while decoding base64url sequence 2025-11-30 18:45:02.662 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT decode('=QQQ', 'base64url'); 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT get_bit('\x1234567890abcdef00'::bytea, 99); 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT set_bit('\x1234567890abcdef00'::bytea, 99, 0); 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT get_byte('\x1234567890abcdef00'::bytea, 99); 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2025-11-30 18:45:02.663 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT set_byte('\x1234567890abcdef00'::bytea, 99, 11); 2025-11-30 18:45:02.665 UTC client backend[43885] pg_regress/strings ERROR: smallint out of range 2025-11-30 18:45:02.665 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT '\x123456'::bytea::int2; 2025-11-30 18:45:02.665 UTC client backend[43885] pg_regress/strings ERROR: integer out of range 2025-11-30 18:45:02.665 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT '\x123456789A'::bytea::int4; 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings ERROR: bigint out of range 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT '\x112233445566778899'::bytea::int8; 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 8 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 24 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 42 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 62 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 80 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 98 2025-11-30 18:45:02.666 UTC client backend[43885] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:02.669 UTC client backend[43885] pg_regress/strings ERROR: null character not permitted 2025-11-30 18:45:02.669 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT chr(0); 2025-11-30 18:45:02.669 UTC unrecognized[43936] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.669 UTC client backend[43885] pg_regress/strings ERROR: negative substring length not allowed 2025-11-30 18:45:02.669 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT SUBSTRING('string'::bytea FROM -10 FOR -2147483646) AS "error"; 2025-11-30 18:45:02.670 UTC client backend[43936] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.670 UTC client backend[43936] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/timestamptz 2025-11-30 18:45:02.671 UTC client backend[43936] pg_regress/timestamptz LOG: connection ready: setup total=31.286 ms, fork=17.354 ms, authentication=0.109 ms 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99\0061'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+00db99\+000061'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+2FFFFF'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \udb99\u0061'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U0000db99\U00000061'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U002FFFFF'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings ERROR: invalid Unicode escape 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings HINT: Unicode escapes must be \XXXX, \+XXXXXX, \uXXXX, or \UXXXXXXXX. 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings STATEMENT: SELECT unistr('wrong: \xyz'); 2025-11-30 18:45:02.671 UTC client backend[43885] pg_regress/strings LOG: disconnection: session time: 0:00:00.348 user=postgres database=regression host=[local] 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at end of input 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT ''::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "A" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT 'ABC'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "]" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[]'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "]" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[()]'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "]" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[(1)]'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "]" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[(1),]'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "2" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[(1),2]'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "," 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[(1),(2),(3)]'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at end of input 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '1,'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at end of input 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '1,2,'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "," 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '1,,2'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near ")" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,)'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near ")" 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,2,)'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "," 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,,2)'::cube AS cube; 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "," 2025-11-30 18:45:02.697 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[(1),(2)],'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: Different point dimensions in (1,2,3) and (2,3). 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[(1,2,3),(2,3)]'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: Different point dimensions in (1,2) and (1,2,3). 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '[(1,2),(1,2,3)]'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "," 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1),(2),'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: Different point dimensions in (1,2,3) and (2,3). 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,2,3),(2,3)'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: Different point dimensions in (1,2) and (1,2,3). 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,2),(1,2,3)'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "a" 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,2,3)ab'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "a" 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,2,3)a'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "(" 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '(1,2)('::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "a" 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '1,2ab'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "e" 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '1 e7'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near "a" 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '1,2a'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube DETAIL: syntax error at or near ".2" 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '1..2'::cube AS cube; 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube ERROR: "-1e-700" is out of range for type double precision at character 8 2025-11-30 18:45:02.698 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT '-1e-700'::cube AS cube; 2025-11-30 18:45:02.699 UTC client backend[43878] pg_regress/box LOG: disconnection: session time: 0:00:00.378 user=postgres database=regression host=[local] 2025-11-30 18:45:02.699 UTC client backend[43938] pg_regress/cube ERROR: UR and LL arrays must be of same length 2025-11-30 18:45:02.699 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube('{0,1,2}'::float[], '{3}'::float[]); 2025-11-30 18:45:02.700 UTC client backend[43938] pg_regress/cube ERROR: Index out of bounds 2025-11-30 18:45:02.700 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube_subset(cube('(1,3,5),(6,7,8)'), ARRAY[4,0]); 2025-11-30 18:45:02.700 UTC client backend[43938] pg_regress/cube ERROR: Index out of bounds 2025-11-30 18:45:02.700 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube_subset(cube('(6,7,8),(6,7,8)'), ARRAY[4,0]); 2025-11-30 18:45:02.700 UTC client backend[43938] pg_regress/cube ERROR: array is too long 2025-11-30 18:45:02.700 UTC client backend[43938] pg_regress/cube DETAIL: A cube cannot have more than 100 dimensions. 2025-11-30 18:45:02.700 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube_subset(cube('(6,7,8),(6,7,8)'), array(SELECT 1 as a FROM generate_series(1,101))); 2025-11-30 18:45:02.702 UTC client backend[43936] pg_regress/timestamptz LOG: disconnection: session time: 0:00:00.045 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.704 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.704 UTC client backend[43938] pg_regress/cube DETAIL: A cube cannot have more than 100 dimensions. 2025-11-30 18:45:02.704 UTC client backend[43938] pg_regress/cube STATEMENT: select '(0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0)'::cube; 2025-11-30 18:45:02.704 UTC client backend[43938] pg_regress/cube ERROR: invalid input syntax for cube at character 8 2025-11-30 18:45:02.704 UTC client backend[43938] pg_regress/cube DETAIL: A cube cannot have more than 100 dimensions. 2025-11-30 18:45:02.704 UTC client backend[43938] pg_regress/cube STATEMENT: select '(0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0),(0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0)'::cube; 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube ERROR: array is too long 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube DETAIL: A cube cannot have more than 100 dimensions. 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube STATEMENT: select cube(array(SELECT 0 as a FROM generate_series(1,101))); 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube ERROR: can't extend cube 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube DETAIL: A cube cannot have more than 100 dimensions. 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube STATEMENT: select cube(array(SELECT 0 as a FROM generate_series(1,101)),array(SELECT 0 as a FROM generate_series(1,101))); 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube ERROR: can't extend cube 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube DETAIL: A cube cannot have more than 100 dimensions. 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube STATEMENT: select cube(cube(array(SELECT 0 as a FROM generate_series(1,100))), 0); 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube ERROR: can't extend cube 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube DETAIL: A cube cannot have more than 100 dimensions. 2025-11-30 18:45:02.705 UTC client backend[43938] pg_regress/cube STATEMENT: select cube(cube(array(SELECT 0 as a FROM generate_series(1,100)),array(SELECT 0 as a FROM generate_series(1,100))), 0, 0); 2025-11-30 18:45:02.711 UTC unrecognized[43945] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.711 UTC client backend[43945] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.711 UTC client backend[43945] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/time 2025-11-30 18:45:02.712 UTC unrecognized[43943] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.712 UTC client backend[43943] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.712 UTC client backend[43943] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/cidr 2025-11-30 18:45:02.712 UTC client backend[43945] pg_regress/time LOG: connection ready: setup total=1.898 ms, fork=0.386 ms, authentication=0.107 ms 2025-11-30 18:45:02.713 UTC client backend[43943] pg_regress/cidr LOG: connection ready: setup total=6.740 ms, fork=5.219 ms, authentication=0.093 ms 2025-11-30 18:45:02.725 UTC client backend[43943] pg_regress/cidr LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.740 UTC client backend[43887] pg_regress/timestamptz ERROR: time zone "america/does_not_exist" not recognized at character 37 2025-11-30 18:45:02.740 UTC client backend[43887] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2025-11-30 18:45:02.741 UTC client backend[43887] pg_regress/timestamptz ERROR: time zone "America/Does_not_exist" not recognized 2025-11-30 18:45:02.741 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT '19970710 173201' AT TIME ZONE 'America/Does_not_exist'; 2025-11-30 18:45:02.743 UTC client backend[43747] pg_regress/plpgsql_trap ERROR: end of function 2025-11-30 18:45:02.743 UTC client backend[43747] pg_regress/plpgsql_trap CONTEXT: PL/pgSQL function trap_timeout() line 15 at RAISE 2025-11-30 18:45:02.743 UTC client backend[43747] pg_regress/plpgsql_trap STATEMENT: select trap_timeout(); 2025-11-30 18:45:02.743 UTC unrecognized[43946] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.743 UTC client backend[43946] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.743 UTC client backend[43946] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.744 UTC client backend[43946] pg_regress LOG: connection ready: setup total=22.097 ms, fork=20.770 ms, authentication=0.114 ms 2025-11-30 18:45:02.748 UTC client backend[43946] pg_regress LOG: disconnection: session time: 0:00:00.004 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.748 UTC unrecognized[43949] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.748 UTC client backend[43949] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.748 UTC client backend[43949] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/text 2025-11-30 18:45:02.748 UTC client backend[43887] pg_regress/timestamptz ERROR: invalid input syntax for type timestamp with time zone: "Jan 01 00:00:00 2024 LMT" at character 8 2025-11-30 18:45:02.748 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT 'Jan 01 00:00:00 2024 LMT'::timestamptz; 2025-11-30 18:45:02.749 UTC client backend[43949] pg_regress/text LOG: connection ready: setup total=5.456 ms, fork=4.114 ms, authentication=0.091 ms 2025-11-30 18:45:02.754 UTC client backend[43889] pg_regress/timestamp ERROR: time zone "america/does_not_exist" not recognized at character 35 2025-11-30 18:45:02.754 UTC client backend[43889] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2025-11-30 18:45:02.755 UTC unrecognized[43951] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.755 UTC client backend[43945] pg_regress/time LOG: disconnection: session time: 0:00:00.044 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.755 UTC client backend[43951] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.755 UTC client backend[43951] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.756 UTC client backend[43951] pg_regress LOG: connection ready: setup total=2.897 ms, fork=1.388 ms, authentication=0.094 ms 2025-11-30 18:45:02.759 UTC client backend[43938] pg_regress/cube ERROR: cube index 0 is out of bounds 2025-11-30 18:45:02.759 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube(array[10,20,30], array[40,50,60])->0; 2025-11-30 18:45:02.759 UTC client backend[43938] pg_regress/cube ERROR: cube index 7 is out of bounds 2025-11-30 18:45:02.759 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube(array[10,20,30], array[40,50,60])->7; 2025-11-30 18:45:02.759 UTC client backend[43938] pg_regress/cube ERROR: cube index -1 is out of bounds 2025-11-30 18:45:02.759 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube(array[10,20,30], array[40,50,60])->-1; 2025-11-30 18:45:02.760 UTC client backend[43938] pg_regress/cube ERROR: cube index -6 is out of bounds 2025-11-30 18:45:02.760 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube(array[10,20,30], array[40,50,60])->-6; 2025-11-30 18:45:02.760 UTC client backend[43938] pg_regress/cube ERROR: cube index -6 is out of bounds 2025-11-30 18:45:02.760 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube(array[10,20,30])->-6; 2025-11-30 18:45:02.760 UTC client backend[43938] pg_regress/cube ERROR: zero cube index is not defined 2025-11-30 18:45:02.760 UTC client backend[43938] pg_regress/cube STATEMENT: SELECT cube(array[40,50,60], array[10,20,30])~>0; 2025-11-30 18:45:02.765 UTC unrecognized[43954] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.765 UTC client backend[43954] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.765 UTC client backend[43954] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/timetz 2025-11-30 18:45:02.767 UTC client backend[43954] pg_regress/timetz LOG: connection ready: setup total=4.966 ms, fork=2.434 ms, authentication=0.111 ms 2025-11-30 18:45:02.768 UTC client backend[43887] pg_regress/timestamptz ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 37 2025-11-30 18:45:02.768 UTC client backend[43887] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 29 17:32:01 1997'); 2025-11-30 18:45:02.768 UTC client backend[43889] pg_regress/timestamp ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 35 2025-11-30 18:45:02.768 UTC client backend[43889] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 29 17:32:01 1997'); 2025-11-30 18:45:02.769 UTC client backend[43887] pg_regress/timestamptz ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 37 2025-11-30 18:45:02.769 UTC client backend[43887] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 -0097'); 2025-11-30 18:45:02.769 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 37 2025-11-30 18:45:02.769 UTC client backend[43887] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2025-11-30 18:45:02.769 UTC client backend[43889] pg_regress/timestamp ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 35 2025-11-30 18:45:02.769 UTC client backend[43889] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 -0097'); 2025-11-30 18:45:02.769 UTC client backend[43889] pg_regress/timestamp ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 35 2025-11-30 18:45:02.769 UTC client backend[43889] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2025-11-30 18:45:02.770 UTC client backend[43889] pg_regress/timestamp ERROR: timestamp out of range: "4714-11-23 23:59:59 BC" at character 8 2025-11-30 18:45:02.770 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT '4714-11-23 23:59:59 BC'::timestamp; 2025-11-30 18:45:02.770 UTC client backend[43889] pg_regress/timestamp ERROR: timestamp out of range: "294277-01-01 00:00:00" at character 8 2025-11-30 18:45:02.770 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT '294277-01-01 00:00:00'::timestamp; 2025-11-30 18:45:02.770 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamp out of range: "4714-11-23 23:59:59+00 BC" at character 8 2025-11-30 18:45:02.770 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT '4714-11-23 23:59:59+00 BC'::timestamptz; 2025-11-30 18:45:02.770 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamp out of range: "294277-01-01 00:00:00+00" at character 8 2025-11-30 18:45:02.770 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT '294277-01-01 00:00:00+00'::timestamptz; 2025-11-30 18:45:02.770 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamp out of range: "294277-12-31 16:00:00-08" at character 8 2025-11-30 18:45:02.770 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT '294277-12-31 16:00:00-08'::timestamptz; 2025-11-30 18:45:02.772 UTC client backend[43889] pg_regress/timestamp ERROR: unit "timezone" not supported for type timestamp without time zone 2025-11-30 18:45:02.772 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT date_trunc( 'timezone', timestamp '2004-02-29 15:44:17.71393' ) AS notsupp_trunc; 2025-11-30 18:45:02.772 UTC client backend[43889] pg_regress/timestamp ERROR: unit "timezone" not supported for type timestamp without time zone 2025-11-30 18:45:02.772 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT date_trunc( 'timezone', timestamp 'infinity' ) AS notsupp_inf_trunc; 2025-11-30 18:45:02.772 UTC client backend[43889] pg_regress/timestamp ERROR: unit "ago" not recognized for type timestamp without time zone 2025-11-30 18:45:02.772 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT date_trunc( 'ago', timestamp 'infinity' ) AS invalid_trunc; 2025-11-30 18:45:02.772 UTC client backend[43887] pg_regress/timestamptz ERROR: unit "timezone" not supported for type timestamp with time zone 2025-11-30 18:45:02.772 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_trunc( 'timezone', timestamp with time zone '2004-02-29 15:44:17.71393' ) AS notsupp_trunc; 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz ERROR: unit "timezone" not supported for type timestamp with time zone 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_trunc( 'timezone', timestamp with time zone 'infinity' ) AS notsupp_inf_trunc; 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz ERROR: unit "ago" not recognized for type timestamp with time zone 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_trunc( 'ago', timestamp with time zone 'infinity' ) AS invalid_trunc; 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz ERROR: unit "timezone" not supported for type timestamp with time zone 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_trunc('timezone', timestamp with time zone 'infinity', 'GMT') AS notsupp_zone_trunc; 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz ERROR: unit "ago" not recognized for type timestamp with time zone 2025-11-30 18:45:02.773 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_trunc('ago', timestamp with time zone 'infinity', 'GMT') AS invalid_zone_trunc; 2025-11-30 18:45:02.773 UTC client backend[43889] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-30 18:45:02.773 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT date_bin('5 months'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2025-11-30 18:45:02.773 UTC client backend[43889] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-30 18:45:02.773 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT date_bin('5 years'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp ERROR: stride must be greater than zero 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT date_bin('0 days'::interval, timestamp '1970-01-01 01:00:00' , timestamp '1970-01-01 00:00:00'); 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp ERROR: stride must be greater than zero 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT date_bin('-2 days'::interval, timestamp '1970-01-01 01:00:00' , timestamp '1970-01-01 00:00:00'); 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp ERROR: interval out of range 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp STATEMENT: select date_bin('15 minutes'::interval, timestamp '294276-12-30', timestamp '4000-12-20 BC'); 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp ERROR: interval out of range 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamp, '2024-01-01'::timestamp); 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp ERROR: timestamp out of range 2025-11-30 18:45:02.774 UTC client backend[43889] pg_regress/timestamp STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamp, '4000-01-01 BC'::timestamp); 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_bin('5 months'::interval, timestamp with time zone '2020-02-01 01:01:01+00', timestamp with time zone '2001-01-01+00'); 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_bin('5 years'::interval, timestamp with time zone '2020-02-01 01:01:01+00', timestamp with time zone '2001-01-01+00'); 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz ERROR: stride must be greater than zero 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_bin('0 days'::interval, timestamp with time zone '1970-01-01 01:00:00+00' , timestamp with time zone '1970-01-01 00:00:00+00'); 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz ERROR: stride must be greater than zero 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT date_bin('-2 days'::interval, timestamp with time zone '1970-01-01 01:00:00+00' , timestamp with time zone '1970-01-01 00:00:00+00'); 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz ERROR: interval out of range 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz STATEMENT: select date_bin('15 minutes'::interval, timestamptz '294276-12-30', timestamptz '4000-12-20 BC'); 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz ERROR: interval out of range 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamptz, '2024-01-01'::timestamptz); 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamp out of range 2025-11-30 18:45:02.775 UTC client backend[43887] pg_regress/timestamptz STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamptz, '4000-01-01 BC'::timestamptz); 2025-11-30 18:45:02.778 UTC client backend[43889] pg_regress/timestamp ERROR: interval out of range 2025-11-30 18:45:02.778 UTC client backend[43889] pg_regress/timestamp STATEMENT: SELECT timestamp '294276-12-31 23:59:59' - timestamp '1999-12-23 19:59:04.224192' AS overflows; 2025-11-30 18:45:02.779 UTC client backend[43887] pg_regress/timestamptz ERROR: interval out of range 2025-11-30 18:45:02.779 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT timestamptz '294276-12-31 23:59:59 UTC' - timestamptz '1999-12-23 19:59:04.224192 UTC' AS overflows; 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp ERROR: date field value out of range: 0-07-15 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp STATEMENT: select make_timestamp(0, 7, 15, 12, 30, 15); 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp ERROR: step size cannot equal zero 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamp, '2020-01-02 03:00'::timestamp, '0 hour'::interval); 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp ERROR: step size cannot be infinite 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval 'infinity'); 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp ERROR: step size cannot be infinite 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval '-infinity'); 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp ERROR: interval out of range 2025-11-30 18:45:02.783 UTC client backend[43889] pg_regress/timestamp STATEMENT: select timestamp 'infinity' - timestamp 'infinity'; 2025-11-30 18:45:02.784 UTC client backend[43889] pg_regress/timestamp ERROR: interval out of range 2025-11-30 18:45:02.784 UTC client backend[43889] pg_regress/timestamp STATEMENT: select timestamp '-infinity' - timestamp '-infinity'; 2025-11-30 18:45:02.784 UTC client backend[43889] pg_regress/timestamp ERROR: interval out of range 2025-11-30 18:45:02.784 UTC client backend[43889] pg_regress/timestamp STATEMENT: select age(timestamp 'infinity', timestamp 'infinity'); 2025-11-30 18:45:02.784 UTC client backend[43889] pg_regress/timestamp ERROR: interval out of range 2025-11-30 18:45:02.784 UTC client backend[43889] pg_regress/timestamp STATEMENT: select age(timestamp '-infinity', timestamp '-infinity'); 2025-11-30 18:45:02.785 UTC client backend[43889] pg_regress/timestamp LOG: disconnection: session time: 0:00:00.460 user=postgres database=regression host=[local] 2025-11-30 18:45:02.789 UTC client backend[43887] pg_regress/timestamptz ERROR: invalid input syntax for type numeric time zone: "2" 2025-11-30 18:45:02.789 UTC client backend[43887] pg_regress/timestamptz HINT: Numeric time zones must have "-" or "+" as first character. 2025-11-30 18:45:02.789 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1973, 07, 15, 08, 15, 55.33, '2'); 2025-11-30 18:45:02.789 UTC client backend[43887] pg_regress/timestamptz ERROR: numeric time zone "+16" out of range 2025-11-30 18:45:02.789 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '+16'); 2025-11-30 18:45:02.789 UTC client backend[43887] pg_regress/timestamptz ERROR: numeric time zone "-16" out of range 2025-11-30 18:45:02.789 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '-16'); 2025-11-30 18:45:02.789 UTC client backend[43951] pg_regress LOG: disconnection: session time: 0:00:00.034 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.789 UTC client backend[43954] pg_regress/timetz LOG: disconnection: session time: 0:00:00.024 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.790 UTC client backend[43887] pg_regress/timestamptz ERROR: time zone "Nehwon/Lankhmar" not recognized 2025-11-30 18:45:02.790 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1910, 12, 24, 0, 0, 0, 'Nehwon/Lankhmar'); 2025-11-30 18:45:02.791 UTC client backend[43887] pg_regress/timestamptz ERROR: step size cannot equal zero 2025-11-30 18:45:02.791 UTC client backend[43887] pg_regress/timestamptz STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamptz, '2020-01-02 03:00'::timestamptz, '0 hour'::interval); 2025-11-30 18:45:02.791 UTC client backend[43887] pg_regress/timestamptz ERROR: step size cannot be infinite 2025-11-30 18:45:02.791 UTC client backend[43887] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval 'infinity'); 2025-11-30 18:45:02.791 UTC client backend[43887] pg_regress/timestamptz ERROR: step size cannot be infinite 2025-11-30 18:45:02.791 UTC client backend[43887] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval '-infinity'); 2025-11-30 18:45:02.791 UTC client backend[43949] pg_regress/text LOG: disconnection: session time: 0:00:00.043 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.797 UTC client backend[43887] pg_regress/timestamptz ERROR: timestamp cannot be NaN 2025-11-30 18:45:02.797 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT to_timestamp('NaN'::float); 2025-11-30 18:45:02.798 UTC unrecognized[43957] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.798 UTC client backend[43957] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.798 UTC client backend[43957] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/varchar 2025-11-30 18:45:02.799 UTC client backend[43957] pg_regress/varchar LOG: connection ready: setup total=1.888 ms, fork=0.400 ms, authentication=0.121 ms 2025-11-30 18:45:02.811 UTC client backend[43887] pg_regress/timestamptz ERROR: interval out of range 2025-11-30 18:45:02.811 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT timestamptz 'infinity' - timestamptz 'infinity'; 2025-11-30 18:45:02.812 UTC client backend[43887] pg_regress/timestamptz ERROR: interval out of range 2025-11-30 18:45:02.812 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT timestamptz '-infinity' - timestamptz '-infinity'; 2025-11-30 18:45:02.812 UTC client backend[43887] pg_regress/timestamptz ERROR: interval out of range 2025-11-30 18:45:02.812 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz 'infinity', timestamptz 'infinity'); 2025-11-30 18:45:02.812 UTC client backend[43887] pg_regress/timestamptz ERROR: interval out of range 2025-11-30 18:45:02.812 UTC client backend[43887] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz '-infinity', timestamptz '-infinity'); 2025-11-30 18:45:02.814 UTC client backend[43887] pg_regress/timestamptz LOG: disconnection: session time: 0:00:00.490 user=postgres database=regression host=[local] 2025-11-30 18:45:02.821 UTC client backend[43957] pg_regress/varchar LOG: disconnection: session time: 0:00:00.023 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.823 UTC unrecognized[43963] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.824 UTC client backend[43963] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.824 UTC client backend[43963] [unknown] LOG: connection authorized: user=postgres database=regression_dblink application_name=pg_regress/dblink 2025-11-30 18:45:02.828 UTC client backend[43963] pg_regress/dblink LOG: connection ready: setup total=5.281 ms, fork=0.278 ms, authentication=0.103 ms 2025-11-30 18:45:02.830 UTC unrecognized[43962] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.830 UTC client backend[43962] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.830 UTC client backend[43962] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/date 2025-11-30 18:45:02.831 UTC client backend[43962] pg_regress/date LOG: connection ready: setup total=8.502 ms, fork=7.010 ms, authentication=0.103 ms 2025-11-30 18:45:02.840 UTC client backend[43881] pg_regress/multirangetypes ERROR: value for domain restrictedmultirange violates check constraint "restrictedmultirange_check" 2025-11-30 18:45:02.840 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select '{[4,50)}'::restrictedmultirange @> 7; 2025-11-30 18:45:02.842 UTC client backend[43962] pg_regress/date LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.846 UTC client backend[43881] pg_regress/multirangetypes ERROR: type "intmultirange" already exists 2025-11-30 18:45:02.846 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intrange". 2025-11-30 18:45:02.846 UTC client backend[43881] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2025-11-30 18:45:02.846 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create type intrange as range(subtype=int); 2025-11-30 18:45:02.852 UTC client backend[43881] pg_regress/multirangetypes ERROR: type "intr_multirange" already exists 2025-11-30 18:45:02.852 UTC client backend[43881] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intr". 2025-11-30 18:45:02.852 UTC client backend[43881] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2025-11-30 18:45:02.852 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create type intr as range(subtype=int); 2025-11-30 18:45:02.853 UTC unrecognized[43967] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.853 UTC client backend[43967] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.853 UTC client backend[43967] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/interval 2025-11-30 18:45:02.853 UTC client backend[43881] pg_regress/multirangetypes ERROR: type "int4" already exists 2025-11-30 18:45:02.853 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create type textrange1 as range(subtype=text, multirange_type_name=int, collation="C"); 2025-11-30 18:45:02.854 UTC client backend[43967] pg_regress/interval LOG: connection ready: setup total=2.930 ms, fork=1.438 ms, authentication=0.107 ms 2025-11-30 18:45:02.854 UTC client backend[43963] pg_regress/dblink ERROR: invalid attribute number 4 2025-11-30 18:45:02.854 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_build_sql_insert('foo','1 2 3 4',4,'{"0", "a", "{a0,b0,c0}"}','{"99", "xyz", "{za0,zb0,zc0}"}'); 2025-11-30 18:45:02.855 UTC client backend[43963] pg_regress/dblink ERROR: invalid attribute number 4 2025-11-30 18:45:02.855 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_build_sql_update('foo','1 2 3 4',4,'{"0", "a", "{a0,b0,c0}"}','{"99", "xyz", "{za0,zb0,zc0}"}'); 2025-11-30 18:45:02.855 UTC client backend[43963] pg_regress/dblink ERROR: invalid attribute number 4 2025-11-30 18:45:02.855 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_build_sql_delete('foo','1 2 3 4',4,'{"0", "a", "{a0,b0,c0}"}'); 2025-11-30 18:45:02.859 UTC client backend[43938] pg_regress/cube LOG: disconnection: session time: 0:00:00.205 user=postgres database=regression_cube host=[local] 2025-11-30 18:45:02.859 UTC unrecognized[43968] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.859 UTC client backend[43968] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.859 UTC client backend[43968] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/char 2025-11-30 18:45:02.860 UTC client backend[43881] pg_regress/multirangetypes ERROR: function multirange_of_text(textrange2) does not exist at character 8 2025-11-30 18:45:02.860 UTC client backend[43881] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:02.860 UTC client backend[43881] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:02.860 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange2('a','Z')); 2025-11-30 18:45:02.860 UTC client backend[43968] pg_regress/char LOG: connection ready: setup total=2.095 ms, fork=0.698 ms, authentication=0.098 ms 2025-11-30 18:45:02.860 UTC client backend[43881] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-30 18:45:02.860 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange1('a','Z')) @> 'b'::text; 2025-11-30 18:45:02.862 UTC client backend[43747] pg_regress/plpgsql_trap ERROR: insert or update on table "leaf" violates foreign key constraint "leaf_f1_fkey" 2025-11-30 18:45:02.862 UTC client backend[43747] pg_regress/plpgsql_trap DETAIL: Key (f1)=(2) is not present in table "root". 2025-11-30 18:45:02.862 UTC client backend[43747] pg_regress/plpgsql_trap STATEMENT: insert into leaf values(2); 2025-11-30 18:45:02.864 UTC client backend[43747] pg_regress/plpgsql_trap ERROR: insert or update on table "leaf" violates foreign key constraint "leaf_f1_fkey" 2025-11-30 18:45:02.864 UTC client backend[43747] pg_regress/plpgsql_trap DETAIL: Key (f1)=(2) is not present in table "root". 2025-11-30 18:45:02.864 UTC client backend[43747] pg_regress/plpgsql_trap STATEMENT: set constraints all immediate; 2025-11-30 18:45:02.865 UTC client backend[43747] pg_regress/plpgsql_trap ERROR: insert or update on table "leaf" violates foreign key constraint "leaf_f1_fkey" 2025-11-30 18:45:02.865 UTC client backend[43747] pg_regress/plpgsql_trap DETAIL: Key (f1)=(2) is not present in table "root". 2025-11-30 18:45:02.865 UTC client backend[43747] pg_regress/plpgsql_trap STATEMENT: commit; 2025-11-30 18:45:02.866 UTC client backend[43968] pg_regress/char LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.868 UTC client backend[43747] pg_regress/plpgsql_trap LOG: disconnection: session time: 0:00:01.159 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:02.870 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot alter multirange type multitextrange1 2025-11-30 18:45:02.870 UTC client backend[43881] pg_regress/multirangetypes HINT: You can alter type textrange1, which will alter the multirange type as well. 2025-11-30 18:45:02.870 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: alter type multitextrange1 owner to regress_multirange_owner; 2025-11-30 18:45:02.873 UTC client backend[43963] pg_regress/dblink ERROR: invalid attribute number 4 2025-11-30 18:45:02.873 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_build_sql_insert('foo_1','1 2 3 4',4,'{"0", "a", "{a0,b0,c0}"}','{"99", "xyz", "{za0,zb0,zc0}"}'); 2025-11-30 18:45:02.873 UTC client backend[43963] pg_regress/dblink ERROR: invalid attribute number 4 2025-11-30 18:45:02.873 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_build_sql_update('foo_1','1 2 3 4',4,'{"0", "a", "{a0,b0,c0}"}','{"99", "xyz", "{za0,zb0,zc0}"}'); 2025-11-30 18:45:02.873 UTC client backend[43963] pg_regress/dblink ERROR: invalid attribute number 4 2025-11-30 18:45:02.873 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_build_sql_delete('foo_1','1 2 3 4',4,'{"0", "a", "{a0,b0,c0}"}'); 2025-11-30 18:45:02.873 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot set privileges of multirange types 2025-11-30 18:45:02.873 UTC client backend[43881] pg_regress/multirangetypes HINT: Set the privileges of the range type instead. 2025-11-30 18:45:02.873 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: revoke usage on type multitextrange1 from public; 2025-11-30 18:45:02.874 UTC unrecognized[43975] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.874 UTC client backend[43975] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.874 UTC client backend[43975] [unknown] LOG: connection authorized: user=postgres database=regression_cube application_name=pg_regress/cube_sci 2025-11-30 18:45:02.875 UTC client backend[43975] pg_regress/cube_sci LOG: connection ready: setup total=2.131 ms, fork=0.649 ms, authentication=0.115 ms 2025-11-30 18:45:02.877 UTC unrecognized[43976] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.877 UTC client backend[43975] pg_regress/cube_sci LOG: disconnection: session time: 0:00:00.003 user=postgres database=regression_cube host=[local] 2025-11-30 18:45:02.877 UTC client backend[43976] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.877 UTC client backend[43976] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/bytea 2025-11-30 18:45:02.878 UTC client backend[43976] pg_regress/bytea LOG: connection ready: setup total=4.698 ms, fork=2.689 ms, authentication=0.112 ms 2025-11-30 18:45:02.885 UTC client backend[43976] pg_regress/bytea LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.889 UTC unrecognized[43979] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.889 UTC unrecognized[43978] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.889 UTC client backend[43979] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.889 UTC client backend[43979] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:02.890 UTC client backend[43978] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.890 UTC client backend[43978] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_trigger 2025-11-30 18:45:02.890 UTC client backend[43979] [unknown] LOG: connection ready: setup total=6.838 ms, fork=5.267 ms, authentication=0.123 ms 2025-11-30 18:45:02.891 UTC client backend[43978] pg_regress/plpgsql_trigger LOG: connection ready: setup total=12.443 ms, fork=8.337 ms, authentication=0.101 ms 2025-11-30 18:45:02.891 UTC client backend[43881] pg_regress/multirangetypes ERROR: permission denied for type multitextrange1 2025-11-30 18:45:02.891 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create temp table test2(f1 multitextrange1[]); 2025-11-30 18:45:02.893 UTC unrecognized[43983] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.893 UTC client backend[43983] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.893 UTC client backend[43983] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/bit 2025-11-30 18:45:02.894 UTC client backend[43979] [unknown] LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:02.894 UTC client backend[43983] pg_regress/bit LOG: connection ready: setup total=1.756 ms, fork=0.419 ms, authentication=0.093 ms 2025-11-30 18:45:02.895 UTC client backend[43963] pg_regress/dblink ERROR: connection not available 2025-11-30 18:45:02.895 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT * FROM dblink('SELECT * FROM foo') AS t(a int, b text, c text[]) WHERE t.a > 7; 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes ERROR: function anyarray_anymultirange_func(integer[], nummultirange) does not exist at character 8 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select anyarray_anymultirange_func(ARRAY[1,2], nummultirange(numrange(10,20))); 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create function bogus_func(anyelement) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:02.896 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create function bogus_func(int) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2025-11-30 18:45:02.897 UTC client backend[43978] pg_regress/plpgsql_trigger LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes ERROR: function multirangetypes_sql(nummultirange, integer[]) does not exist at character 8 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select multirangetypes_sql(nummultirange(numrange(1,10)), ARRAY[2,20]); 2025-11-30 18:45:02.898 UTC unrecognized[43984] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.898 UTC client backend[43984] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.898 UTC client backend[43984] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes ERROR: function anycompatiblearray_anycompatiblemultirange_func(numeric[], int4multirange) does not exist at character 8 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:02.898 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select anycompatiblearray_anycompatiblemultirange_func(ARRAY[1.1,2], multirange(int4range(10,20))); 2025-11-30 18:45:02.899 UTC client backend[43984] [unknown] LOG: connection ready: setup total=2.841 ms, fork=0.338 ms, authentication=0.096 ms 2025-11-30 18:45:02.899 UTC client backend[43881] pg_regress/multirangetypes ERROR: function anycompatiblerange_anycompatiblemultirange_func(numrange, int4multirange) does not exist at character 8 2025-11-30 18:45:02.899 UTC client backend[43881] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:02.899 UTC client backend[43881] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:02.899 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select anycompatiblerange_anycompatiblemultirange_func(numrange(1,2), multirange(int4range(10,20))); 2025-11-30 18:45:02.900 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-30 18:45:02.900 UTC client backend[43881] pg_regress/multirangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-30 18:45:02.900 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2025-11-30 18:45:02.904 UTC client backend[43881] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-30 18:45:02.904 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: select arraymultirange(arrayrange(ARRAY[2,1], ARRAY[1,2])); 2025-11-30 18:45:02.905 UTC unrecognized[43988] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.906 UTC unrecognized[43987] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.906 UTC client backend[43988] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.906 UTC client backend[43988] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:02.906 UTC client backend[43987] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.906 UTC client backend[43987] [unknown] LOG: connection authorized: user=postgres database=regression_plpgsql application_name=pg_regress/plpgsql_varprops 2025-11-30 18:45:02.906 UTC client backend[43988] [unknown] LOG: connection ready: setup total=2.801 ms, fork=1.487 ms, authentication=0.104 ms 2025-11-30 18:45:02.907 UTC client backend[43983] pg_regress/bit LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.907 UTC client backend[43988] [unknown] LOG: disconnection: session time: 0:00:00.001 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:02.907 UTC client backend[43987] pg_regress/plpgsql_varprops LOG: connection ready: setup total=3.549 ms, fork=2.231 ms, authentication=0.090 ms 2025-11-30 18:45:02.907 UTC client backend[43984] [unknown] LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:02.910 UTC client backend[43967] pg_regress/interval LOG: disconnection: session time: 0:00:00.057 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.911 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 39 2025-11-30 18:45:02.911 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x constant int; begin x := 42; -- fail end$$; 2025-11-30 18:45:02.911 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 50 2025-11-30 18:45:02.911 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x constant int; y int; begin for x, y in select 1, 2 loop -- fail end loop; end$$; 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 41 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x constant int[]; begin x[1] := 42; -- fail end$$; 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: syntax error at or near "[" at character 53 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x constant int[]; y int; begin for x[1], y in select 1, 2 loop -- fail (currently, unsupported syntax) end loop; end$$; 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 46 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x constant var_record; begin x.f1 := 42; -- fail end$$; 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" is declared CONSTANT at character 57 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x constant var_record; y int; begin for x.f1, y in select 1, 2 loop -- fail end loop; end$$; 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: division by zero 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL expression "1/0" PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.912 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x int := 1/0; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" must have a default value, since it's declared NOT NULL at character 21 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x int not null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x int not null := 42; begin raise notice 'x = %', x; x := null; -- fail end$$; 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x int not null := null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" must have a default value, since it's declared NOT NULL at character 24 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x record not null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment 2025-11-30 18:45:02.913 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x record not null := row(42); begin raise notice 'x = %', x; x := row(null); -- ok raise notice 'x = %', x; x := null; -- fail end$$; 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x record not null := null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: variable "x" must have a default value, since it's declared NOT NULL at character 28 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record not null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 7 at assignment 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record not null := row(41,42); begin raise notice 'x = %', x; x := row(null,null); -- ok raise notice 'x = %', x; x := null; -- fail end$$; 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: null value cannot be assigned to variable "x" declared NOT NULL 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.914 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record not null := null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: domain int_nn does not allow null values 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x int_nn; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: domain int_nn does not allow null values 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x int_nn := null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: domain int_nn does not allow null values 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x int_nn := 42; begin raise notice 'x = %', x; x := null; -- fail end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: domain var_record_nn does not allow null values 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_nn; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: domain var_record_nn does not allow null values 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_nn := null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: domain var_record_nn does not allow null values 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 6 at assignment 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_nn := row(1,2); begin raise notice 'x = %', x; x := row(null,null); -- ok x := null; -- fail end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check" 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_colnn; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check" 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_colnn := null; -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check" 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:02.915 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_colnn := row(1,null); -- fail begin raise notice 'x = %', x; end$$; 2025-11-30 18:45:02.916 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check" 2025-11-30 18:45:02.916 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment 2025-11-30 18:45:02.916 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_colnn := row(1,2); begin raise notice 'x = %', x; x := null; -- fail end$$; 2025-11-30 18:45:02.916 UTC client backend[43987] pg_regress/plpgsql_varprops ERROR: value for domain var_record_colnn violates check constraint "var_record_colnn_check" 2025-11-30 18:45:02.916 UTC client backend[43987] pg_regress/plpgsql_varprops CONTEXT: PL/pgSQL function inline_code_block line 5 at assignment 2025-11-30 18:45:02.916 UTC client backend[43987] pg_regress/plpgsql_varprops STATEMENT: do $$ declare x var_record_colnn := row(1,2); begin raise notice 'x = %', x; x := row(null,null); -- fail end$$; 2025-11-30 18:45:02.916 UTC client backend[43987] pg_regress/plpgsql_varprops LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_plpgsql host=[local] 2025-11-30 18:45:02.918 UTC unrecognized[43992] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.919 UTC client backend[43992] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.919 UTC client backend[43992] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/varbit 2025-11-30 18:45:02.920 UTC client backend[43992] pg_regress/varbit LOG: connection ready: setup total=4.274 ms, fork=2.709 ms, authentication=0.106 ms 2025-11-30 18:45:02.921 UTC unrecognized[43995] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.921 UTC client backend[43995] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.921 UTC client backend[43995] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/macaddr 2025-11-30 18:45:02.922 UTC client backend[43995] pg_regress/macaddr LOG: connection ready: setup total=1.751 ms, fork=0.352 ms, authentication=0.095 ms 2025-11-30 18:45:02.932 UTC client backend[43992] pg_regress/varbit LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.933 UTC client backend[43995] pg_regress/macaddr LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.936 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-30 18:45:02.936 UTC client backend[43881] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:02.936 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create function mr_outparam_fail(i anyelement, out r anymultirange, out t text) as $$ select '[1,10]', 'foo' $$ language sql; 2025-11-30 18:45:02.938 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-30 18:45:02.938 UTC client backend[43881] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:02.938 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create function mr_inoutparam_fail(inout i anyelement, out r anymultirange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-30 18:45:02.938 UTC client backend[43881] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-30 18:45:02.938 UTC client backend[43881] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:02.938 UTC client backend[43881] pg_regress/multirangetypes STATEMENT: create function mr_table_fail(i anyelement) returns table(i anyelement, r anymultirange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-30 18:45:02.939 UTC unrecognized[44002] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.939 UTC client backend[44002] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.939 UTC client backend[44002] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/macaddr8 2025-11-30 18:45:02.940 UTC client backend[44002] pg_regress/macaddr8 LOG: connection ready: setup total=2.025 ms, fork=0.485 ms, authentication=0.112 ms 2025-11-30 18:45:02.940 UTC client backend[43881] pg_regress/multirangetypes LOG: disconnection: session time: 0:00:00.619 user=postgres database=regression host=[local] 2025-11-30 18:45:02.947 UTC unrecognized[44004] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.948 UTC client backend[44004] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.948 UTC client backend[44004] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/numeric 2025-11-30 18:45:02.949 UTC client backend[44004] pg_regress/numeric LOG: connection ready: setup total=6.900 ms, fork=5.409 ms, authentication=0.100 ms 2025-11-30 18:45:02.951 UTC client backend[44002] pg_regress/macaddr8 LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.959 UTC client backend[44004] pg_regress/numeric LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:02.959 UTC unrecognized[44015] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.959 UTC client backend[44015] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.959 UTC client backend[44015] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/inet 2025-11-30 18:45:02.960 UTC client backend[44015] pg_regress/inet LOG: connection ready: setup total=1.717 ms, fork=0.290 ms, authentication=0.110 ms 2025-11-30 18:45:02.962 UTC unrecognized[44016] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.962 UTC unrecognized[44013] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.962 UTC client backend[44016] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.962 UTC client backend[44016] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:02.962 UTC client backend[44013] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.962 UTC client backend[44013] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.963 UTC client backend[44013] pg_regress LOG: connection ready: setup total=4.655 ms, fork=3.501 ms, authentication=0.089 ms 2025-11-30 18:45:02.963 UTC client backend[44016] [unknown] LOG: connection ready: setup total=1.606 ms, fork=0.302 ms, authentication=0.095 ms 2025-11-30 18:45:02.965 UTC client backend[44016] [unknown] ERROR: relation "foobar" does not exist at character 49 2025-11-30 18:45:02.965 UTC client backend[44016] [unknown] STATEMENT: DECLARE rmt_foo_cursor CURSOR FOR SELECT * FROM foobar 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] ERROR: cursor "rmt_foobar_cursor" does not exist 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] STATEMENT: FETCH 4 FROM rmt_foobar_cursor 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] ERROR: cursor "rmt_foobar_cursor" does not exist 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] STATEMENT: CLOSE rmt_foobar_cursor 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] ERROR: cursor "rmt_foo_cursor" does not exist 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] STATEMENT: FETCH 4 FROM rmt_foo_cursor 2025-11-30 18:45:02.967 UTC client backend[43963] pg_regress/dblink ERROR: cursor "rmt_foo_cursor" does not exist 2025-11-30 18:45:02.967 UTC client backend[43963] pg_regress/dblink CONTEXT: while fetching from cursor "rmt_foo_cursor" on unnamed dblink connection 2025-11-30 18:45:02.967 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT * FROM dblink_fetch('rmt_foo_cursor',4) AS t(a int, b text, c text[]); 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] ERROR: cursor "rmt_foo_cursor" does not exist 2025-11-30 18:45:02.967 UTC client backend[44016] [unknown] STATEMENT: FETCH 4 FROM rmt_foo_cursor 2025-11-30 18:45:02.968 UTC client backend[44016] [unknown] LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:02.969 UTC client backend[43963] pg_regress/dblink ERROR: connection not available 2025-11-30 18:45:02.969 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT * FROM dblink('SELECT * FROM foo') AS t(a int, b text, c text[]) WHERE t.a > 7; 2025-11-30 18:45:02.969 UTC client backend[44013] pg_regress LOG: disconnection: session time: 0:00:00.007 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.972 UTC unrecognized[44020] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.972 UTC client backend[44020] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.972 UTC client backend[44020] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:02.973 UTC client backend[44020] [unknown] LOG: connection ready: setup total=3.785 ms, fork=2.375 ms, authentication=0.100 ms 2025-11-30 18:45:02.974 UTC client backend[44020] [unknown] LOG: disconnection: session time: 0:00:00.002 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:02.975 UTC unrecognized[44025] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.975 UTC unrecognized[44026] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.975 UTC client backend[44025] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.975 UTC client backend[44025] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/enum 2025-11-30 18:45:02.975 UTC unrecognized[44027] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.975 UTC client backend[44026] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.975 UTC client backend[44026] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.975 UTC client backend[44027] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.975 UTC client backend[44027] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.976 UTC client backend[44026] pg_regress LOG: connection ready: setup total=1.724 ms, fork=0.596 ms, authentication=0.089 ms 2025-11-30 18:45:02.976 UTC client backend[44025] pg_regress/enum LOG: connection ready: setup total=3.893 ms, fork=2.335 ms, authentication=0.097 ms 2025-11-30 18:45:02.976 UTC unrecognized[44028] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.977 UTC client backend[44028] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.977 UTC client backend[44028] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:02.977 UTC client backend[44026] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.978 UTC client backend[44015] pg_regress/inet LOG: disconnection: session time: 0:00:00.019 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:02.980 UTC client backend[44028] [unknown] LOG: connection ready: setup total=5.036 ms, fork=1.406 ms, authentication=0.104 ms 2025-11-30 18:45:02.981 UTC unrecognized[44033] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.981 UTC client backend[44027] pg_regress LOG: connection ready: setup total=6.702 ms, fork=0.474 ms, authentication=0.090 ms 2025-11-30 18:45:02.981 UTC client backend[44033] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.981 UTC client backend[44033] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:02.982 UTC client backend[44033] pg_regress LOG: connection ready: setup total=1.372 ms, fork=0.274 ms, authentication=0.089 ms 2025-11-30 18:45:02.983 UTC client backend[44028] [unknown] ERROR: relation "foobar" does not exist at character 15 2025-11-30 18:45:02.983 UTC client backend[44028] [unknown] STATEMENT: SELECT * FROM foobar 2025-11-30 18:45:02.988 UTC client backend[44028] [unknown] ERROR: relation "foobar" does not exist at character 8 2025-11-30 18:45:02.988 UTC client backend[44028] [unknown] STATEMENT: UPDATE foobar SET f3[2] = 'b99' WHERE f1 = 11 2025-11-30 18:45:02.989 UTC unrecognized[44038] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.989 UTC client backend[44038] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.989 UTC client backend[44038] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/cidr 2025-11-30 18:45:02.990 UTC client backend[44038] pg_regress/cidr LOG: connection ready: setup total=2.801 ms, fork=1.295 ms, authentication=0.111 ms 2025-11-30 18:45:02.991 UTC client backend[44033] pg_regress LOG: disconnection: session time: 0:00:00.010 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.993 UTC client backend[44028] [unknown] LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:02.994 UTC client backend[43963] pg_regress/dblink ERROR: could not establish connection 2025-11-30 18:45:02.994 UTC client backend[43963] pg_regress/dblink DETAIL: missing "=" after "myconn" in connection info string 2025-11-30 18:45:02.994 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT * FROM dblink('myconn','SELECT * FROM foo') AS t(a int, b text, c text[]) WHERE t.a > 7; 2025-11-30 18:45:02.995 UTC unrecognized[44041] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:02.996 UTC client backend[44041] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:02.996 UTC client backend[44041] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:02.996 UTC client backend[44041] [unknown] LOG: connection ready: setup total=2.046 ms, fork=0.737 ms, authentication=0.103 ms 2025-11-30 18:45:02.998 UTC client backend[44041] [unknown] ERROR: relation "foobar" does not exist at character 15 2025-11-30 18:45:02.998 UTC client backend[44041] [unknown] STATEMENT: SELECT * FROM foobar 2025-11-30 18:45:02.998 UTC client backend[43963] pg_regress/dblink ERROR: duplicate connection name 2025-11-30 18:45:02.998 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_connect('myconn',connection_parameters()); 2025-11-30 18:45:02.998 UTC client backend[44027] pg_regress LOG: disconnection: session time: 0:00:00.023 user=postgres database=postgres host=[local] 2025-11-30 18:45:02.999 UTC unrecognized[44044] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.000 UTC client backend[44044] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.000 UTC client backend[44044] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.000 UTC unrecognized[44042] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.000 UTC client backend[44044] [unknown] LOG: connection ready: setup total=2.011 ms, fork=0.753 ms, authentication=0.102 ms 2025-11-30 18:45:03.001 UTC client backend[44042] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.001 UTC client backend[44042] [unknown] LOG: connection authorized: user=postgres database=regression_dict_xsyn application_name=pg_regress/dict_xsyn 2025-11-30 18:45:03.003 UTC unrecognized[44045] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.003 UTC client backend[44045] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.003 UTC client backend[44045] [unknown] LOG: connection authorized: user=postgres database=regression_dict_int application_name=pg_regress/dict_int 2025-11-30 18:45:03.004 UTC client backend[44044] [unknown] LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.005 UTC client backend[44042] pg_regress/dict_xsyn LOG: connection ready: setup total=7.486 ms, fork=1.270 ms, authentication=0.092 ms 2025-11-30 18:45:03.007 UTC client backend[44041] [unknown] ERROR: relation "foobar" does not exist at character 49 2025-11-30 18:45:03.007 UTC client backend[44041] [unknown] STATEMENT: DECLARE rmt_foo_cursor CURSOR FOR SELECT * FROM foobar 2025-11-30 18:45:03.008 UTC client backend[44045] pg_regress/dict_int LOG: connection ready: setup total=5.309 ms, fork=0.444 ms, authentication=0.090 ms 2025-11-30 18:45:03.008 UTC client backend[44038] pg_regress/cidr LOG: disconnection: session time: 0:00:00.019 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.013 UTC client backend[44041] [unknown] ERROR: DECLARE CURSOR can only be used in transaction blocks 2025-11-30 18:45:03.013 UTC client backend[44041] [unknown] STATEMENT: DECLARE xact_test CURSOR FOR SELECT * FROM foo 2025-11-30 18:45:03.013 UTC client backend[43963] pg_regress/dblink ERROR: DECLARE CURSOR can only be used in transaction blocks 2025-11-30 18:45:03.013 UTC client backend[43963] pg_regress/dblink CONTEXT: while executing command on dblink connection named "myconn" 2025-11-30 18:45:03.013 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_exec('myconn','DECLARE xact_test CURSOR FOR SELECT * FROM foo'); 2025-11-30 18:45:03.013 UTC client backend[44041] [unknown] WARNING: there is no transaction in progress 2025-11-30 18:45:03.013 UTC client backend[43963] pg_regress/dblink LOG: received message via remote connection: WARNING: there is no transaction in progress 2025-11-30 18:45:03.013 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_exec('myconn','ABORT'); 2025-11-30 18:45:03.014 UTC client backend[44041] [unknown] ERROR: cursor "rmt_foobar_cursor" does not exist 2025-11-30 18:45:03.014 UTC client backend[44041] [unknown] STATEMENT: FETCH 4 FROM rmt_foobar_cursor 2025-11-30 18:45:03.015 UTC client backend[44041] [unknown] ERROR: cursor "rmt_foo_cursor" does not exist 2025-11-30 18:45:03.015 UTC client backend[44041] [unknown] STATEMENT: FETCH 4 FROM rmt_foo_cursor 2025-11-30 18:45:03.015 UTC client backend[43963] pg_regress/dblink ERROR: cursor "rmt_foo_cursor" does not exist 2025-11-30 18:45:03.015 UTC client backend[43963] pg_regress/dblink CONTEXT: while fetching from cursor "rmt_foo_cursor" on dblink connection named "myconn" 2025-11-30 18:45:03.015 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT * FROM dblink_fetch('myconn','rmt_foo_cursor',4) AS t(a int, b text, c text[]); 2025-11-30 18:45:03.015 UTC client backend[44041] [unknown] LOG: disconnection: session time: 0:00:00.019 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.016 UTC client backend[43963] pg_regress/dblink ERROR: could not establish connection 2025-11-30 18:45:03.016 UTC client backend[43963] pg_regress/dblink DETAIL: missing "=" after "myconn" in connection info string 2025-11-30 18:45:03.016 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT * FROM dblink('myconn','SELECT * FROM foo') AS t(a int, b text, c text[]) WHERE t.a > 7; 2025-11-30 18:45:03.017 UTC unrecognized[44051] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.017 UTC client backend[44051] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.017 UTC client backend[44051] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.018 UTC client backend[44051] [unknown] LOG: connection ready: setup total=2.083 ms, fork=0.497 ms, authentication=0.101 ms 2025-11-30 18:45:03.020 UTC unrecognized[44050] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.020 UTC client backend[44050] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.020 UTC client backend[44050] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/text 2025-11-30 18:45:03.021 UTC client backend[44050] pg_regress/text LOG: connection ready: setup total=6.150 ms, fork=4.510 ms, authentication=0.096 ms 2025-11-30 18:45:03.023 UTC client backend[44051] [unknown] LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.024 UTC client backend[43963] pg_regress/dblink ERROR: connection "myconn" not available 2025-11-30 18:45:03.024 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_disconnect('myconn'); 2025-11-30 18:45:03.036 UTC unrecognized[44071] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.037 UTC client backend[44071] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.037 UTC client backend[44071] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.038 UTC client backend[44071] [unknown] LOG: connection ready: setup total=13.074 ms, fork=1.164 ms, authentication=0.134 ms 2025-11-30 18:45:03.038 UTC unrecognized[44072] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.038 UTC client backend[44072] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.038 UTC client backend[44072] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/geometry 2025-11-30 18:45:03.039 UTC client backend[44072] pg_regress/geometry LOG: connection ready: setup total=13.438 ms, fork=11.904 ms, authentication=0.095 ms 2025-11-30 18:45:03.039 UTC unrecognized[44073] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.040 UTC client backend[44073] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.040 UTC client backend[44073] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tstypes 2025-11-30 18:45:03.041 UTC client backend[44073] pg_regress/tstypes LOG: connection ready: setup total=11.337 ms, fork=8.643 ms, authentication=0.087 ms 2025-11-30 18:45:03.041 UTC unrecognized[44074] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.041 UTC client backend[44074] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.041 UTC client backend[44074] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/type_sanity 2025-11-30 18:45:03.042 UTC client backend[44074] pg_regress/type_sanity LOG: connection ready: setup total=12.419 ms, fork=8.405 ms, authentication=0.091 ms 2025-11-30 18:45:03.043 UTC unrecognized[44076] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.043 UTC client backend[44076] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.043 UTC client backend[44076] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/expressions 2025-11-30 18:45:03.044 UTC client backend[44076] pg_regress/expressions LOG: connection ready: setup total=2.437 ms, fork=0.983 ms, authentication=0.094 ms 2025-11-30 18:45:03.045 UTC unrecognized[44080] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.046 UTC client backend[44080] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.046 UTC client backend[44080] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/pg_ndistinct 2025-11-30 18:45:03.047 UTC client backend[44080] pg_regress/pg_ndistinct LOG: connection ready: setup total=3.729 ms, fork=1.593 ms, authentication=0.089 ms 2025-11-30 18:45:03.047 UTC unrecognized[44081] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.047 UTC client backend[44081] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.047 UTC client backend[44081] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats_import 2025-11-30 18:45:03.048 UTC client backend[44081] pg_regress/stats_import LOG: connection ready: setup total=4.878 ms, fork=1.439 ms, authentication=0.089 ms 2025-11-30 18:45:03.049 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "null" at character 8 2025-11-30 18:45:03.049 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Unexpected scalar. 2025-11-30 18:45:03.049 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT 'null'::pg_ndistinct; 2025-11-30 18:45:03.049 UTC unrecognized[44077] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.049 UTC client backend[44077] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.049 UTC client backend[44077] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/opr_sanity 2025-11-30 18:45:03.049 UTC unrecognized[44075] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.050 UTC client backend[44075] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.050 UTC client backend[44075] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/misc_sanity 2025-11-30 18:45:03.050 UTC client backend[44077] pg_regress/opr_sanity LOG: connection ready: setup total=7.799 ms, fork=5.569 ms, authentication=0.097 ms 2025-11-30 18:45:03.050 UTC unrecognized[44078] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.051 UTC client backend[44078] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.051 UTC client backend[44078] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/comments 2025-11-30 18:45:03.051 UTC client backend[44075] pg_regress/misc_sanity LOG: connection ready: setup total=9.227 ms, fork=7.596 ms, authentication=0.098 ms 2025-11-30 18:45:03.051 UTC unrecognized[44083] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.051 UTC client backend[44083] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.051 UTC client backend[44083] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/xid 2025-11-30 18:45:03.051 UTC client backend[44078] pg_regress/comments LOG: connection ready: setup total=8.960 ms, fork=5.418 ms, authentication=0.089 ms 2025-11-30 18:45:03.052 UTC unrecognized[44079] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.052 UTC client backend[44079] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.052 UTC client backend[44079] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/database 2025-11-30 18:45:03.052 UTC client backend[44083] pg_regress/xid LOG: connection ready: setup total=8.554 ms, fork=5.564 ms, authentication=0.126 ms 2025-11-30 18:45:03.053 UTC client backend[44079] pg_regress/database LOG: connection ready: setup total=10.069 ms, fork=5.267 ms, authentication=0.090 ms 2025-11-30 18:45:03.053 UTC unrecognized[44082] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.053 UTC client backend[44082] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.053 UTC client backend[44082] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/pg_dependencies 2025-11-30 18:45:03.054 UTC client backend[44082] pg_regress/pg_dependencies LOG: connection ready: setup total=10.660 ms, fork=4.562 ms, authentication=0.100 ms 2025-11-30 18:45:03.059 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type xid: "" at character 8 2025-11-30 18:45:03.059 UTC client backend[44083] pg_regress/xid STATEMENT: select ''::xid; 2025-11-30 18:45:03.059 UTC unrecognized[44086] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.059 UTC client backend[44086] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.059 UTC client backend[44086] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/unicode 2025-11-30 18:45:03.060 UTC client backend[44086] pg_regress/unicode LOG: connection ready: setup total=3.487 ms, fork=1.742 ms, authentication=0.113 ms 2025-11-30 18:45:03.061 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "{"a": 1}" at character 8 2025-11-30 18:45:03.061 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Initial element must be an array. 2025-11-30 18:45:03.061 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '{"a": 1}'::pg_ndistinct; 2025-11-30 18:45:03.062 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type xid: "asdf" at character 8 2025-11-30 18:45:03.062 UTC client backend[44083] pg_regress/xid STATEMENT: select 'asdf'::xid; 2025-11-30 18:45:03.062 UTC unrecognized[44084] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.063 UTC client backend[44084] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.063 UTC client backend[44084] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/regex 2025-11-30 18:45:03.063 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "null" at character 8 2025-11-30 18:45:03.063 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Unexpected scalar. 2025-11-30 18:45:03.063 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT 'null'::pg_dependencies; 2025-11-30 18:45:03.064 UTC client backend[44084] pg_regress/regex LOG: connection ready: setup total=11.138 ms, fork=6.469 ms, authentication=0.103 ms 2025-11-30 18:45:03.064 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type xid8: "" at character 8 2025-11-30 18:45:03.064 UTC client backend[44083] pg_regress/xid STATEMENT: select ''::xid8; 2025-11-30 18:45:03.067 UTC unrecognized[44087] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.067 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[]" at character 8 2025-11-30 18:45:03.067 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Item array cannot be empty. 2025-11-30 18:45:03.067 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[]'::pg_ndistinct; 2025-11-30 18:45:03.067 UTC unrecognized[44088] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.067 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "{}" at character 8 2025-11-30 18:45:03.067 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Initial element must be an array. 2025-11-30 18:45:03.067 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '{}'::pg_ndistinct; 2025-11-30 18:45:03.068 UTC client backend[44076] pg_regress/expressions WARNING: TIME(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-30 18:45:03.068 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[null]" at character 8 2025-11-30 18:45:03.068 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Item list elements cannot be null. 2025-11-30 18:45:03.068 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[null]'::pg_ndistinct; 2025-11-30 18:45:03.068 UTC client backend[44076] pg_regress/expressions WARNING: TIMESTAMP(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-30 18:45:03.068 UTC unrecognized[44085] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.068 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type xid8: "asdf" at character 8 2025-11-30 18:45:03.068 UTC client backend[44083] pg_regress/xid STATEMENT: select 'asdf'::xid8; 2025-11-30 18:45:03.068 UTC client backend[44085] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.068 UTC client backend[44085] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.069 UTC client backend[44076] pg_regress/expressions WARNING: TIME(7) precision reduced to maximum allowed, 6 2025-11-30 18:45:03.069 UTC client backend[44076] pg_regress/expressions WARNING: TIMESTAMP(7) precision reduced to maximum allowed, 6 2025-11-30 18:45:03.069 UTC client backend[44085] [unknown] LOG: connection ready: setup total=15.645 ms, fork=5.618 ms, authentication=0.105 ms 2025-11-30 18:45:03.069 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes_invalid" : [2,3], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.069 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Only allowed keys are "attributes" and "ndistinct". 2025-11-30 18:45:03.069 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes_invalid" : [2,3], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "invalid" : 3, "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Only allowed keys are "attributes" and "ndistinct". 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "invalid" : 3, "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.070 UTC client backend[44087] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.070 UTC client backend[44087] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/mvcc 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "attributes" : [1,3], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Multiple "attributes" keys are not allowed. 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "attributes" : [1,3], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : 4, "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Multiple "ndistinct" keys are not allowed. 2025-11-30 18:45:03.070 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : 4, "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.071 UTC client backend[44087] pg_regress/mvcc LOG: connection ready: setup total=12.077 ms, fork=7.105 ms, authentication=0.097 ms 2025-11-30 18:45:03.071 UTC client backend[44088] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.071 UTC client backend[44088] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/horology 2025-11-30 18:45:03.072 UTC client backend[44088] pg_regress/horology LOG: connection ready: setup total=9.991 ms, fork=3.943 ms, authentication=0.093 ms 2025-11-30 18:45:03.074 UTC client backend[44042] pg_regress/dict_xsyn LOG: disconnection: session time: 0:00:00.074 user=postgres database=regression_dict_xsyn host=[local] 2025-11-30 18:45:03.076 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "{"a": 1}" at character 8 2025-11-30 18:45:03.076 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Initial element must be an array. 2025-11-30 18:45:03.076 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '{"a": 1}'::pg_dependencies; 2025-11-30 18:45:03.079 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3]}]" at character 8 2025-11-30 18:45:03.079 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Item must contain "ndistinct" key. 2025-11-30 18:45:03.079 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3]}]'::pg_ndistinct; 2025-11-30 18:45:03.080 UTC client backend[44086] pg_regress/unicode ERROR: invalid normalization form: def 2025-11-30 18:45:03.080 UTC client backend[44086] pg_regress/unicode STATEMENT: SELECT "normalize"('abc', 'def'); 2025-11-30 18:45:03.080 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[]" at character 8 2025-11-30 18:45:03.080 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Item array cannot be empty. 2025-11-30 18:45:03.080 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[]'::pg_dependencies; 2025-11-30 18:45:03.081 UTC unrecognized[44089] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.081 UTC client backend[44089] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.081 UTC client backend[44089] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.082 UTC client backend[44089] [unknown] LOG: connection ready: setup total=5.728 ms, fork=3.751 ms, authentication=0.110 ms 2025-11-30 18:45:03.083 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "{}" at character 8 2025-11-30 18:45:03.083 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Initial element must be an array. 2025-11-30 18:45:03.083 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '{}'::pg_dependencies; 2025-11-30 18:45:03.083 UTC client backend[44086] pg_regress/unicode ERROR: invalid normalization form: def 2025-11-30 18:45:03.083 UTC client backend[44086] pg_regress/unicode STATEMENT: SELECT is_normalized('abc', 'def'); 2025-11-30 18:45:03.084 UTC client backend[44086] pg_regress/unicode LOG: disconnection: session time: 0:00:00.025 user=postgres database=regression host=[local] 2025-11-30 18:45:03.085 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[null]" at character 8 2025-11-30 18:45:03.085 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Item list elements cannot be null. 2025-11-30 18:45:03.085 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[null]'::pg_dependencies; 2025-11-30 18:45:03.085 UTC client backend[44084] pg_regress/regex ERROR: regexp_match() does not support the "global" option 2025-11-30 18:45:03.085 UTC client backend[44084] pg_regress/regex HINT: Use the regexp_matches function instead. 2025-11-30 18:45:03.085 UTC client backend[44084] pg_regress/regex STATEMENT: select regexp_match('abc', 'Bd', 'ig'); 2025-11-30 18:45:03.086 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.086 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Item must contain "attributes" key. 2025-11-30 18:45:03.086 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.090 UTC client backend[44073] pg_regress/tstypes ERROR: syntax error in tsvector: "'' '1' '2'" at character 8 2025-11-30 18:45:03.090 UTC client backend[44073] pg_regress/tstypes STATEMENT: SELECT $$'' '1' '2'$$::tsvector; 2025-11-30 18:45:03.091 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [1,2,3,4,5,6,7,8,9], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.091 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: The "attributes" key must contain an array of at least 2 and no more than 8 attributes. 2025-11-30 18:45:03.091 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [1,2,3,4,5,6,7,8,9], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.092 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes_invalid" : [2,3], "dependency" : 4}]" at character 8 2025-11-30 18:45:03.092 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Only allowed keys are "attributes", "dependency" and "degree". 2025-11-30 18:45:03.092 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes_invalid" : [2,3], "dependency" : 4}]'::pg_dependencies; 2025-11-30 18:45:03.092 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "invalid" : 3, "dependency" : 4}]" at character 8 2025-11-30 18:45:03.092 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Only allowed keys are "attributes", "dependency" and "degree". 2025-11-30 18:45:03.092 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "invalid" : 3, "dependency" : 4}]'::pg_dependencies; 2025-11-30 18:45:03.094 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"\ud83d" : [1, 2], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.094 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Must be valid JSON. 2025-11-30 18:45:03.094 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"\ud83d" : [1, 2], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.096 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [1, 2], "\ud83d" : 4}]" at character 8 2025-11-30 18:45:03.096 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Must be valid JSON. 2025-11-30 18:45:03.096 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [1, 2], "\ud83d" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.096 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [1, 2], "ndistinct" : "\ud83d"}]" at character 8 2025-11-30 18:45:03.096 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Must be valid JSON. 2025-11-30 18:45:03.096 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [1, 2], "ndistinct" : "\ud83d"}]'::pg_ndistinct; 2025-11-30 18:45:03.097 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : 4}]" at character 8 2025-11-30 18:45:03.097 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Item must contain "degree" key. 2025-11-30 18:45:03.097 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : 4}]'::pg_dependencies; 2025-11-30 18:45:03.097 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "27/12/2001 04:05:06.789-08" at character 33 2025-11-30 18:45:03.097 UTC client backend[44088] pg_regress/horology HINT: Perhaps you need a different "DateStyle" setting. 2025-11-30 18:45:03.097 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp with time zone '27/12/2001 04:05:06.789-08'; 2025-11-30 18:45:03.098 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : ["\ud83d", 2], "ndistinct" : 1}]" at character 8 2025-11-30 18:45:03.098 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Must be valid JSON. 2025-11-30 18:45:03.098 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : ["\ud83d", 2], "ndistinct" : 1}]'::pg_ndistinct; 2025-11-30 18:45:03.100 UTC client backend[44076] pg_regress/expressions ERROR: operator does not exist: point = box at character 23 2025-11-30 18:45:03.100 UTC client backend[44076] pg_regress/expressions DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:03.100 UTC client backend[44076] pg_regress/expressions HINT: You might need to add explicit type casts. 2025-11-30 18:45:03.100 UTC client backend[44076] pg_regress/expressions STATEMENT: select '(0,0)'::point in ('(0,0,0,0)'::box, point(0,0)); 2025-11-30 18:45:03.100 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "degree" : 1.000}]" at character 8 2025-11-30 18:45:03.100 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Item must contain "dependency" key. 2025-11-30 18:45:03.100 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "degree" : 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : null, "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Unexpected scalar. 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : null, "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [], "ndistinct" : 1}]" at character 8 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: The "attributes" key must be a non-empty array. 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [], "ndistinct" : 1}]'::pg_ndistinct; 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: The "attributes" key must contain an array of at least 2 and no more than 8 attributes. 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,null], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Attribute number array cannot be null. 2025-11-30 18:45:03.102 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,null], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : null}]" at character 8 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Invalid "ndistinct" value. 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : null}]'::pg_ndistinct; 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,"a"], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Invalid "attributes" value. 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,"a"], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : "a"}]" at character 8 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Invalid "ndistinct" value. 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : "a"}]'::pg_ndistinct; 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : []}]" at character 8 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Array found in unexpected place. 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : []}]'::pg_ndistinct; 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : [null]}]" at character 8 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Array found in unexpected place. 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : [null]}]'::pg_ndistinct; 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : [1,null]}]" at character 8 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Array found in unexpected place. 2025-11-30 18:45:03.103 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : [1,null]}]'::pg_ndistinct; 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : {"a": 1}}]" at character 8 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Value of "ndistinct" must be an integer. 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : {"a": 1}}]'::pg_ndistinct; 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [0,1], "ndistinct" : 1}]" at character 8 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Invalid "attributes" element: 0. 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [0,1], "ndistinct" : 1}]'::pg_ndistinct; 2025-11-30 18:45:03.104 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type time with time zone: "T040506.789 America/Los_Angeles" at character 28 2025-11-30 18:45:03.104 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT time with time zone 'T040506.789 America/Los_Angeles'; 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [-7,-9], "ndistinct" : 1}]" at character 8 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Invalid "attributes" element: -9. 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [-7,-9], "ndistinct" : 1}]'::pg_ndistinct; 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : 1, "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Unexpected scalar. 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : 1, "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : "a", "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Unexpected scalar. 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : "a", "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.104 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : 4}]" at character 8 2025-11-30 18:45:03.104 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Item must contain "degree" key. 2025-11-30 18:45:03.104 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : 4}]'::pg_dependencies; 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : {"a": 1}, "ndistinct" : 1}]" at character 8 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Value of "attributes" must be an array of attribute numbers. 2025-11-30 18:45:03.104 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : {"a": 1}, "ndistinct" : 1}]'::pg_ndistinct; 2025-11-30 18:45:03.108 UTC client backend[44078] pg_regress/comments LOG: disconnection: session time: 0:00:00.059 user=postgres database=regression host=[local] 2025-11-30 18:45:03.108 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [1, {"a": 1}], "ndistinct" : 1}]" at character 8 2025-11-30 18:45:03.108 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Attribute lists can only contain attribute numbers. 2025-11-30 18:45:03.108 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [1, {"a": 1}], "ndistinct" : 1}]'::pg_ndistinct; 2025-11-30 18:45:03.110 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type time: "T04" at character 31 2025-11-30 18:45:03.110 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT time without time zone 'T04'; 2025-11-30 18:45:03.111 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,2], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.111 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Invalid "attributes" element: 2 cannot follow 2. 2025-11-30 18:45:03.111 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,2], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.112 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type time with time zone: "T04+08" at character 28 2025-11-30 18:45:03.112 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT time with time zone 'T04+08'; 2025-11-30 18:45:03.112 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : 4}, {"attributes" : [2,3], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.112 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: Duplicated "attributes" array found: [2, 3] 2025-11-30 18:45:03.112 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : 4}, {"attributes" : [2,3], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.112 UTC client backend[44080] pg_regress/pg_ndistinct ERROR: malformed pg_ndistinct: "[{"attributes" : [2,3], "ndistinct" : 4}, {"attributes" : [2,-1], "ndistinct" : 4}, {"attributes" : [2,3,-1], "ndistinct" : 4}, {"attributes" : [1,3,-1,-2], "ndistinct" : 4}]" at character 8 2025-11-30 18:45:03.112 UTC client backend[44080] pg_regress/pg_ndistinct DETAIL: "attributes" array: [2, 3] must be a subset of array: [1, 3, -1, -2] 2025-11-30 18:45:03.112 UTC client backend[44080] pg_regress/pg_ndistinct STATEMENT: SELECT '[{"attributes" : [2,3], "ndistinct" : 4}, {"attributes" : [2,-1], "ndistinct" : 4}, {"attributes" : [2,3,-1], "ndistinct" : 4}, {"attributes" : [1,3,-1,-2], "ndistinct" : 4}]'::pg_ndistinct; 2025-11-30 18:45:03.112 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 J J J" at character 13 2025-11-30 18:45:03.112 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date '1995-08-06 J J J'; 2025-11-30 18:45:03.112 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type date: "J J 1520447" at character 13 2025-11-30 18:45:03.112 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date 'J J 1520447'; 2025-11-30 18:45:03.119 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04M05S06.789+08" at character 33 2025-11-30 18:45:03.119 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04M05S06.789+08'; 2025-11-30 18:45:03.119 UTC client backend[44080] pg_regress/pg_ndistinct LOG: disconnection: session time: 0:00:00.074 user=postgres database=regression host=[local] 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04MM05S06.789-08" at character 33 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04MM05S06.789-08'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "J2452271 T X03456-08" at character 33 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'J2452271 T X03456-08'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "J2452271 T X03456.001e6-08" at character 33 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'J2452271 T X03456.001e6-08'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 epoch" at character 13 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date '1995-08-06 epoch'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 infinity" at character 13 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date '1995-08-06 infinity'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 -infinity" at character 13 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date '1995-08-06 -infinity'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type date: "today infinity" at character 13 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date 'today infinity'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type date: "-infinity infinity" at character 13 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date '-infinity infinity'; 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 epoch" at character 18 2025-11-30 18:45:03.120 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 epoch'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 infinity" at character 18 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 infinity'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 -infinity" at character 18 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 -infinity'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "epoch 01:01:01" at character 18 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp 'epoch 01:01:01'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "infinity 01:01:01" at character 18 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp 'infinity 01:01:01'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity 01:01:01" at character 18 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp '-infinity 01:01:01'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "now epoch" at character 18 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp 'now epoch'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity infinity" at character 18 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp '-infinity infinity'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 epoch" at character 20 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 epoch'; 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 infinity" at character 20 2025-11-30 18:45:03.121 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 infinity'; 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 -infinity" at character 20 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 -infinity'; 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "epoch 01:01:01" at character 20 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz 'epoch 01:01:01'; 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "infinity 01:01:01" at character 20 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz 'infinity 01:01:01'; 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity 01:01:01" at character 20 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity 01:01:01'; 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "now epoch" at character 20 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz 'now epoch'; 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity infinity" at character 20 2025-11-30 18:45:03.122 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity infinity'; 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology ERROR: operator does not exist: date - time with time zone at character 26 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology HINT: You might need to add explicit type casts. 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT date '1991-02-03' - time with time zone '04:05:06 UTC' AS "Subtract Time UTC"; 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology ERROR: timestamp out of range 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology ERROR: timestamp out of range 2025-11-30 18:45:03.124 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp without time zone '294276-12-31 23:59:59' + interval '9223372036854775807 microseconds' AS "out of range"; 2025-11-30 18:45:03.127 UTC client backend[44088] pg_regress/horology ERROR: timestamp out of range 2025-11-30 18:45:03.127 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2025-11-30 18:45:03.127 UTC client backend[44088] pg_regress/horology ERROR: timestamp out of range 2025-11-30 18:45:03.127 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT timestamp with time zone '294276-12-31 23:59:59 UTC' + interval '9223372036854775807 microseconds' AS "out of range"; 2025-11-30 18:45:03.131 UTC client backend[44071] [unknown] LOG: disconnection: session time: 0:00:00.104 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.131 UTC client backend[44088] pg_regress/horology ERROR: cannot cast type time with time zone to interval at character 8 2025-11-30 18:45:03.131 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT CAST(time with time zone '01:02-08' AS interval) AS "+00:01"; 2025-11-30 18:45:03.131 UTC client backend[44088] pg_regress/horology ERROR: cannot cast type interval to time with time zone at character 8 2025-11-30 18:45:03.131 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT CAST(interval '02:03' AS time with time zone) AS "02:03:00-08"; 2025-11-30 18:45:03.138 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait flush-unlogged 2025-11-30 18:45:03.139 UTC client backend[44025] pg_regress/enum LOG: disconnection: session time: 0:00:00.164 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:03.141 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [1,2,3,4,5,6,7,8], "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.141 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: The "attributes" key must contain an array of at least 1 and no more than 7 elements. 2025-11-30 18:45:03.141 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [1,2,3,4,5,6,7,8], "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : ["\ud83d",3], "dependency" : 4, "degree": 0.250}]" at character 8 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Must be valid JSON. 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : ["\ud83d",3], "dependency" : 4, "degree": 0.250}]'::pg_dependencies; 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : "\ud83d", "degree": 0.250}]" at character 8 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Must be valid JSON. 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : "\ud83d", "degree": 0.250}]'::pg_dependencies; 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : 4, "degree": "\ud83d"}]" at character 8 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Must be valid JSON. 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : 4, "degree": "\ud83d"}]'::pg_dependencies; 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"\ud83d" : [2,3], "dependency" : 4, "degree": 0.250}]" at character 8 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Must be valid JSON. 2025-11-30 18:45:03.142 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"\ud83d" : [2,3], "dependency" : 4, "degree": 0.250}]'::pg_dependencies; 2025-11-30 18:45:03.143 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : null, "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.143 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Unexpected scalar. 2025-11-30 18:45:03.143 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : null, "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.143 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,null], "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.143 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Attribute number array cannot be null. 2025-11-30 18:45:03.143 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,null], "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.144 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : null, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.144 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "dependency" value. 2025-11-30 18:45:03.144 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : null, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.144 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,"a"], "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.144 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "attributes" value. 2025-11-30 18:45:03.144 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,"a"], "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.144 UTC client backend[44089] [unknown] LOG: disconnection: session time: 0:00:00.064 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : "a", "degree": 1.000}]" at character 8 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "dependency" value. 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : "a", "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : [], "degree": 1.000}]" at character 8 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Array found in unexpected place. 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : [], "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : [null], "degree": 1.000}]" at character 8 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Array found in unexpected place. 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : [null], "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : [1,null], "degree": 1.000}]" at character 8 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Array found in unexpected place. 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : [1,null], "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : 1, "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Unexpected scalar. 2025-11-30 18:45:03.146 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : 1, "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.147 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : "a", "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.147 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Unexpected scalar. 2025-11-30 18:45:03.147 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : "a", "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.147 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : 4, "degree": NaN}]" at character 8 2025-11-30 18:45:03.147 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Must be valid JSON. 2025-11-30 18:45:03.147 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : 4, "degree": NaN}]'::pg_dependencies; 2025-11-30 18:45:03.148 UTC client backend[44081] pg_regress/stats_import ERROR: argument "schemaname" must not be null 2025-11-30 18:45:03.148 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'relname', 'test', 'relpages', 17::integer); 2025-11-30 18:45:03.149 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes": [], "dependency": 2, "degree": 1}]" at character 8 2025-11-30 18:45:03.149 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: The "attributes" key must be an non-empty array. 2025-11-30 18:45:03.149 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes": [], "dependency": 2, "degree": 1}]' ::pg_dependencies; 2025-11-30 18:45:03.150 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : {"a": 1}, "dependency" : 4, "degree": "1.2"}]" at character 8 2025-11-30 18:45:03.150 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Value of "attributes" must be an array of attribute numbers. 2025-11-30 18:45:03.150 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : {"a": 1}, "dependency" : 4, "degree": "1.2"}]'::pg_dependencies; 2025-11-30 18:45:03.150 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"dependency" : 4, "degree": "1.2"}]" at character 8 2025-11-30 18:45:03.150 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Item must contain "attributes" key 2025-11-30 18:45:03.150 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"dependency" : 4, "degree": "1.2"}]'::pg_dependencies; 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [1,2,3,4,5,6,7], "dependency" : 0, "degree": "1.2"}]" at character 8 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "dependency" value: 0. 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [1,2,3,4,5,6,7], "dependency" : 0, "degree": "1.2"}]'::pg_dependencies; 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [1,2,3,4,5,6,7], "dependency" : -9, "degree": "1.2"}]" at character 8 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "dependency" value: -9. 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [1,2,3,4,5,6,7], "dependency" : -9, "degree": "1.2"}]'::pg_dependencies; 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes": [1,2], "dependency": 2, "degree": 1}]" at character 8 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Item "dependency" value 2 found in the "attributes" list. 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes": [1,2], "dependency": 2, "degree": 1}]' ::pg_dependencies; 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [1, {}], "dependency" : 1, "degree": "1.2"}]" at character 8 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Attribute lists can only contain attribute numbers. 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [1, {}], "dependency" : 1, "degree": "1.2"}]'::pg_dependencies; 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [1,2], "dependency" : {}, "degree": 1.0}]" at character 8 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Value of "dependency" must be an integer. 2025-11-30 18:45:03.151 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [1,2], "dependency" : {}, "degree": 1.0}]'::pg_dependencies; 2025-11-30 18:45:03.152 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [1,2], "dependency" : 3, "degree": {}}]" at character 8 2025-11-30 18:45:03.152 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Value of "degree" must be an integer. 2025-11-30 18:45:03.152 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [1,2], "dependency" : 3, "degree": {}}]'::pg_dependencies; 2025-11-30 18:45:03.152 UTC client backend[44085] [unknown] LOG: disconnection: session time: 0:00:00.092 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.153 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [1,2], "dependency" : 1, "degree": "a"}]" at character 8 2025-11-30 18:45:03.153 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "degree" value. 2025-11-30 18:45:03.153 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [1,2], "dependency" : 1, "degree": "a"}]'::pg_dependencies; 2025-11-30 18:45:03.153 UTC client backend[44072] pg_regress/geometry ERROR: value out of range: underflow 2025-11-30 18:45:03.153 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT p1.f1, p2.f1, p1.f1 * p2.f1 FROM POINT_TBL p1, POINT_TBL p2 WHERE p1.f1[0] < 1; 2025-11-30 18:45:03.155 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes": [2], "dependency": 4, "degree": -Infinity}]" 2025-11-30 18:45:03.155 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Must be valid JSON. 2025-11-30 18:45:03.155 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2], "dependency" : 4, "degree": "-inf"}]'::pg_dependencies::text::pg_dependencies; 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "attributes": [1,2], "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Multiple "attributes" keys are not allowed. 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "attributes": [1,2], "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : 4, "dependency": 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Multiple "dependency" keys are not allowed. 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : 4, "dependency": 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency": 4, "degree": 1.000, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Multiple "degree" keys are not allowed. 2025-11-30 18:45:03.156 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency": 4, "degree": 1.000, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.157 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [0,2], "dependency" : 4, "degree": 0.500}]" at character 8 2025-11-30 18:45:03.157 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "attributes" element: 0. 2025-11-30 18:45:03.157 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [0,2], "dependency" : 4, "degree": 0.500}]'::pg_dependencies; 2025-11-30 18:45:03.157 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [-7,-9], "dependency" : 4, "degree": 0.500}]" at character 8 2025-11-30 18:45:03.157 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "attributes" element: -9. 2025-11-30 18:45:03.157 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [-7,-9], "dependency" : 4, "degree": 0.500}]'::pg_dependencies; 2025-11-30 18:45:03.158 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,2], "dependency" : 4, "degree": 0.500}]" at character 8 2025-11-30 18:45:03.158 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Invalid "attributes" element: 2 cannot follow 2. 2025-11-30 18:45:03.158 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,2], "dependency" : 4, "degree": 0.500}]'::pg_dependencies; 2025-11-30 18:45:03.158 UTC client backend[44082] pg_regress/pg_dependencies ERROR: malformed pg_dependencies: "[{"attributes" : [2,3], "dependency" : 4, "degree": 1.000}, {"attributes" : [2,3], "dependency" : 4, "degree": 1.000}]" at character 8 2025-11-30 18:45:03.158 UTC client backend[44082] pg_regress/pg_dependencies DETAIL: Duplicate "attributes" array: [2, 3] with "dependency": 4. 2025-11-30 18:45:03.158 UTC client backend[44082] pg_regress/pg_dependencies STATEMENT: SELECT '[{"attributes" : [2,3], "dependency" : 4, "degree": 1.000}, {"attributes" : [2,3], "dependency" : 4, "degree": 1.000}]'::pg_dependencies; 2025-11-30 18:45:03.159 UTC client backend[44082] pg_regress/pg_dependencies LOG: disconnection: session time: 0:00:00.111 user=postgres database=regression host=[local] 2025-11-30 18:45:03.167 UTC unrecognized[44092] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.168 UTC client backend[44092] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.168 UTC client backend[44092] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.169 UTC client backend[44092] [unknown] LOG: connection ready: setup total=8.674 ms, fork=6.826 ms, authentication=0.131 ms 2025-11-30 18:45:03.170 UTC client backend[44072] pg_regress/geometry ERROR: value out of range: overflow 2025-11-30 18:45:03.170 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT p1.f1, p2.f1, p1.f1 / p2.f1 FROM POINT_TBL p1, POINT_TBL p2 WHERE p2.f1[0] > 1000; 2025-11-30 18:45:03.176 UTC client backend[44072] pg_regress/geometry ERROR: division by zero 2025-11-30 18:45:03.176 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT p1.f1, p2.f1, p1.f1 / p2.f1 FROM POINT_TBL p1, POINT_TBL p2 WHERE p2.f1 ~= '(0,0)'::point; 2025-11-30 18:45:03.177 UTC checkpointer[43405] LOG: checkpoint complete: wrote 8609 buffers (52.5%), wrote 2 SLRU buffers; 0 WAL file(s) added, 0 removed, 4 recycled; write=0.028 s, sync=0.001 s, total=0.040 s; sync files=0, longest=0.000 s, average=0.000 s; distance=66667 kB, estimate=106744 kB; lsn=0/0C581F10, redo lsn=0/0C53FB68 2025-11-30 18:45:03.181 UTC client backend[44083] pg_regress/xid ERROR: operator does not exist: xid < xid at character 17 2025-11-30 18:45:03.181 UTC client backend[44083] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:03.181 UTC client backend[44083] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-30 18:45:03.181 UTC client backend[44083] pg_regress/xid STATEMENT: select '1'::xid < '2'::xid; 2025-11-30 18:45:03.181 UTC client backend[44088] pg_regress/horology ERROR: date out of range for timestamp 2025-11-30 18:45:03.181 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamp; 2025-11-30 18:45:03.182 UTC client backend[44088] pg_regress/horology ERROR: date out of range for timestamp 2025-11-30 18:45:03.182 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamptz; 2025-11-30 18:45:03.182 UTC client backend[44075] pg_regress/misc_sanity LOG: disconnection: session time: 0:00:00.132 user=postgres database=regression host=[local] 2025-11-30 18:45:03.182 UTC client backend[44088] pg_regress/horology ERROR: date out of range for timestamp 2025-11-30 18:45:03.182 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT '4714-11-24 BC'::date::timestamptz; 2025-11-30 18:45:03.183 UTC client backend[44081] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-30 18:45:03.183 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relpages', 17::integer); 2025-11-30 18:45:03.184 UTC client backend[44081] pg_regress/stats_import WARNING: argument "schemaname" has type double precision, expected type text 2025-11-30 18:45:03.184 UTC client backend[44083] pg_regress/xid ERROR: operator does not exist: xid <= xid at character 17 2025-11-30 18:45:03.184 UTC client backend[44083] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:03.184 UTC client backend[44083] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-30 18:45:03.184 UTC client backend[44083] pg_regress/xid STATEMENT: select '1'::xid <= '2'::xid; 2025-11-30 18:45:03.184 UTC client backend[44081] pg_regress/stats_import ERROR: argument "schemaname" must not be null 2025-11-30 18:45:03.184 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 3.6::float, 'relname', 'test', 'relpages', 17::integer); 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid ERROR: operator does not exist: xid > xid at character 17 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid STATEMENT: select '1'::xid > '2'::xid; 2025-11-30 18:45:03.185 UTC client backend[44081] pg_regress/stats_import WARNING: argument "relname" has type oid, expected type text 2025-11-30 18:45:03.185 UTC client backend[44081] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-30 18:45:03.185 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 0::oid, 'relpages', 17::integer); 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid ERROR: operator does not exist: xid >= xid at character 17 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-30 18:45:03.185 UTC client backend[44083] pg_regress/xid STATEMENT: select '1'::xid >= '2'::xid; 2025-11-30 18:45:03.185 UTC client backend[44081] pg_regress/stats_import ERROR: relation "stats_import.nope" does not exist 2025-11-30 18:45:03.185 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'nope', 'relpages', 17::integer); 2025-11-30 18:45:03.186 UTC client backend[44081] pg_regress/stats_import ERROR: variadic arguments must be name/value pairs 2025-11-30 18:45:03.186 UTC client backend[44081] pg_regress/stats_import HINT: Provide an even number of variadic arguments that can be divided into pairs. 2025-11-30 18:45:03.186 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'test', 'relallvisible'); 2025-11-30 18:45:03.186 UTC client backend[44081] pg_regress/stats_import ERROR: name at variadic position 5 is null 2025-11-30 18:45:03.186 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'test', NULL, '17'::integer); 2025-11-30 18:45:03.192 UTC client backend[44050] pg_regress/text LOG: disconnection: session time: 0:00:00.172 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.192 UTC unrecognized[44094] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.198 UTC unrecognized[44095] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.200 UTC client backend[44095] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.200 UTC client backend[44095] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/uuid 2025-11-30 18:45:03.201 UTC client backend[44095] pg_regress/uuid LOG: connection ready: setup total=4.557 ms, fork=0.881 ms, authentication=0.123 ms 2025-11-30 18:45:03.202 UTC client backend[44092] [unknown] LOG: disconnection: session time: 0:00:00.035 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.202 UTC client backend[44081] pg_regress/stats_import WARNING: argument "relpages" has type text, expected type integer 2025-11-30 18:45:03.203 UTC client backend[44081] pg_regress/stats_import WARNING: unrecognized argument name: "nope" 2025-11-30 18:45:03.204 UTC client backend[44081] pg_regress/stats_import ERROR: cannot modify statistics for relation "testseq" 2025-11-30 18:45:03.204 UTC client backend[44081] pg_regress/stats_import DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:03.204 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'testseq'); 2025-11-30 18:45:03.204 UTC client backend[44081] pg_regress/stats_import ERROR: cannot modify statistics for relation "testseq" 2025-11-30 18:45:03.204 UTC client backend[44081] pg_regress/stats_import DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:03.204 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_clear_relation_stats(schemaname => 'stats_import', relname => 'testseq'); 2025-11-30 18:45:03.204 UTC client backend[43963] pg_regress/dblink ERROR: invalid option "server" 2025-11-30 18:45:03.204 UTC client backend[43963] pg_regress/dblink STATEMENT: CREATE USER MAPPING FOR public SERVER fdtest OPTIONS (server 'localhost'); 2025-11-30 18:45:03.204 UTC client backend[43963] pg_regress/dblink ERROR: invalid option "oauth_issuer" 2025-11-30 18:45:03.204 UTC client backend[43963] pg_regress/dblink STATEMENT: ALTER SERVER fdtest OPTIONS (ADD oauth_issuer 'https://example.com'); 2025-11-30 18:45:03.205 UTC client backend[43963] pg_regress/dblink ERROR: invalid option "oauth_client_id" 2025-11-30 18:45:03.205 UTC client backend[43963] pg_regress/dblink STATEMENT: ALTER SERVER fdtest OPTIONS (ADD oauth_client_id 'myID'); 2025-11-30 18:45:03.205 UTC client backend[43963] pg_regress/dblink ERROR: invalid option "oauth_issuer" 2025-11-30 18:45:03.205 UTC client backend[43963] pg_regress/dblink STATEMENT: ALTER USER MAPPING FOR public SERVER fdtest OPTIONS (ADD oauth_issuer 'https://example.com'); 2025-11-30 18:45:03.205 UTC client backend[43963] pg_regress/dblink ERROR: invalid option "oauth_client_id" 2025-11-30 18:45:03.205 UTC client backend[43963] pg_regress/dblink STATEMENT: ALTER USER MAPPING FOR public SERVER fdtest OPTIONS (ADD oauth_client_id 'myID'); 2025-11-30 18:45:03.205 UTC client backend[44081] pg_regress/stats_import ERROR: cannot modify statistics for relation "testview" 2025-11-30 18:45:03.205 UTC client backend[44081] pg_regress/stats_import DETAIL: This operation is not supported for views. 2025-11-30 18:45:03.205 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_clear_relation_stats(schemaname => 'stats_import', relname => 'testview'); 2025-11-30 18:45:03.205 UTC client backend[44081] pg_regress/stats_import ERROR: argument "schemaname" must not be null 2025-11-30 18:45:03.205 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'relname', 'test', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: schema "nope" does not exist 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'nope', 'relname', 'test', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[43963] pg_regress/dblink ERROR: password or GSSAPI delegated credentials required 2025-11-30 18:45:03.206 UTC client backend[43963] pg_regress/dblink DETAIL: Non-superusers must provide a password in the connection string or send delegated GSSAPI credentials. 2025-11-30 18:45:03.206 UTC client backend[43963] pg_regress/dblink STATEMENT: SELECT dblink_connect('myconn', 'fdtest'); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: relation "stats_import.nope" does not exist 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'nope', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', NULL, 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: must specify either "attname" or "attnum" 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', NULL, 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: column "nope" of relation "test" does not exist 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'nope', 'inherited', false::boolean, 'null_frac', 0.1::real, 'avg_width', 2::integer, 'n_distinct', 0.3::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: cannot specify both "attname" and "attnum" 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'id', 'attnum', 1::smallint, 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: must specify either "attname" or "attnum" 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: cannot modify statistics on system column "xmin" 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'xmin', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import ERROR: argument "inherited" must not be null 2025-11-30 18:45:03.206 UTC client backend[44081] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'id', 'inherited', NULL::boolean, 'null_frac', 0.1::real); 2025-11-30 18:45:03.211 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:03.212 UTC checkpointer[43405] LOG: checkpoint complete: wrote 153 buffers (0.9%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.001 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1477 kB, estimate=96217 kB; lsn=0/0C6CB5C8, redo lsn=0/0C6B10E8 2025-11-30 18:45:03.215 UTC unrecognized[44097] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.215 UTC client backend[44097] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.215 UTC client backend[44097] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.216 UTC client backend[44097] [unknown] LOG: connection ready: setup total=10.625 ms, fork=5.072 ms, authentication=0.120 ms 2025-11-30 18:45:03.219 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2025-11-30 18:45:03.219 UTC client backend[44083] pg_regress/xid STATEMENT: select '31:12:'::pg_snapshot; 2025-11-30 18:45:03.221 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait flush-unlogged 2025-11-30 18:45:03.222 UTC checkpointer[43405] LOG: checkpoint complete: wrote 69 buffers (0.4%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.001 s; sync files=0, longest=0.000 s, average=0.000 s; distance=340 kB, estimate=86629 kB; lsn=0/0C7061B0, redo lsn=0/0C7060F0 2025-11-30 18:45:03.222 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2025-11-30 18:45:03.222 UTC client backend[44083] pg_regress/xid STATEMENT: select '0:1:'::pg_snapshot; 2025-11-30 18:45:03.225 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2025-11-30 18:45:03.225 UTC client backend[44083] pg_regress/xid STATEMENT: select '12:13:0'::pg_snapshot; 2025-11-30 18:45:03.227 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2025-11-30 18:45:03.227 UTC client backend[44083] pg_regress/xid STATEMENT: select '12:16:14,13'::pg_snapshot; 2025-11-30 18:45:03.228 UTC client backend[44081] pg_regress/stats_import WARNING: unrecognized argument name: "nope" 2025-11-30 18:45:03.230 UTC unrecognized[44099] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.231 UTC client backend[44099] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.231 UTC client backend[44099] [unknown] LOG: connection authorized: user=postgres database=regression_dblink application_name=pg_regress/dblink 2025-11-30 18:45:03.232 UTC client backend[44099] pg_regress/dblink LOG: connection ready: setup total=5.608 ms, fork=1.631 ms, authentication=0.109 ms 2025-11-30 18:45:03.234 UTC client backend[44073] pg_regress/tstypes ERROR: lexeme array may not contain nulls 2025-11-30 18:45:03.234 UTC client backend[44073] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', NULL]); 2025-11-30 18:45:03.234 UTC client backend[44073] pg_regress/tstypes ERROR: lexeme array may not contain empty strings 2025-11-30 18:45:03.234 UTC client backend[44073] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', '']); 2025-11-30 18:45:03.235 UTC client backend[44073] pg_regress/tstypes ERROR: weight array may not contain nulls 2025-11-30 18:45:03.235 UTC client backend[44073] pg_regress/tstypes STATEMENT: SELECT ts_filter('base hidden rebel spaceship strike'::tsvector, '{a,b,NULL}'); 2025-11-30 18:45:03.235 UTC client backend[44073] pg_regress/tstypes LOG: disconnection: session time: 0:00:00.197 user=postgres database=regression host=[local] 2025-11-30 18:45:03.236 UTC client backend[44087] pg_regress/mvcc LOG: disconnection: session time: 0:00:00.170 user=postgres database=regression host=[local] 2025-11-30 18:45:03.238 UTC client backend[43963] pg_regress/dblink LOG: disconnection: session time: 0:00:00.414 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.239 UTC client backend[44097] [unknown] LOG: disconnection: session time: 0:00:00.027 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.243 UTC client backend[44081] pg_regress/stats_import WARNING: argument "most_common_vals" must be specified when argument "most_common_freqs" is specified 2025-11-30 18:45:03.245 UTC client backend[44099] pg_regress/dblink ERROR: invalid option "nonexistent" 2025-11-30 18:45:03.245 UTC client backend[44099] pg_regress/dblink HINT: There are no valid options in this context. 2025-11-30 18:45:03.245 UTC client backend[44099] pg_regress/dblink STATEMENT: ALTER FOREIGN DATA WRAPPER dblink_fdw OPTIONS (nonexistent 'fdw'); 2025-11-30 18:45:03.250 UTC unrecognized[44102] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.250 UTC client backend[44102] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.250 UTC client backend[44102] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.251 UTC client backend[44102] [unknown] LOG: connection ready: setup total=5.305 ms, fork=3.185 ms, authentication=0.122 ms 2025-11-30 18:45:03.252 UTC client backend[44095] pg_regress/uuid LOG: disconnection: session time: 0:00:00.054 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:03.261 UTC client backend[44076] pg_regress/expressions LOG: disconnection: session time: 0:00:00.217 user=postgres database=regression host=[local] 2025-11-30 18:45:03.261 UTC client backend[44045] pg_regress/dict_int ERROR: maxlen value has to be >= 1 2025-11-30 18:45:03.261 UTC client backend[44045] pg_regress/dict_int STATEMENT: ALTER TEXT SEARCH DICTIONARY intdict (MAXLEN = -214783648); 2025-11-30 18:45:03.265 UTC client backend[44072] pg_regress/geometry ERROR: operator does not exist: lseg # point at character 23 2025-11-30 18:45:03.265 UTC client backend[44072] pg_regress/geometry DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:03.265 UTC client backend[44072] pg_regress/geometry HINT: You might need to add explicit type casts. 2025-11-30 18:45:03.265 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT p.f1, l.s, l.s # p.f1 AS intersection FROM LSEG_TBL l, POINT_TBL p; 2025-11-30 18:45:03.266 UTC client backend[44081] pg_regress/stats_import WARNING: argument "most_common_freqs" must be specified when argument "most_common_vals" is specified 2025-11-30 18:45:03.266 UTC unrecognized[44103] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.267 UTC client backend[44103] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.267 UTC client backend[44103] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.267 UTC unrecognized[44106] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.267 UTC client backend[44103] [unknown] LOG: connection ready: setup total=15.946 ms, fork=14.313 ms, authentication=0.121 ms 2025-11-30 18:45:03.268 UTC client backend[44106] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.268 UTC client backend[44106] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/name 2025-11-30 18:45:03.268 UTC client backend[44103] [unknown] LOG: disconnection: session time: 0:00:00.002 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.268 UTC client backend[44106] pg_regress/name LOG: connection ready: setup total=2.208 ms, fork=0.404 ms, authentication=0.103 ms 2025-11-30 18:45:03.270 UTC client backend[44102] [unknown] LOG: disconnection: session time: 0:00:00.020 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.271 UTC client backend[44045] pg_regress/dict_int LOG: disconnection: session time: 0:00:00.268 user=postgres database=regression_dict_int host=[local] 2025-11-30 18:45:03.272 UTC client backend[44081] pg_regress/stats_import WARNING: argument "most_common_freqs" has type double precision[], expected type real[] 2025-11-30 18:45:03.273 UTC client backend[44081] pg_regress/stats_import WARNING: argument "most_common_freqs" must be specified when argument "most_common_vals" is specified 2025-11-30 18:45:03.275 UTC client backend[44081] pg_regress/stats_import WARNING: invalid input syntax for type integer: "four" 2025-11-30 18:45:03.276 UTC client backend[44088] pg_regress/horology ERROR: invalid value "/Feb/16" for "Mon" 2025-11-30 18:45:03.276 UTC client backend[44088] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2025-11-30 18:45:03.276 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('97/Feb/16', 'YYMonDD'); 2025-11-30 18:45:03.279 UTC unrecognized[44107] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.280 UTC client backend[44107] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.280 UTC client backend[44107] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.281 UTC client backend[44107] [unknown] LOG: connection ready: setup total=11.779 ms, fork=3.510 ms, authentication=0.113 ms 2025-11-30 18:45:03.281 UTC client backend[44081] pg_regress/stats_import WARNING: "histogram_bounds" array must not contain null values 2025-11-30 18:45:03.283 UTC client backend[44083] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 20 2025-11-30 18:45:03.283 UTC client backend[44083] pg_regress/xid STATEMENT: SELECT pg_snapshot '1:9223372036854775808:3'; 2025-11-30 18:45:03.286 UTC client backend[44081] pg_regress/stats_import WARNING: argument "elem_count_histogram" array must not contain null values 2025-11-30 18:45:03.293 UTC client backend[44081] pg_regress/stats_import WARNING: column "id" is not a range type 2025-11-30 18:45:03.293 UTC client backend[44081] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM. 2025-11-30 18:45:03.294 UTC unrecognized[44101] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.294 UTC client backend[44101] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.294 UTC client backend[44101] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/varchar 2025-11-30 18:45:03.295 UTC client backend[44101] pg_regress/varchar LOG: connection ready: setup total=56.698 ms, fork=34.488 ms, authentication=0.118 ms 2025-11-30 18:45:03.298 UTC client backend[44081] pg_regress/stats_import WARNING: argument "range_empty_frac" must be specified when argument "range_length_histogram" is specified 2025-11-30 18:45:03.301 UTC client backend[44081] pg_regress/stats_import WARNING: argument "range_length_histogram" must be specified when argument "range_empty_frac" is specified 2025-11-30 18:45:03.306 UTC client backend[44084] pg_regress/regex ERROR: invalid regular expression: regular expression is too complex 2025-11-30 18:45:03.306 UTC client backend[44084] pg_regress/regex STATEMENT: select 'x' ~ repeat('x*y*z*', 1000); 2025-11-30 18:45:03.306 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:03.312 UTC checkpointer[43405] LOG: checkpoint complete: wrote 188 buffers (1.1%), wrote 2 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.007 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1548 kB, estimate=78121 kB; lsn=0/0C8B37B8, redo lsn=0/0C889318 2025-11-30 18:45:03.312 UTC client backend[44081] pg_regress/stats_import WARNING: column "id" is not a range type 2025-11-30 18:45:03.312 UTC client backend[44081] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM. 2025-11-30 18:45:03.306 UTC client backend[44106] pg_regress/name LOG: disconnection: session time: 0:00:00.039 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:03.319 UTC client backend[44081] pg_regress/stats_import WARNING: could not determine element type of column "arange" 2025-11-30 18:45:03.319 UTC client backend[44081] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-11-30 18:45:03.322 UTC client backend[44081] pg_regress/stats_import WARNING: could not determine element type of column "id" 2025-11-30 18:45:03.322 UTC client backend[44081] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-11-30 18:45:03.323 UTC unrecognized[44114] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.324 UTC client backend[44083] pg_regress/xid LOG: disconnection: session time: 0:00:00.274 user=postgres database=regression host=[local] 2025-11-30 18:45:03.324 UTC client backend[44081] pg_regress/stats_import WARNING: argument "most_common_elem_freqs" must be specified when argument "most_common_elems" is specified 2025-11-30 18:45:03.325 UTC client backend[44107] [unknown] LOG: disconnection: session time: 0:00:00.052 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.327 UTC client backend[44114] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.327 UTC client backend[44114] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.328 UTC client backend[44081] pg_regress/stats_import WARNING: argument "most_common_elems" must be specified when argument "most_common_elem_freqs" is specified 2025-11-30 18:45:03.328 UTC client backend[44114] pg_regress LOG: connection ready: setup total=7.377 ms, fork=1.765 ms, authentication=0.115 ms 2025-11-30 18:45:03.331 UTC unrecognized[44116] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.332 UTC client backend[44116] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.332 UTC client backend[44116] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/bool 2025-11-30 18:45:03.333 UTC client backend[44116] pg_regress/bool LOG: connection ready: setup total=10.259 ms, fork=4.334 ms, authentication=0.108 ms 2025-11-30 18:45:03.337 UTC client backend[44081] pg_regress/stats_import WARNING: could not determine element type of column "id" 2025-11-30 18:45:03.337 UTC client backend[44081] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-11-30 18:45:03.345 UTC client backend[44114] pg_regress LOG: disconnection: session time: 0:00:00.022 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.360 UTC client backend[44101] pg_regress/varchar LOG: disconnection: session time: 0:00:00.086 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.360 UTC unrecognized[44119] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.360 UTC client backend[44119] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.360 UTC client backend[44119] [unknown] LOG: connection authorized: user=postgres database=regression_dblink 2025-11-30 18:45:03.361 UTC unrecognized[44120] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.361 UTC client backend[44119] [unknown] LOG: connection ready: setup total=3.201 ms, fork=1.820 ms, authentication=0.125 ms 2025-11-30 18:45:03.364 UTC client backend[44120] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.364 UTC client backend[44120] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.365 UTC client backend[44120] pg_regress LOG: connection ready: setup total=4.778 ms, fork=0.660 ms, authentication=0.101 ms 2025-11-30 18:45:03.368 UTC client backend[44120] pg_regress LOG: disconnection: session time: 0:00:00.006 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.374 UTC client backend[44099] pg_regress/dblink ERROR: invalid input syntax for type integer: "not an int" 2025-11-30 18:45:03.374 UTC client backend[44099] pg_regress/dblink STATEMENT: SELECT * FROM dblink_fetch('myconn','error_cursor', 1) AS t(i int); 2025-11-30 18:45:03.374 UTC client backend[44119] [unknown] LOG: disconnection: session time: 0:00:00.014 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.378 UTC client backend[44116] pg_regress/bool LOG: disconnection: session time: 0:00:00.051 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:03.379 UTC unrecognized[44124] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.379 UTC client backend[44099] pg_regress/dblink LOG: disconnection: session time: 0:00:00.150 user=postgres database=regression_dblink host=[local] 2025-11-30 18:45:03.379 UTC client backend[44124] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.379 UTC client backend[44124] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.380 UTC client backend[44124] pg_regress LOG: connection ready: setup total=3.241 ms, fork=1.848 ms, authentication=0.110 ms 2025-11-30 18:45:03.386 UTC unrecognized[44127] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.387 UTC client backend[44127] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.387 UTC client backend[44127] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.388 UTC client backend[44127] pg_regress LOG: connection ready: setup total=1.728 ms, fork=0.437 ms, authentication=0.126 ms 2025-11-30 18:45:03.388 UTC client backend[44124] pg_regress LOG: disconnection: session time: 0:00:00.009 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.395 UTC unrecognized[44130] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.395 UTC unrecognized[44132] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.395 UTC client backend[44130] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.395 UTC client backend[44130] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/char 2025-11-30 18:45:03.395 UTC client backend[44132] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.395 UTC client backend[44132] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gin application_name=pg_regress/bpchar 2025-11-30 18:45:03.396 UTC client backend[44130] pg_regress/char LOG: connection ready: setup total=2.109 ms, fork=0.457 ms, authentication=0.109 ms 2025-11-30 18:45:03.396 UTC client backend[44132] pg_regress/bpchar LOG: connection ready: setup total=1.658 ms, fork=0.282 ms, authentication=0.096 ms 2025-11-30 18:45:03.397 UTC client backend[44072] pg_regress/geometry ERROR: open path cannot be converted to polygon 2025-11-30 18:45:03.397 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT f1, f1::polygon FROM PATH_TBL WHERE isopen(f1); 2025-11-30 18:45:03.397 UTC unrecognized[44131] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.398 UTC client backend[44131] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.398 UTC client backend[44131] [unknown] LOG: connection authorized: user=postgres database=regression_file_fdw application_name=pg_regress/file_fdw 2025-11-30 18:45:03.400 UTC client backend[44127] pg_regress LOG: disconnection: session time: 0:00:00.013 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.401 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:03.402 UTC client backend[44131] pg_regress/file_fdw LOG: connection ready: setup total=7.588 ms, fork=2.670 ms, authentication=0.094 ms 2025-11-30 18:45:03.409 UTC checkpointer[43405] LOG: checkpoint complete: wrote 2162 buffers (13.2%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 1 recycled; write=0.008 s, sync=0.001 s, total=0.008 s; sync files=0, longest=0.000 s, average=0.000 s; distance=10334 kB, estimate=71342 kB; lsn=0/0D2DE6C8, redo lsn=0/0D2A0EB8 2025-11-30 18:45:03.410 UTC client backend[44084] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:03.410 UTC client backend[44084] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=\1)'; 2025-11-30 18:45:03.411 UTC client backend[44084] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:03.411 UTC client backend[44084] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=(\1))'; 2025-11-30 18:45:03.415 UTC client backend[44072] pg_regress/geometry ERROR: division by zero 2025-11-30 18:45:03.415 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT p.f1, p1.f1, p.f1 / p1.f1 FROM PATH_TBL p, POINT_TBL p1 WHERE p1.f1 ~= '(0,0)'::point; 2025-11-30 18:45:03.420 UTC client backend[44084] pg_regress/regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:03.420 UTC client backend[44084] pg_regress/regex STATEMENT: select 'a' ~ '\x7fffffff'; 2025-11-30 18:45:03.422 UTC unrecognized[44134] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.423 UTC client backend[44131] pg_regress/file_fdw ERROR: permission denied to create foreign-data wrapper "file_fdw2" 2025-11-30 18:45:03.423 UTC client backend[44131] pg_regress/file_fdw HINT: Must be superuser to create a foreign-data wrapper. 2025-11-30 18:45:03.423 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN DATA WRAPPER file_fdw2 HANDLER file_fdw_handler VALIDATOR file_fdw_validator; 2025-11-30 18:45:03.423 UTC client backend[44131] pg_regress/file_fdw ERROR: permission denied for foreign-data wrapper file_fdw 2025-11-30 18:45:03.423 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE SERVER file_server2 FOREIGN DATA WRAPPER file_fdw; 2025-11-30 18:45:03.423 UTC client backend[44131] pg_regress/file_fdw ERROR: permission denied for foreign server file_server 2025-11-30 18:45:03.423 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE USER MAPPING FOR regress_file_fdw_user SERVER file_server; 2025-11-30 18:45:03.425 UTC client backend[44134] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.425 UTC client backend[44134] [unknown] LOG: connection authorized: user=postgres database=regression_earthdistance application_name=pg_regress/earthdistance 2025-11-30 18:45:03.425 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "foo" 2025-11-30 18:45:03.425 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (foo 'bar'); 2025-11-30 18:45:03.425 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option name "a=b": must not contain "=" 2025-11-30 18:45:03.425 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS ("a=b" 'true'); 2025-11-30 18:45:03.426 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY format "xml" not recognized 2025-11-30 18:45:03.426 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'xml'); 2025-11-30 18:45:03.427 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY QUOTE requires CSV mode 2025-11-30 18:45:03.427 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', quote ':'); 2025-11-30 18:45:03.427 UTC client backend[44088] pg_regress/horology ERROR: invalid value "JUNK" for "TZ" 2025-11-30 18:45:03.427 UTC client backend[44088] pg_regress/horology DETAIL: Time zone abbreviation is not recognized. 2025-11-30 18:45:03.427 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 JUNK', 'YYYY-MM-DD HH12:MI TZ'); 2025-11-30 18:45:03.427 UTC client backend[44088] pg_regress/horology ERROR: invalid value ".." for "TZ" 2025-11-30 18:45:03.427 UTC client backend[44088] pg_regress/horology DETAIL: Value must be an integer. 2025-11-30 18:45:03.427 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 ...', 'YYYY-MM-DD HH12:MI TZ'); 2025-11-30 18:45:03.427 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY ESCAPE requires CSV mode 2025-11-30 18:45:03.427 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', escape ':'); 2025-11-30 18:45:03.428 UTC client backend[44088] pg_regress/horology ERROR: invalid value "xy" for "OF" 2025-11-30 18:45:03.428 UTC client backend[44088] pg_regress/horology DETAIL: Value must be an integer. 2025-11-30 18:45:03.428 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +xyz', 'YYYY-MM-DD HH12:MI OF'); 2025-11-30 18:45:03.428 UTC client backend[44088] pg_regress/horology ERROR: invalid value "xy" for "OF" 2025-11-30 18:45:03.428 UTC client backend[44088] pg_regress/horology DETAIL: Value must be an integer. 2025-11-30 18:45:03.428 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +01:xyz', 'YYYY-MM-DD HH12:MI OF'); 2025-11-30 18:45:03.428 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot specify HEADER in BINARY mode 2025-11-30 18:45:03.428 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'binary', header 'true'); 2025-11-30 18:45:03.428 UTC client backend[44132] pg_regress/bpchar LOG: disconnection: session time: 0:00:00.033 user=postgres database=regression_btree_gin host=[local] 2025-11-30 18:45:03.429 UTC client backend[44134] pg_regress/earthdistance LOG: connection ready: setup total=13.028 ms, fork=5.591 ms, authentication=0.114 ms 2025-11-30 18:45:03.429 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2018-11-02 12:34:56.123456789" 2025-11-30 18:45:03.429 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT i, to_timestamp('2018-11-02 12:34:56.123456789', 'YYYY-MM-DD HH24:MI:SS.FF' || i) FROM generate_series(1, 6) i; 2025-11-30 18:45:03.429 UTC client backend[44084] pg_regress/regex LOG: disconnection: session time: 0:00:00.370 user=postgres database=regression host=[local] 2025-11-30 18:45:03.431 UTC client backend[44134] pg_regress/earthdistance ERROR: required extension "cube" is not installed 2025-11-30 18:45:03.431 UTC client backend[44134] pg_regress/earthdistance HINT: Use CREATE EXTENSION ... CASCADE to install required extensions too. 2025-11-30 18:45:03.431 UTC client backend[44134] pg_regress/earthdistance STATEMENT: CREATE EXTENSION earthdistance; 2025-11-30 18:45:03.431 UTC client backend[44088] pg_regress/horology ERROR: invalid value "+" for "MON" 2025-11-30 18:45:03.431 UTC client backend[44088] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2025-11-30 18:45:03.431 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2000 + + JUN', 'YYYY MON'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: invalid value "x1" for "MM" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: Value must be an integer. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('2011 x12 x18', 'YYYYxMMxDD'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: invalid combination of date conventions 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology HINT: Do not mix Gregorian and ISO week date conventions in a formatting template. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2005527', 'YYYYIWID'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: source string too short for "MM" formatting field 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 remain. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('19971', 'YYYYMMDD'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: invalid value "1)" for "MM" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 could be parsed. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('19971)24', 'YYYYMMDD'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: invalid value "da" for "DD" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: Value must be an integer. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('Friday 1-January-1999', 'DY DD MON YYYY'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: invalid value "uary" for "YYYY" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: Value must be an integer. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('Fri 1-January-1999', 'DY DD MON YYYY'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: conflicting values for "Mon" field in formatting string 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: This value contradicts a previous setting for the same field type. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('1997-11-Jan-16', 'YYYY-MM-Mon-DD'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: invalid value "xy" for "DD" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: Value must be an integer. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('199711xy', 'YYYYMMDD'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: value for "YYYY" in source string is out of range 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology DETAIL: Value must be in the range -2147483648 to 2147483647. 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('10000000000', 'FMYYYY'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 25:00:00" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 25:00:00', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:60:00" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:60:00', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:50:60" 2025-11-30 18:45:03.432 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:60', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: hour "15" is invalid for the 12-hour clock 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology HINT: Use the 24-hour clock, or give an hour between 1 and 12. 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:55', 'YYYY-MM-DD HH:MI:SS'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016-13-01 15:50:55" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-13-01 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30 15:50:55" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-02-30 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29 15:50:55" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-29 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-30 18:45:03.433 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY QUOTE requires CSV mode 2025-11-30 18:45:03.433 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'binary', quote ':'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSS'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSSS'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: value for "Y,YYY" in source string is out of range 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('1000000000,999', 'Y,YYY'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "0.-2147483648" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('0.-2147483648', 'SS.MS'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "613566758" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('613566758', 'W'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2024 613566758 1" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_timestamp('2024 613566758 1', 'YYYY WW D'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016-13-10" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('2016-13-10', 'YYYY-MM-DD'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('2016-02-30', 'YYYY-MM-DD'); 2025-11-30 18:45:03.433 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY ESCAPE requires CSV mode 2025-11-30 18:45:03.433 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'binary', escape ':'); 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29" 2025-11-30 18:45:03.433 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('2015-02-29', 'YYYY-MM-DD'); 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2015 366" 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('2015 366', 'YYYY DDD'); 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2016 367" 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('2016 367', 'YYYY DDD'); 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "100000000" 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('100000000', 'CC'); 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "-100000000" 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('-100000000', 'CC'); 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "-2147483648 01" 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('-2147483648 01', 'CC YY'); 2025-11-30 18:45:03.434 UTC client backend[44072] pg_regress/geometry ERROR: must request at least 2 points 2025-11-30 18:45:03.434 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT f1, polygon(1, f1) FROM CIRCLE_TBL WHERE f1 >= '<(0,0),1>'; 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology ERROR: date/time field value out of range: "2147483647 01" 2025-11-30 18:45:03.434 UTC client backend[44088] pg_regress/horology STATEMENT: SELECT to_date('2147483647 01', 'CC YY'); 2025-11-30 18:45:03.434 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter cannot be "a" 2025-11-30 18:45:03.434 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', delimiter 'a'); 2025-11-30 18:45:03.434 UTC client backend[44072] pg_regress/geometry ERROR: cannot convert circle with radius zero to polygon 2025-11-30 18:45:03.434 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT f1, polygon(10, f1) FROM CIRCLE_TBL WHERE f1 < '<(0,0),1>'; 2025-11-30 18:45:03.434 UTC client backend[44130] pg_regress/char LOG: disconnection: session time: 0:00:00.039 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.435 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY ESCAPE requires CSV mode 2025-11-30 18:45:03.435 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', escape '-'); 2025-11-30 18:45:03.435 UTC client backend[44131] pg_regress/file_fdw ERROR: CSV quote character must not appear in the NULL specification 2025-11-30 18:45:03.435 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', quote '-', null '=-='); 2025-11-30 18:45:03.435 UTC client backend[44088] pg_regress/horology LOG: disconnection: session time: 0:00:00.369 user=postgres database=regression host=[local] 2025-11-30 18:45:03.440 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter character must not appear in the NULL specification 2025-11-30 18:45:03.440 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', delimiter '-', null '=-='); 2025-11-30 18:45:03.441 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter and quote must be different 2025-11-30 18:45:03.441 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', delimiter '-', quote '-'); 2025-11-30 18:45:03.442 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter must be a single one-byte character 2025-11-30 18:45:03.442 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', delimiter '---'); 2025-11-30 18:45:03.443 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY quote must be a single one-byte character 2025-11-30 18:45:03.443 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', quote '---'); 2025-11-30 18:45:03.446 UTC client backend[44079] pg_regress/database LOG: disconnection: session time: 0:00:00.398 user=postgres database=regression host=[local] 2025-11-30 18:45:03.447 UTC client backend[44072] pg_regress/geometry ERROR: value out of range: overflow 2025-11-30 18:45:03.447 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT c.f1, p.f1, c.f1 / p.f1 FROM CIRCLE_TBL c, POINT_TBL p WHERE p.f1[0] > 1000; 2025-11-30 18:45:03.448 UTC client backend[44072] pg_regress/geometry ERROR: division by zero 2025-11-30 18:45:03.448 UTC client backend[44072] pg_regress/geometry STATEMENT: SELECT c.f1, p.f1, c.f1 / p.f1 FROM CIRCLE_TBL c, POINT_TBL p WHERE p.f1 ~= '(0,0)'::point; 2025-11-30 18:45:03.454 UTC client backend[44072] pg_regress/geometry LOG: disconnection: session time: 0:00:00.416 user=postgres database=regression host=[local] 2025-11-30 18:45:03.461 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY escape must be a single one-byte character 2025-11-30 18:45:03.461 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', escape '---'); 2025-11-30 18:45:03.461 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter cannot be "\" 2025-11-30 18:45:03.461 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', delimiter '\'); 2025-11-30 18:45:03.462 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter cannot be "." 2025-11-30 18:45:03.462 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', delimiter '.'); 2025-11-30 18:45:03.462 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter cannot be "1" 2025-11-30 18:45:03.462 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', delimiter '1'); 2025-11-30 18:45:03.463 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter cannot be "a" 2025-11-30 18:45:03.463 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'text', delimiter 'a'); 2025-11-30 18:45:03.463 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY delimiter cannot be newline or carriage return 2025-11-30 18:45:03.463 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', delimiter ' '); 2025-11-30 18:45:03.464 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY null representation cannot use newline or carriage return 2025-11-30 18:45:03.464 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'csv', null ' '); 2025-11-30 18:45:03.465 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY ON_ERROR "unsupported" not recognized 2025-11-30 18:45:03.465 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (on_error 'unsupported'); 2025-11-30 18:45:03.465 UTC client backend[44131] pg_regress/file_fdw ERROR: only ON_ERROR STOP is allowed in BINARY mode 2025-11-30 18:45:03.465 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (format 'binary', on_error 'ignore'); 2025-11-30 18:45:03.466 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY LOG_VERBOSITY "unsupported" not recognized 2025-11-30 18:45:03.466 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (log_verbosity 'unsupported'); 2025-11-30 18:45:03.466 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY REJECT_LIMIT requires ON_ERROR to be set to IGNORE 2025-11-30 18:45:03.466 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (reject_limit '1'); 2025-11-30 18:45:03.467 UTC client backend[44131] pg_regress/file_fdw ERROR: REJECT_LIMIT (0) must be greater than zero 2025-11-30 18:45:03.467 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (on_error 'ignore', reject_limit '0'); 2025-11-30 18:45:03.470 UTC unrecognized[44139] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.474 UTC client backend[44139] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.474 UTC client backend[44139] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/bytea 2025-11-30 18:45:03.475 UTC client backend[44139] pg_regress/bytea LOG: connection ready: setup total=12.517 ms, fork=4.511 ms, authentication=0.111 ms 2025-11-30 18:45:03.477 UTC client backend[44131] pg_regress/file_fdw ERROR: either filename or program is required for file_fdw foreign tables 2025-11-30 18:45:03.477 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server; 2025-11-30 18:45:03.486 UTC client backend[44131] pg_regress/file_fdw ERROR: column name mismatch in header line field 1: got "1", expected "a" 2025-11-30 18:45:03.486 UTC client backend[44131] pg_regress/file_fdw CONTEXT: COPY header_doesnt_match, line 1: "1,foo" 2025-11-30 18:45:03.486 UTC client backend[44131] pg_regress/file_fdw STATEMENT: SELECT * FROM header_doesnt_match; 2025-11-30 18:45:03.487 UTC client backend[44131] pg_regress/file_fdw ERROR: COPY FORCE_NOT_NULL requires CSV mode 2025-11-30 18:45:03.487 UTC client backend[44131] pg_regress/file_fdw STATEMENT: SELECT * FROM text_csv; 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_not_null" 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw HINT: There are no valid options in this context. 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw STATEMENT: ALTER FOREIGN DATA WRAPPER file_fdw OPTIONS (ADD force_not_null '*'); 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_not_null" 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw HINT: There are no valid options in this context. 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw STATEMENT: ALTER SERVER file_server OPTIONS (ADD force_not_null '*'); 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_not_null" 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw HINT: There are no valid options in this context. 2025-11-30 18:45:03.488 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE USER MAPPING FOR public SERVER file_server OPTIONS (force_not_null '*'); 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_not_null" 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (force_not_null '*'); 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_null" 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw HINT: There are no valid options in this context. 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw STATEMENT: ALTER FOREIGN DATA WRAPPER file_fdw OPTIONS (ADD force_null '*'); 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_null" 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw HINT: There are no valid options in this context. 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw STATEMENT: ALTER SERVER file_server OPTIONS (ADD force_null '*'); 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_null" 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw HINT: There are no valid options in this context. 2025-11-30 18:45:03.489 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE USER MAPPING FOR public SERVER file_server OPTIONS (force_null '*'); 2025-11-30 18:45:03.490 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid option "force_null" 2025-11-30 18:45:03.490 UTC client backend[44131] pg_regress/file_fdw STATEMENT: CREATE FOREIGN TABLE tbl () SERVER file_server OPTIONS (force_null '*'); 2025-11-30 18:45:03.514 UTC client backend[44081] pg_regress/stats_import LOG: disconnection: session time: 0:00:00.469 user=postgres database=regression host=[local] 2025-11-30 18:45:03.517 UTC client backend[44134] pg_regress/earthdistance ERROR: cannot drop extension cube because other objects depend on it 2025-11-30 18:45:03.517 UTC client backend[44134] pg_regress/earthdistance DETAIL: extension earthdistance depends on extension cube 2025-11-30 18:45:03.517 UTC client backend[44134] pg_regress/earthdistance HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:03.517 UTC client backend[44134] pg_regress/earthdistance STATEMENT: drop extension cube; 2025-11-30 18:45:03.518 UTC client backend[44131] pg_regress/file_fdw ERROR: invalid input syntax for type real: "aaa" 2025-11-30 18:45:03.518 UTC client backend[44131] pg_regress/file_fdw CONTEXT: COPY agg_bad, line 3, column b: "aaa" 2025-11-30 18:45:03.518 UTC client backend[44131] pg_regress/file_fdw STATEMENT: SELECT * FROM agg_bad; 2025-11-30 18:45:03.520 UTC client backend[44134] pg_regress/earthdistance ERROR: cannot drop type cube because extension cube requires it 2025-11-30 18:45:03.520 UTC client backend[44134] pg_regress/earthdistance HINT: You can drop extension cube instead. 2025-11-30 18:45:03.520 UTC client backend[44134] pg_regress/earthdistance STATEMENT: drop type cube; 2025-11-30 18:45:03.520 UTC client backend[44131] pg_regress/file_fdw ERROR: skipped more than REJECT_LIMIT (1) rows due to data type incompatibility 2025-11-30 18:45:03.520 UTC client backend[44131] pg_regress/file_fdw CONTEXT: COPY agg_bad, line 5, column b: "bbb" 2025-11-30 18:45:03.520 UTC client backend[44131] pg_regress/file_fdw STATEMENT: SELECT * FROM agg_bad; 2025-11-30 18:45:03.521 UTC unrecognized[44143] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.525 UTC client backend[44143] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.525 UTC client backend[44143] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.526 UTC client backend[44143] pg_regress LOG: connection ready: setup total=8.751 ms, fork=3.528 ms, authentication=0.119 ms 2025-11-30 18:45:03.526 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot insert into foreign table "agg_csv" 2025-11-30 18:45:03.526 UTC client backend[44131] pg_regress/file_fdw STATEMENT: INSERT INTO agg_csv VALUES(1,2.0); 2025-11-30 18:45:03.526 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot update foreign table "agg_csv" 2025-11-30 18:45:03.526 UTC client backend[44131] pg_regress/file_fdw STATEMENT: UPDATE agg_csv SET a = 1; 2025-11-30 18:45:03.527 UTC client backend[44143] pg_regress LOG: disconnection: session time: 0:00:00.006 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.527 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot delete from foreign table "agg_csv" 2025-11-30 18:45:03.527 UTC client backend[44131] pg_regress/file_fdw STATEMENT: DELETE FROM agg_csv WHERE a = 100; 2025-11-30 18:45:03.527 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot truncate foreign table "agg_csv" 2025-11-30 18:45:03.527 UTC client backend[44131] pg_regress/file_fdw STATEMENT: TRUNCATE agg_csv; 2025-11-30 18:45:03.527 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot insert into foreign table "agg_csv" 2025-11-30 18:45:03.527 UTC client backend[44131] pg_regress/file_fdw STATEMENT: COPY agg_csv FROM STDIN; 2025-11-30 18:45:03.529 UTC client backend[44134] pg_regress/earthdistance ERROR: cannot drop extension cube because other objects depend on it 2025-11-30 18:45:03.529 UTC client backend[44134] pg_regress/earthdistance DETAIL: column f1 of table foo depends on type cube 2025-11-30 18:45:03.529 UTC client backend[44134] pg_regress/earthdistance HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:03.529 UTC client backend[44134] pg_regress/earthdistance STATEMENT: drop extension cube; 2025-11-30 18:45:03.533 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot update foreign table "agg_csv" 2025-11-30 18:45:03.533 UTC client backend[44131] pg_regress/file_fdw STATEMENT: UPDATE agg SET a = 1; 2025-11-30 18:45:03.534 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot delete from foreign table "agg_csv" 2025-11-30 18:45:03.534 UTC client backend[44131] pg_regress/file_fdw STATEMENT: DELETE FROM agg WHERE a = 100; 2025-11-30 18:45:03.541 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot insert into foreign table "p1" 2025-11-30 18:45:03.541 UTC client backend[44131] pg_regress/file_fdw CONTEXT: COPY pt, line 2: "1,qux" 2025-11-30 18:45:03.541 UTC client backend[44131] pg_regress/file_fdw STATEMENT: COPY pt FROM '/tmp/cirrus-ci-build/contrib/file_fdw/data/list2.bad' with (format 'csv', delimiter ','); 2025-11-30 18:45:03.542 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot insert into foreign table "p1" 2025-11-30 18:45:03.542 UTC client backend[44131] pg_regress/file_fdw STATEMENT: INSERT INTO pt VALUES (1, 'xyzzy'); 2025-11-30 18:45:03.543 UTC client backend[44131] pg_regress/file_fdw ERROR: cannot insert into foreign table "p1" 2025-11-30 18:45:03.543 UTC client backend[44131] pg_regress/file_fdw STATEMENT: UPDATE pt set a = 1 where a = 2; 2025-11-30 18:45:03.553 UTC unrecognized[44146] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.554 UTC client backend[44146] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.554 UTC client backend[44146] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.554 UTC client backend[44146] pg_regress LOG: connection ready: setup total=4.321 ms, fork=2.952 ms, authentication=0.113 ms 2025-11-30 18:45:03.556 UTC client backend[44139] pg_regress/bytea LOG: disconnection: session time: 0:00:00.088 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.568 UTC unrecognized[44151] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.568 UTC client backend[44131] pg_regress/file_fdw ERROR: permission denied for foreign table agg_text 2025-11-30 18:45:03.568 UTC client backend[44131] pg_regress/file_fdw STATEMENT: SELECT * FROM agg_text ORDER BY a; 2025-11-30 18:45:03.568 UTC client backend[44151] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.568 UTC client backend[44151] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/bit 2025-11-30 18:45:03.569 UTC client backend[44151] pg_regress/bit LOG: connection ready: setup total=4.481 ms, fork=2.893 ms, authentication=0.128 ms 2025-11-30 18:45:03.570 UTC unrecognized[44148] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.571 UTC client backend[44148] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.571 UTC client backend[44148] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.571 UTC client backend[44148] pg_regress LOG: connection ready: setup total=16.586 ms, fork=15.320 ms, authentication=0.105 ms 2025-11-30 18:45:03.572 UTC client backend[44148] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.586 UTC client backend[44131] pg_regress/file_fdw ERROR: permission denied to set the "filename" option of a file_fdw foreign table 2025-11-30 18:45:03.586 UTC client backend[44131] pg_regress/file_fdw DETAIL: Only roles with privileges of the "pg_read_server_files" role may set this option. 2025-11-30 18:45:03.586 UTC client backend[44131] pg_regress/file_fdw STATEMENT: ALTER FOREIGN TABLE agg_text OPTIONS (SET format 'text'); 2025-11-30 18:45:03.589 UTC client backend[44074] pg_regress/type_sanity LOG: disconnection: session time: 0:00:00.550 user=postgres database=regression host=[local] 2025-11-30 18:45:03.595 UTC client backend[44146] pg_regress LOG: disconnection: session time: 0:00:00.042 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.596 UTC client backend[44131] pg_regress/file_fdw LOG: disconnection: session time: 0:00:00.198 user=postgres database=regression_file_fdw host=[local] 2025-11-30 18:45:03.603 UTC unrecognized[44156] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.603 UTC client backend[44156] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.603 UTC client backend[44156] [unknown] LOG: connection authorized: user=postgres database=regression_fuzzystrmatch application_name=pg_regress/fuzzystrmatch 2025-11-30 18:45:03.604 UTC client backend[44151] pg_regress/bit LOG: disconnection: session time: 0:00:00.036 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.608 UTC client backend[44156] pg_regress/fuzzystrmatch LOG: connection ready: setup total=7.718 ms, fork=0.745 ms, authentication=0.127 ms 2025-11-30 18:45:03.609 UTC unrecognized[44153] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.610 UTC client backend[44153] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.610 UTC client backend[44153] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.610 UTC client backend[44153] pg_regress LOG: connection ready: setup total=32.355 ms, fork=31.037 ms, authentication=0.110 ms 2025-11-30 18:45:03.616 UTC client backend[44156] pg_regress/fuzzystrmatch LOG: disconnection: session time: 0:00:00.014 user=postgres database=regression_fuzzystrmatch host=[local] 2025-11-30 18:45:03.617 UTC unrecognized[44160] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.617 UTC client backend[44160] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.617 UTC client backend[44160] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/varbit 2025-11-30 18:45:03.618 UTC client backend[44160] pg_regress/varbit LOG: connection ready: setup total=3.033 ms, fork=1.476 ms, authentication=0.118 ms 2025-11-30 18:45:03.637 UTC client backend[44160] pg_regress/varbit LOG: disconnection: session time: 0:00:00.020 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.644 UTC unrecognized[44166] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.644 UTC client backend[44166] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.644 UTC client backend[44166] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/numeric 2025-11-30 18:45:03.645 UTC client backend[44166] pg_regress/numeric LOG: connection ready: setup total=2.258 ms, fork=0.774 ms, authentication=0.105 ms 2025-11-30 18:45:03.648 UTC unrecognized[44168] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.649 UTC client backend[44168] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.649 UTC client backend[44168] [unknown] LOG: connection authorized: user=postgres database=regression_fuzzystrmatch application_name=pg_regress/fuzzystrmatch_utf8 2025-11-30 18:45:03.650 UTC client backend[44168] pg_regress/fuzzystrmatch_utf8 LOG: connection ready: setup total=2.486 ms, fork=0.759 ms, authentication=0.103 ms 2025-11-30 18:45:03.657 UTC client backend[43482] pg_regress/check_btree LOG: disconnection: session time: 0:00:03.072 user=postgres database=regression_amcheck host=[local] 2025-11-30 18:45:03.659 UTC client backend[44168] pg_regress/fuzzystrmatch_utf8 LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression_fuzzystrmatch host=[local] 2025-11-30 18:45:03.671 UTC client backend[44153] pg_regress LOG: disconnection: session time: 0:00:00.061 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.672 UTC unrecognized[44170] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.673 UTC client backend[44170] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.673 UTC client backend[44170] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.674 UTC client backend[44170] pg_regress LOG: connection ready: setup total=23.394 ms, fork=21.126 ms, authentication=0.120 ms 2025-11-30 18:45:03.674 UTC client backend[44170] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.675 UTC unrecognized[44174] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.675 UTC client backend[44174] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.675 UTC client backend[44174] [unknown] LOG: connection authorized: user=postgres database=regression_hstore application_name=pg_regress/hstore 2025-11-30 18:45:03.680 UTC client backend[44174] pg_regress/hstore LOG: connection ready: setup total=6.802 ms, fork=1.785 ms, authentication=0.118 ms 2025-11-30 18:45:03.687 UTC unrecognized[44177] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.688 UTC client backend[44177] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.688 UTC client backend[44177] [unknown] LOG: connection authorized: user=postgres database=regression_amcheck application_name=pg_regress/check_gin 2025-11-30 18:45:03.689 UTC client backend[44177] pg_regress/check_gin LOG: connection ready: setup total=8.682 ms, fork=7.134 ms, authentication=0.117 ms 2025-11-30 18:45:03.708 UTC unrecognized[44178] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.708 UTC client backend[44178] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.708 UTC client backend[44178] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.709 UTC client backend[44178] pg_regress LOG: connection ready: setup total=3.985 ms, fork=2.627 ms, authentication=0.112 ms 2025-11-30 18:45:03.719 UTC unrecognized[44181] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.719 UTC client backend[44181] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.719 UTC client backend[44181] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.720 UTC client backend[44181] pg_regress LOG: connection ready: setup total=3.701 ms, fork=2.414 ms, authentication=0.118 ms 2025-11-30 18:45:03.720 UTC client backend[44181] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.724 UTC client backend[44166] pg_regress/numeric LOG: disconnection: session time: 0:00:00.079 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.726 UTC unrecognized[44184] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.727 UTC client backend[44184] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.727 UTC client backend[44184] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:03.728 UTC client backend[44184] pg_regress LOG: connection ready: setup total=2.410 ms, fork=1.091 ms, authentication=0.108 ms 2025-11-30 18:45:03.734 UTC client backend[44174] pg_regress/hstore ERROR: syntax error in hstore, near "=" at position 2 at character 8 2025-11-30 18:45:03.734 UTC client backend[44174] pg_regress/hstore STATEMENT: select ' =>null'::hstore; 2025-11-30 18:45:03.734 UTC client backend[44174] pg_regress/hstore ERROR: syntax error in hstore: unexpected end of string at character 8 2025-11-30 18:45:03.734 UTC client backend[44174] pg_regress/hstore STATEMENT: select 'aa=>"'::hstore; 2025-11-30 18:45:03.736 UTC unrecognized[44186] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.736 UTC client backend[44178] pg_regress LOG: disconnection: session time: 0:00:00.028 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.736 UTC client backend[44186] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.736 UTC client backend[44186] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/uuid 2025-11-30 18:45:03.737 UTC client backend[44186] pg_regress/uuid LOG: connection ready: setup total=2.145 ms, fork=0.534 ms, authentication=0.126 ms 2025-11-30 18:45:03.738 UTC client backend[44134] pg_regress/earthdistance ERROR: cannot drop extension cube because other objects depend on it 2025-11-30 18:45:03.738 UTC client backend[44134] pg_regress/earthdistance DETAIL: column f1 of table foo depends on type c.cube 2025-11-30 18:45:03.738 UTC client backend[44134] pg_regress/earthdistance HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:03.738 UTC client backend[44134] pg_regress/earthdistance STATEMENT: drop extension cube; 2025-11-30 18:45:03.743 UTC client backend[44184] pg_regress LOG: disconnection: session time: 0:00:00.016 user=postgres database=postgres host=[local] 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore ERROR: array must have even number of elements 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore STATEMENT: select ARRAY['a','g','b','h','asd']::hstore; 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore ERROR: array must have two columns 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore STATEMENT: select ARRAY[['a','g','b'],['h','asd','i']]::hstore; 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore ERROR: wrong number of array subscripts 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore STATEMENT: select ARRAY[[['a','g'],['b','h'],['asd','i']]]::hstore; 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore ERROR: array must have even number of elements 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore STATEMENT: select hstore(ARRAY['a','g','b','h','asd']); 2025-11-30 18:45:03.747 UTC unrecognized[44188] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore ERROR: array must have two columns 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore STATEMENT: select hstore(ARRAY[['a','g','b'],['h','asd','i']]); 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore ERROR: wrong number of array subscripts 2025-11-30 18:45:03.747 UTC client backend[44174] pg_regress/hstore STATEMENT: select hstore(ARRAY[[['a','g'],['b','h'],['asd','i']]]); 2025-11-30 18:45:03.747 UTC client backend[44188] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.747 UTC client backend[44188] [unknown] LOG: connection authorized: user=postgres database=regression_hstore_plperl application_name=pg_regress/hstore_plperl 2025-11-30 18:45:03.748 UTC client backend[44174] pg_regress/hstore ERROR: arrays must have same bounds 2025-11-30 18:45:03.748 UTC client backend[44174] pg_regress/hstore STATEMENT: select hstore(ARRAY['a'], '{}'::text[]); 2025-11-30 18:45:03.748 UTC client backend[44174] pg_regress/hstore ERROR: arrays must have same bounds 2025-11-30 18:45:03.748 UTC client backend[44174] pg_regress/hstore STATEMENT: select hstore('{}'::text[], ARRAY['a']); 2025-11-30 18:45:03.752 UTC client backend[44188] pg_regress/hstore_plperl LOG: connection ready: setup total=5.861 ms, fork=0.737 ms, authentication=0.105 ms 2025-11-30 18:45:03.754 UTC client backend[44134] pg_regress/earthdistance ERROR: cannot drop schema c because other objects depend on it 2025-11-30 18:45:03.754 UTC client backend[44134] pg_regress/earthdistance DETAIL: extension cube depends on schema c column f1 of table foo depends on type c.cube 2025-11-30 18:45:03.754 UTC client backend[44134] pg_regress/earthdistance HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:03.754 UTC client backend[44134] pg_regress/earthdistance STATEMENT: drop schema c; 2025-11-30 18:45:03.754 UTC client backend[44186] pg_regress/uuid LOG: disconnection: session time: 0:00:00.018 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.758 UTC client backend[44174] pg_regress/hstore ERROR: domain hstestdom1 does not allow null values 2025-11-30 18:45:03.758 UTC client backend[44174] pg_regress/hstore STATEMENT: select populate_record(v, hstore('e', null)) from testhstore1 v; 2025-11-30 18:45:03.759 UTC client backend[44174] pg_regress/hstore ERROR: domain hstestdom1 does not allow null values 2025-11-30 18:45:03.759 UTC client backend[44174] pg_regress/hstore STATEMENT: select populate_record(v, hstore('b', 'foo') || hstore('e', null)) from testhstore1 v; 2025-11-30 18:45:03.759 UTC client backend[44174] pg_regress/hstore ERROR: domain hstestdom1 does not allow null values 2025-11-30 18:45:03.759 UTC client backend[44174] pg_regress/hstore STATEMENT: select populate_record(null::testhstore1, hstore('c', '3.45') || hstore('a', '123')); 2025-11-30 18:45:03.760 UTC client backend[44174] pg_regress/hstore ERROR: domain hstestdom1 does not allow null values 2025-11-30 18:45:03.760 UTC client backend[44174] pg_regress/hstore STATEMENT: select populate_record(null::testhstore1, ''); 2025-11-30 18:45:03.761 UTC client backend[44174] pg_regress/hstore ERROR: domain hstestdom1 does not allow null values 2025-11-30 18:45:03.761 UTC client backend[44174] pg_regress/hstore STATEMENT: select v #= hstore('e', null) from testhstore1 v; 2025-11-30 18:45:03.762 UTC client backend[44174] pg_regress/hstore ERROR: domain hstestdom1 does not allow null values 2025-11-30 18:45:03.762 UTC client backend[44174] pg_regress/hstore STATEMENT: select null::testhstore1 #= (hstore('c', '3.45') || hstore('a', '123')); 2025-11-30 18:45:03.762 UTC client backend[44174] pg_regress/hstore ERROR: domain hstestdom1 does not allow null values 2025-11-30 18:45:03.762 UTC client backend[44174] pg_regress/hstore STATEMENT: select null::testhstore1 #= hstore ''; 2025-11-30 18:45:03.774 UTC unrecognized[44191] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.774 UTC client backend[44191] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.774 UTC client backend[44191] [unknown] LOG: connection authorized: user=postgres database=regression_hstore_plpython application_name=pg_regress 2025-11-30 18:45:03.779 UTC client backend[44077] pg_regress/opr_sanity LOG: disconnection: session time: 0:00:00.730 user=postgres database=regression host=[local] 2025-11-30 18:45:03.779 UTC client backend[44191] pg_regress LOG: connection ready: setup total=20.451 ms, fork=14.219 ms, authentication=0.120 ms 2025-11-30 18:45:03.804 UTC client backend[44174] pg_regress/hstore ERROR: value 0 out of bounds for option "siglen" 2025-11-30 18:45:03.804 UTC client backend[44174] pg_regress/hstore DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:03.804 UTC client backend[44174] pg_regress/hstore STATEMENT: create index hidx on testhstore using gist(h gist_hstore_ops(siglen=0)); 2025-11-30 18:45:03.805 UTC client backend[44174] pg_regress/hstore ERROR: value 2025 out of bounds for option "siglen" 2025-11-30 18:45:03.805 UTC client backend[44174] pg_regress/hstore DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:03.805 UTC client backend[44174] pg_regress/hstore STATEMENT: create index hidx on testhstore using gist(h gist_hstore_ops(siglen=2025)); 2025-11-30 18:45:03.818 UTC unrecognized[44196] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.819 UTC client backend[44196] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.819 UTC client backend[44196] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/not_equal 2025-11-30 18:45:03.820 UTC client backend[44196] pg_regress/not_equal LOG: connection ready: setup total=34.322 ms, fork=11.488 ms, authentication=0.117 ms 2025-11-30 18:45:03.821 UTC client backend[44191] pg_regress LOG: disconnection: session time: 0:00:00.048 user=postgres database=regression_hstore_plpython host=[local] 2025-11-30 18:45:03.841 UTC unrecognized[44203] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.848 UTC client backend[44196] pg_regress/not_equal ERROR: conflicting key value violates exclusion constraint "zoo_cage_animal_excl" 2025-11-30 18:45:03.848 UTC client backend[44196] pg_regress/not_equal DETAIL: Key (cage, animal)=(123, lion) conflicts with existing key (cage, animal)=(123, zebra). 2025-11-30 18:45:03.848 UTC client backend[44196] pg_regress/not_equal STATEMENT: INSERT INTO zoo VALUES(123, 'lion'); 2025-11-30 18:45:03.848 UTC client backend[44196] pg_regress/not_equal LOG: disconnection: session time: 0:00:00.051 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.849 UTC client backend[43731] isolation/receipt-report/s3 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:03.849 UTC client backend[43731] isolation/receipt-report/s3 DETAIL: Reason code: Canceled on conflict out to pivot 4529, during read. 2025-11-30 18:45:03.849 UTC client backend[43731] isolation/receipt-report/s3 HINT: The transaction might succeed if retried. 2025-11-30 18:45:03.849 UTC client backend[43731] isolation/receipt-report/s3 STATEMENT: SELECT * FROM receipt WHERE deposit_date = DATE '2008-12-22'; 2025-11-30 18:45:03.850 UTC client backend[44188] pg_regress/hstore_plperl ERROR: cannot transform non-hash Perl value to hstore 2025-11-30 18:45:03.850 UTC client backend[44188] pg_regress/hstore_plperl CONTEXT: PL/Perl function "test2" 2025-11-30 18:45:03.850 UTC client backend[44188] pg_regress/hstore_plperl STATEMENT: SELECT test2(); 2025-11-30 18:45:03.852 UTC client backend[44188] pg_regress/hstore_plperl ERROR: cannot transform non-hash Perl value to hstore 2025-11-30 18:45:03.852 UTC client backend[44188] pg_regress/hstore_plperl CONTEXT: PL/Perl function "test2" 2025-11-30 18:45:03.852 UTC client backend[44188] pg_regress/hstore_plperl STATEMENT: SELECT test2(); 2025-11-30 18:45:03.865 UTC client backend[43726] isolation/receipt-report/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:03.865 UTC client backend[43726] isolation/receipt-report/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:03.865 UTC client backend[43726] isolation/receipt-report/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:03.865 UTC client backend[43726] isolation/receipt-report/s1 STATEMENT: COMMIT; 2025-11-30 18:45:03.876 UTC client backend[44188] pg_regress/hstore_plperl LOG: disconnection: session time: 0:00:00.128 user=postgres database=regression_hstore_plperl host=[local] 2025-11-30 18:45:03.876 UTC client backend[43726] isolation/receipt-report/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:03.876 UTC client backend[43726] isolation/receipt-report/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:03.876 UTC client backend[43726] isolation/receipt-report/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:03.876 UTC client backend[43726] isolation/receipt-report/s1 STATEMENT: COMMIT; 2025-11-30 18:45:03.877 UTC client backend[44203] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.878 UTC client backend[44203] [unknown] LOG: connection authorized: user=postgres database=regression_hstore_plpython application_name=pg_regress/hstore_plpython 2025-11-30 18:45:03.878 UTC client backend[44203] pg_regress/hstore_plpython LOG: connection ready: setup total=38.482 ms, fork=0.772 ms, authentication=0.119 ms 2025-11-30 18:45:03.888 UTC unrecognized[44212] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.888 UTC client backend[44212] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.888 UTC client backend[44212] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/enum 2025-11-30 18:45:03.889 UTC unrecognized[44223] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.889 UTC client backend[44212] pg_regress/enum LOG: connection ready: setup total=35.574 ms, fork=33.640 ms, authentication=0.122 ms 2025-11-30 18:45:03.890 UTC unrecognized[44224] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.891 UTC client backend[44224] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.891 UTC client backend[44224] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copyencoding 2025-11-30 18:45:03.892 UTC client backend[44224] pg_regress/copyencoding LOG: connection ready: setup total=3.479 ms, fork=1.970 ms, authentication=0.104 ms 2025-11-30 18:45:03.894 UTC client backend[44223] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.894 UTC client backend[44223] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copyselect 2025-11-30 18:45:03.894 UTC unrecognized[44226] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.895 UTC client backend[44223] pg_regress/copyselect LOG: connection ready: setup total=8.322 ms, fork=1.601 ms, authentication=0.108 ms 2025-11-30 18:45:03.899 UTC client backend[44224] pg_regress/copyencoding ERROR: invalid byte sequence for encoding "EUC_JP": 0xe3 0x81 2025-11-30 18:45:03.899 UTC client backend[44224] pg_regress/copyencoding CONTEXT: COPY copy_encoding_tab, line 1 2025-11-30 18:45:03.899 UTC client backend[44224] pg_regress/copyencoding STATEMENT: COPY copy_encoding_tab FROM '/tmp/cirrus-ci-build/build/testrun/regress-running/regress/results/copyencoding_utf8.csv' WITH (FORMAT csv, ENCODING 'EUC_JP'); 2025-11-30 18:45:03.899 UTC client backend[44224] pg_regress/copyencoding ERROR: invalid byte sequence for encoding "EUC_JP": 0xe3 0x81 2025-11-30 18:45:03.899 UTC client backend[44224] pg_regress/copyencoding CONTEXT: COPY copy_encoding_tab, line 1 2025-11-30 18:45:03.899 UTC client backend[44224] pg_regress/copyencoding STATEMENT: COPY copy_encoding_tab FROM '/tmp/cirrus-ci-build/build/testrun/regress-running/regress/results/copyencoding_utf8.csv' WITH (FORMAT csv); 2025-11-30 18:45:03.901 UTC client backend[44226] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.901 UTC client backend[44226] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copy 2025-11-30 18:45:03.902 UTC client backend[44226] pg_regress/copy LOG: connection ready: setup total=8.558 ms, fork=0.984 ms, authentication=0.110 ms 2025-11-30 18:45:03.906 UTC client backend[44212] pg_regress/enum LOG: disconnection: session time: 0:00:00.019 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.910 UTC client backend[44224] pg_regress/copyencoding LOG: disconnection: session time: 0:00:00.020 user=postgres database=regression host=[local] 2025-11-30 18:45:03.918 UTC unrecognized[44230] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.918 UTC client backend[44230] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.918 UTC client backend[44230] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/bool 2025-11-30 18:45:03.919 UTC unrecognized[44225] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.919 UTC client backend[44230] pg_regress/bool LOG: connection ready: setup total=2.260 ms, fork=0.600 ms, authentication=0.128 ms 2025-11-30 18:45:03.919 UTC client backend[44225] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.919 UTC client backend[44225] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copydml 2025-11-30 18:45:03.920 UTC client backend[44225] pg_regress/copydml LOG: connection ready: setup total=29.251 ms, fork=24.422 ms, authentication=0.110 ms 2025-11-30 18:45:03.921 UTC unrecognized[44231] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.931 UTC client backend[44231] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.931 UTC client backend[44231] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/insert_conflict 2025-11-30 18:45:03.932 UTC client backend[44231] pg_regress/insert_conflict LOG: connection ready: setup total=13.609 ms, fork=1.657 ms, authentication=0.236 ms 2025-11-30 18:45:03.936 UTC unrecognized[44227] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.936 UTC client backend[44227] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.936 UTC client backend[44227] [unknown] LOG: connection authorized: user=postgres database=regression_hstore_plperl application_name=pg_regress/hstore_plperlu 2025-11-30 18:45:03.937 UTC client backend[44226] pg_regress/copy ERROR: end-of-copy marker is not alone on its line 2025-11-30 18:45:03.937 UTC client backend[44226] pg_regress/copy CONTEXT: COPY copytest2, line 3 2025-11-30 18:45:03.937 UTC client backend[44226] pg_regress/copy STATEMENT: copy copytest2(test) from stdin; 2025-11-30 18:45:03.937 UTC client backend[44226] pg_regress/copy ERROR: end-of-copy marker is not alone on its line 2025-11-30 18:45:03.937 UTC client backend[44226] pg_regress/copy CONTEXT: COPY copytest2, line 3 2025-11-30 18:45:03.937 UTC client backend[44226] pg_regress/copy STATEMENT: copy copytest2(test) from stdin; 2025-11-30 18:45:03.938 UTC client backend[44227] pg_regress/hstore_plperlu LOG: connection ready: setup total=32.413 ms, fork=27.064 ms, authentication=0.112 ms 2025-11-30 18:45:03.942 UTC client backend[44230] pg_regress/bool LOG: disconnection: session time: 0:00:00.024 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:03.942 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:03.942 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (key) do nothing; 2025-11-30 18:45:03.943 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:03.943 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (fruit) do nothing; 2025-11-30 18:45:03.952 UTC client backend[44203] pg_regress/hstore_plpython ERROR: not a Python mapping 2025-11-30 18:45:03.952 UTC client backend[44203] pg_regress/hstore_plpython CONTEXT: while creating return value PL/Python function "test1bad" 2025-11-30 18:45:03.952 UTC client backend[44203] pg_regress/hstore_plpython STATEMENT: SELECT test1bad(); 2025-11-30 18:45:03.957 UTC unrecognized[44232] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.958 UTC client backend[44203] pg_regress/hstore_plpython ERROR: value for domain hstore_foo violates check constraint "hstore_foo_check" 2025-11-30 18:45:03.958 UTC client backend[44203] pg_regress/hstore_plpython CONTEXT: while creating return value PL/Python function "test2dom" 2025-11-30 18:45:03.958 UTC client backend[44203] pg_regress/hstore_plpython STATEMENT: SELECT test2dom('bar'); 2025-11-30 18:45:03.958 UTC client backend[44232] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.958 UTC client backend[44232] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/insert 2025-11-30 18:45:03.959 UTC client backend[44232] pg_regress/insert LOG: connection ready: setup total=23.009 ms, fork=21.245 ms, authentication=0.113 ms 2025-11-30 18:45:03.963 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:03.963 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (lower(fruit) text_pattern_ops, upper(fruit) collate "C") do nothing; 2025-11-30 18:45:03.966 UTC client backend[44223] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2025-11-30 18:45:03.966 UTC client backend[44223] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2025-11-30 18:45:03.966 UTC client backend[44223] pg_regress/copyselect STATEMENT: copy v_test1 to stdout; 2025-11-30 18:45:03.967 UTC client backend[44232] pg_regress/insert ERROR: null value in column "col2" of relation "inserttest" violates not-null constraint 2025-11-30 18:45:03.967 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (null, null, testing). 2025-11-30 18:45:03.967 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT, DEFAULT); 2025-11-30 18:45:03.968 UTC client backend[44203] pg_regress/hstore_plpython LOG: disconnection: session time: 0:00:00.126 user=postgres database=regression_hstore_plpython host=[local] 2025-11-30 18:45:03.987 UTC unrecognized[44235] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:03.988 UTC client backend[44235] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:03.988 UTC client backend[44235] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/partitions 2025-11-30 18:45:03.989 UTC client backend[44235] pg_regress/partitions LOG: connection ready: setup total=22.991 ms, fork=21.324 ms, authentication=0.119 ms 2025-11-30 18:45:03.990 UTC client backend[44223] pg_regress/copyselect ERROR: COPY (SELECT INTO) is not supported 2025-11-30 18:45:03.990 UTC client backend[44223] pg_regress/copyselect STATEMENT: copy (select t into temp test3 from test1 where id=3) to stdout; 2025-11-30 18:45:03.990 UTC client backend[44223] pg_regress/copyselect ERROR: syntax error at or near "from" at character 28 2025-11-30 18:45:03.990 UTC client backend[44223] pg_regress/copyselect STATEMENT: copy (select * from test1) from stdin; 2025-11-30 18:45:03.998 UTC client backend[44226] pg_regress/copy ERROR: cannot perform COPY FREEZE on a partitioned table 2025-11-30 18:45:03.998 UTC client backend[44226] pg_regress/copy STATEMENT: copy parted_copytest from '/tmp/cirrus-ci-build/build/testrun/regress-running/regress/results/parted_copytest.csv' (freeze); 2025-11-30 18:45:04.001 UTC client backend[44223] pg_regress/copyselect ERROR: syntax error at or near "(" at character 28 2025-11-30 18:45:04.001 UTC client backend[44223] pg_regress/copyselect STATEMENT: copy (select * from test1) (t,id) to stdout; 2025-11-30 18:45:04.002 UTC client backend[44134] pg_regress/earthdistance LOG: disconnection: session time: 0:00:00.580 user=postgres database=regression_earthdistance host=[local] 2025-11-30 18:45:04.018 UTC client backend[44231] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE requires inference specification or constraint name at character 52 2025-11-30 18:45:04.018 UTC client backend[44231] pg_regress/insert_conflict HINT: For example, ON CONFLICT (column_name). 2025-11-30 18:45:04.018 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict do update set fruit = excluded.fruit; 2025-11-30 18:45:04.023 UTC client backend[44225] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-11-30 18:45:04.023 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-30 18:45:04.023 UTC client backend[44231] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "excluded" at character 117 2025-11-30 18:45:04.023 UTC client backend[44231] pg_regress/insert_conflict DETAIL: There is an entry for table "excluded", but it cannot be referenced from this part of the query. 2025-11-30 18:45:04.023 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruit RETURNING excluded.fruit; 2025-11-30 18:45:04.024 UTC client backend[44225] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-11-30 18:45:04.024 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'g') to stdout; 2025-11-30 18:45:04.024 UTC client backend[44231] pg_regress/insert_conflict ERROR: column "keyy" does not exist at character 64 2025-11-30 18:45:04.024 UTC client backend[44231] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "insertconflicttest.key" or the column "excluded.key". 2025-11-30 18:45:04.024 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (keyy) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.024 UTC client backend[44225] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-11-30 18:45:04.024 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-30 18:45:04.024 UTC client backend[44231] pg_regress/insert_conflict ERROR: column excluded.fruitt does not exist at character 92 2025-11-30 18:45:04.024 UTC client backend[44231] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "excluded.fruit". 2025-11-30 18:45:04.024 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruitt; 2025-11-30 18:45:04.025 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.025 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.025 UTC client backend[44225] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-11-30 18:45:04.025 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-30 18:45:04.025 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.025 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (4, 'Mango') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.026 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.026 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (5, 'Lemon') on conflict (fruit) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.027 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.027 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (6, 'Passionfruit') on conflict (lower(fruit)) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.027 UTC client backend[44225] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-11-30 18:45:04.027 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-30 18:45:04.029 UTC client backend[44231] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "insertconflicttest" at character 106 2025-11-30 18:45:04.029 UTC client backend[44231] pg_regress/insert_conflict HINT: Perhaps you meant to reference the table alias "ict". 2025-11-30 18:45:04.029 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest AS ict values (6, 'Passionfruit') on conflict (key) do update set fruit = insertconflicttest.fruit; 2025-11-30 18:45:04.030 UTC client backend[44225] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-11-30 18:45:04.030 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-30 18:45:04.030 UTC client backend[44231] pg_regress/insert_conflict ERROR: column "insertconflicttest" of relation "insertconflicttest" does not exist at character 90 2025-11-30 18:45:04.030 UTC client backend[44231] pg_regress/insert_conflict HINT: SET target columns cannot be qualified with the relation name. 2025-11-30 18:45:04.030 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set insertconflicttest.fruit = 'Mango'; 2025-11-30 18:45:04.033 UTC client backend[44225] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-11-30 18:45:04.033 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-30 18:45:04.035 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.035 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (9, 'Banana') on conflict (key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.035 UTC client backend[44225] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-11-30 18:45:04.035 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-30 18:45:04.035 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.035 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (10, 'Blueberry') on conflict (key, key, key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.036 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.036 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (11, 'Cherry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.036 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.036 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (12, 'Date') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.036 UTC client backend[44235] pg_regress/partitions ERROR: conflicting key value violates exclusion constraint "parttmp_1_to_10_id_valid_at_excl" 2025-11-30 18:45:04.036 UTC client backend[44235] pg_regress/partitions DETAIL: Key (id, valid_at)=(2, [01-15-2000,02-01-2000)) conflicts with existing key (id, valid_at)=(2, [01-01-2000,02-01-2000)). 2025-11-30 18:45:04.036 UTC client backend[44235] pg_regress/partitions STATEMENT: insert into parttmp (id, valid_at) values (2, '[2000-01-15, 2000-02-01)'); 2025-11-30 18:45:04.037 UTC client backend[44225] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-11-30 18:45:04.037 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-30 18:45:04.041 UTC client backend[44225] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-11-30 18:45:04.041 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-30 18:45:04.041 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.041 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (13, 'Grape') on conflict (key, fruit) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.042 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.042 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (14, 'Raisin') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.043 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.043 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (15, 'Cranberry') on conflict (key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.043 UTC client backend[44235] pg_regress/partitions ERROR: cannot match partition key to index on column "id" using non-equal operator "<>" 2025-11-30 18:45:04.043 UTC client backend[44235] pg_regress/partitions STATEMENT: create table parttmp (id int, valid_at daterange, exclude using gist (id with <>, valid_at with &&)) partition by range (id); 2025-11-30 18:45:04.043 UTC client backend[44225] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-11-30 18:45:04.043 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-30 18:45:04.044 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.044 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (16, 'Melon') on conflict (key, key, key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.044 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.044 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (17, 'Mulberry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.045 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.045 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (18, 'Pineapple') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.045 UTC client backend[44225] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-11-30 18:45:04.045 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-30 18:45:04.045 UTC client backend[44235] pg_regress/partitions LOG: disconnection: session time: 0:00:00.058 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:04.047 UTC client backend[44226] pg_regress/copy ERROR: cannot use "match" with HEADER in COPY TO 2025-11-30 18:45:04.047 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest to stdout with (header match); 2025-11-30 18:45:04.047 UTC client backend[44226] pg_regress/copy ERROR: header requires a Boolean value, a non-negative integer, or the string "match" 2025-11-30 18:45:04.047 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header wrong_choice); 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy ERROR: column name mismatch in header line field 1: got "a", expected "c" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest (c, b, a) from stdin with (header match); 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy ERROR: column name mismatch in header line field 3: got null value ("\N"), expected "c" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b \N" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy ERROR: wrong number of fields in header line: got 2, expected 3 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy ERROR: wrong number of fields in header line: got 4, expected 3 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c d" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy ERROR: column name mismatch in header line field 3: got "d", expected "c" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b d" 2025-11-30 18:45:04.048 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-30 18:45:04.049 UTC client backend[44226] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2025-11-30 18:45:04.049 UTC client backend[44226] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a ........pg.dropped.2........ c" 2025-11-30 18:45:04.049 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-30 18:45:04.049 UTC client backend[44226] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2025-11-30 18:45:04.049 UTC client backend[44226] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a c b" 2025-11-30 18:45:04.049 UTC client backend[44226] pg_regress/copy STATEMENT: copy header_copytest (a, c) from stdin with (header match); 2025-11-30 18:45:04.050 UTC client backend[44225] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-11-30 18:45:04.050 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-30 18:45:04.052 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.052 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (22, 'Apricot') on conflict (upper(fruit)) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.052 UTC client backend[44226] pg_regress/copy ERROR: value too long for type character varying(5) 2025-11-30 18:45:04.052 UTC client backend[44226] pg_regress/copy STATEMENT: copy oversized_column_default (col2) from stdin; 2025-11-30 18:45:04.052 UTC client backend[44226] pg_regress/copy ERROR: value too long for type character varying(5) 2025-11-30 18:45:04.052 UTC client backend[44226] pg_regress/copy STATEMENT: copy oversized_column_default from stdin (default ''); 2025-11-30 18:45:04.053 UTC client backend[44225] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-11-30 18:45:04.053 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-30 18:45:04.053 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.053 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.056 UTC client backend[44225] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-11-30 18:45:04.056 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-30 18:45:04.058 UTC client backend[44223] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2025-11-30 18:45:04.058 UTC client backend[44223] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2025-11-30 18:45:04.058 UTC client backend[44223] pg_regress/copyselect STATEMENT: COPY v_test1 TO STDOUT 2025-11-30 18:45:04.059 UTC client backend[44225] pg_regress/copydml ERROR: COPY query must not be a utility command 2025-11-30 18:45:04.059 UTC client backend[44225] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-30 18:45:04.059 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.059 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (27, 'Prune') on conflict (key, upper(fruit)) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.061 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.061 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (28, 'Redcurrant') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.062 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.062 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (29, 'Nectarine') on conflict (key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.068 UTC client backend[44223] pg_regress/copyselect ERROR: division by zero 2025-11-30 18:45:04.068 UTC client backend[44223] pg_regress/copyselect STATEMENT: copy (select 1) to stdout; select 1/0; 2025-11-30 18:45:04.068 UTC client backend[44223] pg_regress/copyselect ERROR: division by zero 2025-11-30 18:45:04.068 UTC client backend[44223] pg_regress/copyselect STATEMENT: select 1/0; copy (select 1) to stdout; 2025-11-30 18:45:04.070 UTC client backend[44223] pg_regress/copyselect LOG: disconnection: session time: 0:00:00.181 user=postgres database=regression host=[local] 2025-11-30 18:45:04.070 UTC client backend[44231] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "fruit_index" 2025-11-30 18:45:04.070 UTC client backend[44231] pg_regress/insert_conflict DETAIL: Key (fruit)=(Peach) already exists. 2025-11-30 18:45:04.070 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (26, 'Peach') on conflict (key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.071 UTC client backend[44225] pg_regress/copydml LOG: disconnection: session time: 0:00:00.155 user=postgres database=regression host=[local] 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT); 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (1, 2); 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 42 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttest (col1) values (1, 2); 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 48 2025-11-30 18:45:04.074 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttest (col1) values (DEFAULT, DEFAULT); 2025-11-30 18:45:04.079 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.079 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) do update set fruit = excluded.fruit; 2025-11-30 18:45:04.079 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.079 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) where fruit like '%berry' or fruit = 'consequential' do nothing; 2025-11-30 18:45:04.079 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.079 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) where fruit like '%berry' do update set fruit = excluded.fruit; 2025-11-30 18:45:04.086 UTC client backend[44232] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 32 2025-11-30 18:45:04.086 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttest (f2[1], f2[2]) values (1,default); 2025-11-30 18:45:04.087 UTC unrecognized[44244] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.088 UTC client backend[44244] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.088 UTC client backend[44244] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/stratnum 2025-11-30 18:45:04.089 UTC client backend[44244] pg_regress/stratnum LOG: connection ready: setup total=2.043 ms, fork=0.502 ms, authentication=0.109 ms 2025-11-30 18:45:04.089 UTC client backend[44227] pg_regress/hstore_plperlu LOG: disconnection: session time: 0:00:00.156 user=postgres database=regression_hstore_plperl host=[local] 2025-11-30 18:45:04.091 UTC client backend[44244] pg_regress/stratnum LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:04.092 UTC client backend[44232] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 33 2025-11-30 18:45:04.092 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttest (f3.if1, f3.if2) values (1,default); 2025-11-30 18:45:04.102 UTC client backend[44231] pg_regress/insert_conflict ERROR: column excluded.ctid does not exist at character 82 2025-11-30 18:45:04.102 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into syscolconflicttest values (1) on conflict (key) do update set data = excluded.ctid::text; 2025-11-30 18:45:04.103 UTC unrecognized[44250] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.104 UTC client backend[44250] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.104 UTC client backend[44250] [unknown] LOG: connection authorized: user=postgres database=regression_btree_gist application_name=pg_regress/without_overlaps 2025-11-30 18:45:04.105 UTC client backend[44250] pg_regress/without_overlaps LOG: connection ready: setup total=3.960 ms, fork=2.391 ms, authentication=0.108 ms 2025-11-30 18:45:04.120 UTC unrecognized[44249] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.120 UTC client backend[44249] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.120 UTC client backend[44249] [unknown] LOG: connection authorized: user=postgres database=regression_hstore_plperl application_name=pg_regress/create_transform 2025-11-30 18:45:04.121 UTC client backend[44249] pg_regress/create_transform LOG: connection ready: setup total=20.364 ms, fork=18.846 ms, authentication=0.109 ms 2025-11-30 18:45:04.127 UTC unrecognized[44251] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.127 UTC client backend[44251] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.127 UTC client backend[44251] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.128 UTC client backend[44251] pg_regress LOG: connection ready: setup total=8.661 ms, fork=7.451 ms, authentication=0.098 ms 2025-11-30 18:45:04.128 UTC client backend[44251] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.168 UTC unrecognized[44255] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.168 UTC client backend[44255] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.168 UTC client backend[44255] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.169 UTC client backend[44255] pg_regress LOG: connection ready: setup total=37.059 ms, fork=35.643 ms, authentication=0.109 ms 2025-11-30 18:45:04.169 UTC unrecognized[44256] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.169 UTC client backend[44256] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.169 UTC client backend[44256] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.170 UTC client backend[44256] pg_regress LOG: connection ready: setup total=4.369 ms, fork=1.782 ms, authentication=0.103 ms 2025-11-30 18:45:04.174 UTC client backend[44226] pg_regress/copy ERROR: cannot perform COPY FREEZE on a foreign table 2025-11-30 18:45:04.174 UTC client backend[44226] pg_regress/copy STATEMENT: copy copytest_foreign_table from stdin (freeze); 2025-11-30 18:45:04.176 UTC client backend[44226] pg_regress/copy ERROR: cannot copy from unpopulated materialized view "copytest_mv" 2025-11-30 18:45:04.176 UTC client backend[44226] pg_regress/copy HINT: Use the REFRESH MATERIALIZED VIEW command. 2025-11-30 18:45:04.176 UTC client backend[44226] pg_regress/copy STATEMENT: COPY copytest_mv(id) TO stdout WITH (header); 2025-11-30 18:45:04.188 UTC client backend[44256] pg_regress LOG: disconnection: session time: 0:00:00.020 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.190 UTC client backend[44250] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng_pk" 2025-11-30 18:45:04.190 UTC client backend[44250] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=(1, [06-01-2000,01-01-2001)) conflicts with existing key (id, valid_at)=(1, [01-01-2000,01-01-2001)). 2025-11-30 18:45:04.190 UTC client backend[44250] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng VALUES (1, '[2000-06-01,2001-01-01)'); 2025-11-30 18:45:04.191 UTC client backend[44249] pg_regress/create_transform ERROR: type "foo" does not exist 2025-11-30 18:45:04.191 UTC client backend[44249] pg_regress/create_transform STATEMENT: CREATE TRANSFORM FOR foo LANGUAGE plperl (FROM SQL WITH FUNCTION hstore_to_plperl(internal), TO SQL WITH FUNCTION plperl_to_hstore(internal)); 2025-11-30 18:45:04.191 UTC client backend[44249] pg_regress/create_transform ERROR: language "foo" does not exist 2025-11-30 18:45:04.191 UTC client backend[44249] pg_regress/create_transform STATEMENT: CREATE TRANSFORM FOR hstore LANGUAGE foo (FROM SQL WITH FUNCTION hstore_to_plperl(internal), TO SQL WITH FUNCTION plperl_to_hstore(internal)); 2025-11-30 18:45:04.194 UTC client backend[44249] pg_regress/create_transform ERROR: return data type of FROM SQL function must be internal 2025-11-30 18:45:04.194 UTC client backend[44249] pg_regress/create_transform STATEMENT: CREATE TRANSFORM FOR hstore LANGUAGE plperl (FROM SQL WITH FUNCTION hstore_out(hstore), TO SQL WITH FUNCTION plperl_to_hstore(internal)); 2025-11-30 18:45:04.194 UTC client backend[44249] pg_regress/create_transform ERROR: first argument of transform function must be type internal 2025-11-30 18:45:04.194 UTC client backend[44249] pg_regress/create_transform STATEMENT: CREATE TRANSFORM FOR hstore LANGUAGE plperl (FROM SQL WITH FUNCTION internal_in(cstring), TO SQL WITH FUNCTION plperl_to_hstore(internal)); 2025-11-30 18:45:04.195 UTC unrecognized[44258] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.195 UTC client backend[44258] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.195 UTC client backend[44258] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.196 UTC client backend[44258] pg_regress LOG: connection ready: setup total=2.490 ms, fork=1.179 ms, authentication=0.109 ms 2025-11-30 18:45:04.196 UTC client backend[44249] pg_regress/create_transform ERROR: transform for type hstore language "plperl" already exists 2025-11-30 18:45:04.196 UTC client backend[44249] pg_regress/create_transform STATEMENT: CREATE TRANSFORM FOR hstore LANGUAGE plperl (FROM SQL WITH FUNCTION hstore_to_plperl(internal), TO SQL WITH FUNCTION plperl_to_hstore(internal)); 2025-11-30 18:45:04.197 UTC client backend[44255] pg_regress LOG: disconnection: session time: 0:00:00.029 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.198 UTC client backend[44249] pg_regress/create_transform ERROR: type "foo" does not exist 2025-11-30 18:45:04.198 UTC client backend[44249] pg_regress/create_transform STATEMENT: DROP TRANSFORM FOR foo LANGUAGE plperl; 2025-11-30 18:45:04.198 UTC client backend[44249] pg_regress/create_transform ERROR: language "foo" does not exist 2025-11-30 18:45:04.198 UTC client backend[44249] pg_regress/create_transform STATEMENT: DROP TRANSFORM FOR hstore LANGUAGE foo; 2025-11-30 18:45:04.204 UTC unrecognized[44260] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.205 UTC client backend[44260] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.205 UTC client backend[44260] [unknown] LOG: connection authorized: user=postgres database=regression_intarray application_name=pg_regress/_int 2025-11-30 18:45:04.209 UTC client backend[44258] pg_regress LOG: disconnection: session time: 0:00:00.014 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.210 UTC client backend[44260] pg_regress/_int LOG: connection ready: setup total=5.984 ms, fork=0.557 ms, authentication=0.109 ms 2025-11-30 18:45:04.214 UTC client backend[44250] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-11-30 18:45:04.214 UTC client backend[44250] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=(3, [01-01-2000,01-01-2001)) is not present in table "temporal_rng". 2025-11-30 18:45:04.214 UTC client backend[44250] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_fk_rng2rng VALUES (3, '[2000-01-01,2001-01-01)', 3); 2025-11-30 18:45:04.216 UTC client backend[44250] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-11-30 18:45:04.216 UTC client backend[44250] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=(2, [01-01-2001,01-01-2002)) is not present in table "temporal_rng". 2025-11-30 18:45:04.216 UTC client backend[44250] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_fk_rng2rng VALUES (4, '[2001-01-01,2002-01-01)', 2); 2025-11-30 18:45:04.217 UTC client backend[44250] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-11-30 18:45:04.217 UTC client backend[44250] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=(2, [01-01-2000,01-01-2002)) is not present in table "temporal_rng". 2025-11-30 18:45:04.217 UTC client backend[44250] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_fk_rng2rng VALUES (5, '[2000-01-01,2002-01-01)', 2); 2025-11-30 18:45:04.224 UTC client backend[44226] pg_regress/copy LOG: disconnection: session time: 0:00:00.330 user=postgres database=regression host=[local] 2025-11-30 18:45:04.235 UTC client backend[44231] pg_regress/insert_conflict ERROR: table reference "excluded" is ambiguous at character 76 2025-11-30 18:45:04.235 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into excluded values(1, '2') on conflict (key) do update set data = excluded.data RETURNING *; 2025-11-30 18:45:04.239 UTC unrecognized[44262] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.239 UTC client backend[44250] pg_regress/without_overlaps LOG: disconnection: session time: 0:00:00.135 user=postgres database=regression_btree_gist host=[local] 2025-11-30 18:45:04.240 UTC client backend[44262] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.240 UTC client backend[44262] [unknown] LOG: connection authorized: user=postgres database=regression_isn application_name=pg_regress/isn 2025-11-30 18:45:04.244 UTC client backend[44262] pg_regress/isn LOG: connection ready: setup total=30.340 ms, fork=25.182 ms, authentication=0.107 ms 2025-11-30 18:45:04.250 UTC client backend[44231] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "twoconstraints_f1_key" 2025-11-30 18:45:04.250 UTC client backend[44231] pg_regress/insert_conflict DETAIL: Key (f1)=(1) already exists. 2025-11-30 18:45:04.250 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(1, '((2,2),(3,3))'); 2025-11-30 18:45:04.251 UTC client backend[44231] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2025-11-30 18:45:04.251 UTC client backend[44231] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2025-11-30 18:45:04.251 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))'); 2025-11-30 18:45:04.252 UTC client backend[44231] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2025-11-30 18:45:04.252 UTC client backend[44231] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2025-11-30 18:45:04.252 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))') on conflict on constraint twoconstraints_f1_key do nothing; 2025-11-30 18:45:04.253 UTC client backend[44232] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 33 2025-11-30 18:45:04.253 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (1,default); 2025-11-30 18:45:04.254 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-11-30 18:45:04.254 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (0,2); 2025-11-30 18:45:04.254 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-11-30 18:45:04.254 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (3,4), (0,6); 2025-11-30 18:45:04.254 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-11-30 18:45:04.254 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) select 0,8; 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 34 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,default); 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,array[null]); 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,'{null}'), (2,'{bar}'); 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-30 18:45:04.255 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) select 3, '{null,quux}'; 2025-11-30 18:45:04.267 UTC client backend[44231] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-11-30 18:45:04.267 UTC client backend[44231] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-11-30 18:45:04.267 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (4,1), (4,2) on conflict(f1) do update set f2 = 0; 2025-11-30 18:45:04.268 UTC client backend[44231] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-11-30 18:45:04.268 UTC client backend[44231] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-11-30 18:45:04.268 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (5,1), (5,2) on conflict(f1) do update set f2 = 0; 2025-11-30 18:45:04.270 UTC client backend[44231] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-11-30 18:45:04.270 UTC client backend[44231] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-11-30 18:45:04.270 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (6,1), (6,2) on conflict(f1) do update set f2 = 0; 2025-11-30 18:45:04.281 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.281 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_test values (2, 'b') on conflict (b) do update set a = excluded.a; 2025-11-30 18:45:04.298 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_nnarray violates check constraint "insert_nnarray_check" 2025-11-30 18:45:04.298 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttesta (f1[1]) values (1); 2025-11-30 18:45:04.303 UTC client backend[44232] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-30 18:45:04.303 UTC client backend[44232] pg_regress/insert STATEMENT: insert into inserttestb (f1.if1) values (1); 2025-11-30 18:45:04.309 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-11-30 18:45:04.309 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 11). 2025-11-30 18:45:04.309 UTC client backend[44232] pg_regress/insert STATEMENT: insert into range_parted values ('a', 11); 2025-11-30 18:45:04.321 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-11-30 18:45:04.321 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (a, 11). 2025-11-30 18:45:04.321 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part1 values ('a', 11); 2025-11-30 18:45:04.322 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-11-30 18:45:04.322 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (b, 1). 2025-11-30 18:45:04.322 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part1 values ('b', 1); 2025-11-30 18:45:04.324 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part4" violates partition constraint 2025-11-30 18:45:04.324 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (b, 21). 2025-11-30 18:45:04.324 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part4 values ('b', 21); 2025-11-30 18:45:04.325 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part4" violates partition constraint 2025-11-30 18:45:04.325 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (a, 10). 2025-11-30 18:45:04.325 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part4 values ('a', 10); 2025-11-30 18:45:04.328 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-11-30 18:45:04.328 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (null, null). 2025-11-30 18:45:04.328 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part1 values (null); 2025-11-30 18:45:04.329 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-11-30 18:45:04.329 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (1, null). 2025-11-30 18:45:04.329 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part1 values (1); 2025-11-30 18:45:04.347 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2025-11-30 18:45:04.347 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (cc, 1). 2025-11-30 18:45:04.347 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_aa_bb values ('cc', 1); 2025-11-30 18:45:04.352 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2025-11-30 18:45:04.352 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (AAa, 1). 2025-11-30 18:45:04.352 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_aa_bb values ('AAa', 1); 2025-11-30 18:45:04.354 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2025-11-30 18:45:04.354 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (null, null). 2025-11-30 18:45:04.354 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_aa_bb values (null); 2025-11-30 18:45:04.363 UTC unrecognized[44268] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.364 UTC client backend[44249] pg_regress/create_transform LOG: disconnection: session time: 0:00:00.244 user=postgres database=regression_hstore_plperl host=[local] 2025-11-30 18:45:04.365 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_default" violates partition constraint 2025-11-30 18:45:04.365 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (aa, 2). 2025-11-30 18:45:04.365 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_default values ('aa', 2); 2025-11-30 18:45:04.368 UTC client backend[44268] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.368 UTC client backend[44268] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.369 UTC client backend[44268] pg_regress LOG: connection ready: setup total=7.107 ms, fork=1.126 ms, authentication=0.114 ms 2025-11-30 18:45:04.374 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_default" violates partition constraint 2025-11-30 18:45:04.374 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (null, 2). 2025-11-30 18:45:04.374 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_default values (null, 2); 2025-11-30 18:45:04.416 UTC client backend[44268] pg_regress LOG: disconnection: session time: 0:00:00.052 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.420 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_ee_ff1" violates partition constraint 2025-11-30 18:45:04.420 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (EE, 11). 2025-11-30 18:45:04.420 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_ee_ff1 values ('EE', 11); 2025-11-30 18:45:04.440 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_default_p2" violates partition constraint 2025-11-30 18:45:04.440 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (gg, 43). 2025-11-30 18:45:04.440 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_default_p2 values ('gg', 43); 2025-11-30 18:45:04.452 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_ee_ff1" violates partition constraint 2025-11-30 18:45:04.452 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (cc, 1). 2025-11-30 18:45:04.452 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_ee_ff1 values ('cc', 1); 2025-11-30 18:45:04.452 UTC unrecognized[44271] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.452 UTC client backend[44271] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.452 UTC client backend[44271] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.453 UTC client backend[44271] pg_regress LOG: connection ready: setup total=32.835 ms, fork=31.502 ms, authentication=0.112 ms 2025-11-30 18:45:04.457 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "part_default" found for row 2025-11-30 18:45:04.457 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (43). 2025-11-30 18:45:04.457 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_default values ('gg', 43); 2025-11-30 18:45:04.483 UTC client backend[44174] pg_regress/hstore ERROR: hstore allows only one subscript 2025-11-30 18:45:04.483 UTC client backend[44174] pg_regress/hstore STATEMENT: select f2['d']['e'] from test_json_agg; 2025-11-30 18:45:04.483 UTC client backend[44174] pg_regress/hstore ERROR: hstore allows only one subscript 2025-11-30 18:45:04.483 UTC client backend[44174] pg_regress/hstore STATEMENT: select f2['d':'e'] from test_json_agg; 2025-11-30 18:45:04.493 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for ISBN number: "1234567890", should be X at character 8 2025-11-30 18:45:04.493 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '1234567890'::ISBN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for ISMN number: "M123456780", should be 5 at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT 'M123456780'::ISMN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for ISSN number: "12345670", should be 9 at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '12345670'::ISSN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for ISBN number: "9780123456780", should be 6 at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9780123456780'::ISBN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for ISBN number: "9791234567890", should be 6 at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9791234567890'::ISBN13; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for UPC number: "0123456789010", should be 2 at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '0123456789010'::UPC; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for EAN13 number: "1234567890120", should be 8 at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '1234567890120'::EAN13; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISMN to ISBN for number: "9790123456785" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9790123456785'::ISBN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISSN to ISBN for number: "9771234567898" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9771234567898'::ISBN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast UPC to ISBN for number: "0123456789012" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '0123456789012'::ISBN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISMN to ISBN for number: "9790123456785" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9790123456785'::ISBN13; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISSN to ISBN for number: "9771234567898" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9771234567898'::ISBN13; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast UPC to ISBN for number: "0123456789012" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '0123456789012'::ISBN13; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISBN to ISMN for number: "9780123456786" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9780123456786'::ISMN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISSN to ISMN for number: "9771234567898" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9771234567898'::ISMN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISBN to ISMN for number: "9791234567896" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9791234567896'::ISMN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast UPC to ISMN for number: "0123456789012" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '0123456789012'::ISMN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISBN to ISSN for number: "9780123456786" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9780123456786'::ISSN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISMN to ISSN for number: "9790123456785" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9790123456785'::ISSN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISBN to ISSN for number: "9791234567896" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9791234567896'::ISSN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast UPC to ISSN for number: "0123456789012" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '0123456789012'::ISSN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISBN to UPC for number: "9780123456786" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9780123456786'::UPC; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISSN to UPC for number: "9771234567898" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9771234567898'::UPC; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISMN to UPC for number: "9790123456785" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9790123456785'::UPC; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast ISBN to UPC for number: "9791234567896" at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '9791234567896'::UPC; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid input syntax for EAN13 number: "postgresql..." at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT 'postgresql...'::EAN13; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: invalid input syntax for ISBN number: "postgresql..." at character 8 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT 'postgresql...'::ISBN; 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn ERROR: cannot cast type bigint to ean13 at character 21 2025-11-30 18:45:04.496 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT 9780123456786::EAN13; 2025-11-30 18:45:04.497 UTC client backend[44262] pg_regress/isn ERROR: cannot cast type bigint to isbn at character 21 2025-11-30 18:45:04.497 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT 9780123456786::ISBN; 2025-11-30 18:45:04.498 UTC client backend[44262] pg_regress/isn ERROR: invalid check digit for EAN13 number: "2222222222221", should be 2 at character 8 2025-11-30 18:45:04.498 UTC client backend[44262] pg_regress/isn STATEMENT: SELECT '2222222222221'::ean13; 2025-11-30 18:45:04.502 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-11-30 18:45:04.502 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 0). 2025-11-30 18:45:04.502 UTC client backend[44232] pg_regress/insert STATEMENT: insert into range_parted values ('a', 0); 2025-11-30 18:45:04.503 UTC client backend[44271] pg_regress LOG: disconnection: session time: 0:00:00.050 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.507 UTC client backend[44174] pg_regress/hstore LOG: disconnection: session time: 0:00:00.832 user=postgres database=regression_hstore host=[local] 2025-11-30 18:45:04.512 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-11-30 18:45:04.512 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 20). 2025-11-30 18:45:04.512 UTC client backend[44232] pg_regress/insert STATEMENT: insert into range_parted values ('a', 20); 2025-11-30 18:45:04.513 UTC unrecognized[44278] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.513 UTC client backend[44278] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.513 UTC client backend[44278] [unknown] LOG: connection authorized: user=postgres database=regression_jsonb_plperl application_name=pg_regress/jsonb_plperl 2025-11-30 18:45:04.513 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-11-30 18:45:04.513 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, null). 2025-11-30 18:45:04.513 UTC client backend[44232] pg_regress/insert STATEMENT: insert into range_parted values ('a'); 2025-11-30 18:45:04.515 UTC unrecognized[44279] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.515 UTC client backend[44279] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.515 UTC client backend[44279] [unknown] LOG: connection authorized: user=postgres database=regression_hstore application_name=pg_regress/hstore_utf8 2025-11-30 18:45:04.515 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "part_def" violates partition constraint 2025-11-30 18:45:04.515 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (b, 10). 2025-11-30 18:45:04.515 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_def values ('b', 10); 2025-11-30 18:45:04.515 UTC unrecognized[44274] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.516 UTC client backend[44274] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.516 UTC client backend[44274] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.516 UTC client backend[44279] pg_regress/hstore_utf8 LOG: connection ready: setup total=4.787 ms, fork=3.347 ms, authentication=0.093 ms 2025-11-30 18:45:04.516 UTC client backend[44274] pg_regress LOG: connection ready: setup total=14.274 ms, fork=13.005 ms, authentication=0.097 ms 2025-11-30 18:45:04.517 UTC client backend[44278] pg_regress/jsonb_plperl LOG: connection ready: setup total=6.410 ms, fork=1.415 ms, authentication=0.107 ms 2025-11-30 18:45:04.518 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "part_ee_ff" found for row 2025-11-30 18:45:04.518 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (0). 2025-11-30 18:45:04.518 UTC client backend[44232] pg_regress/insert STATEMENT: insert into list_parted values ('EE', 0); 2025-11-30 18:45:04.519 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "part_ee_ff" found for row 2025-11-30 18:45:04.519 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (0). 2025-11-30 18:45:04.519 UTC client backend[44232] pg_regress/insert STATEMENT: insert into part_ee_ff values ('EE', 0); 2025-11-30 18:45:04.519 UTC client backend[44279] pg_regress/hstore_utf8 LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_hstore host=[local] 2025-11-30 18:45:04.525 UTC client backend[44274] pg_regress LOG: disconnection: session time: 0:00:00.010 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.537 UTC client backend[44278] pg_regress/jsonb_plperl ERROR: cannot convert infinity to jsonb 2025-11-30 18:45:04.537 UTC client backend[44278] pg_regress/jsonb_plperl CONTEXT: PL/Perl function "roundtrip" 2025-11-30 18:45:04.537 UTC client backend[44278] pg_regress/jsonb_plperl STATEMENT: SELECT roundtrip('1E+131071'); 2025-11-30 18:45:04.542 UTC client backend[44278] pg_regress/jsonb_plperl LOG: disconnection: session time: 0:00:00.030 user=postgres database=regression_jsonb_plperl host=[local] 2025-11-30 18:45:04.554 UTC unrecognized[44285] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.554 UTC client backend[44285] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.554 UTC client backend[44285] [unknown] LOG: connection authorized: user=postgres database=regression_jsonb_plperl application_name=pg_regress/jsonb_plperlu 2025-11-30 18:45:04.555 UTC client backend[44285] pg_regress/jsonb_plperlu LOG: connection ready: setup total=6.820 ms, fork=5.350 ms, authentication=0.118 ms 2025-11-30 18:45:04.607 UTC client backend[44285] pg_regress/jsonb_plperlu LOG: disconnection: session time: 0:00:00.053 user=postgres database=regression_jsonb_plperl host=[local] 2025-11-30 18:45:04.618 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "hpart0" violates partition constraint 2025-11-30 18:45:04.618 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (11). 2025-11-30 18:45:04.618 UTC client backend[44232] pg_regress/insert STATEMENT: insert into hpart0 values(11); 2025-11-30 18:45:04.621 UTC unrecognized[44288] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.621 UTC client backend[44231] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:04.621 UTC client backend[44231] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_1 values (40, 'cuarenta') on conflict (a) do update set b = excluded.b; 2025-11-30 18:45:04.621 UTC client backend[44288] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.621 UTC client backend[44288] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.622 UTC client backend[44288] pg_regress LOG: connection ready: setup total=2.026 ms, fork=0.700 ms, authentication=0.111 ms 2025-11-30 18:45:04.633 UTC client backend[44288] pg_regress LOG: disconnection: session time: 0:00:00.011 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.636 UTC unrecognized[44290] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.636 UTC client backend[44290] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.636 UTC client backend[44290] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.637 UTC client backend[44290] pg_regress LOG: connection ready: setup total=5.445 ms, fork=3.625 ms, authentication=0.112 ms 2025-11-30 18:45:04.638 UTC client backend[44290] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.643 UTC unrecognized[44294] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.643 UTC client backend[44294] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.643 UTC client backend[44294] [unknown] LOG: connection authorized: user=postgres database=regression_jsonb_plpython application_name=pg_regress/jsonb_plpython 2025-11-30 18:45:04.643 UTC client backend[44262] pg_regress/isn LOG: disconnection: session time: 0:00:00.404 user=postgres database=regression_isn host=[local] 2025-11-30 18:45:04.648 UTC client backend[44294] pg_regress/jsonb_plpython LOG: connection ready: setup total=7.172 ms, fork=2.027 ms, authentication=0.107 ms 2025-11-30 18:45:04.652 UTC client backend[44231] pg_regress/insert_conflict LOG: disconnection: session time: 0:00:00.731 user=postgres database=regression host=[local] 2025-11-30 18:45:04.656 UTC unrecognized[44296] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.656 UTC client backend[44296] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.656 UTC client backend[44296] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.657 UTC client backend[44296] pg_regress LOG: connection ready: setup total=3.831 ms, fork=2.518 ms, authentication=0.106 ms 2025-11-30 18:45:04.662 UTC client backend[44260] pg_regress/_int ERROR: input array is too big (199 maximum allowed, 1001 current), use gist__intbig_ops opclass instead 2025-11-30 18:45:04.662 UTC client backend[44260] pg_regress/_int STATEMENT: INSERT INTO test__int SELECT array(SELECT x FROM generate_series(1, 1001) x); 2025-11-30 18:45:04.668 UTC client backend[44296] pg_regress LOG: disconnection: session time: 0:00:00.011 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.676 UTC client backend[44294] pg_regress/jsonb_plpython ERROR: could not convert value "(1+2j)" to jsonb 2025-11-30 18:45:04.676 UTC client backend[44294] pg_regress/jsonb_plpython CONTEXT: while creating return value PL/Python function "testcomplexnumbers" 2025-11-30 18:45:04.676 UTC client backend[44294] pg_regress/jsonb_plpython STATEMENT: SELECT testComplexNumbers(); 2025-11-30 18:45:04.679 UTC client backend[44294] pg_regress/jsonb_plpython LOG: disconnection: session time: 0:00:00.036 user=postgres database=regression_jsonb_plpython host=[local] 2025-11-30 18:45:04.681 UTC client backend[44260] pg_regress/_int ERROR: value 0 out of bounds for option "numranges" 2025-11-30 18:45:04.681 UTC client backend[44260] pg_regress/_int DETAIL: Valid values are between "1" and "252". 2025-11-30 18:45:04.681 UTC client backend[44260] pg_regress/_int STATEMENT: CREATE INDEX text_idx on test__int using gist (a gist__int_ops(numranges = 0)); 2025-11-30 18:45:04.681 UTC client backend[44260] pg_regress/_int ERROR: value 253 out of bounds for option "numranges" 2025-11-30 18:45:04.681 UTC client backend[44260] pg_regress/_int DETAIL: Valid values are between "1" and "252". 2025-11-30 18:45:04.681 UTC client backend[44260] pg_regress/_int STATEMENT: CREATE INDEX text_idx on test__int using gist (a gist__int_ops(numranges = 253)); 2025-11-30 18:45:04.711 UTC unrecognized[44301] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.712 UTC client backend[44301] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.712 UTC client backend[44301] [unknown] LOG: connection authorized: user=postgres database=regression_lo application_name=pg_regress/lo 2025-11-30 18:45:04.716 UTC client backend[44301] pg_regress/lo LOG: connection ready: setup total=22.120 ms, fork=16.487 ms, authentication=0.112 ms 2025-11-30 18:45:04.724 UTC client backend[44301] pg_regress/lo ERROR: large object 43213 does not exist 2025-11-30 18:45:04.724 UTC client backend[44301] pg_regress/lo STATEMENT: SELECT lo_get(43213); 2025-11-30 18:45:04.725 UTC client backend[44301] pg_regress/lo ERROR: large object 43214 does not exist 2025-11-30 18:45:04.725 UTC client backend[44301] pg_regress/lo STATEMENT: SELECT lo_get(43214); 2025-11-30 18:45:04.728 UTC client backend[44301] pg_regress/lo ERROR: large object 43223 does not exist 2025-11-30 18:45:04.728 UTC client backend[44301] pg_regress/lo STATEMENT: SELECT lo_get(43223); 2025-11-30 18:45:04.730 UTC client backend[44301] pg_regress/lo ERROR: large object 43224 does not exist 2025-11-30 18:45:04.730 UTC client backend[44301] pg_regress/lo STATEMENT: SELECT lo_get(43224); 2025-11-30 18:45:04.731 UTC client backend[44301] pg_regress/lo ERROR: large object 43225 does not exist 2025-11-30 18:45:04.731 UTC client backend[44301] pg_regress/lo STATEMENT: SELECT lo_get(43225); 2025-11-30 18:45:04.732 UTC client backend[44301] pg_regress/lo LOG: disconnection: session time: 0:00:00.021 user=postgres database=regression_lo host=[local] 2025-11-30 18:45:04.744 UTC unrecognized[44306] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.745 UTC client backend[44306] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.745 UTC client backend[44306] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.746 UTC client backend[44306] pg_regress LOG: connection ready: setup total=1.779 ms, fork=0.488 ms, authentication=0.108 ms 2025-11-30 18:45:04.746 UTC client backend[44306] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.752 UTC unrecognized[44308] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.753 UTC client backend[44308] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.753 UTC client backend[44308] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.754 UTC client backend[44308] pg_regress LOG: connection ready: setup total=3.200 ms, fork=1.948 ms, authentication=0.105 ms 2025-11-30 18:45:04.785 UTC unrecognized[44313] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.785 UTC client backend[44313] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.785 UTC client backend[44313] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.786 UTC client backend[44313] pg_regress LOG: connection ready: setup total=1.861 ms, fork=0.486 ms, authentication=0.113 ms 2025-11-30 18:45:04.786 UTC client backend[44313] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.790 UTC unrecognized[44316] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.790 UTC unrecognized[44317] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.790 UTC client backend[44316] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.790 UTC client backend[44316] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.791 UTC client backend[44317] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.791 UTC client backend[44317] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.791 UTC client backend[44316] pg_regress LOG: connection ready: setup total=1.544 ms, fork=0.360 ms, authentication=0.099 ms 2025-11-30 18:45:04.791 UTC client backend[44317] pg_regress LOG: connection ready: setup total=1.357 ms, fork=0.266 ms, authentication=0.088 ms 2025-11-30 18:45:04.792 UTC client backend[44317] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.800 UTC unrecognized[44319] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.800 UTC client backend[44319] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.800 UTC client backend[44319] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.801 UTC client backend[44319] pg_regress LOG: connection ready: setup total=5.718 ms, fork=4.417 ms, authentication=0.111 ms 2025-11-30 18:45:04.814 UTC client backend[44319] pg_regress LOG: disconnection: session time: 0:00:00.014 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.820 UTC unrecognized[44324] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.820 UTC client backend[44324] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.820 UTC client backend[44324] [unknown] LOG: connection authorized: user=postgres database=regression_passwordcheck application_name=pg_regress/passwordcheck 2025-11-30 18:45:04.820 UTC client backend[44308] pg_regress LOG: disconnection: session time: 0:00:00.068 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.823 UTC client backend[44316] pg_regress LOG: disconnection: session time: 0:00:00.033 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.825 UTC client backend[44324] pg_regress/passwordcheck LOG: connection ready: setup total=7.475 ms, fork=1.634 ms, authentication=0.108 ms 2025-11-30 18:45:04.828 UTC unrecognized[44326] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.828 UTC client backend[44326] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.828 UTC client backend[44326] [unknown] LOG: connection authorized: user=postgres database=regression_ltree_plpython application_name=pg_regress 2025-11-30 18:45:04.830 UTC client backend[44324] pg_regress/passwordcheck ERROR: password is too short 2025-11-30 18:45:04.830 UTC client backend[44324] pg_regress/passwordcheck DETAIL: password must be at least "passwordcheck.min_password_length" (8) bytes long 2025-11-30 18:45:04.830 UTC client backend[44324] pg_regress/passwordcheck STATEMENT: ALTER USER regress_passwordcheck_user1 PASSWORD 'tooshrt'; 2025-11-30 18:45:04.833 UTC client backend[44326] pg_regress LOG: connection ready: setup total=5.279 ms, fork=0.300 ms, authentication=0.097 ms 2025-11-30 18:45:04.834 UTC client backend[44324] pg_regress/passwordcheck ERROR: password must not contain user name 2025-11-30 18:45:04.834 UTC client backend[44324] pg_regress/passwordcheck STATEMENT: ALTER USER regress_passwordcheck_user1 PASSWORD 'xyzregress_passwordcheck_user1'; 2025-11-30 18:45:04.834 UTC client backend[44324] pg_regress/passwordcheck ERROR: password must contain both letters and nonletters 2025-11-30 18:45:04.834 UTC client backend[44324] pg_regress/passwordcheck STATEMENT: ALTER USER regress_passwordcheck_user1 PASSWORD 'alessnicelongpassword'; 2025-11-30 18:45:04.834 UTC client backend[44324] pg_regress/passwordcheck ERROR: password must not equal user name 2025-11-30 18:45:04.834 UTC client backend[44324] pg_regress/passwordcheck STATEMENT: ALTER USER regress_passwordcheck_user1 PASSWORD 'md507a112732ed9f2087fa90b192d44e358'; 2025-11-30 18:45:04.835 UTC client backend[44324] pg_regress/passwordcheck LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression_passwordcheck host=[local] 2025-11-30 18:45:04.837 UTC unrecognized[44321] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.837 UTC client backend[44321] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.837 UTC client backend[44321] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.839 UTC unrecognized[44327] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.839 UTC client backend[44327] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.839 UTC client backend[44327] [unknown] LOG: connection authorized: user=postgres database=regression_ltree application_name=pg_regress/ltree 2025-11-30 18:45:04.844 UTC client backend[44327] pg_regress/ltree LOG: connection ready: setup total=10.246 ms, fork=3.198 ms, authentication=0.098 ms 2025-11-30 18:45:04.856 UTC client backend[44321] pg_regress LOG: connection ready: setup total=45.026 ms, fork=25.590 ms, authentication=0.112 ms 2025-11-30 18:45:04.857 UTC client backend[44321] pg_regress LOG: disconnection: session time: 0:00:00.020 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.857 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mlparted1" found for row 2025-11-30 18:45:04.857 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains ((b + 0)) = (5). 2025-11-30 18:45:04.857 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted (a, b) values (1, 5); 2025-11-30 18:45:04.865 UTC unrecognized[44330] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.865 UTC client backend[44330] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.865 UTC client backend[44330] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:04.866 UTC client backend[44330] pg_regress LOG: connection ready: setup total=2.280 ms, fork=1.032 ms, authentication=0.108 ms 2025-11-30 18:45:04.866 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mlparted11" violates check constraint "check_b" 2025-11-30 18:45:04.866 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (1, 4). 2025-11-30 18:45:04.866 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted values (1, 2); 2025-11-30 18:45:04.881 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mlparted1" violates partition constraint 2025-11-30 18:45:04.881 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (3, 2). 2025-11-30 18:45:04.881 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted1 (a, b) values (2, 3); 2025-11-30 18:45:04.884 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "lparted_nonullpart" found for row 2025-11-30 18:45:04.884 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (null). 2025-11-30 18:45:04.884 UTC client backend[44232] pg_regress/insert STATEMENT: insert into lparted_nonullpart values (1); 2025-11-30 18:45:04.887 UTC client backend[44330] pg_regress LOG: disconnection: session time: 0:00:00.022 user=postgres database=postgres host=[local] 2025-11-30 18:45:04.892 UTC unrecognized[44332] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.893 UTC client backend[44332] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.893 UTC client backend[44332] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/page 2025-11-30 18:45:04.897 UTC client backend[44332] pg_regress/page LOG: connection ready: setup total=5.386 ms, fork=0.366 ms, authentication=0.110 ms 2025-11-30 18:45:04.925 UTC client backend[44327] pg_regress/ltree ERROR: ltree syntax error at character 1 at character 8 2025-11-30 18:45:04.925 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '.2.3'::ltree; 2025-11-30 18:45:04.925 UTC client backend[44327] pg_regress/ltree ERROR: ltree syntax error at character 3 at character 8 2025-11-30 18:45:04.925 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1..3'::ltree; 2025-11-30 18:45:04.925 UTC client backend[44327] pg_regress/ltree ERROR: ltree syntax error at character 8 2025-11-30 18:45:04.925 UTC client backend[44327] pg_regress/ltree DETAIL: Unexpected end of input. 2025-11-30 18:45:04.925 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1.2.'::ltree; 2025-11-30 18:45:04.926 UTC client backend[44327] pg_regress/ltree ERROR: label string is too long 2025-11-30 18:45:04.926 UTC client backend[44327] pg_regress/ltree DETAIL: Label length is 1001, must be at most 1000, at character 1002. 2025-11-30 18:45:04.926 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT repeat('x', 1000 + 1)::ltree; 2025-11-30 18:45:04.927 UTC client backend[44327] pg_regress/ltree ERROR: invalid positions 2025-11-30 18:45:04.927 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT subpath('Top.Child1.Child2',-4); 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 1 at character 8 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '.2.3'::lquery; 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 3 at character 8 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1..3'::lquery; 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 8 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree DETAIL: Unexpected end of input. 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1.2.'::lquery; 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 1 at character 8 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '@.2.3'::lquery; 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 3 at character 8 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1.@.3'::lquery; 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 5 at character 8 2025-11-30 18:45:04.935 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1.2.@'::lquery; 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 2 at character 8 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree DETAIL: Empty labels are not allowed. 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '!.2.3'::lquery; 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 4 at character 8 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree DETAIL: Empty labels are not allowed. 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1.!.3'::lquery; 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 6 at character 8 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree DETAIL: Empty labels are not allowed. 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1.2.!'::lquery; 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 7 at character 8 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '1.2.3|@.4'::lquery; 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree ERROR: label string is too long 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree DETAIL: Label length is 1001, must be at most 1000, at character 1002. 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT (repeat('x', 1000 + 1) || '*@@*')::lquery; 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree ERROR: label string is too long 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree DETAIL: Label length is 1001, must be at most 1000, at character 1003. 2025-11-30 18:45:04.936 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT ('!' || repeat('x', 1000 + 1))::lquery; 2025-11-30 18:45:04.937 UTC unrecognized[44335] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:04.940 UTC client backend[44335] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:04.940 UTC client backend[44335] [unknown] LOG: connection authorized: user=postgres database=regression_ltree_plpython application_name=pg_regress/ltree_plpython 2025-11-30 18:45:04.941 UTC client backend[44335] pg_regress/ltree_plpython LOG: connection ready: setup total=6.308 ms, fork=2.541 ms, authentication=0.125 ms 2025-11-30 18:45:04.941 UTC client backend[44327] pg_regress/ltree ERROR: number of ltree labels (65536) exceeds the maximum allowed (65535) 2025-11-30 18:45:04.941 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT nlevel(('1' || repeat('.1', 65535))::ltree); 2025-11-30 18:45:04.944 UTC client backend[44327] pg_regress/ltree ERROR: number of ltree levels (65536) exceeds the maximum allowed (65535) 2025-11-30 18:45:04.944 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT nlevel(('1' || repeat('.1', 65534))::ltree || '1'); 2025-11-30 18:45:04.946 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mlparted5a" violates check constraint "check_b" 2025-11-30 18:45:04.946 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (1, 45, a). 2025-11-30 18:45:04.946 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'a'); 2025-11-30 18:45:04.948 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mlparted5a" violates partition constraint 2025-11-30 18:45:04.948 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (b, 1, 40). 2025-11-30 18:45:04.948 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted5 (a, b, c) values (1, 40, 'a'); 2025-11-30 18:45:04.965 UTC client backend[44326] pg_regress LOG: disconnection: session time: 0:00:00.137 user=postgres database=regression_ltree_plpython host=[local] 2025-11-30 18:45:04.968 UTC client backend[44327] pg_regress/ltree ERROR: number of lquery items (65536) exceeds the maximum allowed (65535) 2025-11-30 18:45:04.968 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT ('1' || repeat('.1', 65535))::lquery IS NULL; 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page ERROR: block number 1 is out of range for relation "test1" 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page STATEMENT: SELECT octet_length(get_raw_page('test1', 'main', 1)) AS main_1; 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 8 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree DETAIL: Low limit (65536) exceeds the maximum allowed (65535), at character 3. 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '*{65536}'::lquery; 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 8 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree DETAIL: High limit (65536) exceeds the maximum allowed (65535), at character 4. 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '*{,65536}'::lquery; 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree ERROR: lquery syntax error at character 8 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree DETAIL: Low limit (4) is greater than high limit (3), at character 5. 2025-11-30 18:45:04.969 UTC client backend[44327] pg_regress/ltree STATEMENT: SELECT '*{4,3}'::lquery; 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page ERROR: block number 1 is out of range for relation "test1" 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page STATEMENT: SELECT octet_length(get_raw_page('test1', 'vm', 1)) AS vm_1; 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page ERROR: invalid block number 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page STATEMENT: SELECT octet_length(get_raw_page('test1', 'main', -1)); 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page ERROR: relation "xxx" does not exist 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page STATEMENT: SELECT octet_length(get_raw_page('xxx', 'main', 0)); 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page ERROR: invalid fork name 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page HINT: Valid fork names are "main", "fsm", "vm", and "init". 2025-11-30 18:45:04.969 UTC client backend[44332] pg_regress/page STATEMENT: SELECT octet_length(get_raw_page('test1', 'xxx', 0)); 2025-11-30 18:45:04.970 UTC client backend[44332] pg_regress/page ERROR: invalid block number 2025-11-30 18:45:04.970 UTC client backend[44332] pg_regress/page STATEMENT: SELECT page_checksum(get_raw_page('test1', 0), -1); 2025-11-30 18:45:04.976 UTC client backend[44332] pg_regress/page ERROR: cannot get raw page from relation "test_partitioned" 2025-11-30 18:45:04.976 UTC client backend[44332] pg_regress/page DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:04.976 UTC client backend[44332] pg_regress/page STATEMENT: select get_raw_page('test_partitioned', 0); 2025-11-30 18:45:04.976 UTC client backend[44332] pg_regress/page ERROR: cannot get raw page from relation "test_partitioned_index" 2025-11-30 18:45:04.976 UTC client backend[44332] pg_regress/page DETAIL: This operation is not supported for partitioned indexes. 2025-11-30 18:45:04.976 UTC client backend[44332] pg_regress/page STATEMENT: select get_raw_page('test_partitioned_index', 0); 2025-11-30 18:45:04.978 UTC client backend[44332] pg_regress/page ERROR: block number 0 is out of range for relation "test_part1" 2025-11-30 18:45:04.978 UTC client backend[44332] pg_regress/page STATEMENT: select get_raw_page('test_part1', 0); 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mlparted_def" found for row 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (a) = (70). 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted values (70, 100); 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mlparted_def1" violates partition constraint 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (52, 50, null). 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted_def1 values (52, 50); 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mlparted_def2" violates partition constraint 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (34, 50, null). 2025-11-30 18:45:04.983 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted_def2 values (34, 50); 2025-11-30 18:45:05.003 UTC client backend[44335] pg_regress/ltree_plpython ERROR: ltree syntax error at character 1 2025-11-30 18:45:05.003 UTC client backend[44335] pg_regress/ltree_plpython CONTEXT: while creating return value PL/Python function "test2" 2025-11-30 18:45:05.003 UTC client backend[44335] pg_regress/ltree_plpython STATEMENT: SELECT test2(); 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page ERROR: invalid page size 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page STATEMENT: SELECT fsm_page_contents('aaa'::bytea); 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page ERROR: invalid page size 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page STATEMENT: SELECT page_checksum('bbb'::bytea, 0); 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page ERROR: invalid page size 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.004 UTC client backend[44332] pg_regress/page STATEMENT: SELECT page_header('ccc'::bytea); 2025-11-30 18:45:05.006 UTC client backend[44332] pg_regress/page LOG: disconnection: session time: 0:00:00.114 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.007 UTC client backend[44335] pg_regress/ltree_plpython LOG: disconnection: session time: 0:00:00.070 user=postgres database=regression_ltree_plpython host=[local] 2025-11-30 18:45:05.012 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mlparted5_cd" found for row 2025-11-30 18:45:05.012 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (c). 2025-11-30 18:45:05.012 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'c', 1); 2025-11-30 18:45:05.012 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mlparted5" found for row 2025-11-30 18:45:05.012 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (f). 2025-11-30 18:45:05.012 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'f', 1); 2025-11-30 18:45:05.017 UTC unrecognized[44340] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.017 UTC client backend[44340] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.017 UTC client backend[44340] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.018 UTC client backend[44340] pg_regress LOG: connection ready: setup total=1.943 ms, fork=0.658 ms, authentication=0.114 ms 2025-11-30 18:45:05.019 UTC client backend[44340] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.024 UTC client backend[44260] pg_regress/_int ERROR: value 0 out of bounds for option "siglen" 2025-11-30 18:45:05.024 UTC client backend[44260] pg_regress/_int DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:05.024 UTC client backend[44260] pg_regress/_int STATEMENT: CREATE INDEX text_idx on test__int using gist (a gist__intbig_ops(siglen = 0)); 2025-11-30 18:45:05.025 UTC client backend[44260] pg_regress/_int ERROR: value 2025 out of bounds for option "siglen" 2025-11-30 18:45:05.025 UTC client backend[44260] pg_regress/_int DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:05.025 UTC client backend[44260] pg_regress/_int STATEMENT: CREATE INDEX text_idx on test__int using gist (a gist__intbig_ops(siglen = 2025)); 2025-11-30 18:45:05.029 UTC client backend[44327] pg_regress/ltree ERROR: value 0 out of bounds for option "siglen" 2025-11-30 18:45:05.029 UTC client backend[44327] pg_regress/ltree DETAIL: Valid values are between "4" and "2024". 2025-11-30 18:45:05.029 UTC client backend[44327] pg_regress/ltree STATEMENT: create index tstidx on ltreetest using gist (t gist_ltree_ops(siglen=0)); 2025-11-30 18:45:05.030 UTC client backend[44327] pg_regress/ltree ERROR: value 2025 out of bounds for option "siglen" 2025-11-30 18:45:05.030 UTC client backend[44327] pg_regress/ltree DETAIL: Valid values are between "4" and "2024". 2025-11-30 18:45:05.030 UTC client backend[44327] pg_regress/ltree STATEMENT: create index tstidx on ltreetest using gist (t gist_ltree_ops(siglen=2025)); 2025-11-30 18:45:05.030 UTC client backend[44327] pg_regress/ltree ERROR: value 2028 out of bounds for option "siglen" 2025-11-30 18:45:05.030 UTC client backend[44327] pg_regress/ltree DETAIL: Valid values are between "4" and "2024". 2025-11-30 18:45:05.030 UTC client backend[44327] pg_regress/ltree STATEMENT: create index tstidx on ltreetest using gist (t gist_ltree_ops(siglen=2028)); 2025-11-30 18:45:05.031 UTC client backend[44327] pg_regress/ltree ERROR: siglen value must be a multiple of 4 2025-11-30 18:45:05.031 UTC client backend[44327] pg_regress/ltree STATEMENT: create index tstidx on ltreetest using gist (t gist_ltree_ops(siglen=2019)); 2025-11-30 18:45:05.039 UTC unrecognized[44345] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.040 UTC client backend[44345] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.040 UTC client backend[44345] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.040 UTC client backend[44345] pg_regress LOG: connection ready: setup total=2.514 ms, fork=1.193 ms, authentication=0.119 ms 2025-11-30 18:45:05.044 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mlparted5_cd" found for row 2025-11-30 18:45:05.044 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (c). 2025-11-30 18:45:05.044 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'c', 1); 2025-11-30 18:45:05.044 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mlparted5" found for row 2025-11-30 18:45:05.044 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (f). 2025-11-30 18:45:05.044 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'f', 1); 2025-11-30 18:45:05.052 UTC client backend[44345] pg_regress LOG: disconnection: session time: 0:00:00.013 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.063 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "key_desc_1" found for row 2025-11-30 18:45:05.063 UTC client backend[44232] pg_regress/insert STATEMENT: insert into key_desc values (1, 1); 2025-11-30 18:45:05.064 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "key_desc_1" found for row 2025-11-30 18:45:05.064 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (1). 2025-11-30 18:45:05.064 UTC client backend[44232] pg_regress/insert STATEMENT: insert into key_desc values (1, 1); 2025-11-30 18:45:05.064 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "key_desc" found for row 2025-11-30 18:45:05.064 UTC client backend[44232] pg_regress/insert STATEMENT: insert into key_desc values (2, 1); 2025-11-30 18:45:05.065 UTC unrecognized[44344] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.066 UTC client backend[44344] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.066 UTC client backend[44344] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/btree 2025-11-30 18:45:05.067 UTC client backend[44344] pg_regress/btree LOG: connection ready: setup total=41.452 ms, fork=39.872 ms, authentication=0.119 ms 2025-11-30 18:45:05.068 UTC client backend[44232] pg_regress/insert ERROR: every bound following MINVALUE must also be MINVALUE at character 75 2025-11-30 18:45:05.068 UTC client backend[44232] pg_regress/insert STATEMENT: create table mcrparted0 partition of mcrparted for values from (minvalue, 0, 0) to (1, maxvalue, maxvalue); 2025-11-30 18:45:05.069 UTC client backend[44232] pg_regress/insert ERROR: every bound following MAXVALUE must also be MAXVALUE at character 100 2025-11-30 18:45:05.069 UTC client backend[44232] pg_regress/insert STATEMENT: create table mcrparted2 partition of mcrparted for values from (10, 6, minvalue) to (10, maxvalue, minvalue); 2025-11-30 18:45:05.069 UTC client backend[44232] pg_regress/insert ERROR: every bound following MINVALUE must also be MINVALUE at character 79 2025-11-30 18:45:05.069 UTC client backend[44232] pg_regress/insert STATEMENT: create table mcrparted4 partition of mcrparted for values from (21, minvalue, 0) to (30, 20, minvalue); 2025-11-30 18:45:05.072 UTC client backend[44344] pg_regress/btree ERROR: invalid block number -1 2025-11-30 18:45:05.072 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_stats('test1_a_idx', -1); 2025-11-30 18:45:05.072 UTC client backend[44344] pg_regress/btree ERROR: block 0 is a meta page 2025-11-30 18:45:05.072 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_stats('test1_a_idx', 0); 2025-11-30 18:45:05.073 UTC client backend[44344] pg_regress/btree ERROR: block number 2 is out of range 2025-11-30 18:45:05.073 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_stats('test1_a_idx', 2); 2025-11-30 18:45:05.076 UTC client backend[44344] pg_regress/btree ERROR: block 0 is a meta page 2025-11-30 18:45:05.076 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_multi_page_stats('test2_col1_idx', 0, 1); 2025-11-30 18:45:05.077 UTC client backend[44344] pg_regress/btree ERROR: block number 7 is out of range 2025-11-30 18:45:05.077 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_multi_page_stats('test2_col1_idx', 7, 2); 2025-11-30 18:45:05.078 UTC client backend[44344] pg_regress/btree ERROR: invalid block number -1 2025-11-30 18:45:05.078 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_items('test1_a_idx', -1); 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree ERROR: block 0 is a meta page 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_items('test1_a_idx', 0); 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree ERROR: block number 2 is out of range 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_items('test1_a_idx', 2); 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree ERROR: invalid block number 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_items(get_raw_page('test1_a_idx', -1)); 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree ERROR: block is a meta page 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_items(get_raw_page('test1_a_idx', 0)); 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree ERROR: block number 2 is out of range for relation "test1_a_idx" 2025-11-30 18:45:05.079 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT * FROM bt_page_items(get_raw_page('test1_a_idx', 2)); 2025-11-30 18:45:05.080 UTC client backend[44344] pg_regress/btree ERROR: "test1_a_hash" is not a btree index 2025-11-30 18:45:05.080 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_metap('test1_a_hash'); 2025-11-30 18:45:05.080 UTC client backend[44344] pg_regress/btree ERROR: "test1_a_hash" is not a btree index 2025-11-30 18:45:05.080 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_page_stats('test1_a_hash', 0); 2025-11-30 18:45:05.081 UTC client backend[44344] pg_regress/btree ERROR: "test1_a_hash" is not a btree index 2025-11-30 18:45:05.081 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_page_items('test1_a_hash', 0); 2025-11-30 18:45:05.081 UTC client backend[44344] pg_regress/btree ERROR: block is a meta page 2025-11-30 18:45:05.081 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_page_items(get_raw_page('test1_a_hash', 0)); 2025-11-30 18:45:05.091 UTC unrecognized[44348] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.091 UTC client backend[44348] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.091 UTC client backend[44348] [unknown] LOG: connection authorized: user=postgres database=regression_pg_buffercache application_name=pg_regress/pg_buffercache 2025-11-30 18:45:05.096 UTC client backend[44348] pg_regress/pg_buffercache LOG: connection ready: setup total=10.513 ms, fork=5.451 ms, authentication=0.138 ms 2025-11-30 18:45:05.104 UTC client backend[44327] pg_regress/ltree ERROR: value 0 out of bounds for option "siglen" 2025-11-30 18:45:05.104 UTC client backend[44327] pg_regress/ltree DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:05.104 UTC client backend[44327] pg_regress/ltree STATEMENT: create index _tstidx on _ltreetest using gist (t gist__ltree_ops(siglen=0)); 2025-11-30 18:45:05.105 UTC client backend[44327] pg_regress/ltree ERROR: value 2025 out of bounds for option "siglen" 2025-11-30 18:45:05.105 UTC client backend[44327] pg_regress/ltree DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:05.105 UTC client backend[44327] pg_regress/ltree STATEMENT: create index _tstidx on _ltreetest using gist (t gist__ltree_ops(siglen=2025)); 2025-11-30 18:45:05.128 UTC client backend[44344] pg_regress/btree ERROR: block is not a valid btree leaf page 2025-11-30 18:45:05.128 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_page_items(get_raw_page('test1_b_gist', 0)); 2025-11-30 18:45:05.129 UTC unrecognized[44350] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.129 UTC client backend[44350] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.129 UTC client backend[44350] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.130 UTC client backend[44350] pg_regress LOG: connection ready: setup total=4.859 ms, fork=3.560 ms, authentication=0.116 ms 2025-11-30 18:45:05.130 UTC client backend[44350] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache ERROR: permission denied for view pg_buffercache 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache; 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache ERROR: permission denied for view pg_buffercache_os_pages 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_os_pages; 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache ERROR: permission denied for function pg_buffercache_pages 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_pages() AS p (wrong int); 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache ERROR: permission denied for function pg_buffercache_summary 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_summary(); 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache ERROR: permission denied for function pg_buffercache_usage_counts 2025-11-30 18:45:05.133 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_usage_counts(); 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache ERROR: must be superuser to use pg_buffercache_evict() 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_evict(1); 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache ERROR: must be superuser to use pg_buffercache_evict_relation() 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_evict_relation(1); 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache ERROR: must be superuser to use pg_buffercache_evict_all() 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_evict_all(); 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache ERROR: must be superuser to use pg_buffercache_mark_dirty() 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_mark_dirty(1); 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache ERROR: must be superuser to use pg_buffercache_mark_dirty_relation() 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_mark_dirty_relation(1); 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache ERROR: must be superuser to use pg_buffercache_mark_dirty_all() 2025-11-30 18:45:05.150 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_mark_dirty_all(); 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache ERROR: bad buffer ID: -1 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_evict(-1); 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache ERROR: bad buffer ID: 0 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_evict(0); 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache ERROR: bad buffer ID: 2147483647 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_evict(2147483647); 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache ERROR: bad buffer ID: -1 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_mark_dirty(-1); 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache ERROR: bad buffer ID: 0 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_mark_dirty(0); 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache ERROR: bad buffer ID: 2147483647 2025-11-30 18:45:05.151 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_mark_dirty(2147483647); 2025-11-30 18:45:05.152 UTC client backend[44344] pg_regress/btree ERROR: invalid page size 2025-11-30 18:45:05.152 UTC client backend[44344] pg_regress/btree DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.152 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_page_items('aaa'::bytea); 2025-11-30 18:45:05.153 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mcrparted" found for row 2025-11-30 18:45:05.153 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (a, abs(b), c) = (null, null, null). 2025-11-30 18:45:05.153 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mcrparted values (null, null, null); 2025-11-30 18:45:05.153 UTC client backend[44348] pg_regress/pg_buffercache ERROR: relation uses local buffers, pg_buffercache_evict_relation() is intended to be used for shared buffers only 2025-11-30 18:45:05.153 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_evict_relation('temp_pg_buffercache'); 2025-11-30 18:45:05.153 UTC client backend[44348] pg_regress/pg_buffercache ERROR: relation uses local buffers, pg_buffercache_mark_dirty_relation() is intended to be used for shared buffers only 2025-11-30 18:45:05.153 UTC client backend[44348] pg_regress/pg_buffercache STATEMENT: SELECT * FROM pg_buffercache_mark_dirty_relation('temp_pg_buffercache'); 2025-11-30 18:45:05.159 UTC unrecognized[44352] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.160 UTC client backend[44352] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.160 UTC client backend[44352] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.164 UTC client backend[44352] pg_regress LOG: connection ready: setup total=8.784 ms, fork=3.972 ms, authentication=0.151 ms 2025-11-30 18:45:05.179 UTC client backend[44344] pg_regress/btree ERROR: input page is not a valid btree page 2025-11-30 18:45:05.179 UTC client backend[44344] pg_regress/btree DETAIL: Expected special size 16, got 0. 2025-11-30 18:45:05.179 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_page_items(get_raw_page('test1', 0)); 2025-11-30 18:45:05.179 UTC client backend[44344] pg_regress/btree ERROR: input page is not a valid btree page 2025-11-30 18:45:05.179 UTC client backend[44344] pg_regress/btree DETAIL: Expected special size 16, got 8. 2025-11-30 18:45:05.179 UTC client backend[44344] pg_regress/btree STATEMENT: SELECT bt_page_items(get_raw_page('test1_a_brin', 0)); 2025-11-30 18:45:05.182 UTC client backend[44344] pg_regress/btree LOG: disconnection: session time: 0:00:00.116 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.193 UTC client backend[44352] pg_regress LOG: disconnection: session time: 0:00:00.033 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.202 UTC unrecognized[44354] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.202 UTC client backend[44354] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.202 UTC client backend[44354] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/init 2025-11-30 18:45:05.206 UTC client backend[44232] pg_regress/insert ERROR: no partition of relation "mcrparted" found for row 2025-11-30 18:45:05.206 UTC client backend[44232] pg_regress/insert DETAIL: Partition key of the failing row contains (a, abs(b), c) = (11, 1, -1). 2025-11-30 18:45:05.206 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mcrparted values (11, 1, -1); 2025-11-30 18:45:05.206 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mcrparted3" violates partition constraint 2025-11-30 18:45:05.206 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (11, 1, -1). 2025-11-30 18:45:05.206 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mcrparted3 values (11, 1, -1); 2025-11-30 18:45:05.207 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "mcrparted4" violates partition constraint 2025-11-30 18:45:05.207 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (30, 21, 20). 2025-11-30 18:45:05.207 UTC client backend[44232] pg_regress/insert STATEMENT: insert into mcrparted4 values (30, 21, 20); 2025-11-30 18:45:05.214 UTC unrecognized[44357] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.216 UTC client backend[44357] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.216 UTC client backend[44357] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/brin 2025-11-30 18:45:05.218 UTC client backend[44357] pg_regress/brin LOG: connection ready: setup total=4.076 ms, fork=0.750 ms, authentication=0.181 ms 2025-11-30 18:45:05.222 UTC client backend[44354] pg_regress/init LOG: connection ready: setup total=21.246 ms, fork=0.510 ms, authentication=0.214 ms 2025-11-30 18:45:05.223 UTC client backend[44357] pg_regress/brin ERROR: page is not a BRIN page of type "metapage" 2025-11-30 18:45:05.223 UTC client backend[44357] pg_regress/brin DETAIL: Expected special type 0000f091, got 0000f092. 2025-11-30 18:45:05.223 UTC client backend[44357] pg_regress/brin STATEMENT: SELECT * FROM brin_metapage_info(get_raw_page('test1_a_idx', 1)); 2025-11-30 18:45:05.224 UTC client backend[44357] pg_regress/brin ERROR: page is not a BRIN page of type "revmap" 2025-11-30 18:45:05.224 UTC client backend[44357] pg_regress/brin DETAIL: Expected special type 0000f092, got 0000f091. 2025-11-30 18:45:05.224 UTC client backend[44357] pg_regress/brin STATEMENT: SELECT * FROM brin_revmap_data(get_raw_page('test1_a_idx', 0)) LIMIT 5; 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin ERROR: "test1_a_btree" is not a BRIN index 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin STATEMENT: SELECT brin_page_items(get_raw_page('test1_a_btree', 0), 'test1_a_btree'); 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin ERROR: input page is not a valid BRIN page 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin DETAIL: Expected special size 8, got 16. 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin STATEMENT: SELECT brin_page_items(get_raw_page('test1_a_btree', 0), 'test1_a_idx'); 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin ERROR: input page is not a valid BRIN page 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin DETAIL: Expected special size 8, got 0. 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin STATEMENT: SELECT brin_page_type(get_raw_page('test1', 0)); 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin ERROR: input page is not a valid BRIN page 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin DETAIL: Expected special size 8, got 0. 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin STATEMENT: SELECT * FROM brin_metapage_info(get_raw_page('test1', 0)); 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin ERROR: input page is not a valid BRIN page 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin DETAIL: Expected special size 8, got 0. 2025-11-30 18:45:05.226 UTC client backend[44357] pg_regress/brin STATEMENT: SELECT * FROM brin_revmap_data(get_raw_page('test1', 0)); 2025-11-30 18:45:05.237 UTC client backend[44327] pg_regress/ltree LOG: disconnection: session time: 0:00:00.400 user=postgres database=regression_ltree host=[local] 2025-11-30 18:45:05.238 UTC client backend[44348] pg_regress/pg_buffercache LOG: disconnection: session time: 0:00:00.147 user=postgres database=regression_pg_buffercache host=[local] 2025-11-30 18:45:05.242 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2025-11-30 18:45:05.242 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (2, hi there). 2025-11-30 18:45:05.242 UTC client backend[44232] pg_regress/insert STATEMENT: insert into brtrigpartcon values (1, 'hi there'); 2025-11-30 18:45:05.242 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2025-11-30 18:45:05.242 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (2, hi there). 2025-11-30 18:45:05.242 UTC client backend[44232] pg_regress/insert STATEMENT: insert into brtrigpartcon1 values (1, 'hi there'); 2025-11-30 18:45:05.246 UTC client backend[44232] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2025-11-30 18:45:05.246 UTC client backend[44232] pg_regress/insert DETAIL: Failing row contains (a, b) = (2, hi there). 2025-11-30 18:45:05.246 UTC client backend[44232] pg_regress/insert STATEMENT: with result as (insert into brtrigpartcon values (1, 'hi there') returning 1) insert into inserttest3 (f3) select * from result; 2025-11-30 18:45:05.247 UTC client backend[44354] pg_regress/init ERROR: gen_salt: Unknown salt algorithm 2025-11-30 18:45:05.247 UTC client backend[44354] pg_regress/init STATEMENT: select gen_salt('foo'); 2025-11-30 18:45:05.248 UTC client backend[44354] pg_regress/init ERROR: Cannot use "foo": No such hash algorithm 2025-11-30 18:45:05.248 UTC client backend[44354] pg_regress/init STATEMENT: select digest('foo', 'foo'); 2025-11-30 18:45:05.248 UTC client backend[44354] pg_regress/init ERROR: Cannot use "foo": No such hash algorithm 2025-11-30 18:45:05.248 UTC client backend[44354] pg_regress/init STATEMENT: select hmac('foo', 'foo', 'foo'); 2025-11-30 18:45:05.248 UTC client backend[44354] pg_regress/init ERROR: Cannot use "foo": No such cipher algorithm 2025-11-30 18:45:05.248 UTC client backend[44354] pg_regress/init STATEMENT: select encrypt('foo', 'foo', 'foo'); 2025-11-30 18:45:05.248 UTC unrecognized[44361] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.248 UTC client backend[44354] pg_regress/init LOG: disconnection: session time: 0:00:00.046 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.260 UTC client backend[44361] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.260 UTC client backend[44361] [unknown] LOG: connection authorized: user=postgres database=regression_pg_buffercache application_name=pg_regress/pg_buffercache_numa 2025-11-30 18:45:05.261 UTC client backend[44361] pg_regress/pg_buffercache_numa LOG: connection ready: setup total=14.754 ms, fork=1.677 ms, authentication=0.164 ms 2025-11-30 18:45:05.262 UTC unrecognized[44364] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.262 UTC client backend[44361] pg_regress/pg_buffercache_numa LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_pg_buffercache host=[local] 2025-11-30 18:45:05.262 UTC client backend[44364] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.262 UTC client backend[44364] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/md5 2025-11-30 18:45:05.263 UTC client backend[44364] pg_regress/md5 LOG: connection ready: setup total=1.832 ms, fork=0.368 ms, authentication=0.103 ms 2025-11-30 18:45:05.265 UTC client backend[44364] pg_regress/md5 LOG: disconnection: session time: 0:00:00.003 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.292 UTC unrecognized[44373] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.292 UTC client backend[44373] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.292 UTC client backend[44373] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/sha1 2025-11-30 18:45:05.293 UTC client backend[44373] pg_regress/sha1 LOG: connection ready: setup total=3.585 ms, fork=2.076 ms, authentication=0.122 ms 2025-11-30 18:45:05.298 UTC client backend[44373] pg_regress/sha1 LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.304 UTC unrecognized[44377] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.304 UTC client backend[44377] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.304 UTC client backend[44377] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/hmac-md5 2025-11-30 18:45:05.305 UTC client backend[44377] pg_regress/hmac-md5 LOG: connection ready: setup total=1.894 ms, fork=0.382 ms, authentication=0.122 ms 2025-11-30 18:45:05.306 UTC client backend[44357] pg_regress/brin LOG: disconnection: session time: 0:00:00.091 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.327 UTC client backend[44377] pg_regress/hmac-md5 LOG: disconnection: session time: 0:00:00.023 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.333 UTC unrecognized[44382] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.333 UTC client backend[44382] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.333 UTC client backend[44382] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/gin 2025-11-30 18:45:05.334 UTC client backend[44382] pg_regress/gin LOG: connection ready: setup total=3.555 ms, fork=2.049 ms, authentication=0.129 ms 2025-11-30 18:45:05.336 UTC unrecognized[44384] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.337 UTC client backend[44384] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.337 UTC client backend[44384] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.337 UTC client backend[44384] pg_regress LOG: connection ready: setup total=2.749 ms, fork=1.406 ms, authentication=0.110 ms 2025-11-30 18:45:05.338 UTC client backend[44384] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.339 UTC client backend[44382] pg_regress/gin ERROR: input page is not a GIN metapage 2025-11-30 18:45:05.339 UTC client backend[44382] pg_regress/gin DETAIL: Flags 0002, expected 0008 2025-11-30 18:45:05.339 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT * FROM gin_metapage_info(get_raw_page('test1_y_idx', 1)); 2025-11-30 18:45:05.340 UTC client backend[44382] pg_regress/gin ERROR: input page is not a compressed GIN data leaf page 2025-11-30 18:45:05.340 UTC client backend[44382] pg_regress/gin DETAIL: Flags 0002, expected 0083 2025-11-30 18:45:05.340 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT * FROM gin_leafpage_items(get_raw_page('test1_y_idx', 1)); 2025-11-30 18:45:05.344 UTC unrecognized[44386] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.345 UTC client backend[44386] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.345 UTC client backend[44386] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.345 UTC client backend[44386] pg_regress LOG: connection ready: setup total=2.572 ms, fork=1.296 ms, authentication=0.118 ms 2025-11-30 18:45:05.361 UTC unrecognized[44390] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.362 UTC client backend[44390] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.362 UTC client backend[44390] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.362 UTC client backend[44390] pg_regress LOG: connection ready: setup total=5.653 ms, fork=4.204 ms, authentication=0.136 ms 2025-11-30 18:45:05.363 UTC client backend[44390] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.369 UTC unrecognized[44392] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.369 UTC client backend[44392] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.369 UTC client backend[44392] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.370 UTC client backend[44392] pg_regress LOG: connection ready: setup total=3.581 ms, fork=2.165 ms, authentication=0.133 ms 2025-11-30 18:45:05.377 UTC unrecognized[44393] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.377 UTC client backend[44393] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.377 UTC client backend[44393] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/hmac-sha1 2025-11-30 18:45:05.378 UTC client backend[44393] pg_regress/hmac-sha1 LOG: connection ready: setup total=7.550 ms, fork=5.975 ms, authentication=0.122 ms 2025-11-30 18:45:05.383 UTC client backend[44393] pg_regress/hmac-sha1 LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.407 UTC unrecognized[44396] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.408 UTC client backend[44396] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.408 UTC client backend[44396] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/blowfish 2025-11-30 18:45:05.409 UTC client backend[44396] pg_regress/blowfish LOG: connection ready: setup total=3.041 ms, fork=1.537 ms, authentication=0.124 ms 2025-11-30 18:45:05.409 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.409 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x0000000000000000', '\x0000000000000000', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.409 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.409 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\xffffffffffffffff', '\xffffffffffffffff', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x1000000000000001', '\x3000000000000000', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x1111111111111111', '\x1111111111111111', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x0123456789abcdef', '\xfedcba9876543210', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x01a1d6d039776742', '\xfedcba9876543210', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\xffffffffffffffff', '\x0000000000000000', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\xfedcba9876543210', '\xf0e1d2c3b4a5968778695a4b3c2d1e0f', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x01234567890123456789', '\x33443344334433443344334433443344', 'bf-ecb'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Key was too big 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x6b77b4d63006dee605b156e27403979358deb9e7154616d959f1652bd5', '\x37363534333231204e6f77206973207468652074696d6520666f7220', 'bf-cbc'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Key was too big 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\x6b77b4d63006dee605b156e27403979358deb9e7154616d959f1652bd5ff92cc', '\x37363534333231204e6f77206973207468652074696d6520666f722000', 'bf-cbc'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Key was too big 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: SELECT encrypt('\xfedcba9876543210', '\xf0e1d2c3b4a5968778695a4b3c2d1e0f001122334455667704689104c2fd3b2f584023641aba61761f1f1f1f0e0e0e0effffffffffffffff', 'bf-ecb/pad:none'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encrypt('', 'foo', 'bf'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encrypt('foo', '0123456789', 'bf'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Key was too big 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encrypt('foo', '0123456789012345678901', 'bf'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encode(decrypt(encrypt('foo', '0123456', 'bf'), '0123456', 'bf'), 'escape'); 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt_iv error: Cipher cannot be initialized 2025-11-30 18:45:05.410 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encrypt_iv('foo', '0123456', 'abcd', 'bf'); 2025-11-30 18:45:05.411 UTC client backend[44396] pg_regress/blowfish ERROR: decrypt_iv error: Cipher cannot be initialized 2025-11-30 18:45:05.411 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encode(decrypt_iv('\x95c7e89322525d59', '0123456', 'abcd', 'bf'), 'escape'); 2025-11-30 18:45:05.411 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.411 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encrypt('Lets try a longer message.', '0123456789', 'bf'); 2025-11-30 18:45:05.411 UTC client backend[44396] pg_regress/blowfish ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.411 UTC client backend[44396] pg_regress/blowfish STATEMENT: select encode(decrypt(encrypt('Lets try a longer message.', '0123456789', 'bf'), '0123456789', 'bf'), 'escape'); 2025-11-30 18:45:05.411 UTC client backend[44396] pg_regress/blowfish LOG: disconnection: session time: 0:00:00.003 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.443 UTC client backend[44386] pg_regress LOG: disconnection: session time: 0:00:00.099 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.453 UTC client backend[44392] pg_regress LOG: disconnection: session time: 0:00:00.084 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.458 UTC unrecognized[44400] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.458 UTC client backend[44400] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.458 UTC client backend[44400] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/rijndael 2025-11-30 18:45:05.459 UTC client backend[44400] pg_regress/rijndael LOG: connection ready: setup total=9.093 ms, fork=7.619 ms, authentication=0.117 ms 2025-11-30 18:45:05.460 UTC client backend[44400] pg_regress/rijndael ERROR: encrypt error: Encryption failed 2025-11-30 18:45:05.460 UTC client backend[44400] pg_regress/rijndael STATEMENT: SELECT encrypt( '\x00112233445566778899aabbccddeeff00', '\x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f', 'aes-cbc/pad:none'); 2025-11-30 18:45:05.461 UTC client backend[44400] pg_regress/rijndael ERROR: decrypt error: Decryption failed 2025-11-30 18:45:05.461 UTC client backend[44400] pg_regress/rijndael STATEMENT: select encode(decrypt(encrypt('foo', '0123456', 'aes') || '\x00'::bytea, '0123456', 'aes'), 'escape'); 2025-11-30 18:45:05.461 UTC client backend[44400] pg_regress/rijndael ERROR: decrypt_iv error: Decryption failed 2025-11-30 18:45:05.461 UTC client backend[44400] pg_regress/rijndael STATEMENT: select encode(decrypt_iv('\xa21a9c15231465964e3396d32095e67eb52bab05f556a581621dee1b85385789', '0123456', 'abcd', 'aes'), 'escape'); 2025-11-30 18:45:05.463 UTC client backend[44400] pg_regress/rijndael LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.465 UTC unrecognized[44403] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.465 UTC client backend[44403] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.465 UTC client backend[44403] [unknown] LOG: connection authorized: user=postgres database=regression_pg_prewarm application_name=pg_regress/pg_prewarm 2025-11-30 18:45:05.466 UTC unrecognized[44404] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.467 UTC client backend[44404] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.467 UTC client backend[44404] [unknown] LOG: connection authorized: user=postgres database=regression_pg_overexplain application_name=pg_regress/pg_overexplain 2025-11-30 18:45:05.470 UTC unrecognized[44407] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.470 UTC client backend[44403] pg_regress/pg_prewarm LOG: connection ready: setup total=7.934 ms, fork=2.518 ms, authentication=0.121 ms 2025-11-30 18:45:05.470 UTC client backend[44407] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.470 UTC client backend[44407] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/sha2 2025-11-30 18:45:05.471 UTC client backend[44404] pg_regress/pg_overexplain LOG: connection ready: setup total=8.436 ms, fork=2.356 ms, authentication=0.108 ms 2025-11-30 18:45:05.471 UTC client backend[44407] pg_regress/sha2 LOG: connection ready: setup total=2.034 ms, fork=0.714 ms, authentication=0.111 ms 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin ERROR: invalid page size 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT gin_leafpage_items('aaa'::bytea); 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin ERROR: invalid page size 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT gin_metapage_info('bbb'::bytea); 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin ERROR: invalid page size 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT gin_page_opaque_info('ccc'::bytea); 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin ERROR: input page is not a valid GIN metapage 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin DETAIL: Expected special size 8, got 0. 2025-11-30 18:45:05.471 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT * FROM gin_metapage_info(get_raw_page('test1', 0)); 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain ERROR: unrecognized EXPLAIN option "debuff" at character 10 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain STATEMENT: EXPLAIN (DEBUFF) SELECT 1; 2025-11-30 18:45:05.472 UTC client backend[44382] pg_regress/gin ERROR: input page is not a valid GIN data leaf page 2025-11-30 18:45:05.472 UTC client backend[44382] pg_regress/gin DETAIL: Expected special size 8, got 0. 2025-11-30 18:45:05.472 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT * FROM gin_page_opaque_info(get_raw_page('test1', 0)); 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain ERROR: unrecognized EXPLAIN option "debug" at character 10 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain STATEMENT: EXPLAIN (DEBUG) SELECT 1; 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain ERROR: unrecognized EXPLAIN option "range_table" at character 10 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain STATEMENT: EXPLAIN (RANGE_TABLE) SELECT 1; 2025-11-30 18:45:05.472 UTC client backend[44382] pg_regress/gin ERROR: input page is not a valid GIN data leaf page 2025-11-30 18:45:05.472 UTC client backend[44382] pg_regress/gin DETAIL: Expected special size 8, got 0. 2025-11-30 18:45:05.472 UTC client backend[44382] pg_regress/gin STATEMENT: SELECT * FROM gin_leafpage_items(get_raw_page('test1', 0)); 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain ERROR: unrecognized EXPLAIN option "debuff" at character 10 2025-11-30 18:45:05.472 UTC client backend[44404] pg_regress/pg_overexplain STATEMENT: EXPLAIN (DEBUFF) SELECT 1; 2025-11-30 18:45:05.474 UTC client backend[44407] pg_regress/sha2 LOG: disconnection: session time: 0:00:00.003 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.474 UTC client backend[44382] pg_regress/gin LOG: disconnection: session time: 0:00:00.141 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.474 UTC client backend[44403] pg_regress/pg_prewarm ERROR: relation "test" does not have storage 2025-11-30 18:45:05.474 UTC client backend[44403] pg_regress/pg_prewarm DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:05.474 UTC client backend[44403] pg_regress/pg_prewarm STATEMENT: SELECT pg_prewarm('test', 'buffer'); 2025-11-30 18:45:05.479 UTC client backend[44232] pg_regress/insert LOG: disconnection: session time: 0:00:01.522 user=postgres database=regression host=[local] 2025-11-30 18:45:05.484 UTC unrecognized[44414] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.485 UTC client backend[44414] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.485 UTC client backend[44414] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/gist 2025-11-30 18:45:05.485 UTC client backend[44414] pg_regress/gist LOG: connection ready: setup total=1.988 ms, fork=0.571 ms, authentication=0.110 ms 2025-11-30 18:45:05.491 UTC unrecognized[44416] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.491 UTC client backend[44416] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.491 UTC client backend[44416] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/des 2025-11-30 18:45:05.496 UTC client backend[44416] pg_regress/des LOG: connection ready: setup total=8.958 ms, fork=2.461 ms, authentication=0.108 ms 2025-11-30 18:45:05.497 UTC client backend[44416] pg_regress/des ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.497 UTC client backend[44416] pg_regress/des STATEMENT: SELECT encrypt('\x0123456789abcdef', '\xfedcba9876543210', 'des-ecb/pad:none'); 2025-11-30 18:45:05.500 UTC client backend[44416] pg_regress/des ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.500 UTC client backend[44416] pg_regress/des STATEMENT: select encrypt('', 'foo', 'des'); 2025-11-30 18:45:05.501 UTC unrecognized[44427] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.501 UTC unrecognized[44428] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.501 UTC client backend[44416] pg_regress/des ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.501 UTC client backend[44416] pg_regress/des STATEMENT: select encrypt('foo', '01234589', 'des'); 2025-11-30 18:45:05.501 UTC client backend[44428] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.501 UTC client backend[44416] pg_regress/des ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.501 UTC client backend[44416] pg_regress/des STATEMENT: select encode(decrypt(encrypt('foo', '0123456', 'des'), '0123456', 'des'), 'escape'); 2025-11-30 18:45:05.501 UTC client backend[44428] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_misc 2025-11-30 18:45:05.501 UTC client backend[44427] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.501 UTC client backend[44427] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_function_c 2025-11-30 18:45:05.502 UTC client backend[44427] pg_regress/create_function_c LOG: connection ready: setup total=5.723 ms, fork=1.746 ms, authentication=0.112 ms 2025-11-30 18:45:05.502 UTC unrecognized[44430] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.503 UTC client backend[44430] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.503 UTC client backend[44430] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_procedure 2025-11-30 18:45:05.503 UTC client backend[44430] pg_regress/create_procedure LOG: connection ready: setup total=3.243 ms, fork=0.884 ms, authentication=0.096 ms 2025-11-30 18:45:05.504 UTC client backend[44430] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist at character 6 2025-11-30 18:45:05.504 UTC client backend[44430] pg_regress/create_procedure DETAIL: There is no procedure of that name. 2025-11-30 18:45:05.504 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CALL nonexistent(); 2025-11-30 18:45:05.504 UTC client backend[44430] pg_regress/create_procedure ERROR: random() is not a procedure at character 6 2025-11-30 18:45:05.504 UTC client backend[44430] pg_regress/create_procedure HINT: To call a function, use SELECT. 2025-11-30 18:45:05.504 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CALL random(); 2025-11-30 18:45:05.504 UTC client backend[44403] pg_regress/pg_prewarm LOG: disconnection: session time: 0:00:00.039 user=postgres database=regression_pg_prewarm host=[local] 2025-11-30 18:45:05.505 UTC client backend[44427] pg_regress/create_function_c ERROR: could not access file "nosuchfile": No such file or directory 2025-11-30 18:45:05.505 UTC client backend[44427] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C AS 'nosuchfile'; 2025-11-30 18:45:05.509 UTC unrecognized[44432] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.509 UTC client backend[44427] pg_regress/create_function_c ERROR: could not find function "nosuchsymbol" in file "/tmp/cirrus-ci-build/build/src/test/regress/regress.so" 2025-11-30 18:45:05.509 UTC client backend[44427] 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-11-30 18:45:05.509 UTC unrecognized[44434] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.509 UTC client backend[44432] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.509 UTC client backend[44432] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_operator 2025-11-30 18:45:05.510 UTC client backend[44432] pg_regress/create_operator LOG: connection ready: setup total=6.654 ms, fork=2.076 ms, authentication=0.160 ms 2025-11-30 18:45:05.511 UTC client backend[44434] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.511 UTC client backend[44434] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_table 2025-11-30 18:45:05.512 UTC client backend[44434] pg_regress/create_table LOG: connection ready: setup total=3.444 ms, fork=0.727 ms, authentication=0.107 ms 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator ERROR: operator right argument type must be specified 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator DETAIL: Postfix operators are not supported. 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #%# ( leftarg = int8, -- fail, postfix is no longer supported procedure = factorial ); 2025-11-30 18:45:05.512 UTC client backend[44427] pg_regress/create_function_c ERROR: there is no built-in function named "nosuch" 2025-11-30 18:45:05.512 UTC client backend[44427] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE internal AS 'nosuch'; 2025-11-30 18:45:05.512 UTC unrecognized[44433] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator ERROR: operator does not exist: @@##@@ integer at character 8 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator DETAIL: There is no operator of that name. 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator STATEMENT: select @@##@@ 24; 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator ERROR: operator does not exist: @#@ integer at character 8 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator DETAIL: An operator of that name exists, but it is not in the search_path. 2025-11-30 18:45:05.512 UTC client backend[44432] pg_regress/create_operator STATEMENT: select @#@ 24; 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: operator does not exist: @#@ numeric at character 8 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator DETAIL: No operator of that name accepts the given argument type. 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator HINT: You might need to add an explicit type cast. 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: select @#@ 24.0; 2025-11-30 18:45:05.513 UTC client backend[44433] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.513 UTC client backend[44433] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_schema 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: operator does not exist: ###### integer 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (NONE, int4) IS 'bad prefix'; 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: postfix operators are not supported 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (int4, NONE) IS 'bad postfix'; 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: operator does not exist: integer ###### bigint 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (int4, int8) IS 'bad infix'; 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: operator does not exist: ###### integer 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (NONE, int4); 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: postfix operators are not supported 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (int4, NONE); 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: operator does not exist: integer ###### bigint 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (int4, int8); 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: syntax error at or near "=>" at character 17 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR => ( rightarg = int8, procedure = factorial ); 2025-11-30 18:45:05.513 UTC client backend[44433] pg_regress/create_schema LOG: connection ready: setup total=6.973 ms, fork=3.938 ms, authentication=0.108 ms 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator ERROR: syntax error at or near ";" at character 14 2025-11-30 18:45:05.513 UTC client backend[44432] pg_regress/create_operator STATEMENT: SELECT 10 !=-; 2025-11-30 18:45:05.514 UTC unrecognized[44429] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.514 UTC client backend[44434] pg_regress/create_table ERROR: column "u" has pseudo-type unknown 2025-11-30 18:45:05.514 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE unknowntab ( u unknown -- fail ); 2025-11-30 18:45:05.514 UTC client backend[44427] pg_regress/create_function_c LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression host=[local] 2025-11-30 18:45:05.514 UTC client backend[44429] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.514 UTC client backend[44429] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_type 2025-11-30 18:45:05.515 UTC client backend[44429] pg_regress/create_type LOG: connection ready: setup total=15.111 ms, fork=8.578 ms, authentication=0.110 ms 2025-11-30 18:45:05.516 UTC client backend[44434] pg_regress/create_table ERROR: column "u" has pseudo-type unknown 2025-11-30 18:45:05.516 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TYPE unknown_comptype AS ( u unknown -- fail ); 2025-11-30 18:45:05.516 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.516 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE SEQUENCE schema_not_existing.seq; 2025-11-30 18:45:05.517 UTC client backend[44434] pg_regress/create_table ERROR: unrecognized parameter "Fillfactor" 2025-11-30 18:45:05.517 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE tas_case WITH ("Fillfactor" = 10) AS SELECT 1 a; 2025-11-30 18:45:05.520 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.520 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE TABLE schema_not_existing.tab (id int); 2025-11-30 18:45:05.521 UTC client backend[44429] pg_regress/create_type ERROR: type "shell" already exists 2025-11-30 18:45:05.521 UTC client backend[44429] pg_regress/create_type STATEMENT: CREATE TYPE shell; 2025-11-30 18:45:05.521 UTC client backend[44429] pg_regress/create_type ERROR: type "shell" does not exist 2025-11-30 18:45:05.521 UTC client backend[44429] pg_regress/create_type STATEMENT: DROP TYPE shell; 2025-11-30 18:45:05.523 UTC client backend[44414] pg_regress/gist ERROR: "test_gist_btree" is not a GiST index 2025-11-30 18:45:05.523 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT gist_page_items(get_raw_page('test_gist_btree', 0), 'test_gist_btree'); 2025-11-30 18:45:05.525 UTC client backend[44404] pg_regress/pg_overexplain LOG: disconnection: session time: 0:00:00.059 user=postgres database=regression_pg_overexplain host=[local] 2025-11-30 18:45:05.526 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.526 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE VIEW schema_not_existing.view AS SELECT 1; 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type WARNING: type attribute "Internallength" not recognized at character 27 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type WARNING: type attribute "Input" not recognized at character 50 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type WARNING: type attribute "Output" not recognized at character 71 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type WARNING: type attribute "Alignment" not recognized at character 94 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type WARNING: type attribute "Default" not recognized at character 115 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type WARNING: type attribute "Passedbyvalue" not recognized at character 132 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type ERROR: type input function must be specified 2025-11-30 18:45:05.526 UTC client backend[44429] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type ( "Internallength" = 4, "Input" = int42_in, "Output" = int42_out, "Alignment" = int4, "Default" = 42, "Passedbyvalue" ); 2025-11-30 18:45:05.527 UTC client backend[44429] pg_regress/create_type ERROR: type input function array_in must return type bogus_type 2025-11-30 18:45:05.527 UTC client backend[44429] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type (INPUT = array_in, OUTPUT = array_out, ELEMENT = int, INTERNALLENGTH = 32); 2025-11-30 18:45:05.527 UTC client backend[44429] pg_regress/create_type ERROR: type "bogus_type" does not exist 2025-11-30 18:45:05.527 UTC client backend[44429] 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-11-30 18:45:05.527 UTC client backend[44429] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type (INPUT = array_in, OUTPUT = array_out, ELEMENT = int, INTERNALLENGTH = 32); 2025-11-30 18:45:05.527 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.527 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE INDEX ON schema_not_existing.tab (id); 2025-11-30 18:45:05.528 UTC client backend[44429] pg_regress/create_type ERROR: type "bad" does not exist 2025-11-30 18:45:05.528 UTC client backend[44429] pg_regress/create_type STATEMENT: COMMENT ON TYPE bad IS 'bad comment'; 2025-11-30 18:45:05.529 UTC client backend[44429] pg_regress/create_type ERROR: column "nope" of relation "default_test_row" does not exist 2025-11-30 18:45:05.529 UTC client backend[44429] pg_regress/create_type STATEMENT: COMMENT ON COLUMN default_test_row.nope IS 'bad comment'; 2025-11-30 18:45:05.529 UTC client backend[44429] pg_regress/create_type ERROR: type "text_w_default" already exists 2025-11-30 18:45:05.529 UTC client backend[44429] pg_regress/create_type STATEMENT: CREATE TYPE text_w_default; 2025-11-30 18:45:05.529 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.529 UTC client backend[44433] 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-11-30 18:45:05.530 UTC client backend[44430] pg_regress/create_procedure ERROR: ptest1(unknown) is a procedure at character 8 2025-11-30 18:45:05.530 UTC client backend[44430] pg_regress/create_procedure HINT: To call a procedure, use CALL. 2025-11-30 18:45:05.530 UTC client backend[44430] pg_regress/create_procedure STATEMENT: SELECT ptest1('x'); 2025-11-30 18:45:05.530 UTC client backend[44414] pg_regress/gist ERROR: input page is not a valid GiST page 2025-11-30 18:45:05.530 UTC client backend[44414] pg_regress/gist DETAIL: Expected 0000ff81, got 00000000. 2025-11-30 18:45:05.530 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT gist_page_items(get_raw_page('test_gist_btree', 0), 'test_gist_idx'); 2025-11-30 18:45:05.531 UTC client backend[44428] pg_regress/create_misc LOG: connection ready: setup total=33.798 ms, fork=1.405 ms, authentication=0.120 ms 2025-11-30 18:45:05.532 UTC client backend[44434] pg_regress/create_table ERROR: only temporary relations may be created in temporary schemas at character 23 2025-11-30 18:45:05.532 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE UNLOGGED TABLE pg_temp.unlogged3 (a int primary key); 2025-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type ERROR: cannot drop function base_fn_in(cstring) because other objects depend on it 2025-11-30 18:45:05.532 UTC client backend[44429] 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-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type STATEMENT: DROP FUNCTION base_fn_in(cstring); 2025-11-30 18:45:05.532 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.532 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE SEQUENCE schema_not_existing.seq; 2025-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type ERROR: cannot drop function base_fn_out(base_type) because other objects depend on it 2025-11-30 18:45:05.532 UTC client backend[44429] 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-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type STATEMENT: DROP FUNCTION base_fn_out(base_type); 2025-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type ERROR: cannot drop type base_type because other objects depend on it 2025-11-30 18:45:05.532 UTC client backend[44429] 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-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.532 UTC client backend[44429] pg_regress/create_type STATEMENT: DROP TYPE base_type; 2025-11-30 18:45:05.533 UTC client backend[44429] pg_regress/create_type ERROR: invalid NUMERIC type modifier at character 30 2025-11-30 18:45:05.533 UTC client backend[44429] pg_regress/create_type STATEMENT: CREATE TEMP TABLE mytab (foo widget(42,13,7)); 2025-11-30 18:45:05.535 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.535 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE TABLE schema_not_existing.tab (id int); 2025-11-30 18:45:05.536 UTC client backend[44430] pg_regress/create_procedure ERROR: CREATE TABLE is not yet supported in unquoted SQL function body 2025-11-30 18:45:05.536 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL BEGIN ATOMIC CREATE TABLE x (a int); END; 2025-11-30 18:45:05.537 UTC client backend[44432] pg_regress/create_operator ERROR: permission denied for schema schema_op1 2025-11-30 18:45:05.537 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR schema_op1.#*# ( rightarg = int8, procedure = factorial ); 2025-11-30 18:45:05.538 UTC client backend[44429] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2025-11-30 18:45:05.538 UTC client backend[44429] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('(1,2)', 'widget'); 2025-11-30 18:45:05.538 UTC client backend[44414] pg_regress/gist ERROR: invalid page size 2025-11-30 18:45:05.538 UTC client backend[44414] pg_regress/gist DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.538 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT gist_page_items_bytea('aaa'::bytea); 2025-11-30 18:45:05.538 UTC client backend[44429] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2025-11-30 18:45:05.538 UTC client backend[44429] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('{"(1,2)"}', 'widget[]'); 2025-11-30 18:45:05.538 UTC client backend[44416] pg_regress/des ERROR: encrypt_iv error: Cipher cannot be initialized 2025-11-30 18:45:05.538 UTC client backend[44416] pg_regress/des STATEMENT: select encrypt_iv('foo', '0123456', 'abcd', 'des'); 2025-11-30 18:45:05.538 UTC client backend[44429] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2025-11-30 18:45:05.538 UTC client backend[44429] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('("(1,2)")', 'mytab'); 2025-11-30 18:45:05.541 UTC client backend[44434] pg_regress/create_table ERROR: cannot create temporary relation in non-temporary schema at character 19 2025-11-30 18:45:05.541 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TEMP TABLE public.temp_to_perm (a int primary key); 2025-11-30 18:45:05.541 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.541 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE VIEW schema_not_existing.view AS SELECT 1; 2025-11-30 18:45:05.541 UTC client backend[44416] pg_regress/des ERROR: decrypt_iv error: Cipher cannot be initialized 2025-11-30 18:45:05.541 UTC client backend[44416] pg_regress/des STATEMENT: select encode(decrypt_iv('\x50735067b073bb93', '0123456', 'abcd', 'des'), 'escape'); 2025-11-30 18:45:05.542 UTC client backend[44416] pg_regress/des ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.542 UTC client backend[44416] pg_regress/des STATEMENT: select encrypt('Lets try a longer message.', '01234567', 'des'); 2025-11-30 18:45:05.542 UTC client backend[44429] pg_regress/create_type ERROR: type "myvarchar" is only a shell 2025-11-30 18:45:05.542 UTC client backend[44429] pg_regress/create_type STATEMENT: ALTER TYPE myvarchar SET (storage = extended); 2025-11-30 18:45:05.543 UTC client backend[44429] pg_regress/create_type ERROR: cannot change type's storage to PLAIN 2025-11-30 18:45:05.543 UTC client backend[44429] pg_regress/create_type STATEMENT: ALTER TYPE myvarchar SET (storage = plain); 2025-11-30 18:45:05.544 UTC client backend[44414] pg_regress/gist ERROR: invalid page size 2025-11-30 18:45:05.544 UTC client backend[44414] pg_regress/gist DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.544 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT gist_page_items('aaa'::bytea, 'test_gist_idx'::regclass); 2025-11-30 18:45:05.544 UTC client backend[44416] pg_regress/des ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.544 UTC client backend[44416] pg_regress/des STATEMENT: select encode(decrypt(encrypt('Lets try a longer message.', '01234567', 'des'), '01234567', 'des'), 'escape'); 2025-11-30 18:45:05.545 UTC client backend[44416] pg_regress/des LOG: disconnection: session time: 0:00:00.055 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.545 UTC client backend[44414] pg_regress/gist ERROR: invalid page size 2025-11-30 18:45:05.545 UTC client backend[44414] pg_regress/gist DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.545 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT gist_page_opaque_info('aaa'::bytea); 2025-11-30 18:45:05.547 UTC client backend[44432] pg_regress/create_operator ERROR: SETOF type not allowed for operator argument 2025-11-30 18:45:05.547 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = SETOF int8, procedure = factorial ); 2025-11-30 18:45:05.548 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.548 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE INDEX ON schema_not_existing.tab (id); 2025-11-30 18:45:05.548 UTC client backend[44434] pg_regress/create_table ERROR: partitioned tables cannot be unlogged 2025-11-30 18:45:05.548 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE UNLOGGED TABLE unlogged1 (a int) PARTITION BY RANGE (a); 2025-11-30 18:45:05.548 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-11-30 18:45:05.548 UTC client backend[44433] 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-11-30 18:45:05.548 UTC client backend[44414] pg_regress/gist ERROR: input page is not a valid GiST page 2025-11-30 18:45:05.548 UTC client backend[44414] pg_regress/gist DETAIL: Expected special size 16, got 0. 2025-11-30 18:45:05.548 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT * FROM gist_page_opaque_info(get_raw_page('test_gist', 0)); 2025-11-30 18:45:05.549 UTC client backend[44434] pg_regress/create_table ERROR: ALTER action SET LOGGED cannot be performed on relation "unlogged1" 2025-11-30 18:45:05.549 UTC client backend[44434] pg_regress/create_table DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:05.549 UTC client backend[44434] pg_regress/create_table STATEMENT: ALTER TABLE unlogged1 SET LOGGED; 2025-11-30 18:45:05.549 UTC client backend[44432] pg_regress/create_operator ERROR: SETOF type not allowed for operator argument 2025-11-30 18:45:05.549 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( rightarg = SETOF int8, procedure = factorial ); 2025-11-30 18:45:05.549 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-11-30 18:45:05.549 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE SEQUENCE schema_not_existing.seq; 2025-11-30 18:45:05.549 UTC client backend[44434] pg_regress/create_table ERROR: ALTER action SET UNLOGGED cannot be performed on relation "unlogged1" 2025-11-30 18:45:05.549 UTC client backend[44434] pg_regress/create_table DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:05.549 UTC client backend[44434] pg_regress/create_table STATEMENT: ALTER TABLE unlogged1 SET UNLOGGED; 2025-11-30 18:45:05.550 UTC client backend[44429] pg_regress/create_type ERROR: cannot drop function myvarcharsend(myvarchar) because other objects depend on it 2025-11-30 18:45:05.550 UTC client backend[44429] 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-11-30 18:45:05.550 UTC client backend[44429] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.550 UTC client backend[44429] pg_regress/create_type STATEMENT: DROP FUNCTION myvarcharsend(myvarchar); 2025-11-30 18:45:05.550 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-11-30 18:45:05.550 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE TABLE schema_not_existing.tab (id int); 2025-11-30 18:45:05.550 UTC client backend[44430] pg_regress/create_procedure ERROR: calling procedures with output arguments is not supported in SQL functions 2025-11-30 18:45:05.550 UTC client backend[44430] pg_regress/create_procedure CONTEXT: SQL function "ptest4b" 2025-11-30 18:45:05.550 UTC client backend[44430] 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-11-30 18:45:05.550 UTC client backend[44429] pg_regress/create_type ERROR: cannot drop type myvarchar because other objects depend on it 2025-11-30 18:45:05.550 UTC client backend[44429] 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-11-30 18:45:05.550 UTC client backend[44429] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.550 UTC client backend[44429] pg_regress/create_type STATEMENT: DROP TYPE myvarchar; 2025-11-30 18:45:05.551 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-11-30 18:45:05.551 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE VIEW schema_not_existing.view AS SELECT 1; 2025-11-30 18:45:05.552 UTC client backend[44429] pg_regress/create_type LOG: disconnection: session time: 0:00:00.043 user=postgres database=regression host=[local] 2025-11-30 18:45:05.553 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "invalid_att" not recognized 2025-11-30 18:45:05.554 UTC client backend[44414] pg_regress/gist ERROR: input page is not a valid GiST page 2025-11-30 18:45:05.554 UTC client backend[44414] pg_regress/gist DETAIL: Expected special size 16, got 0. 2025-11-30 18:45:05.554 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT gist_page_items_bytea(get_raw_page('test_gist', 0)); 2025-11-30 18:45:05.554 UTC client backend[44414] pg_regress/gist ERROR: input page is not a valid GiST page 2025-11-30 18:45:05.554 UTC client backend[44414] pg_regress/gist DETAIL: Expected 0000ff81, got 00000000. 2025-11-30 18:45:05.554 UTC client backend[44414] pg_regress/gist STATEMENT: SELECT gist_page_items_bytea(get_raw_page('test_gist_btree', 0)); 2025-11-30 18:45:05.554 UTC client backend[44434] pg_regress/create_table ERROR: relation "as_select1" already exists 2025-11-30 18:45:05.554 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE as_select1 AS SELECT * FROM pg_class WHERE relkind = 'r'; 2025-11-30 18:45:05.554 UTC client backend[44432] pg_regress/create_operator ERROR: operator argument types must be specified 2025-11-30 18:45:05.554 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #@%# ( procedure = factorial ); 2025-11-30 18:45:05.554 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-11-30 18:45:05.554 UTC client backend[44433] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE INDEX ON schema_not_existing.tab (id); 2025-11-30 18:45:05.555 UTC client backend[44433] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-11-30 18:45:05.555 UTC client backend[44433] 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-11-30 18:45:05.555 UTC client backend[44432] pg_regress/create_operator ERROR: operator function must be specified 2025-11-30 18:45:05.555 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #@%# ( rightarg = int8 ); 2025-11-30 18:45:05.559 UTC client backend[44414] pg_regress/gist LOG: disconnection: session time: 0:00:00.075 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.560 UTC client backend[44432] pg_regress/create_operator ERROR: permission denied for type type_op3 2025-11-30 18:45:05.560 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = type_op3, rightarg = int8, procedure = fn_op3 ); 2025-11-30 18:45:05.563 UTC client backend[44432] pg_regress/create_operator ERROR: permission denied for type type_op4 2025-11-30 18:45:05.563 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = type_op4, procedure = fn_op4 ); 2025-11-30 18:45:05.564 UTC client backend[44432] pg_regress/create_operator ERROR: permission denied for function fn_op5 2025-11-30 18:45:05.564 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = int8, procedure = fn_op5 ); 2025-11-30 18:45:05.565 UTC client backend[44432] pg_regress/create_operator ERROR: permission denied for type type_op6 2025-11-30 18:45:05.565 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = int8, procedure = fn_op6 ); 2025-11-30 18:45:05.566 UTC client backend[44432] pg_regress/create_operator ERROR: operator cannot be its own negator 2025-11-30 18:45:05.566 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, negator = === ); 2025-11-30 18:45:05.566 UTC client backend[44432] pg_regress/create_operator ERROR: operator cannot be its own negator 2025-11-30 18:45:05.566 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR ===!!! ( leftarg = integer, rightarg = integer, procedure = int4ne, negator = ===!!! ); 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator ERROR: commutator operator = is already the commutator of operator = 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, commutator = = ); 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator ERROR: negator operator <> is already the negator of operator = 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, negator = <> ); 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Leftarg" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Rightarg" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Procedure" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Commutator" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Negator" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Restrict" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Join" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Hashes" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator WARNING: operator attribute "Merges" not recognized 2025-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator ERROR: operator function must be specified 2025-11-30 18:45:05.567 UTC client backend[44432] 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-11-30 18:45:05.567 UTC client backend[44432] pg_regress/create_operator LOG: disconnection: session time: 0:00:00.062 user=postgres database=regression host=[local] 2025-11-30 18:45:05.569 UTC client backend[44430] pg_regress/create_procedure ERROR: procedure ptest9(numeric) does not exist at character 6 2025-11-30 18:45:05.569 UTC client backend[44430] pg_regress/create_procedure DETAIL: No procedure of that name accepts the given argument types. 2025-11-30 18:45:05.569 UTC client backend[44430] pg_regress/create_procedure HINT: You might need to add explicit type casts. 2025-11-30 18:45:05.569 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CALL ptest9(1./0.); 2025-11-30 18:45:05.571 UTC client backend[44434] pg_regress/create_table ERROR: relation "as_select1" already exists 2025-11-30 18:45:05.571 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE as_select1 AS EXECUTE select1; 2025-11-30 18:45:05.574 UTC client backend[44430] pg_regress/create_procedure ERROR: procedure name "ptest10" is not unique 2025-11-30 18:45:05.574 UTC client backend[44430] pg_regress/create_procedure HINT: Specify the argument list to select the procedure unambiguously. 2025-11-30 18:45:05.574 UTC client backend[44430] pg_regress/create_procedure STATEMENT: drop procedure ptest10; 2025-11-30 18:45:05.574 UTC client backend[44430] pg_regress/create_procedure ERROR: procedure name "ptest10" is not unique 2025-11-30 18:45:05.574 UTC client backend[44430] pg_regress/create_procedure STATEMENT: drop procedure ptest10(int, int, int); 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: version() is not a procedure at character 6 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure HINT: To call a function, use SELECT. 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CALL version(); 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: sum(integer) is not a procedure at character 6 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure HINT: To call a function, use SELECT. 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CALL sum(1); 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 40 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL WINDOW AS $$ INSERT INTO cp_test VALUES (1, 'a') $$; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 40 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL STRICT AS $$ INSERT INTO cp_test VALUES (1, 'a') $$; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: VARIADIC parameter must be the last parameter at character 43 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx(a VARIADIC int[], b OUT int) LANGUAGE SQL AS $$ SELECT a[1] $$; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: procedure OUT parameters cannot appear after one with a default value at character 43 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx(a int DEFAULT 42, b OUT int) LANGUAGE SQL AS $$ SELECT a $$; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 30 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE ptest1(text) STRICT; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: ptest1(text) is not a function 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: ALTER FUNCTION ptest1(text) VOLATILE; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: cp_testfunc1(integer) is not a procedure 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE cp_testfunc1(int) VOLATILE; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE nonexistent() VOLATILE; 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: ptest1(text) is not a function 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: DROP FUNCTION ptest1(text); 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: cp_testfunc1(integer) is not a procedure 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: DROP PROCEDURE cp_testfunc1(int); 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist 2025-11-30 18:45:05.580 UTC client backend[44430] pg_regress/create_procedure STATEMENT: DROP PROCEDURE nonexistent(); 2025-11-30 18:45:05.581 UTC client backend[44430] pg_regress/create_procedure ERROR: permission denied for procedure ptest1 2025-11-30 18:45:05.581 UTC client backend[44430] pg_regress/create_procedure STATEMENT: CALL ptest1('a'); 2025-11-30 18:45:05.585 UTC client backend[44430] pg_regress/create_procedure LOG: disconnection: session time: 0:00:00.083 user=postgres database=regression host=[local] 2025-11-30 18:45:05.611 UTC client backend[44433] pg_regress/create_schema LOG: disconnection: session time: 0:00:00.100 user=postgres database=regression host=[local] 2025-11-30 18:45:05.613 UTC unrecognized[44445] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.614 UTC client backend[44445] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.614 UTC client backend[44445] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.615 UTC client backend[44445] pg_regress LOG: connection ready: setup total=1.857 ms, fork=0.435 ms, authentication=0.131 ms 2025-11-30 18:45:05.616 UTC client backend[44445] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.620 UTC unrecognized[44441] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.621 UTC client backend[44441] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.621 UTC client backend[44441] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/3des 2025-11-30 18:45:05.622 UTC client backend[44441] pg_regress/3des LOG: connection ready: setup total=23.118 ms, fork=20.329 ms, authentication=1.051 ms 2025-11-30 18:45:05.624 UTC unrecognized[44448] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.624 UTC client backend[44448] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.624 UTC client backend[44448] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.624 UTC client backend[44441] pg_regress/3des LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.625 UTC client backend[44448] pg_regress LOG: connection ready: setup total=1.927 ms, fork=0.692 ms, authentication=0.110 ms 2025-11-30 18:45:05.635 UTC unrecognized[44452] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.639 UTC client backend[44448] pg_regress LOG: disconnection: session time: 0:00:00.015 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.641 UTC unrecognized[44451] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.642 UTC client backend[44452] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.642 UTC client backend[44452] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/cast5 2025-11-30 18:45:05.642 UTC client backend[44451] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.642 UTC client backend[44451] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/hash 2025-11-30 18:45:05.643 UTC client backend[44452] pg_regress/cast5 LOG: connection ready: setup total=8.702 ms, fork=0.297 ms, authentication=7.006 ms 2025-11-30 18:45:05.643 UTC client backend[44434] pg_regress/create_table ERROR: syntax error at or near "OIDS" at character 29 2025-11-30 18:45:05.643 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH OIDS; 2025-11-30 18:45:05.643 UTC client backend[44434] pg_regress/create_table ERROR: tables declared WITH OIDS are not supported 2025-11-30 18:45:05.643 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH (oids); 2025-11-30 18:45:05.643 UTC client backend[44434] pg_regress/create_table ERROR: tables declared WITH OIDS are not supported 2025-11-30 18:45:05.643 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH (oids = true); 2025-11-30 18:45:05.643 UTC client backend[44451] pg_regress/hash LOG: connection ready: setup total=9.634 ms, fork=4.016 ms, authentication=0.106 ms 2025-11-30 18:45:05.644 UTC client backend[44428] pg_regress/create_misc LOG: disconnection: session time: 0:00:00.145 user=postgres database=regression host=[local] 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 STATEMENT: SELECT encrypt('\x0123456789ABCDEF', '\x0123456712345678234567893456789A', 'cast5-ecb/pad:none'); 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 STATEMENT: SELECT encrypt('\x0123456789ABCDEF', '\x01234567123456782345', 'cast5-ecb/pad:none'); 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 STATEMENT: SELECT encrypt('\x0123456789ABCDEF', '\x0123456712', 'cast5-ecb/pad:none'); 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 STATEMENT: select encrypt('', 'foo', 'cast5'); 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.646 UTC client backend[44452] pg_regress/cast5 STATEMENT: select encrypt('foo', '0123456789', 'cast5'); 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 STATEMENT: select encode(decrypt(encrypt('foo', '0123456', 'cast5'), '0123456', 'cast5'), 'escape'); 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt_iv error: Cipher cannot be initialized 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 STATEMENT: select encrypt_iv('foo', '0123456', 'abcd', 'cast5'); 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 ERROR: decrypt_iv error: Cipher cannot be initialized 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 STATEMENT: select encode(decrypt_iv('\x384a970695ce016a', '0123456', 'abcd', 'cast5'), 'escape'); 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 STATEMENT: select encrypt('Lets try a longer message.', '0123456789', 'cast5'); 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 ERROR: encrypt error: Cipher cannot be initialized 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 STATEMENT: select encode(decrypt(encrypt('Lets try a longer message.', '0123456789', 'cast5'), '0123456789', 'cast5'), 'escape'); 2025-11-30 18:45:05.647 UTC client backend[44452] pg_regress/cast5 LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: block number 6 is out of range for relation "test_hash_a_idx" 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_type(get_raw_page('test_hash_a_idx', 6)); 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: invalid block number 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', -1); 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: invalid overflow block number 0 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', 0); 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: invalid overflow block number 1 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', 1); 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: invalid overflow block number 2 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', 2); 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: invalid overflow block number 3 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', 3); 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: invalid overflow block number 4 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', 4); 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash ERROR: invalid overflow block number 5 2025-11-30 18:45:05.651 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', 5); 2025-11-30 18:45:05.652 UTC client backend[44451] pg_regress/hash ERROR: block number 6 is out of range for relation "test_hash_a_idx" 2025-11-30 18:45:05.652 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_a_idx', 6); 2025-11-30 18:45:05.652 UTC client backend[44451] pg_regress/hash ERROR: "test_hash_part_idx" is not a hash index 2025-11-30 18:45:05.652 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_bitmap_info('test_hash_part_idx', 1); 2025-11-30 18:45:05.652 UTC client backend[44177] pg_regress/check_gin LOG: disconnection: session time: 0:00:01.965 user=postgres database=regression_amcheck host=[local] 2025-11-30 18:45:05.653 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash meta page 2025-11-30 18:45:05.653 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT magic, version, ntuples, bsize, bmsize, bmshift, maxbucket, highmask, lowmask, ovflpoint, firstfree, nmaps, procid, spares, mapp FROM hash_metapage_info(get_raw_page('test_hash_a_idx', 1)); 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash meta page 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT magic, version, ntuples, bsize, bmsize, bmshift, maxbucket, highmask, lowmask, ovflpoint, firstfree, nmaps, procid, spares, mapp FROM hash_metapage_info(get_raw_page('test_hash_a_idx', 2)); 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash meta page 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT magic, version, ntuples, bsize, bmsize, bmshift, maxbucket, highmask, lowmask, ovflpoint, firstfree, nmaps, procid, spares, mapp FROM hash_metapage_info(get_raw_page('test_hash_a_idx', 3)); 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash meta page 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT magic, version, ntuples, bsize, bmsize, bmshift, maxbucket, highmask, lowmask, ovflpoint, firstfree, nmaps, procid, spares, mapp FROM hash_metapage_info(get_raw_page('test_hash_a_idx', 4)); 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash meta page 2025-11-30 18:45:05.654 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT magic, version, ntuples, bsize, bmsize, bmshift, maxbucket, highmask, lowmask, ovflpoint, firstfree, nmaps, procid, spares, mapp FROM hash_metapage_info(get_raw_page('test_hash_a_idx', 5)); 2025-11-30 18:45:05.655 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash bucket or overflow page 2025-11-30 18:45:05.655 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT live_items, dead_items, page_size, hasho_prevblkno, hasho_nextblkno, hasho_bucket, hasho_flag, hasho_page_id FROM hash_page_stats(get_raw_page('test_hash_a_idx', 0)); 2025-11-30 18:45:05.655 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash bucket or overflow page 2025-11-30 18:45:05.655 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT live_items, dead_items, page_size, hasho_prevblkno, hasho_nextblkno, hasho_bucket, hasho_flag, hasho_page_id FROM hash_page_stats(get_raw_page('test_hash_a_idx', 5)); 2025-11-30 18:45:05.655 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash bucket or overflow page 2025-11-30 18:45:05.655 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_page_items(get_raw_page('test_hash_a_idx', 0)); 2025-11-30 18:45:05.656 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash bucket or overflow page 2025-11-30 18:45:05.656 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT * FROM hash_page_items(get_raw_page('test_hash_a_idx', 5)); 2025-11-30 18:45:05.656 UTC unrecognized[44460] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.657 UTC client backend[44460] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.657 UTC client backend[44460] [unknown] LOG: connection authorized: user=postgres database=regression_amcheck application_name=pg_regress/check_heap 2025-11-30 18:45:05.657 UTC unrecognized[44454] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.658 UTC client backend[44460] pg_regress/check_heap LOG: connection ready: setup total=1.996 ms, fork=0.415 ms, authentication=0.117 ms 2025-11-30 18:45:05.658 UTC client backend[44454] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.658 UTC client backend[44454] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_pgrowlocks application_name=pg_regress 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: "test_hash_a_btree" is not a hash index 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_bitmap_info('test_hash_a_btree', 0); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: invalid page size 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_metapage_info('aaa'::bytea); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: invalid page size 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_items('bbb'::bytea); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: invalid page size 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_stats('ccc'::bytea); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: invalid page size 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected 8192 bytes, got 3. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_type('ddd'::bytea); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: input page is not a valid hash page 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected special size 16, got 0. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_metapage_info(get_raw_page('test_hash', 0)); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: input page is not a valid hash page 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected special size 16, got 0. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_items(get_raw_page('test_hash', 0)); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: input page is not a valid hash page 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected special size 16, got 0. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_stats(get_raw_page('test_hash', 0)); 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash ERROR: input page is not a valid hash page 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash DETAIL: Expected special size 16, got 0. 2025-11-30 18:45:05.661 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_type(get_raw_page('test_hash', 0)); 2025-11-30 18:45:05.662 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash meta page 2025-11-30 18:45:05.662 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_metapage_info(decode(repeat('00', 8192), 'hex')); 2025-11-30 18:45:05.662 UTC unrecognized[44462] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.662 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash bucket or overflow page 2025-11-30 18:45:05.662 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_items(decode(repeat('00', 8192), 'hex')); 2025-11-30 18:45:05.662 UTC client backend[44454] pg_regress LOG: connection ready: setup total=15.498 ms, fork=10.501 ms, authentication=0.113 ms 2025-11-30 18:45:05.663 UTC client backend[44462] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.663 UTC client backend[44462] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/crypt-des 2025-11-30 18:45:05.663 UTC client backend[44462] pg_regress/crypt-des LOG: connection ready: setup total=2.070 ms, fork=0.657 ms, authentication=0.113 ms 2025-11-30 18:45:05.664 UTC client backend[44451] pg_regress/hash ERROR: page is not a hash bucket or overflow page 2025-11-30 18:45:05.664 UTC client backend[44451] pg_regress/hash STATEMENT: SELECT hash_page_stats(decode(repeat('00', 8192), 'hex')); 2025-11-30 18:45:05.664 UTC client backend[44460] pg_regress/check_heap ERROR: invalid skip option 2025-11-30 18:45:05.664 UTC client backend[44460] pg_regress/check_heap HINT: Valid skip options are "all-visible", "all-frozen", and "none". 2025-11-30 18:45:05.664 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam(relation := 'heaptest', skip := 'rope'); 2025-11-30 18:45:05.665 UTC client backend[44454] pg_regress LOG: disconnection: session time: 0:00:00.007 user=postgres database=isolation_regression_pgrowlocks host=[local] 2025-11-30 18:45:05.665 UTC client backend[44462] pg_regress/crypt-des ERROR: invalid salt 2025-11-30 18:45:05.665 UTC client backend[44462] pg_regress/crypt-des STATEMENT: SELECT crypt('password', 'a'); 2025-11-30 18:45:05.669 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 51 2025-11-30 18:45:05.669 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_column (id int DEFAULT (id)); 2025-11-30 18:45:05.670 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 51 2025-11-30 18:45:05.670 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_column (id int DEFAULT (bar.id)); 2025-11-30 18:45:05.670 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 59 2025-11-30 18:45:05.670 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg_column (id int DEFAULT (avg(id))); 2025-11-30 18:45:05.670 UTC client backend[44460] pg_regress/check_heap ERROR: permission denied for function verify_heapam 2025-11-30 18:45:05.670 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam(relation := 'heaptest'); 2025-11-30 18:45:05.671 UTC client backend[44451] pg_regress/hash LOG: disconnection: session time: 0:00:00.033 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.671 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 58 2025-11-30 18:45:05.671 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_non_column (a int DEFAULT (avg(non_existent))); 2025-11-30 18:45:05.671 UTC client backend[44460] pg_regress/check_heap ERROR: ending block number must be between 0 and 0 2025-11-30 18:45:05.671 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam(relation := 'heaptest', startblock := 0, endblock := 10000); 2025-11-30 18:45:05.671 UTC client backend[44460] pg_regress/check_heap ERROR: starting block number must be between 0 and 0 2025-11-30 18:45:05.671 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam(relation := 'heaptest', startblock := 10000, endblock := 11000); 2025-11-30 18:45:05.672 UTC client backend[44434] pg_regress/create_table ERROR: aggregate functions are not allowed in DEFAULT expressions at character 47 2025-11-30 18:45:05.672 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (avg(1))); 2025-11-30 18:45:05.672 UTC client backend[44434] pg_regress/create_table ERROR: cannot use subquery in DEFAULT expression at character 46 2025-11-30 18:45:05.672 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (select 1)); 2025-11-30 18:45:05.673 UTC client backend[44434] pg_regress/create_table ERROR: set-returning functions are not allowed in DEFAULT expressions at character 47 2025-11-30 18:45:05.673 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (generate_series(1,3))); 2025-11-30 18:45:05.675 UTC unrecognized[44466] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.675 UTC client backend[44466] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.675 UTC client backend[44466] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.675 UTC client backend[44460] pg_regress/check_heap ERROR: cannot check relation "test_partitioned" 2025-11-30 18:45:05.675 UTC client backend[44460] pg_regress/check_heap DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:05.675 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam('test_partitioned', startblock := NULL, endblock := NULL); 2025-11-30 18:45:05.677 UTC client backend[44466] pg_regress LOG: connection ready: setup total=4.454 ms, fork=2.226 ms, authentication=0.134 ms 2025-11-30 18:45:05.678 UTC client backend[44466] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.680 UTC unrecognized[44470] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.680 UTC client backend[44470] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.680 UTC client backend[44470] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_pgrowlocks application_name=isolation/pgrowlocks 2025-11-30 18:45:05.681 UTC client backend[44462] pg_regress/crypt-des ERROR: use of built-in crypto functions is disabled 2025-11-30 18:45:05.681 UTC client backend[44462] pg_regress/crypt-des STATEMENT: UPDATE ctest SET salt = gen_salt('des'); 2025-11-30 18:45:05.681 UTC client backend[44462] pg_regress/crypt-des ERROR: use of built-in crypto functions is disabled 2025-11-30 18:45:05.681 UTC client backend[44462] pg_regress/crypt-des STATEMENT: UPDATE ctest SET res = crypt(data, salt); 2025-11-30 18:45:05.681 UTC client backend[44470] isolation/pgrowlocks LOG: connection ready: setup total=2.424 ms, fork=0.399 ms, authentication=0.114 ms 2025-11-30 18:45:05.683 UTC client backend[44462] pg_regress/crypt-des LOG: disconnection: session time: 0:00:00.021 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.684 UTC client backend[44434] pg_regress/create_table ERROR: cannot create partitioned table as inheritance child 2025-11-30 18:45:05.684 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) INHERITS (some_table) PARTITION BY LIST (a); 2025-11-30 18:45:05.684 UTC unrecognized[44472] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.685 UTC client backend[44472] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.685 UTC client backend[44472] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.685 UTC client backend[44434] pg_regress/create_table ERROR: cannot use "list" partition strategy with more than one column 2025-11-30 18:45:05.685 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a1 int, a2 int ) PARTITION BY LIST (a1, a2); 2025-11-30 18:45:05.685 UTC client backend[44472] pg_regress LOG: connection ready: setup total=1.502 ms, fork=0.312 ms, authentication=0.104 ms 2025-11-30 18:45:05.686 UTC client backend[44434] pg_regress/create_table ERROR: set-returning functions are not allowed in partition key expressions 2025-11-30 18:45:05.686 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (retset(a)); 2025-11-30 18:45:05.686 UTC unrecognized[44471] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.686 UTC client backend[44471] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.686 UTC client backend[44471] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_pgrowlocks application_name=isolation/pgrowlocks 2025-11-30 18:45:05.686 UTC client backend[44434] pg_regress/create_table ERROR: aggregate functions are not allowed in partition key expressions 2025-11-30 18:45:05.686 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE ((avg(a))); 2025-11-30 18:45:05.687 UTC client backend[44434] pg_regress/create_table ERROR: window functions are not allowed in partition key expressions 2025-11-30 18:45:05.687 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE ((avg(a) OVER (PARTITION BY b))); 2025-11-30 18:45:05.687 UTC client backend[44471] isolation/pgrowlocks LOG: connection ready: setup total=3.812 ms, fork=2.491 ms, authentication=0.101 ms 2025-11-30 18:45:05.688 UTC client backend[44434] pg_regress/create_table ERROR: cannot use subquery in partition key expression 2025-11-30 18:45:05.688 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY LIST ((a LIKE (SELECT 1))); 2025-11-30 18:45:05.688 UTC client backend[44434] pg_regress/create_table ERROR: cannot use constant expression as partition key 2025-11-30 18:45:05.688 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE ((42)); 2025-11-30 18:45:05.689 UTC client backend[44434] pg_regress/create_table ERROR: cannot use constant expression as partition key 2025-11-30 18:45:05.689 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (const_func()); 2025-11-30 18:45:05.690 UTC client backend[44434] pg_regress/create_table ERROR: unrecognized partitioning strategy "magic" at character 53 2025-11-30 18:45:05.690 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY MAGIC (a); 2025-11-30 18:45:05.690 UTC client backend[44434] pg_regress/create_table ERROR: column "b" named in partition key does not exist at character 57 2025-11-30 18:45:05.690 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (b); 2025-11-30 18:45:05.691 UTC client backend[44434] pg_regress/create_table ERROR: cannot use system column "xmin" in partition key at character 57 2025-11-30 18:45:05.691 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (xmin); 2025-11-30 18:45:05.691 UTC client backend[44434] pg_regress/create_table ERROR: partition key column 1 has pseudo-type record 2025-11-30 18:45:05.691 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE (((a, b))); 2025-11-30 18:45:05.692 UTC client backend[44434] pg_regress/create_table ERROR: partition key column 2 has pseudo-type unknown 2025-11-30 18:45:05.692 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE (a, ('unknown')); 2025-11-30 18:45:05.693 UTC client backend[44434] pg_regress/create_table ERROR: functions in partition key expression must be marked IMMUTABLE 2025-11-30 18:45:05.693 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (immut_func(a)); 2025-11-30 18:45:05.695 UTC unrecognized[44474] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.695 UTC client backend[44434] pg_regress/create_table ERROR: data type point has no default operator class for access method "btree" 2025-11-30 18:45:05.695 UTC client backend[44434] pg_regress/create_table HINT: You must specify a btree operator class or define a default btree operator class for the data type. 2025-11-30 18:45:05.695 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY LIST (a); 2025-11-30 18:45:05.695 UTC client backend[44474] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.695 UTC client backend[44474] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_pgrowlocks application_name=isolation/pgrowlocks 2025-11-30 18:45:05.695 UTC client backend[44434] pg_regress/create_table ERROR: operator class "point_ops" does not exist for access method "btree" 2025-11-30 18:45:05.695 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY LIST (a point_ops); 2025-11-30 18:45:05.696 UTC client backend[44474] isolation/pgrowlocks LOG: connection ready: setup total=7.723 ms, fork=6.234 ms, authentication=0.114 ms 2025-11-30 18:45:05.696 UTC unrecognized[44475] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.696 UTC client backend[44434] pg_regress/create_table ERROR: data type point has no default operator class for access method "btree" 2025-11-30 18:45:05.696 UTC client backend[44434] pg_regress/create_table HINT: You must specify a btree operator class or define a default btree operator class for the data type. 2025-11-30 18:45:05.696 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY RANGE (a); 2025-11-30 18:45:05.696 UTC client backend[44475] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.696 UTC client backend[44475] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/checksum 2025-11-30 18:45:05.697 UTC client backend[44434] pg_regress/create_table ERROR: operator class "point_ops" does not exist for access method "btree" 2025-11-30 18:45:05.697 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY RANGE (a point_ops); 2025-11-30 18:45:05.697 UTC client backend[44434] pg_regress/create_table ERROR: cannot add NO INHERIT constraint to partitioned table "partitioned" 2025-11-30 18:45:05.697 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, CONSTRAINT check_a CHECK (a > 0) NO INHERIT ) PARTITION BY RANGE (a); 2025-11-30 18:45:05.699 UTC client backend[44475] pg_regress/checksum LOG: connection ready: setup total=9.754 ms, fork=5.270 ms, authentication=0.111 ms 2025-11-30 18:45:05.701 UTC client backend[44475] pg_regress/checksum LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.701 UTC client backend[44434] pg_regress/create_table ERROR: cannot drop function plusone(integer) because other objects depend on it 2025-11-30 18:45:05.701 UTC client backend[44434] pg_regress/create_table DETAIL: table partitioned depends on function plusone(integer) 2025-11-30 18:45:05.701 UTC client backend[44434] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.701 UTC client backend[44434] pg_regress/create_table STATEMENT: DROP FUNCTION plusone(int); 2025-11-30 18:45:05.702 UTC client backend[44434] pg_regress/create_table ERROR: cannot inherit from partitioned table "partitioned2" 2025-11-30 18:45:05.702 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail () INHERITS (partitioned2); 2025-11-30 18:45:05.706 UTC client backend[44460] pg_regress/check_heap ERROR: cannot check relation "test_index" 2025-11-30 18:45:05.706 UTC client backend[44460] pg_regress/check_heap DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:05.706 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam('test_index', startblock := NULL, endblock := NULL); 2025-11-30 18:45:05.707 UTC client backend[44460] pg_regress/check_heap ERROR: cannot check relation "test_view" 2025-11-30 18:45:05.707 UTC client backend[44460] pg_regress/check_heap DETAIL: This operation is not supported for views. 2025-11-30 18:45:05.707 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam('test_view', startblock := NULL, endblock := NULL); 2025-11-30 18:45:05.710 UTC unrecognized[44478] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.710 UTC client backend[44472] pg_regress LOG: disconnection: session time: 0:00:00.026 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.710 UTC client backend[44478] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.710 UTC client backend[44478] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/crypt-md5 2025-11-30 18:45:05.711 UTC client backend[44478] pg_regress/crypt-md5 LOG: connection ready: setup total=1.959 ms, fork=0.464 ms, authentication=0.118 ms 2025-11-30 18:45:05.713 UTC client backend[44460] pg_regress/check_heap ERROR: cannot check relation "test_foreign_table" 2025-11-30 18:45:05.713 UTC client backend[44460] pg_regress/check_heap DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:05.713 UTC client backend[44460] pg_regress/check_heap STATEMENT: SELECT * FROM verify_heapam('test_foreign_table', startblock := NULL, endblock := NULL); 2025-11-30 18:45:05.715 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:05.720 UTC client backend[44478] pg_regress/crypt-md5 LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.731 UTC client backend[44434] pg_regress/create_table ERROR: no partition of relation "partitioned2" found for row 2025-11-30 18:45:05.731 UTC client backend[44434] pg_regress/create_table DETAIL: Partition key of the failing row contains ((a + 1), substr(b, 1, 5)) = (2, hello). 2025-11-30 18:45:05.731 UTC client backend[44434] pg_regress/create_table STATEMENT: INSERT INTO partitioned2 VALUES (1, 'hello'); 2025-11-30 18:45:05.731 UTC unrecognized[44484] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.732 UTC client backend[44484] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.732 UTC client backend[44484] [unknown] LOG: connection authorized: user=postgres database=regression_pgstattuple application_name=pg_regress/pgstattuple 2025-11-30 18:45:05.733 UTC unrecognized[44482] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.733 UTC client backend[44482] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.733 UTC client backend[44482] [unknown] LOG: connection authorized: user=postgres database=regression_pageinspect application_name=pg_regress/oldextversions 2025-11-30 18:45:05.734 UTC client backend[44482] pg_regress/oldextversions LOG: connection ready: setup total=6.891 ms, fork=5.416 ms, authentication=0.113 ms 2025-11-30 18:45:05.738 UTC client backend[44484] pg_regress/pgstattuple LOG: connection ready: setup total=7.185 ms, fork=0.647 ms, authentication=0.127 ms 2025-11-30 18:45:05.738 UTC unrecognized[44485] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.738 UTC client backend[44485] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.738 UTC client backend[44485] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/crypt-blowfish 2025-11-30 18:45:05.739 UTC client backend[44485] pg_regress/crypt-blowfish LOG: connection ready: setup total=8.422 ms, fork=0.366 ms, authentication=0.133 ms 2025-11-30 18:45:05.746 UTC checkpointer[43405] LOG: checkpoint complete: wrote 9751 buffers (59.5%), wrote 2 SLRU buffers; 0 WAL file(s) added, 0 removed, 11 recycled; write=0.029 s, sync=0.001 s, total=0.032 s; sync files=0, longest=0.000 s, average=0.000 s; distance=186393 kB, estimate=186393 kB; lsn=0/189AFEB8, redo lsn=0/188A74C0 2025-11-30 18:45:05.757 UTC client backend[44485] pg_regress/crypt-blowfish ERROR: invalid salt 2025-11-30 18:45:05.757 UTC client backend[44485] pg_regress/crypt-blowfish STATEMENT: SELECT crypt('foox', '$2a$'); 2025-11-30 18:45:05.760 UTC client backend[44485] pg_regress/crypt-blowfish ERROR: invalid salt 2025-11-30 18:45:05.760 UTC client backend[44485] pg_regress/crypt-blowfish STATEMENT: SELECT crypt('foox', '$2a$40$RQiOJ.3ELirrXwxIZY8q0O'); 2025-11-30 18:45:05.761 UTC client backend[44485] pg_regress/crypt-blowfish ERROR: invalid salt 2025-11-30 18:45:05.761 UTC client backend[44485] pg_regress/crypt-blowfish STATEMENT: SELECT crypt('foox', '$2a$00$RQiOJ.3ELirrXwxIZY8q0O'); 2025-11-30 18:45:05.764 UTC client backend[44460] pg_regress/check_heap LOG: disconnection: session time: 0:00:00.108 user=postgres database=regression_amcheck host=[local] 2025-11-30 18:45:05.772 UTC client backend[44482] pg_regress/oldextversions ERROR: function has wrong number of declared columns 2025-11-30 18:45:05.772 UTC client backend[44482] pg_regress/oldextversions HINT: To resolve the problem, update the "pageinspect" extension to the latest version. 2025-11-30 18:45:05.772 UTC client backend[44482] pg_regress/oldextversions STATEMENT: SELECT * FROM brin_page_items(get_raw_page('test_1_a_brin_idx', 2), 'test_1_a_brin_idx'); 2025-11-30 18:45:05.777 UTC client backend[44434] pg_regress/create_table ERROR: cannot drop column "a" because it is part of the partition key of relation "partitioned" 2025-11-30 18:45:05.777 UTC client backend[44434] pg_regress/create_table STATEMENT: alter table partitioned drop column a; 2025-11-30 18:45:05.777 UTC client backend[44434] pg_regress/create_table ERROR: cannot drop type intdom1 because other objects depend on it 2025-11-30 18:45:05.777 UTC client backend[44434] pg_regress/create_table DETAIL: table partitioned depends on type intdom1 2025-11-30 18:45:05.777 UTC client backend[44434] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.777 UTC client backend[44434] pg_regress/create_table STATEMENT: drop domain intdom1; 2025-11-30 18:45:05.778 UTC client backend[44434] pg_regress/create_table ERROR: relation "partitioned" does not exist at character 7 2025-11-30 18:45:05.778 UTC client backend[44434] pg_regress/create_table STATEMENT: table partitioned; 2025-11-30 18:45:05.780 UTC client backend[44434] pg_regress/create_table ERROR: cannot drop column "a" because it is part of the partition key of relation "partitioned" 2025-11-30 18:45:05.780 UTC client backend[44434] pg_regress/create_table STATEMENT: alter table partitioned drop column a; 2025-11-30 18:45:05.780 UTC client backend[44434] pg_regress/create_table ERROR: cannot drop type intdom1 because other objects depend on it 2025-11-30 18:45:05.780 UTC client backend[44434] pg_regress/create_table DETAIL: table partitioned depends on type intdom1 2025-11-30 18:45:05.780 UTC client backend[44434] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:05.780 UTC client backend[44434] pg_regress/create_table STATEMENT: drop domain intdom1; 2025-11-30 18:45:05.781 UTC client backend[44434] pg_regress/create_table ERROR: relation "partitioned" does not exist at character 7 2025-11-30 18:45:05.781 UTC client backend[44434] pg_regress/create_table STATEMENT: table partitioned; 2025-11-30 18:45:05.782 UTC client backend[44482] pg_regress/oldextversions LOG: disconnection: session time: 0:00:00.049 user=postgres database=regression_pageinspect host=[local] 2025-11-30 18:45:05.804 UTC client backend[44485] pg_regress/crypt-blowfish LOG: disconnection: session time: 0:00:00.072 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.808 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2025-11-30 18:45:05.808 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename); 2025-11-30 18:45:05.809 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2025-11-30 18:45:05.809 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename.somename); 2025-11-30 18:45:05.809 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_pkey" is not a GIN index 2025-11-30 18:45:05.809 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatginindex('test_pkey'); 2025-11-30 18:45:05.810 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2025-11-30 18:45:05.810 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (a); 2025-11-30 18:45:05.810 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 79 2025-11-30 18:45:05.810 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(a)); 2025-11-30 18:45:05.810 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_pkey" is not a hash index 2025-11-30 18:45:05.810 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_pkey'); 2025-11-30 18:45:05.811 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 79 2025-11-30 18:45:05.811 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(somename)); 2025-11-30 18:45:05.811 UTC client backend[44470] isolation/pgrowlocks/control connection LOG: disconnection: session time: 0:00:00.132 user=postgres database=isolation_regression_pgrowlocks host=[local] 2025-11-30 18:45:05.812 UTC client backend[44434] pg_regress/create_table ERROR: aggregate functions are not allowed in partition bound at character 75 2025-11-30 18:45:05.812 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(1)); 2025-11-30 18:45:05.812 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_ginidx" is not a btree index 2025-11-30 18:45:05.812 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatindex('test_ginidx'); 2025-11-30 18:45:05.812 UTC client backend[44471] isolation/pgrowlocks/s1 LOG: disconnection: session time: 0:00:00.126 user=postgres database=isolation_regression_pgrowlocks host=[local] 2025-11-30 18:45:05.813 UTC client backend[44434] pg_regress/create_table ERROR: cannot use subquery in partition bound at character 75 2025-11-30 18:45:05.813 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((select 1)); 2025-11-30 18:45:05.813 UTC client backend[44474] isolation/pgrowlocks/s2 LOG: disconnection: session time: 0:00:00.119 user=postgres database=isolation_regression_pgrowlocks host=[local] 2025-11-30 18:45:05.813 UTC client backend[44434] pg_regress/create_table ERROR: set-returning functions are not allowed in partition bound at character 75 2025-11-30 18:45:05.813 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (generate_series(4, 6)); 2025-11-30 18:45:05.814 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_ginidx" is not a hash index 2025-11-30 18:45:05.814 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_ginidx'); 2025-11-30 18:45:05.814 UTC client backend[44434] pg_regress/create_table ERROR: collations are not supported by type integer at character 81 2025-11-30 18:45:05.814 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((1+1) collate "POSIX"); 2025-11-30 18:45:05.814 UTC client backend[44434] pg_regress/create_table ERROR: syntax error at or near ")" at character 64 2025-11-30 18:45:05.814 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES IN (); 2025-11-30 18:45:05.814 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_hashidx" is not a btree index 2025-11-30 18:45:05.814 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatindex('test_hashidx'); 2025-11-30 18:45:05.815 UTC client backend[44434] pg_regress/create_table ERROR: invalid bound specification for a list partition at character 60 2025-11-30 18:45:05.815 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES FROM (1) TO (2); 2025-11-30 18:45:05.816 UTC client backend[44434] pg_regress/create_table ERROR: invalid bound specification for a list partition at character 60 2025-11-30 18:45:05.816 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2025-11-30 18:45:05.816 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_hashidx" is not a GIN index 2025-11-30 18:45:05.816 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatginindex('test_hashidx'); 2025-11-30 18:45:05.818 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_default_part" conflicts with existing default partition "part_default" at character 57 2025-11-30 18:45:05.818 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF list_parted DEFAULT; 2025-11-30 18:45:05.821 UTC client backend[44434] pg_regress/create_table ERROR: specified value cannot be cast to type boolean for column "a" at character 59 2025-11-30 18:45:05.821 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE bools_true PARTITION OF bools FOR VALUES IN (1); 2025-11-30 18:45:05.821 UTC unrecognized[44494] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.822 UTC client backend[44494] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.822 UTC client backend[44494] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/crypt-xdes 2025-11-30 18:45:05.822 UTC client backend[44484] pg_regress/pgstattuple ERROR: cannot get tuple-level statistics for relation "test_partitioned" 2025-11-30 18:45:05.822 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:05.822 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple('test_partitioned'); 2025-11-30 18:45:05.823 UTC client backend[44494] pg_regress/crypt-xdes LOG: connection ready: setup total=3.104 ms, fork=1.582 ms, authentication=0.119 ms 2025-11-30 18:45:05.824 UTC client backend[44484] pg_regress/pgstattuple ERROR: cannot get tuple-level statistics for relation "test_partitioned_index" 2025-11-30 18:45:05.824 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for partitioned indexes. 2025-11-30 18:45:05.824 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple('test_partitioned_index'); 2025-11-30 18:45:05.829 UTC client backend[44494] pg_regress/crypt-xdes ERROR: invalid salt 2025-11-30 18:45:05.829 UTC client backend[44494] pg_regress/crypt-xdes STATEMENT: SELECT crypt('foox', '_J9..BWH'); 2025-11-30 18:45:05.829 UTC client backend[44494] pg_regress/crypt-xdes ERROR: crypt(3) returned NULL 2025-11-30 18:45:05.829 UTC client backend[44494] pg_regress/crypt-xdes STATEMENT: SELECT crypt('password', '_........'); 2025-11-30 18:45:05.829 UTC client backend[44494] pg_regress/crypt-xdes ERROR: crypt(3) returned NULL 2025-11-30 18:45:05.829 UTC client backend[44494] pg_regress/crypt-xdes STATEMENT: SELECT crypt('password', '_..!!!!!!'); 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partitioned" is of wrong relation kind 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple_approx('test_partitioned'); 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple ERROR: cannot get page count of relation "test_partitioned" 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pg_relpages('test_partitioned'); 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partitioned" is not a btree index 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatindex('test_partitioned'); 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partitioned" is not a GIN index 2025-11-30 18:45:05.829 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatginindex('test_partitioned'); 2025-11-30 18:45:05.830 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partitioned" is not a hash index 2025-11-30 18:45:05.830 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_partitioned'); 2025-11-30 18:45:05.830 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partitioned_hash_index" is not a hash index 2025-11-30 18:45:05.830 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_partitioned_hash_index'); 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple ERROR: cannot get tuple-level statistics for relation "test_view" 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for views. 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple('test_view'); 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_view" is of wrong relation kind 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for views. 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple_approx('test_view'); 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple ERROR: cannot get page count of relation "test_view" 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for views. 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pg_relpages('test_view'); 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_view" is not a btree index 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatindex('test_view'); 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_view" is not a GIN index 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatginindex('test_view'); 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_view" is not a hash index 2025-11-30 18:45:05.831 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_view'); 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple ERROR: cannot get tuple-level statistics for relation "test_foreign_table" 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple('test_foreign_table'); 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_foreign_table" is of wrong relation kind 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple_approx('test_foreign_table'); 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple ERROR: cannot get page count of relation "test_foreign_table" 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pg_relpages('test_foreign_table'); 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_foreign_table" is not a btree index 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatindex('test_foreign_table'); 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_foreign_table" is not a GIN index 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatginindex('test_foreign_table'); 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_foreign_table" is not a hash index 2025-11-30 18:45:05.833 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_foreign_table'); 2025-11-30 18:45:05.836 UTC client backend[44494] pg_regress/crypt-xdes LOG: disconnection: session time: 0:00:00.014 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.837 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partition" is not a btree index 2025-11-30 18:45:05.837 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatindex('test_partition'); 2025-11-30 18:45:05.837 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partition" is not a GIN index 2025-11-30 18:45:05.837 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatginindex('test_partition'); 2025-11-30 18:45:05.837 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_partition" is not a hash index 2025-11-30 18:45:05.837 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_partition'); 2025-11-30 18:45:05.840 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_sequence" is not a btree index 2025-11-30 18:45:05.840 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatindex('test_sequence'); 2025-11-30 18:45:05.840 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_sequence" is not a GIN index 2025-11-30 18:45:05.840 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstatginindex('test_sequence'); 2025-11-30 18:45:05.841 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_sequence" is not a hash index 2025-11-30 18:45:05.841 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstathashindex('test_sequence'); 2025-11-30 18:45:05.841 UTC client backend[44484] pg_regress/pgstattuple ERROR: relation "test_sequence" is of wrong relation kind 2025-11-30 18:45:05.841 UTC client backend[44484] pg_regress/pgstattuple DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:05.841 UTC client backend[44484] pg_regress/pgstattuple STATEMENT: select pgstattuple_approx('test_sequence'); 2025-11-30 18:45:05.842 UTC unrecognized[44499] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.843 UTC client backend[44499] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.843 UTC client backend[44499] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-armor 2025-11-30 18:45:05.844 UTC client backend[44499] pg_regress/pgp-armor LOG: connection ready: setup total=1.866 ms, fork=0.402 ms, authentication=0.119 ms 2025-11-30 18:45:05.845 UTC client backend[44499] pg_regress/pgp-armor ERROR: Corrupt ascii-armor 2025-11-30 18:45:05.845 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select dearmor(' -----BEGIN PGP MESSAGE----- em9va2E= =ZZZZ -----END PGP MESSAGE----- '); 2025-11-30 18:45:05.845 UTC client backend[44499] pg_regress/pgp-armor ERROR: Corrupt ascii-armor 2025-11-30 18:45:05.845 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select * from pgp_armor_headers(' -----BEGIN PGP MESSAGE----- foo: em9va2E= =ZZZZ -----END PGP MESSAGE----- '); 2025-11-30 18:45:05.845 UTC client backend[44499] pg_regress/pgp-armor ERROR: Corrupt ascii-armor 2025-11-30 18:45:05.845 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select * from pgp_armor_headers(' -----BEGIN PGP MESSAGE----- em9va2E= =ZZZZ -----END PGP MESSAGE----- '); 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor ERROR: mismatched array dimensions 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array['foo'], array['too', 'many']); 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor ERROR: mismatched array dimensions 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array['too', 'many'], array['foo']); 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor ERROR: wrong number of array subscripts 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array[['']], array['foo']); 2025-11-30 18:45:05.847 UTC client backend[44484] pg_regress/pgstattuple LOG: disconnection: session time: 0:00:00.115 user=postgres database=regression_pgstattuple host=[local] 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor ERROR: wrong number of array subscripts 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array['foo'], array[['']]); 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor ERROR: null value not allowed for header key 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array[null], array['foo']); 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor ERROR: null value not allowed for header value 2025-11-30 18:45:05.847 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array['foo'], array[null]); 2025-11-30 18:45:05.849 UTC client backend[44499] pg_regress/pgp-armor ERROR: header key must not contain newlines 2025-11-30 18:45:05.849 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array[E'embedded\nnewline'], array['foo']); 2025-11-30 18:45:05.849 UTC client backend[44499] pg_regress/pgp-armor ERROR: header value must not contain newlines 2025-11-30 18:45:05.849 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array['foo'], array[E'embedded\nnewline']); 2025-11-30 18:45:05.849 UTC client backend[44434] pg_regress/create_table ERROR: partition "bigintp_10_2" would overlap partition "bigintp_10" at character 63 2025-11-30 18:45:05.849 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE bigintp_10_2 PARTITION OF bigintp FOR VALUES IN ('10'); 2025-11-30 18:45:05.852 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2025-11-30 18:45:05.852 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (somename) TO ('2019-01-01'); 2025-11-30 18:45:05.853 UTC client backend[44499] pg_regress/pgp-armor ERROR: header key must not contain ": " 2025-11-30 18:45:05.853 UTC client backend[44499] pg_regress/pgp-armor STATEMENT: select armor('', array['embedded: colon+space'], array['foo']); 2025-11-30 18:45:05.855 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2025-11-30 18:45:05.855 UTC client backend[44434] 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-11-30 18:45:05.855 UTC client backend[44499] pg_regress/pgp-armor LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.856 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2025-11-30 18:45:05.856 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (a) TO ('2019-01-01'); 2025-11-30 18:45:05.859 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 84 2025-11-30 18:45:05.859 UTC client backend[44434] 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-11-30 18:45:05.859 UTC unrecognized[44505] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.859 UTC unrecognized[44506] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.860 UTC client backend[44505] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.860 UTC client backend[44505] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.860 UTC client backend[44434] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 84 2025-11-30 18:45:05.860 UTC client backend[44434] 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-11-30 18:45:05.860 UTC client backend[44505] pg_regress LOG: connection ready: setup total=2.553 ms, fork=1.217 ms, authentication=0.130 ms 2025-11-30 18:45:05.861 UTC client backend[44506] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.861 UTC client backend[44506] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.861 UTC client backend[44434] pg_regress/create_table ERROR: aggregate functions are not allowed in partition bound at character 80 2025-11-30 18:45:05.861 UTC client backend[44434] 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-11-30 18:45:05.861 UTC unrecognized[44507] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.861 UTC client backend[44506] pg_regress LOG: connection ready: setup total=2.778 ms, fork=0.586 ms, authentication=0.100 ms 2025-11-30 18:45:05.862 UTC client backend[44507] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.862 UTC client backend[44507] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-decrypt 2025-11-30 18:45:05.862 UTC client backend[44505] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.862 UTC client backend[44507] pg_regress/pgp-decrypt LOG: connection ready: setup total=1.675 ms, fork=0.366 ms, authentication=0.100 ms 2025-11-30 18:45:05.863 UTC client backend[44506] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.864 UTC client backend[44507] pg_regress/pgp-decrypt ERROR: Wrong key or corrupt data 2025-11-30 18:45:05.864 UTC client backend[44507] pg_regress/pgp-decrypt STATEMENT: select pgp_sym_decrypt(dearmor(' -----BEGIN PGP MESSAGE----- Comment: dat1.blowfish.sha1.mdc.s2k3.z0 jA0EBAMCfFNwxnvodX9g0jwB4n4s26/g5VmKzVab1bX1SmwY7gvgvlWdF3jKisvS yA6Ce1QTMK3KdL2MPfamsTUSAML8huCJMwYQFfE= =JcP+ -----END PGP MESSAGE----- '), 'foobar'); 2025-11-30 18:45:05.869 UTC client backend[44434] pg_regress/create_table ERROR: cannot use subquery in partition bound at character 80 2025-11-30 18:45:05.869 UTC client backend[44434] 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-11-30 18:45:05.870 UTC unrecognized[44510] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.870 UTC client backend[44510] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.870 UTC client backend[44510] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.871 UTC client backend[44510] pg_regress LOG: connection ready: setup total=2.193 ms, fork=0.967 ms, authentication=0.117 ms 2025-11-30 18:45:05.872 UTC client backend[44507] pg_regress/pgp-decrypt ERROR: Wrong key or corrupt data 2025-11-30 18:45:05.872 UTC client backend[44507] pg_regress/pgp-decrypt STATEMENT: select pgp_sym_decrypt(dearmor(' -----BEGIN PGP MESSAGE----- ww0EBwMCxf8PTrQBmJdl0jcB6y2joE7GSLKRv7trbNsF5Z8ou5NISLUg31llVH/S0B2wl4bvzZjV VsxxqLSPzNLAeIspJk5G =mSd/ -----END PGP MESSAGE----- '), 'wrong-key', 'debug=1'); 2025-11-30 18:45:05.872 UTC client backend[44507] pg_regress/pgp-decrypt ERROR: Not text data 2025-11-30 18:45:05.872 UTC client backend[44507] pg_regress/pgp-decrypt STATEMENT: select pgp_sym_decrypt(pgp_sym_encrypt_bytea('P', 'key'), 'key', 'debug=1'); 2025-11-30 18:45:05.873 UTC unrecognized[44511] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.873 UTC client backend[44507] pg_regress/pgp-decrypt ERROR: Wrong key or corrupt data 2025-11-30 18:45:05.873 UTC client backend[44507] pg_regress/pgp-decrypt STATEMENT: select pgp_sym_decrypt(dearmor(' -----BEGIN PGP MESSAGE----- ww0EBwMC9rK/dMkF5Zlt0jcBlzAQ1mQY2qYbKYbw8h3EZ5Jk0K2IiY92R82TRhWzBIF/8cmXDPtP GXsd65oYJZp3Khz0qfyn =Nmpq -----END PGP MESSAGE----- '), 'wrong-key', 'debug=1'); 2025-11-30 18:45:05.873 UTC client backend[44507] pg_regress/pgp-decrypt ERROR: Unsupported compression algorithm 2025-11-30 18:45:05.873 UTC client backend[44507] pg_regress/pgp-decrypt STATEMENT: select pgp_sym_decrypt(dearmor(' -----BEGIN PGP MESSAGE----- jA0EBwMCRhFrAKNcLVJg0mMBLJG1cCASNk/x/3dt1zJ+2eo7jHfjgg3N6wpB3XIe QCwkWJwlBG5pzbO5gu7xuPQN+TbPJ7aQ2sLx3bAHhtYb0i3vV9RO10Gw++yUyd4R UCAAw2JRIISttRHMfDpDuZJpvYo= =AZ9M -----END PGP MESSAGE----- '), 'key', 'debug=1'); 2025-11-30 18:45:05.873 UTC client backend[44507] pg_regress/pgp-decrypt LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:05.876 UTC client backend[44434] pg_regress/create_table ERROR: set-returning functions are not allowed in partition bound at character 80 2025-11-30 18:45:05.876 UTC client backend[44434] 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-11-30 18:45:05.877 UTC client backend[44434] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2025-11-30 18:45:05.877 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES IN ('a'); 2025-11-30 18:45:05.878 UTC client backend[44434] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2025-11-30 18:45:05.878 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2025-11-30 18:45:05.878 UTC client backend[44434] pg_regress/create_table ERROR: FROM must specify exactly one value per partitioning column 2025-11-30 18:45:05.878 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a', 1) TO ('z'); 2025-11-30 18:45:05.879 UTC client backend[44511] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.879 UTC client backend[44511] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.879 UTC client backend[44511] pg_regress LOG: connection ready: setup total=9.733 ms, fork=3.003 ms, authentication=0.132 ms 2025-11-30 18:45:05.879 UTC client backend[44434] pg_regress/create_table ERROR: TO must specify exactly one value per partitioning column 2025-11-30 18:45:05.879 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a') TO ('z', 1); 2025-11-30 18:45:05.881 UTC client backend[44510] pg_regress LOG: disconnection: session time: 0:00:00.010 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.881 UTC client backend[44434] pg_regress/create_table ERROR: cannot specify NULL in range bound 2025-11-30 18:45:05.881 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM (null) TO (maxvalue); 2025-11-30 18:45:05.885 UTC client backend[44434] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2025-11-30 18:45:05.885 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2025-11-30 18:45:05.889 UTC client backend[44511] pg_regress LOG: disconnection: session time: 0:00:00.016 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.891 UTC client backend[44434] pg_regress/create_table ERROR: every hash partition modulus must be a factor of the next larger modulus 2025-11-30 18:45:05.891 UTC client backend[44434] pg_regress/create_table DETAIL: The new modulus 25 is not divisible by 10, the modulus of existing partition "hpart_4". 2025-11-30 18:45:05.891 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 25, REMAINDER 3); 2025-11-30 18:45:05.892 UTC client backend[44434] pg_regress/create_table ERROR: every hash partition modulus must be a factor of the next larger modulus 2025-11-30 18:45:05.892 UTC client backend[44434] pg_regress/create_table DETAIL: The new modulus 150 is not a factor of 200, the modulus of existing partition "hpart_3". 2025-11-30 18:45:05.892 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 150, REMAINDER 3); 2025-11-30 18:45:05.893 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "hpart_4" at character 60 2025-11-30 18:45:05.893 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 100, REMAINDER 3); 2025-11-30 18:45:05.893 UTC client backend[44434] pg_regress/create_table ERROR: invalid bound specification for a hash partition at character 60 2025-11-30 18:45:05.893 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES FROM ('a', 1) TO ('z'); 2025-11-30 18:45:05.894 UTC client backend[44434] pg_regress/create_table ERROR: invalid bound specification for a hash partition at character 60 2025-11-30 18:45:05.894 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES IN (1000); 2025-11-30 18:45:05.895 UTC client backend[44434] pg_regress/create_table ERROR: a hash-partitioned table may not have a default partition 2025-11-30 18:45:05.895 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF hash_parted DEFAULT; 2025-11-30 18:45:05.895 UTC unrecognized[44517] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.895 UTC client backend[44517] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.895 UTC client backend[44517] [unknown] LOG: connection authorized: user=postgres database=regression_pg_trgm application_name=pg_regress/pg_trgm 2025-11-30 18:45:05.897 UTC unrecognized[44515] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.898 UTC client backend[44515] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.898 UTC client backend[44515] [unknown] LOG: connection authorized: user=postgres database=regression_pg_surgery application_name=pg_regress/heap_surgery 2025-11-30 18:45:05.900 UTC client backend[44517] pg_regress/pg_trgm LOG: connection ready: setup total=5.960 ms, fork=0.890 ms, authentication=0.133 ms 2025-11-30 18:45:05.902 UTC client backend[44515] pg_regress/heap_surgery LOG: connection ready: setup total=18.406 ms, fork=8.019 ms, authentication=0.113 ms 2025-11-30 18:45:05.911 UTC client backend[44515] pg_regress/heap_surgery ERROR: argument must be empty or one-dimensional array 2025-11-30 18:45:05.911 UTC client backend[44515] pg_regress/heap_surgery STATEMENT: select heap_force_kill('htab2'::regclass, ARRAY[['(0, 2)']]::tid[]); 2025-11-30 18:45:05.911 UTC client backend[44515] pg_regress/heap_surgery ERROR: array must not contain nulls 2025-11-30 18:45:05.911 UTC client backend[44515] pg_regress/heap_surgery STATEMENT: select heap_force_kill('htab2'::regclass, ARRAY[NULL]::tid[]); 2025-11-30 18:45:05.916 UTC client backend[44434] pg_regress/create_table ERROR: "unparted" is not partitioned 2025-11-30 18:45:05.916 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF unparted FOR VALUES IN ('a'); 2025-11-30 18:45:05.916 UTC client backend[44434] pg_regress/create_table ERROR: "unparted" is not partitioned 2025-11-30 18:45:05.916 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF unparted FOR VALUES WITH (MODULUS 2, REMAINDER 1); 2025-11-30 18:45:05.920 UTC unrecognized[44521] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.921 UTC client backend[44521] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.921 UTC client backend[44521] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.922 UTC client backend[44521] pg_regress LOG: connection ready: setup total=3.963 ms, fork=2.627 ms, authentication=0.123 ms 2025-11-30 18:45:05.922 UTC client backend[44521] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.922 UTC client backend[44434] pg_regress/create_table ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2025-11-30 18:45:05.922 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF temp_parted FOR VALUES IN ('a'); 2025-11-30 18:45:05.923 UTC client backend[44515] pg_regress/heap_surgery ERROR: cannot operate on relation "vw" 2025-11-30 18:45:05.923 UTC client backend[44515] pg_regress/heap_surgery DETAIL: This operation is not supported for views. 2025-11-30 18:45:05.923 UTC client backend[44515] pg_regress/heap_surgery STATEMENT: select heap_force_kill('vw'::regclass, ARRAY['(0, 1)']::tid[]); 2025-11-30 18:45:05.926 UTC client backend[44515] pg_regress/heap_surgery ERROR: cannot operate on relation "vw" 2025-11-30 18:45:05.926 UTC client backend[44515] pg_regress/heap_surgery DETAIL: This operation is not supported for views. 2025-11-30 18:45:05.926 UTC client backend[44515] pg_regress/heap_surgery STATEMENT: select heap_force_freeze('vw'::regclass, ARRAY['(0, 1)']::tid[]); 2025-11-30 18:45:05.927 UTC unrecognized[44525] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.928 UTC client backend[44525] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.928 UTC client backend[44525] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.928 UTC unrecognized[44524] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.928 UTC client backend[44524] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.928 UTC client backend[44524] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.928 UTC client backend[44525] pg_regress LOG: connection ready: setup total=1.592 ms, fork=0.350 ms, authentication=0.113 ms 2025-11-30 18:45:05.929 UTC client backend[44524] pg_regress LOG: connection ready: setup total=2.529 ms, fork=0.601 ms, authentication=0.114 ms 2025-11-30 18:45:05.930 UTC client backend[44515] pg_regress/heap_surgery LOG: disconnection: session time: 0:00:00.038 user=postgres database=regression_pg_surgery host=[local] 2025-11-30 18:45:05.932 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part_null_z" at character 65 2025-11-30 18:45:05.932 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN (null); 2025-11-30 18:45:05.932 UTC client backend[44524] pg_regress LOG: disconnection: session time: 0:00:00.005 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.939 UTC unrecognized[44531] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.940 UTC client backend[44531] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.940 UTC client backend[44531] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-encrypt 2025-11-30 18:45:05.940 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part_ab" at character 65 2025-11-30 18:45:05.940 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('b', 'c'); 2025-11-30 18:45:05.941 UTC client backend[44531] pg_regress/pgp-encrypt LOG: connection ready: setup total=1.913 ms, fork=0.426 ms, authentication=0.121 ms 2025-11-30 18:45:05.942 UTC client backend[44434] pg_regress/create_table ERROR: updated partition constraint for default partition "list_parted2_def" would be violated by some row 2025-11-30 18:45:05.942 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('W', 'X', 'Y'); 2025-11-30 18:45:05.943 UTC unrecognized[44530] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.943 UTC client backend[44530] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.943 UTC client backend[44530] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:05.944 UTC client backend[44530] pg_regress LOG: connection ready: setup total=7.654 ms, fork=2.973 ms, authentication=0.122 ms 2025-11-30 18:45:05.944 UTC client backend[44434] pg_regress/create_table ERROR: empty range bound specified for partition "fail_part" at character 68 2025-11-30 18:45:05.944 UTC client backend[44434] pg_regress/create_table DETAIL: Specified lower bound (1) is greater than or equal to upper bound (0). 2025-11-30 18:45:05.944 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (0); 2025-11-30 18:45:05.945 UTC client backend[44434] pg_regress/create_table ERROR: empty range bound specified for partition "fail_part" at character 68 2025-11-30 18:45:05.945 UTC client backend[44434] pg_regress/create_table DETAIL: Specified lower bound (1) is greater than or equal to upper bound (1). 2025-11-30 18:45:05.945 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (1); 2025-11-30 18:45:05.947 UTC client backend[44531] pg_regress/pgp-encrypt ERROR: Not text data 2025-11-30 18:45:05.947 UTC client backend[44531] pg_regress/pgp-encrypt STATEMENT: select pgp_sym_decrypt(pgp_sym_encrypt_bytea('Binary', 'baz'), 'baz'); 2025-11-30 18:45:05.948 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part0" at character 68 2025-11-30 18:45:05.948 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (minvalue) TO (2); 2025-11-30 18:45:05.948 UTC client backend[44525] pg_regress LOG: disconnection: session time: 0:00:00.021 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.956 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part0" at character 68 2025-11-30 18:45:05.956 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (-1) TO (1); 2025-11-30 18:45:05.957 UTC client backend[44530] pg_regress LOG: disconnection: session time: 0:00:00.015 user=postgres database=postgres host=[local] 2025-11-30 18:45:05.959 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part1" at character 68 2025-11-30 18:45:05.959 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (9) TO (maxvalue); 2025-11-30 18:45:05.962 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part2" at character 76 2025-11-30 18:45:05.962 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (30); 2025-11-30 18:45:05.963 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part2" at character 76 2025-11-30 18:45:05.963 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (50); 2025-11-30 18:45:05.965 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_default_part" conflicts with existing default partition "range2_default" at character 59 2025-11-30 18:45:05.965 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF range_parted2 DEFAULT; 2025-11-30 18:45:05.966 UTC client backend[44434] pg_regress/create_table ERROR: updated partition constraint for default partition "range2_default" would be violated by some row 2025-11-30 18:45:05.966 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (80) TO (90); 2025-11-30 18:45:05.969 UTC client backend[44517] pg_regress/pg_trgm ERROR: value 0 out of bounds for option "siglen" 2025-11-30 18:45:05.969 UTC client backend[44517] pg_regress/pg_trgm DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:05.969 UTC client backend[44517] pg_regress/pg_trgm STATEMENT: create index trgm_idx on test_trgm using gist (t gist_trgm_ops(siglen=0)); 2025-11-30 18:45:05.969 UTC client backend[44517] pg_regress/pg_trgm ERROR: value 2025 out of bounds for option "siglen" 2025-11-30 18:45:05.969 UTC client backend[44517] pg_regress/pg_trgm DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:05.969 UTC client backend[44517] pg_regress/pg_trgm STATEMENT: create index trgm_idx on test_trgm using gist (t gist_trgm_ops(siglen=2025)); 2025-11-30 18:45:05.969 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part00" at character 68 2025-11-30 18:45:05.969 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (0, minvalue) TO (0, 1); 2025-11-30 18:45:05.973 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part12" at character 71 2025-11-30 18:45:05.973 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, 10) TO (1, 20); 2025-11-30 18:45:05.975 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part10" at character 68 2025-11-30 18:45:05.975 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, minvalue) TO (1, maxvalue); 2025-11-30 18:45:05.981 UTC unrecognized[44535] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:05.983 UTC client backend[44434] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "h2part_4" at character 61 2025-11-30 18:45:05.983 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 2, REMAINDER 1); 2025-11-30 18:45:05.984 UTC client backend[44434] pg_regress/create_table ERROR: modulus for hash partition must be an integer value greater than zero 2025-11-30 18:45:05.984 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 0, REMAINDER 1); 2025-11-30 18:45:05.985 UTC client backend[44434] pg_regress/create_table ERROR: remainder for hash partition must be less than modulus 2025-11-30 18:45:05.985 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 8, REMAINDER 8); 2025-11-30 18:45:05.992 UTC client backend[44434] pg_regress/create_table ERROR: column "b" specified more than once 2025-11-30 18:45:05.992 UTC client backend[44434] 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-11-30 18:45:05.996 UTC client backend[44535] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:05.996 UTC client backend[44535] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=pg_regress/postgres_fdw 2025-11-30 18:45:06.000 UTC client backend[44535] pg_regress/postgres_fdw LOG: connection ready: setup total=20.453 ms, fork=0.922 ms, authentication=0.127 ms 2025-11-30 18:45:06.039 UTC unrecognized[44538] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.039 UTC client backend[44434] pg_regress/create_table ERROR: cannot drop inherited constraint "check_a" of relation "part_b" 2025-11-30 18:45:06.039 UTC client backend[44434] pg_regress/create_table STATEMENT: ALTER TABLE part_b DROP CONSTRAINT check_a; 2025-11-30 18:45:06.039 UTC client backend[44538] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.039 UTC client backend[44538] [unknown] LOG: connection authorized: user=postgres database=regression_pg_visibility application_name=pg_regress/pg_visibility 2025-11-30 18:45:06.044 UTC client backend[44538] pg_regress/pg_visibility LOG: connection ready: setup total=5.437 ms, fork=0.446 ms, authentication=0.120 ms 2025-11-30 18:45:06.050 UTC client backend[44434] pg_regress/create_table ERROR: cannot drop inherited constraint "check_b" of relation "part_b" 2025-11-30 18:45:06.050 UTC client backend[44434] pg_regress/create_table STATEMENT: ALTER TABLE part_b DROP CONSTRAINT check_b; 2025-11-30 18:45:06.050 UTC client backend[44535] pg_regress/postgres_fdw ERROR: parameter "extensions" must be a list of extension names 2025-11-30 18:45:06.050 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: ALTER SERVER testserver1 OPTIONS (ADD extensions 'foo; bar'); 2025-11-30 18:45:06.050 UTC client backend[44535] pg_regress/postgres_fdw WARNING: extension "foo" is not installed 2025-11-30 18:45:06.050 UTC client backend[44535] pg_regress/postgres_fdw WARNING: extension "bar" is not installed 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw ERROR: invalid option "sslmode" 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR public SERVER testserver1 OPTIONS (ADD sslmode 'require'); 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw ERROR: invalid option "oauth_issuer" 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: ALTER SERVER testserver1 OPTIONS (ADD oauth_issuer 'https://example.com'); 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw ERROR: invalid option "oauth_client_id" 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: ALTER SERVER testserver1 OPTIONS (ADD oauth_client_id 'myID'); 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw ERROR: invalid option "oauth_issuer" 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR public SERVER testserver1 OPTIONS (ADD oauth_issuer 'https://example.com'); 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw ERROR: invalid option "oauth_client_id" 2025-11-30 18:45:06.051 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR public SERVER testserver1 OPTIONS (ADD oauth_client_id 'myID'); 2025-11-30 18:45:06.052 UTC client backend[44538] pg_regress/pg_visibility ERROR: could not open relation with OID 28321 2025-11-30 18:45:06.052 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: SELECT * FROM pg_visibility_map(28321); 2025-11-30 18:45:06.052 UTC client backend[44538] pg_regress/pg_visibility ERROR: could not open relation with OID 28321 2025-11-30 18:45:06.052 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: SELECT * FROM pg_visibility_map(28321); 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_partitioned" is of wrong relation kind 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility('test_partitioned', 0); 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_partitioned" is of wrong relation kind 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map('test_partitioned'); 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_partitioned" is of wrong relation kind 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map_summary('test_partitioned'); 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_partitioned" is of wrong relation kind 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_check_frozen('test_partitioned'); 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_partitioned" is of wrong relation kind 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:06.054 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_truncate_visibility_map('test_partitioned'); 2025-11-30 18:45:06.056 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_index" is of wrong relation kind 2025-11-30 18:45:06.056 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:06.056 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility('test_index', 0); 2025-11-30 18:45:06.056 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_index" is of wrong relation kind 2025-11-30 18:45:06.056 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:06.056 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map('test_index'); 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_index" is of wrong relation kind 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map_summary('test_index'); 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_index" is of wrong relation kind 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_check_frozen('test_index'); 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_index" is of wrong relation kind 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:06.057 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_truncate_visibility_map('test_index'); 2025-11-30 18:45:06.063 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_view" is of wrong relation kind 2025-11-30 18:45:06.063 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for views. 2025-11-30 18:45:06.063 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility('test_view', 0); 2025-11-30 18:45:06.063 UTC unrecognized[44540] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.063 UTC client backend[44540] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.063 UTC client backend[44540] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.064 UTC client backend[44540] postgres_fdw LOG: connection ready: setup total=4.771 ms, fork=3.457 ms, authentication=0.128 ms 2025-11-30 18:45:06.064 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_view" is of wrong relation kind 2025-11-30 18:45:06.064 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for views. 2025-11-30 18:45:06.064 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map('test_view'); 2025-11-30 18:45:06.064 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_view" is of wrong relation kind 2025-11-30 18:45:06.064 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for views. 2025-11-30 18:45:06.064 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map_summary('test_view'); 2025-11-30 18:45:06.065 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_view" is of wrong relation kind 2025-11-30 18:45:06.065 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for views. 2025-11-30 18:45:06.065 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_check_frozen('test_view'); 2025-11-30 18:45:06.065 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_view" is of wrong relation kind 2025-11-30 18:45:06.065 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for views. 2025-11-30 18:45:06.065 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_truncate_visibility_map('test_view'); 2025-11-30 18:45:06.066 UTC client backend[44434] pg_regress/create_table ERROR: column "c" named in partition key does not exist at character 98 2025-11-30 18:45:06.066 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE fail_part_col_not_found PARTITION OF parted FOR VALUES IN ('c') PARTITION BY RANGE (c); 2025-11-30 18:45:06.069 UTC client backend[44540] postgres_fdw LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:06.071 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_sequence" is of wrong relation kind 2025-11-30 18:45:06.071 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:06.071 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility('test_sequence', 0); 2025-11-30 18:45:06.071 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_sequence" is of wrong relation kind 2025-11-30 18:45:06.071 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:06.071 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map('test_sequence'); 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_sequence" is of wrong relation kind 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map_summary('test_sequence'); 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_sequence" is of wrong relation kind 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_check_frozen('test_sequence'); 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_sequence" is of wrong relation kind 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:06.072 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_truncate_visibility_map('test_sequence'); 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_foreign_table" is of wrong relation kind 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility('test_foreign_table', 0); 2025-11-30 18:45:06.073 UTC unrecognized[44541] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_foreign_table" is of wrong relation kind 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map('test_foreign_table'); 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_foreign_table" is of wrong relation kind 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_visibility_map_summary('test_foreign_table'); 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_foreign_table" is of wrong relation kind 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_check_frozen('test_foreign_table'); 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility ERROR: relation "test_foreign_table" is of wrong relation kind 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:06.073 UTC client backend[44538] pg_regress/pg_visibility STATEMENT: select pg_truncate_visibility_map('test_foreign_table'); 2025-11-30 18:45:06.074 UTC client backend[44541] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.074 UTC client backend[44541] [unknown] LOG: connection authorized: user=postgres database=no such database application_name=postgres_fdw 2025-11-30 18:45:06.074 UTC client backend[44541] [unknown] FATAL: database "no such database" does not exist 2025-11-30 18:45:06.074 UTC client backend[44535] pg_regress/postgres_fdw ERROR: could not connect to server "loopback" 2025-11-30 18:45:06.074 UTC client backend[44535] pg_regress/postgres_fdw DETAIL: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: database "no such database" does not exist 2025-11-30 18:45:06.074 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: SELECT c3, c4 FROM ft1 ORDER BY c3, c1 LIMIT 1; 2025-11-30 18:45:06.079 UTC unrecognized[44542] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.079 UTC client backend[44542] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.079 UTC client backend[44542] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.080 UTC client backend[44542] postgres_fdw LOG: connection ready: setup total=3.065 ms, fork=1.823 ms, authentication=0.104 ms 2025-11-30 18:45:06.081 UTC unrecognized[44539] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.081 UTC client backend[44539] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.081 UTC client backend[44539] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.082 UTC client backend[44539] pg_regress LOG: connection ready: setup total=27.260 ms, fork=2.091 ms, authentication=0.119 ms 2025-11-30 18:45:06.083 UTC client backend[44434] pg_regress/create_table ERROR: null value in column "b" of relation "parted_notnull_inh_test1" violates not-null constraint 2025-11-30 18:45:06.083 UTC client backend[44434] pg_regress/create_table DETAIL: Failing row contains (1, null). 2025-11-30 18:45:06.083 UTC client backend[44434] pg_regress/create_table STATEMENT: insert into parted_notnull_inh_test (b) values (null); 2025-11-30 18:45:06.084 UTC client backend[44542] postgres_fdw LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:06.100 UTC client backend[44538] pg_regress/pg_visibility LOG: disconnection: session time: 0:00:00.061 user=postgres database=regression_pg_visibility host=[local] 2025-11-30 18:45:06.113 UTC unrecognized[44543] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.113 UTC client backend[44543] [unknown] LOG: connection authenticated: user="no such user" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.113 UTC client backend[44543] [unknown] LOG: connection authorized: user=no such user database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.113 UTC client backend[44543] [unknown] FATAL: role "no such user" does not exist 2025-11-30 18:45:06.113 UTC client backend[44535] pg_regress/postgres_fdw ERROR: could not connect to server "loopback" 2025-11-30 18:45:06.113 UTC client backend[44535] pg_regress/postgres_fdw DETAIL: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: role "no such user" does not exist 2025-11-30 18:45:06.113 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: SELECT c3, c4 FROM ft1 ORDER BY c3, c1 LIMIT 1; 2025-11-30 18:45:06.118 UTC unrecognized[44545] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.118 UTC client backend[44545] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.118 UTC client backend[44545] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.119 UTC client backend[44545] postgres_fdw LOG: connection ready: setup total=3.501 ms, fork=2.124 ms, authentication=0.115 ms 2025-11-30 18:45:06.119 UTC client backend[44539] pg_regress LOG: disconnection: session time: 0:00:00.062 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.160 UTC unrecognized[44550] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.160 UTC client backend[44550] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.160 UTC client backend[44550] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.161 UTC client backend[44550] pg_regress LOG: connection ready: setup total=2.843 ms, fork=1.556 ms, authentication=0.117 ms 2025-11-30 18:45:06.161 UTC client backend[44550] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.164 UTC unrecognized[44552] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.164 UTC client backend[44552] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.164 UTC client backend[44552] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.165 UTC client backend[44552] pg_regress LOG: connection ready: setup total=1.777 ms, fork=0.629 ms, authentication=0.105 ms 2025-11-30 18:45:06.173 UTC client backend[44552] pg_regress LOG: disconnection: session time: 0:00:00.009 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.177 UTC client backend[44535] pg_regress/postgres_fdw ERROR: cannot add relation "ft1" to publication 2025-11-30 18:45:06.177 UTC client backend[44535] pg_regress/postgres_fdw DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:06.177 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: CREATE PUBLICATION testpub_ftbl FOR TABLE ft1; 2025-11-30 18:45:06.191 UTC unrecognized[44554] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.192 UTC client backend[44554] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.192 UTC client backend[44554] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=pg_regress 2025-11-30 18:45:06.196 UTC client backend[44554] pg_regress LOG: connection ready: setup total=18.538 ms, fork=13.402 ms, authentication=0.128 ms 2025-11-30 18:45:06.201 UTC client backend[44554] pg_regress LOG: disconnection: session time: 0:00:00.010 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.218 UTC unrecognized[44557] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.219 UTC client backend[44557] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.219 UTC client backend[44557] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=isolation/eval_plan_qual 2025-11-30 18:45:06.219 UTC client backend[44557] isolation/eval_plan_qual LOG: connection ready: setup total=11.443 ms, fork=9.101 ms, authentication=0.117 ms 2025-11-30 18:45:06.224 UTC unrecognized[44558] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.225 UTC client backend[44558] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.225 UTC client backend[44558] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=isolation/eval_plan_qual 2025-11-30 18:45:06.226 UTC client backend[44558] isolation/eval_plan_qual LOG: connection ready: setup total=4.908 ms, fork=2.667 ms, authentication=0.116 ms 2025-11-30 18:45:06.229 UTC unrecognized[44560] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.229 UTC unrecognized[44559] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.229 UTC client backend[44560] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.229 UTC client backend[44560] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=isolation/eval_plan_qual 2025-11-30 18:45:06.230 UTC client backend[44560] isolation/eval_plan_qual LOG: connection ready: setup total=3.527 ms, fork=2.194 ms, authentication=0.110 ms 2025-11-30 18:45:06.237 UTC client backend[44559] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.237 UTC client backend[44559] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.238 UTC client backend[44559] pg_regress LOG: connection ready: setup total=11.548 ms, fork=2.769 ms, authentication=0.121 ms 2025-11-30 18:45:06.247 UTC client backend[44531] pg_regress/pgp-encrypt LOG: disconnection: session time: 0:00:00.307 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:06.255 UTC unrecognized[44563] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.255 UTC unrecognized[44564] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.255 UTC client backend[44563] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.255 UTC client backend[44563] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.255 UTC client backend[44564] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.255 UTC client backend[44564] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-encrypt-md5 2025-11-30 18:45:06.256 UTC client backend[44563] postgres_fdw LOG: connection ready: setup total=2.955 ms, fork=1.593 ms, authentication=0.125 ms 2025-11-30 18:45:06.256 UTC client backend[44564] pg_regress/pgp-encrypt-md5 LOG: connection ready: setup total=1.826 ms, fork=0.446 ms, authentication=0.101 ms 2025-11-30 18:45:06.259 UTC client backend[44564] pg_regress/pgp-encrypt-md5 LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:06.263 UTC client backend[44559] pg_regress LOG: disconnection: session time: 0:00:00.034 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.267 UTC unrecognized[44569] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.268 UTC client backend[44569] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.268 UTC client backend[44569] [unknown] LOG: connection authorized: user=postgres database=regression_seg application_name=pg_regress/security 2025-11-30 18:45:06.272 UTC client backend[44569] pg_regress/security LOG: connection ready: setup total=5.640 ms, fork=0.453 ms, authentication=0.117 ms 2025-11-30 18:45:06.275 UTC unrecognized[44568] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.275 UTC client backend[44568] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.275 UTC client backend[44568] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-pubkey-decrypt 2025-11-30 18:45:06.276 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt LOG: connection ready: setup total=9.518 ms, fork=8.149 ms, authentication=0.109 ms 2025-11-30 18:45:06.290 UTC client backend[44563] postgres_fdw LOG: disconnection: session time: 0:00:00.035 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.292 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt ERROR: Wrong key or corrupt data 2025-11-30 18:45:06.292 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt STATEMENT: select pgp_pub_decrypt(dearmor(data), dearmor(seckey)) from keytbl, encdata where keytbl.id=2 and encdata.id=2; 2025-11-30 18:45:06.302 UTC unrecognized[44570] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.302 UTC client backend[44570] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.302 UTC client backend[44570] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.303 UTC client backend[44570] postgres_fdw LOG: connection ready: setup total=9.638 ms, fork=8.295 ms, authentication=0.119 ms 2025-11-30 18:45:06.303 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt ERROR: Wrong key 2025-11-30 18:45:06.303 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt STATEMENT: select pgp_pub_decrypt(dearmor(data), dearmor(seckey)) from keytbl, encdata where keytbl.id=2 and encdata.id=1; 2025-11-30 18:45:06.304 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt ERROR: No encryption key found 2025-11-30 18:45:06.304 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt STATEMENT: select pgp_pub_decrypt(dearmor(data), dearmor(seckey)) from keytbl, encdata where keytbl.id=4 and encdata.id=1; 2025-11-30 18:45:06.304 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt ERROR: Wrong key or corrupt data 2025-11-30 18:45:06.304 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt STATEMENT: select pgp_pub_decrypt(dearmor(data), dearmor(seckey), '123') from keytbl, encdata where keytbl.id=7 and encdata.id=4; 2025-11-30 18:45:06.307 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt ERROR: Need password for secret key 2025-11-30 18:45:06.307 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt STATEMENT: select pgp_pub_decrypt(dearmor(data), dearmor(seckey)) from keytbl, encdata where keytbl.id=5 and encdata.id=1; 2025-11-30 18:45:06.308 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt ERROR: Wrong key or corrupt data 2025-11-30 18:45:06.308 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt STATEMENT: select pgp_pub_decrypt(dearmor(data), dearmor(seckey), 'foo') from keytbl, encdata where keytbl.id=5 and encdata.id=1; 2025-11-30 18:45:06.309 UTC client backend[44535] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-11-30 18:45:06.309 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: SELECT * from ft1 where c1 < 1; 2025-11-30 18:45:06.309 UTC client backend[44535] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-11-30 18:45:06.309 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1 (c1) VALUES (1); 2025-11-30 18:45:06.309 UTC client backend[44535] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-11-30 18:45:06.309 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: DELETE FROM ft1 WHERE c1 = 1; 2025-11-30 18:45:06.311 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt ERROR: Wrong key or corrupt data 2025-11-30 18:45:06.311 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt STATEMENT: select pgp_pub_decrypt(dearmor(data), dearmor(seckey)) from keytbl, encdata where keytbl.id=6 and encdata.id=5; 2025-11-30 18:45:06.312 UTC client backend[44568] pg_regress/pgp-pubkey-decrypt LOG: disconnection: session time: 0:00:00.037 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:06.330 UTC client backend[44535] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-11-30 18:45:06.330 UTC client backend[44535] pg_regress/postgres_fdw STATEMENT: TRUNCATE ft1; 2025-11-30 18:45:06.341 UTC client backend[44569] pg_regress/security LOG: disconnection: session time: 0:00:00.073 user=postgres database=regression_seg host=[local] 2025-11-30 18:45:06.341 UTC client backend[44570] postgres_fdw LOG: disconnection: session time: 0:00:00.039 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.354 UTC unrecognized[44575] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.354 UTC client backend[44575] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.354 UTC client backend[44575] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.355 UTC client backend[44575] postgres_fdw LOG: connection ready: setup total=1.898 ms, fork=0.566 ms, authentication=0.133 ms 2025-11-30 18:45:06.367 UTC unrecognized[44576] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.368 UTC client backend[44576] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.368 UTC client backend[44576] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-pubkey-encrypt 2025-11-30 18:45:06.368 UTC client backend[44434] pg_regress/create_table ERROR: cannot specify storage parameters for a partitioned table 2025-11-30 18:45:06.368 UTC client backend[44434] pg_regress/create_table HINT: Specify storage parameters for its leaf partitions instead. 2025-11-30 18:45:06.368 UTC client backend[44434] pg_regress/create_table STATEMENT: CREATE TABLE parted_col_comment (a int, b text) PARTITION BY LIST (a) WITH (fillfactor=100); 2025-11-30 18:45:06.369 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt LOG: connection ready: setup total=4.954 ms, fork=2.843 ms, authentication=0.117 ms 2025-11-30 18:45:06.383 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt ERROR: No encryption key found 2025-11-30 18:45:06.383 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt STATEMENT: select pgp_pub_decrypt( pgp_pub_encrypt('Secret msg', dearmor(pubkey)), dearmor(seckey)) from keytbl where keytbl.id=4; 2025-11-30 18:45:06.384 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt ERROR: Refusing to encrypt with secret key 2025-11-30 18:45:06.384 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt STATEMENT: select pgp_pub_decrypt( pgp_pub_encrypt('Secret msg', dearmor(seckey)), dearmor(seckey)) from keytbl where keytbl.id=1; 2025-11-30 18:45:06.385 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt ERROR: Not text data 2025-11-30 18:45:06.385 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt STATEMENT: select pgp_pub_decrypt( pgp_pub_encrypt_bytea('Secret msg', dearmor(pubkey)), dearmor(seckey)) from keytbl where keytbl.id=1; 2025-11-30 18:45:06.386 UTC client backend[44576] pg_regress/pgp-pubkey-encrypt LOG: disconnection: session time: 0:00:00.019 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:06.390 UTC unrecognized[44579] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.391 UTC client backend[44579] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.391 UTC client backend[44579] [unknown] LOG: connection authorized: user=postgres database=regression_seg application_name=pg_regress/seg 2025-11-30 18:45:06.392 UTC client backend[44579] pg_regress/seg LOG: connection ready: setup total=1.955 ms, fork=0.397 ms, authentication=0.123 ms 2025-11-30 18:45:06.395 UTC client backend[44575] postgres_fdw LOG: disconnection: session time: 0:00:00.041 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.396 UTC unrecognized[44581] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.396 UTC client backend[44581] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.396 UTC client backend[44581] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-info 2025-11-30 18:45:06.397 UTC client backend[44581] pg_regress/pgp-info LOG: connection ready: setup total=1.901 ms, fork=0.399 ms, authentication=0.116 ms 2025-11-30 18:45:06.398 UTC unrecognized[44582] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.399 UTC client backend[44582] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.399 UTC client backend[44582] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.399 UTC client backend[44582] postgres_fdw LOG: connection ready: setup total=2.416 ms, fork=1.194 ms, authentication=0.107 ms 2025-11-30 18:45:06.400 UTC client backend[44581] pg_regress/pgp-info ERROR: No encryption key found 2025-11-30 18:45:06.400 UTC client backend[44581] pg_regress/pgp-info STATEMENT: select pgp_key_id(dearmor(pubkey)) from keytbl where id=4; 2025-11-30 18:45:06.402 UTC client backend[44581] pg_regress/pgp-info ERROR: No encryption key found 2025-11-30 18:45:06.402 UTC client backend[44581] pg_regress/pgp-info STATEMENT: select pgp_key_id(dearmor(seckey)) from keytbl where id=4; 2025-11-30 18:45:06.404 UTC client backend[44581] pg_regress/pgp-info LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:06.425 UTC client backend[44434] pg_regress/create_table ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2025-11-30 18:45:06.425 UTC client backend[44434] pg_regress/create_table STATEMENT: create table perm_part partition of temp_parted default; 2025-11-30 18:45:06.425 UTC client backend[44434] pg_regress/create_table ERROR: cannot create a temporary relation as partition of permanent relation "perm_parted" 2025-11-30 18:45:06.425 UTC client backend[44434] pg_regress/create_table STATEMENT: create temp table temp_part partition of perm_parted default; 2025-11-30 18:45:06.431 UTC client backend[44434] 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-11-30 18:45:06.431 UTC client backend[44434] 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-11-30 18:45:06.431 UTC client backend[44434] pg_regress/create_table STATEMENT: insert into tab_part_create values (1); 2025-11-30 18:45:06.444 UTC unrecognized[44585] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.444 UTC client backend[44585] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.444 UTC client backend[44585] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/crypt-shacrypt 2025-11-30 18:45:06.445 UTC client backend[44585] pg_regress/crypt-shacrypt LOG: connection ready: setup total=2.043 ms, fork=0.546 ms, authentication=0.120 ms 2025-11-30 18:45:06.445 UTC client backend[44557] isolation/eval_plan_qual/control connection LOG: disconnection: session time: 0:00:00.227 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.447 UTC client backend[44558] isolation/eval_plan_qual/s0 LOG: disconnection: session time: 0:00:00.223 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.448 UTC client backend[44560] isolation/eval_plan_qual/s1 LOG: disconnection: session time: 0:00:00.218 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.448 UTC client backend[44582] postgres_fdw LOG: disconnection: session time: 0:00:00.050 user=postgres database=isolation_regression_postgres_fdw host=[local] 2025-11-30 18:45:06.475 UTC client backend[44585] pg_regress/crypt-shacrypt ERROR: gen_salt: Incorrect number of rounds 2025-11-30 18:45:06.475 UTC client backend[44585] pg_regress/crypt-shacrypt STATEMENT: UPDATE ctest SET salt = gen_salt('sha256crypt', 10); 2025-11-30 18:45:06.475 UTC client backend[44585] pg_regress/crypt-shacrypt ERROR: gen_salt: Incorrect number of rounds 2025-11-30 18:45:06.475 UTC client backend[44585] pg_regress/crypt-shacrypt STATEMENT: UPDATE ctest SET salt = gen_salt('sha256crypt', 1000000000); 2025-11-30 18:45:06.482 UTC client backend[44545] postgres_fdw LOG: disconnection: session time: 0:00:00.364 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:06.489 UTC client backend[44434] pg_regress/create_table ERROR: updated partition constraint for default partition "defcheck_def" would be violated by some row 2025-11-30 18:45:06.489 UTC client backend[44434] pg_regress/create_table STATEMENT: create table defcheck_0 partition of defcheck for values in (0); 2025-11-30 18:45:06.498 UTC unrecognized[44588] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.498 UTC client backend[44588] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.498 UTC client backend[44588] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.499 UTC client backend[44588] postgres_fdw LOG: connection ready: setup total=13.462 ms, fork=12.018 ms, authentication=0.140 ms 2025-11-30 18:45:06.502 UTC client backend[44585] pg_regress/crypt-shacrypt ERROR: gen_salt: Incorrect number of rounds 2025-11-30 18:45:06.502 UTC client backend[44585] pg_regress/crypt-shacrypt STATEMENT: UPDATE ctest SET salt = gen_salt('sha512crypt', 10); 2025-11-30 18:45:06.502 UTC client backend[44585] pg_regress/crypt-shacrypt ERROR: gen_salt: Incorrect number of rounds 2025-11-30 18:45:06.502 UTC client backend[44585] pg_regress/crypt-shacrypt STATEMENT: UPDATE ctest SET salt = gen_salt('sha512crypt', 1000000000); 2025-11-30 18:45:06.544 UTC unrecognized[44591] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.545 UTC client backend[44591] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.545 UTC client backend[44591] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.546 UTC client backend[44591] pg_regress LOG: connection ready: setup total=12.570 ms, fork=11.231 ms, authentication=0.124 ms 2025-11-30 18:45:06.546 UTC client backend[44591] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at end of input 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT ''::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at or near "A" 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT 'ABC'::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at or near "A" 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT '1ABC'::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at or near "." 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT '1.'::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at or near ".." 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT '1.....'::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at or near "." 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT '.1'::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at or near "." 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT '1..2.'::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: bad seg representation at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg DETAIL: syntax error at or near "e" 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT '1 e7'::seg AS seg; 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg ERROR: "1e700" is out of range for type real at character 8 2025-11-30 18:45:06.552 UTC client backend[44579] pg_regress/seg STATEMENT: SELECT '1e700'::seg AS seg; 2025-11-30 18:45:06.571 UTC client backend[44579] pg_regress/seg LOG: disconnection: session time: 0:00:00.180 user=postgres database=regression_seg host=[local] 2025-11-30 18:45:06.576 UTC client backend[44517] pg_regress/pg_trgm LOG: disconnection: session time: 0:00:00.681 user=postgres database=regression_pg_trgm host=[local] 2025-11-30 18:45:06.578 UTC unrecognized[44596] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.578 UTC unrecognized[44597] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.578 UTC client backend[44596] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.578 UTC client backend[44596] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=pg_regress/postgres_fdw 2025-11-30 18:45:06.578 UTC client backend[44597] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.578 UTC client backend[44597] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.579 UTC client backend[44597] pg_regress LOG: connection ready: setup total=2.078 ms, fork=0.929 ms, authentication=0.100 ms 2025-11-30 18:45:06.579 UTC client backend[44596] pg_regress/postgres_fdw LOG: connection ready: setup total=2.523 ms, fork=0.953 ms, authentication=0.126 ms 2025-11-30 18:45:06.585 UTC unrecognized[44600] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.585 UTC client backend[44600] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.585 UTC client backend[44600] [unknown] LOG: connection authorized: user=postgres database=regression_pg_trgm application_name=pg_regress/pg_word_trgm 2025-11-30 18:45:06.586 UTC client backend[44600] pg_regress/pg_word_trgm LOG: connection ready: setup total=1.684 ms, fork=0.330 ms, authentication=0.105 ms 2025-11-30 18:45:06.593 UTC client backend[44535] pg_regress/postgres_fdw LOG: disconnection: session time: 0:00:00.612 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:06.594 UTC client backend[44588] postgres_fdw LOG: disconnection: session time: 0:00:00.096 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:06.598 UTC client backend[44597] pg_regress LOG: disconnection: session time: 0:00:00.020 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.601 UTC unrecognized[44598] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.601 UTC client backend[44598] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.601 UTC client backend[44598] [unknown] LOG: connection authorized: user=postgres database=regression_seg application_name=pg_regress/partition 2025-11-30 18:45:06.602 UTC client backend[44598] pg_regress/partition LOG: connection ready: setup total=24.808 ms, fork=23.110 ms, authentication=0.114 ms 2025-11-30 18:45:06.608 UTC unrecognized[44603] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.608 UTC client backend[44603] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.608 UTC client backend[44603] [unknown] LOG: connection authorized: user=postgres database=regression_spi application_name=pg_regress/autoinc 2025-11-30 18:45:06.611 UTC unrecognized[44602] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.611 UTC client backend[44602] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.611 UTC client backend[44602] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:06.612 UTC client backend[44602] postgres_fdw LOG: connection ready: setup total=14.101 ms, fork=12.308 ms, authentication=0.102 ms 2025-11-30 18:45:06.613 UTC client backend[44603] pg_regress/autoinc LOG: connection ready: setup total=7.570 ms, fork=2.639 ms, authentication=0.120 ms 2025-11-30 18:45:06.621 UTC client backend[44603] pg_regress/autoinc LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_spi host=[local] 2025-11-30 18:45:06.640 UTC client backend[44600] pg_regress/pg_word_trgm LOG: disconnection: session time: 0:00:00.055 user=postgres database=regression_pg_trgm host=[local] 2025-11-30 18:45:06.654 UTC client backend[44598] pg_regress/partition LOG: disconnection: session time: 0:00:00.053 user=postgres database=regression_seg host=[local] 2025-11-30 18:45:06.668 UTC unrecognized[44611] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.668 UTC client backend[44611] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.668 UTC client backend[44611] [unknown] LOG: connection authorized: user=postgres database=regression_spi application_name=pg_regress/refint 2025-11-30 18:45:06.669 UTC client backend[44611] pg_regress/refint LOG: connection ready: setup total=2.163 ms, fork=0.666 ms, authentication=0.120 ms 2025-11-30 18:45:06.679 UTC unrecognized[44607] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.680 UTC client backend[44607] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.680 UTC client backend[44607] [unknown] LOG: connection authorized: user=postgres database=regression_pg_trgm application_name=pg_regress/pg_strict_word_trgm 2025-11-30 18:45:06.681 UTC client backend[44607] pg_regress/pg_strict_word_trgm LOG: connection ready: setup total=34.514 ms, fork=1.453 ms, authentication=0.122 ms 2025-11-30 18:45:06.682 UTC client backend[44607] pg_regress/pg_strict_word_trgm ERROR: relation "test_trgm3" does not exist 2025-11-30 18:45:06.682 UTC client backend[44607] pg_regress/pg_strict_word_trgm STATEMENT: COPY test_trgm3 FROM STDIN 2025-11-30 18:45:06.726 UTC client backend[44434] pg_regress/create_table LOG: disconnection: session time: 0:00:01.216 user=postgres database=regression host=[local] 2025-11-30 18:45:06.742 UTC unrecognized[44614] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.743 UTC client backend[44614] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.743 UTC client backend[44614] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.744 UTC client backend[44614] pg_regress LOG: connection ready: setup total=7.899 ms, fork=6.576 ms, authentication=0.125 ms 2025-11-30 18:45:06.744 UTC client backend[44614] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.745 UTC client backend[44611] pg_regress/refint ERROR: tuple references non-existent key 2025-11-30 18:45:06.745 UTC client backend[44611] pg_regress/refint DETAIL: Trigger "check_fkeys2_pkey_exist" found tuple referencing non-existent key in "pkeys". 2025-11-30 18:45:06.745 UTC client backend[44611] pg_regress/refint STATEMENT: insert into fkeys2 values (70, '5', 3); 2025-11-30 18:45:06.750 UTC client backend[44611] pg_regress/refint ERROR: tuple references non-existent key 2025-11-30 18:45:06.750 UTC client backend[44611] pg_regress/refint DETAIL: Trigger "check_fkeys_pkey_exist" found tuple referencing non-existent key in "pkeys". 2025-11-30 18:45:06.750 UTC client backend[44611] pg_regress/refint STATEMENT: insert into fkeys values (70, '5', 1); 2025-11-30 18:45:06.750 UTC client backend[44611] pg_regress/refint ERROR: tuple references non-existent key 2025-11-30 18:45:06.750 UTC client backend[44611] pg_regress/refint DETAIL: Trigger "check_fkeys_pkey2_exist" found tuple referencing non-existent key in "fkeys2". 2025-11-30 18:45:06.750 UTC client backend[44611] pg_regress/refint STATEMENT: insert into fkeys values (60, '6', 4); 2025-11-30 18:45:06.775 UTC client backend[44607] pg_regress/pg_strict_word_trgm LOG: disconnection: session time: 0:00:00.127 user=postgres database=regression_pg_trgm host=[local] 2025-11-30 18:45:06.776 UTC unrecognized[44619] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.777 UTC client backend[44619] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.777 UTC client backend[44619] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.778 UTC client backend[44619] pg_regress LOG: connection ready: setup total=23.851 ms, fork=22.519 ms, authentication=0.123 ms 2025-11-30 18:45:06.792 UTC client backend[44611] pg_regress/refint ERROR: "check_fkeys2_fkey_restrict": tuple is referenced in "fkeys" 2025-11-30 18:45:06.792 UTC client backend[44611] pg_regress/refint CONTEXT: SQL statement "delete from fkeys2 where fkey21 = $1 and fkey22 = $2 " 2025-11-30 18:45:06.792 UTC client backend[44611] pg_regress/refint STATEMENT: delete from pkeys where pkey1 = 30 and pkey2 = '3'; 2025-11-30 18:45:06.796 UTC client backend[44611] pg_regress/refint ERROR: duplicate key value violates unique constraint "pkeys_i" 2025-11-30 18:45:06.796 UTC client backend[44611] pg_regress/refint DETAIL: Key (pkey1, pkey2)=(7, 70) already exists. 2025-11-30 18:45:06.796 UTC client backend[44611] pg_regress/refint STATEMENT: update pkeys set pkey1 = 7, pkey2 = '70' where pkey1 = 10 and pkey2 = '1'; 2025-11-30 18:45:06.811 UTC client backend[44611] pg_regress/refint LOG: disconnection: session time: 0:00:00.143 user=postgres database=regression_spi host=[local] 2025-11-30 18:45:06.813 UTC unrecognized[44634] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.813 UTC client backend[44585] pg_regress/crypt-shacrypt LOG: disconnection: session time: 0:00:00.369 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:06.814 UTC client backend[44634] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.814 UTC client backend[44634] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_index_spgist 2025-11-30 18:45:06.814 UTC client backend[44634] pg_regress/create_index_spgist LOG: connection ready: setup total=1.839 ms, fork=0.280 ms, authentication=0.118 ms 2025-11-30 18:45:06.816 UTC unrecognized[44633] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.816 UTC client backend[44633] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.816 UTC client backend[44633] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_view 2025-11-30 18:45:06.816 UTC unrecognized[44636] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.816 UTC client backend[44636] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.816 UTC client backend[44636] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/index_including_gist 2025-11-30 18:45:06.817 UTC client backend[44633] pg_regress/create_view LOG: connection ready: setup total=6.120 ms, fork=4.622 ms, authentication=0.108 ms 2025-11-30 18:45:06.817 UTC client backend[44636] pg_regress/index_including_gist LOG: connection ready: setup total=2.640 ms, fork=1.343 ms, authentication=0.099 ms 2025-11-30 18:45:06.824 UTC unrecognized[44638] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.824 UTC client backend[44638] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.824 UTC client backend[44638] [unknown] LOG: connection authorized: user=postgres database=regression_pgcrypto application_name=pg_regress/pgp-compression 2025-11-30 18:45:06.825 UTC client backend[44638] pg_regress/pgp-compression LOG: connection ready: setup total=3.698 ms, fork=1.407 ms, authentication=0.117 ms 2025-11-30 18:45:06.826 UTC unrecognized[44637] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.826 UTC client backend[44637] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.826 UTC client backend[44637] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/index_including 2025-11-30 18:45:06.827 UTC client backend[44637] pg_regress/index_including LOG: connection ready: setup total=12.104 ms, fork=10.702 ms, authentication=0.106 ms 2025-11-30 18:45:06.836 UTC client backend[44619] pg_regress LOG: disconnection: session time: 0:00:00.059 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.836 UTC unrecognized[44640] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.837 UTC client backend[44640] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.837 UTC client backend[44640] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_index 2025-11-30 18:45:06.838 UTC client backend[44640] pg_regress/create_index LOG: connection ready: setup total=12.408 ms, fork=4.781 ms, authentication=0.137 ms 2025-11-30 18:45:06.845 UTC unrecognized[44642] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.845 UTC client backend[44633] pg_regress/create_view ERROR: relation "noview" does not exist 2025-11-30 18:45:06.845 UTC client backend[44633] pg_regress/create_view STATEMENT: COMMENT ON VIEW noview IS 'no view'; 2025-11-30 18:45:06.847 UTC client backend[44638] pg_regress/pgp-compression LOG: disconnection: session time: 0:00:00.024 user=postgres database=regression_pgcrypto host=[local] 2025-11-30 18:45:06.852 UTC client backend[44642] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.852 UTC client backend[44642] [unknown] LOG: connection authorized: user=postgres database=regression_tablefunc application_name=pg_regress/tablefunc 2025-11-30 18:45:06.853 UTC client backend[44640] pg_regress/create_index ERROR: syntax error at or near "ON" at character 28 2025-11-30 18:45:06.853 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE INDEX IF NOT EXISTS ON onek USING btree(unique1 int4_ops); 2025-11-30 18:45:06.857 UTC client backend[44642] pg_regress/tablefunc LOG: connection ready: setup total=14.697 ms, fork=1.020 ms, authentication=0.127 ms 2025-11-30 18:45:06.859 UTC client backend[44637] pg_regress/index_including ERROR: could not create unique index "tbl_include_unique2_idx_unique" 2025-11-30 18:45:06.859 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2025-11-30 18:45:06.859 UTC client backend[44637] 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-11-30 18:45:06.865 UTC client backend[44642] pg_regress/tablefunc ERROR: number of rows cannot be negative 2025-11-30 18:45:06.865 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT avg(normal_rand)::int, count(*) FROM normal_rand(-1, 250, 0.2); 2025-11-30 18:45:06.867 UTC client backend[44637] pg_regress/index_including ERROR: could not create unique index "tbl_include_unique2_c1_c2_c3_c4_key" 2025-11-30 18:45:06.867 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2025-11-30 18:45:06.867 UTC client backend[44637] pg_regress/index_including STATEMENT: ALTER TABLE tbl_include_unique2 add UNIQUE (c1, c2) INCLUDE (c3, c4); 2025-11-30 18:45:06.887 UTC client backend[44633] pg_regress/create_view ERROR: cannot drop constraint view_base_table_pkey on table view_base_table because other objects depend on it 2025-11-30 18:45:06.887 UTC client backend[44633] pg_regress/create_view DETAIL: view key_dependent_view depends on constraint view_base_table_pkey on table view_base_table 2025-11-30 18:45:06.887 UTC client backend[44633] pg_regress/create_view HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:06.887 UTC client backend[44633] pg_regress/create_view STATEMENT: ALTER TABLE view_base_table DROP CONSTRAINT view_base_table_pkey; 2025-11-30 18:45:06.899 UTC client backend[44637] pg_regress/index_including ERROR: could not create unique index "tbl_include_box_pk_pkey" 2025-11-30 18:45:06.899 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2025-11-30 18:45:06.899 UTC client backend[44637] pg_regress/index_including STATEMENT: ALTER TABLE tbl_include_box_pk add PRIMARY KEY (c1, c2) INCLUDE (c3, c4); 2025-11-30 18:45:06.905 UTC client backend[44637] pg_regress/index_including ERROR: duplicate key value violates unique constraint "covering" 2025-11-30 18:45:06.905 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-11-30 18:45:06.905 UTC client backend[44637] 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-11-30 18:45:06.906 UTC client backend[44633] pg_regress/create_view ERROR: cannot drop columns from view 2025-11-30 18:45:06.906 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a FROM viewtest_tbl WHERE a <> 20; 2025-11-30 18:45:06.912 UTC unrecognized[44646] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab source data query 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc DETAIL: The query must return 3 columns: row_name, category, and value. 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab('SELECT rowid, val FROM ct where rowclass = ''group1'' and (attribute = ''att2'' or attribute = ''att3'') ORDER BY 1,2;') AS ct(row_name text, category_1 text, category_2 text); 2025-11-30 18:45:06.912 UTC client backend[44646] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab return type 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc DETAIL: Return row must have at least two columns. 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab('SELECT rowid, attribute, val FROM ct where rowclass = ''group1'' and (attribute = ''att2'' or attribute = ''att3'') ORDER BY 1,2;') AS ct(row_name text); 2025-11-30 18:45:06.912 UTC client backend[44646] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab return type 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc DETAIL: Source row_name datatype text does not match return row_name datatype integer. 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab('SELECT rowid, attribute, val FROM ct where rowclass = ''group1'' and (attribute = ''att2'' or attribute = ''att3'') ORDER BY 1,2;') AS ct(row_name int, category_1 text, category_2 text); 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab return type 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc DETAIL: Source value datatype text does not match return value datatype integer in column 3. 2025-11-30 18:45:06.912 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab('SELECT rowid, attribute, val FROM ct where rowclass = ''group1'' and (attribute = ''att2'' or attribute = ''att3'') ORDER BY 1,2;') AS ct(row_name text, category_1 text, category_2 int); 2025-11-30 18:45:06.913 UTC client backend[44646] pg_regress LOG: connection ready: setup total=2.874 ms, fork=1.143 ms, authentication=0.121 ms 2025-11-30 18:45:06.915 UTC client backend[44646] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.927 UTC client backend[44633] pg_regress/create_view ERROR: cannot change name of view column "a" to "?column?" 2025-11-30 18:45:06.927 UTC client backend[44633] pg_regress/create_view HINT: Use ALTER VIEW ... RENAME COLUMN ... to change name of view column instead. 2025-11-30 18:45:06.927 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT 1, * FROM viewtest_tbl; 2025-11-30 18:45:06.928 UTC client backend[44633] pg_regress/create_view ERROR: cannot change data type of view column "b" from integer to numeric 2025-11-30 18:45:06.928 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b::numeric, c, d FROM viewtest_tbl; 2025-11-30 18:45:06.931 UTC client backend[44633] pg_regress/create_view ERROR: cannot change data type of view column "c" from numeric(10,1) to numeric(10,2) 2025-11-30 18:45:06.931 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b, c::numeric(10,2), d FROM viewtest_tbl; 2025-11-30 18:45:06.933 UTC client backend[44637] pg_regress/index_including ERROR: duplicate key value violates unique constraint "covering" 2025-11-30 18:45:06.933 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-11-30 18:45:06.933 UTC client backend[44637] 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-11-30 18:45:06.933 UTC client backend[44637] pg_regress/index_including ERROR: null value in column "c2" of relation "tbl" violates not-null constraint 2025-11-30 18:45:06.933 UTC client backend[44637] pg_regress/index_including DETAIL: Failing row contains (1, null, 3, (4,4),(4,4)). 2025-11-30 18:45:06.933 UTC client backend[44637] 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-11-30 18:45:06.945 UTC unrecognized[44649] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.946 UTC client backend[44649] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.946 UTC client backend[44649] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.946 UTC client backend[44649] pg_regress LOG: connection ready: setup total=2.554 ms, fork=1.265 ms, authentication=0.123 ms 2025-11-30 18:45:06.960 UTC unrecognized[44652] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.961 UTC client backend[44652] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:06.961 UTC client backend[44652] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:06.961 UTC client backend[44652] pg_regress LOG: connection ready: setup total=1.806 ms, fork=0.562 ms, authentication=0.125 ms 2025-11-30 18:45:06.962 UTC client backend[44652] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.963 UTC client backend[44633] pg_regress/create_view ERROR: cannot change collation of view column "d" from "C" to "POSIX" 2025-11-30 18:45:06.963 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b, c, d COLLATE "POSIX" FROM viewtest_tbl; 2025-11-30 18:45:06.973 UTC client backend[44649] pg_regress LOG: disconnection: session time: 0:00:00.028 user=postgres database=postgres host=[local] 2025-11-30 18:45:06.980 UTC client backend[44642] pg_regress/tablefunc ERROR: crosstab categories query must return at least one row 2025-11-30 18:45:06.980 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab( 'SELECT rowid, rowdt, attribute, val FROM cth ORDER BY 1', 'SELECT DISTINCT attribute FROM cth WHERE attribute = ''a'' ORDER BY 1') AS c(rowid text, rowdt timestamp, temperature int4, test_result text, test_startdate timestamp, volts float8); 2025-11-30 18:45:06.982 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab categories query 2025-11-30 18:45:06.982 UTC client backend[44642] pg_regress/tablefunc DETAIL: The query must return one column. 2025-11-30 18:45:06.982 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab( 'SELECT rowid, rowdt, attribute, val FROM cth ORDER BY 1', 'SELECT DISTINCT rowdt, attribute FROM cth ORDER BY 2') AS c(rowid text, rowdt timestamp, temperature int4, test_result text, test_startdate timestamp, volts float8); 2025-11-30 18:45:06.982 UTC client backend[44642] pg_regress/tablefunc ERROR: crosstab category value must not be null 2025-11-30 18:45:06.982 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab( 'SELECT rowid, rowdt, attribute, val FROM cth ORDER BY 1', 'SELECT NULL::text') AS c(rowid text, rowdt timestamp, temperature int4, test_result text, test_startdate timestamp, volts float8); 2025-11-30 18:45:06.984 UTC client backend[44637] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_c1_c2_c3_c4_key" 2025-11-30 18:45:06.984 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-11-30 18:45:06.984 UTC client backend[44637] 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-11-30 18:45:06.985 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab source data query 2025-11-30 18:45:06.985 UTC client backend[44642] pg_regress/tablefunc DETAIL: The query must return at least 3 columns: row_name, category, and value. 2025-11-30 18:45:06.985 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab( 'SELECT rowid, attribute FROM cth ORDER BY 1', 'SELECT DISTINCT attribute FROM cth ORDER BY 1') AS c(rowid text, temperature text, test_result text, test_startdate text, volts text); 2025-11-30 18:45:06.986 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab return type 2025-11-30 18:45:06.986 UTC client backend[44642] pg_regress/tablefunc DETAIL: Return row must have 7 columns, not 6. 2025-11-30 18:45:06.986 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab( 'SELECT rowid, rowdt, rowdt, attribute, val FROM cth ORDER BY 1', 'SELECT DISTINCT attribute FROM cth ORDER BY 1') AS c(rowid text, rowdt timestamp, temperature int4, test_result text, test_startdate timestamp, volts float8); 2025-11-30 18:45:06.986 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid crosstab return type 2025-11-30 18:45:06.986 UTC client backend[44642] pg_regress/tablefunc DETAIL: Return row must have at least two columns. 2025-11-30 18:45:06.986 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM crosstab( 'SELECT rowid, attribute, val FROM cth ORDER BY 1', 'SELECT DISTINCT attribute FROM cth ORDER BY 1') AS c(rowid text); 2025-11-30 18:45:06.986 UTC client backend[44633] pg_regress/create_view ERROR: cannot create temporary relation in non-temporary schema 2025-11-30 18:45:06.986 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE VIEW temp_view_test.v3_temp AS SELECT * FROM temp_table; 2025-11-30 18:45:06.989 UTC client backend[44633] pg_regress/create_view ERROR: cannot create temporary relation in non-temporary schema 2025-11-30 18:45:06.989 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE SCHEMA test_view_schema CREATE TEMP VIEW testview AS SELECT 1; 2025-11-30 18:45:06.991 UTC client backend[44637] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_pkey" 2025-11-30 18:45:06.991 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-11-30 18:45:06.991 UTC client backend[44637] 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-11-30 18:45:06.992 UTC client backend[44640] pg_regress/create_index ERROR: relation "six_wrong" does not exist 2025-11-30 18:45:06.992 UTC client backend[44640] pg_regress/create_index STATEMENT: COMMENT ON INDEX six_wrong IS 'bad index'; 2025-11-30 18:45:06.993 UTC client backend[44637] pg_regress/index_including ERROR: null value in column "c2" of relation "tbl" violates not-null constraint 2025-11-30 18:45:06.993 UTC client backend[44637] pg_regress/index_including DETAIL: Failing row contains (1, null, 3, (4,4),(4,4)). 2025-11-30 18:45:06.993 UTC client backend[44637] 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-11-30 18:45:06.999 UTC unrecognized[44656] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:06.999 UTC unrecognized[44655] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.000 UTC client backend[44656] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.000 UTC client backend[44656] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_tcn application_name=pg_regress 2025-11-30 18:45:07.000 UTC client backend[44655] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.000 UTC client backend[44655] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.001 UTC client backend[44655] pg_regress LOG: connection ready: setup total=3.474 ms, fork=1.404 ms, authentication=0.109 ms 2025-11-30 18:45:07.004 UTC client backend[44656] pg_regress LOG: connection ready: setup total=6.064 ms, fork=0.897 ms, authentication=0.121 ms 2025-11-30 18:45:07.010 UTC client backend[44656] pg_regress LOG: disconnection: session time: 0:00:00.010 user=postgres database=isolation_regression_tcn host=[local] 2025-11-30 18:45:07.015 UTC client backend[44642] pg_regress/tablefunc ERROR: infinite recursion detected 2025-11-30 18:45:07.015 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0, '~') AS t(keyid int, parent_keyid int, level int, branch text); 2025-11-30 18:45:07.017 UTC client backend[44655] pg_regress LOG: disconnection: session time: 0:00:00.017 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.018 UTC client backend[44637] pg_regress/index_including ERROR: conflicting key value violates exclusion constraint "tbl_c1_c3_c4_excl" 2025-11-30 18:45:07.018 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1)=(1) conflicts with existing key (c1)=(1). 2025-11-30 18:45:07.018 UTC client backend[44637] 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-11-30 18:45:07.020 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.020 UTC client backend[44642] pg_regress/tablefunc DETAIL: Source key type integer does not match return key type text. 2025-11-30 18:45:07.020 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0, '~') AS t(keyid text, parent_keyid int, level int, branch text); 2025-11-30 18:45:07.021 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.021 UTC client backend[44642] pg_regress/tablefunc DETAIL: Source key type integer does not match return key type double precision. 2025-11-30 18:45:07.021 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0, '~') AS t(keyid float8, parent_keyid float8, level int, branch text); 2025-11-30 18:45:07.023 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.023 UTC client backend[44642] pg_regress/tablefunc DETAIL: Source parent key type integer does not match return parent key type double precision. 2025-11-30 18:45:07.023 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0, '~') AS t(keyid int, parent_keyid float8, level int, branch text); 2025-11-30 18:45:07.026 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.026 UTC client backend[44642] pg_regress/tablefunc DETAIL: Return row must have 3 columns, not 4. 2025-11-30 18:45:07.026 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0) AS t(keyid int, parent_keyid int, level int, branch text); 2025-11-30 18:45:07.029 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.029 UTC client backend[44642] pg_regress/tablefunc DETAIL: Return row must have 4 columns, not 3. 2025-11-30 18:45:07.029 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0, '~') AS t(keyid int, parent_keyid int, level int); 2025-11-30 18:45:07.031 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.031 UTC client backend[44642] pg_regress/tablefunc DETAIL: Source parent key type integer does not match return parent key type text. 2025-11-30 18:45:07.031 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0) AS t(keyid int, parent_keyid text, level int); 2025-11-30 18:45:07.034 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.034 UTC client backend[44642] pg_regress/tablefunc DETAIL: Third return column (depth) must be type integer. 2025-11-30 18:45:07.034 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0, '~') AS t(keyid int, parent_keyid int, level float, branch float); 2025-11-30 18:45:07.036 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.036 UTC client backend[44642] pg_regress/tablefunc DETAIL: Fourth return column (branch) must be type text. 2025-11-30 18:45:07.036 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', 'keyid', 'parent_keyid', '2', 0, '~') AS t(keyid int, parent_keyid int, level int, branch float); 2025-11-30 18:45:07.042 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.042 UTC client backend[44642] pg_regress/tablefunc DETAIL: Fifth return column (serial) must be type integer. 2025-11-30 18:45:07.042 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_text', 'keyid', 'parent_keyid', 'pos', 'row2', 0, '~') AS t(keyid text, parent_keyid text, level int, branch text, pos text); 2025-11-30 18:45:07.046 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby return type 2025-11-30 18:45:07.046 UTC client backend[44642] pg_regress/tablefunc DETAIL: Fourth return column (serial) must be type integer. 2025-11-30 18:45:07.046 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_text', 'keyid', 'parent_keyid', 'pos', 'row2', 0) AS t(keyid text, parent_keyid text, level int, pos text); 2025-11-30 18:45:07.049 UTC client backend[44642] pg_regress/tablefunc ERROR: invalid connectby source data query 2025-11-30 18:45:07.049 UTC client backend[44642] pg_regress/tablefunc DETAIL: The query must return at least two columns. 2025-11-30 18:45:07.049 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', '1; --', 'parent_keyid', '2', 0) AS t(keyid int, parent_keyid int, level int); 2025-11-30 18:45:07.049 UTC client backend[44637] pg_regress/index_including ERROR: cannot alter statistics on non-expression column "c1" of index "tbl_idx" 2025-11-30 18:45:07.049 UTC client backend[44637] pg_regress/index_including HINT: Alter statistics on table column instead. 2025-11-30 18:45:07.049 UTC client backend[44637] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 1 SET STATISTICS 1000; 2025-11-30 18:45:07.052 UTC client backend[44642] pg_regress/tablefunc ERROR: infinite recursion detected 2025-11-30 18:45:07.052 UTC client backend[44642] pg_regress/tablefunc STATEMENT: SELECT * FROM connectby('connectby_int', '1::int, NULL::int; --', 'parent_keyid', '2', 0) AS t(keyid int, parent_keyid int, level int); 2025-11-30 18:45:07.052 UTC client backend[44637] pg_regress/index_including ERROR: cannot alter statistics on included column "c2" of index "tbl_idx" 2025-11-30 18:45:07.052 UTC client backend[44637] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 3 SET STATISTICS 1000; 2025-11-30 18:45:07.052 UTC client backend[44637] pg_regress/index_including ERROR: column number 4 of relation "tbl_idx" does not exist 2025-11-30 18:45:07.052 UTC client backend[44637] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 4 SET STATISTICS 1000; 2025-11-30 18:45:07.054 UTC unrecognized[44660] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.054 UTC client backend[44660] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.054 UTC client backend[44660] [unknown] LOG: connection authorized: user=postgres database=regression_tsm_system_rows application_name=pg_regress/tsm_system_rows 2025-11-30 18:45:07.059 UTC client backend[44660] pg_regress/tsm_system_rows LOG: connection ready: setup total=15.063 ms, fork=3.446 ms, authentication=0.122 ms 2025-11-30 18:45:07.062 UTC unrecognized[44663] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.070 UTC client backend[44663] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.070 UTC client backend[44663] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_tcn application_name=isolation/tcn 2025-11-30 18:45:07.071 UTC unrecognized[44664] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.071 UTC client backend[44663] isolation/tcn LOG: connection ready: setup total=9.826 ms, fork=1.204 ms, authentication=0.134 ms 2025-11-30 18:45:07.071 UTC client backend[44664] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.071 UTC client backend[44664] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.072 UTC client backend[44664] pg_regress LOG: connection ready: setup total=2.395 ms, fork=0.842 ms, authentication=0.108 ms 2025-11-30 18:45:07.073 UTC client backend[44664] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.077 UTC client backend[44660] pg_regress/tsm_system_rows ERROR: sample size must not be negative 2025-11-30 18:45:07.077 UTC client backend[44660] pg_regress/tsm_system_rows STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE system_rows (-1); 2025-11-30 18:45:07.077 UTC client backend[44660] pg_regress/tsm_system_rows ERROR: tablesample method system_rows does not support REPEATABLE at character 44 2025-11-30 18:45:07.077 UTC client backend[44660] pg_regress/tsm_system_rows STATEMENT: SELECT * FROM test_tablesample TABLESAMPLE system_rows (10) REPEATABLE (0); 2025-11-30 18:45:07.082 UTC unrecognized[44666] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.082 UTC client backend[44666] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.082 UTC client backend[44666] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.083 UTC client backend[44660] pg_regress/tsm_system_rows ERROR: cannot drop extension tsm_system_rows because other objects depend on it 2025-11-30 18:45:07.083 UTC client backend[44660] pg_regress/tsm_system_rows DETAIL: view vv depends on function system_rows(internal) 2025-11-30 18:45:07.083 UTC client backend[44660] pg_regress/tsm_system_rows HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:07.083 UTC client backend[44660] pg_regress/tsm_system_rows STATEMENT: DROP EXTENSION tsm_system_rows; 2025-11-30 18:45:07.083 UTC client backend[44666] pg_regress LOG: connection ready: setup total=2.523 ms, fork=1.227 ms, authentication=0.127 ms 2025-11-30 18:45:07.083 UTC client backend[44660] pg_regress/tsm_system_rows LOG: disconnection: session time: 0:00:00.035 user=postgres database=regression_tsm_system_rows host=[local] 2025-11-30 18:45:07.086 UTC unrecognized[44667] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.095 UTC client backend[44666] pg_regress LOG: disconnection: session time: 0:00:00.013 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.098 UTC client backend[44667] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.098 UTC client backend[44667] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_tcn application_name=isolation/tcn 2025-11-30 18:45:07.099 UTC client backend[44667] isolation/tcn LOG: connection ready: setup total=16.365 ms, fork=2.884 ms, authentication=0.136 ms 2025-11-30 18:45:07.109 UTC client backend[44642] pg_regress/tablefunc LOG: disconnection: session time: 0:00:00.265 user=postgres database=regression_tablefunc host=[local] 2025-11-30 18:45:07.111 UTC unrecognized[44671] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.111 UTC client backend[44671] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.111 UTC client backend[44671] [unknown] LOG: connection authorized: user=postgres database=regression_tsm_system_time application_name=pg_regress/tsm_system_time 2025-11-30 18:45:07.116 UTC client backend[44671] pg_regress/tsm_system_time LOG: connection ready: setup total=12.903 ms, fork=5.568 ms, authentication=0.120 ms 2025-11-30 18:45:07.117 UTC client backend[44633] pg_regress/create_view ERROR: invalid value for boolean option "security_barrier": 100 2025-11-30 18:45:07.117 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE VIEW mysecview5 WITH (security_barrier=100) -- Error AS SELECT * FROM tbl1 WHERE a > 100; 2025-11-30 18:45:07.117 UTC client backend[44633] pg_regress/create_view ERROR: unrecognized parameter "invalid_option" 2025-11-30 18:45:07.117 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE VIEW mysecview6 WITH (invalid_option) -- Error AS SELECT * FROM tbl1 WHERE a < 100; 2025-11-30 18:45:07.121 UTC client backend[44633] pg_regress/create_view ERROR: invalid value for boolean option "security_invoker": 100 2025-11-30 18:45:07.121 UTC client backend[44633] pg_regress/create_view STATEMENT: CREATE VIEW mysecview10 WITH (security_invoker=100) -- Error AS SELECT * FROM tbl1 WHERE a <> 100; 2025-11-30 18:45:07.135 UTC client backend[44671] pg_regress/tsm_system_time ERROR: sample collection time must not be negative 2025-11-30 18:45:07.135 UTC client backend[44671] pg_regress/tsm_system_time STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE system_time (-1); 2025-11-30 18:45:07.135 UTC client backend[44671] pg_regress/tsm_system_time ERROR: tablesample method system_time does not support REPEATABLE at character 44 2025-11-30 18:45:07.135 UTC client backend[44671] pg_regress/tsm_system_time STATEMENT: SELECT * FROM test_tablesample TABLESAMPLE system_time (10) REPEATABLE (0); 2025-11-30 18:45:07.137 UTC client backend[44637] pg_regress/index_including ERROR: relation "tbl_c1_c2_c3_c4_key" does not exist 2025-11-30 18:45:07.137 UTC client backend[44637] pg_regress/index_including STATEMENT: REINDEX INDEX tbl_c1_c2_c3_c4_key; 2025-11-30 18:45:07.141 UTC client backend[44671] pg_regress/tsm_system_time ERROR: cannot drop extension tsm_system_time because other objects depend on it 2025-11-30 18:45:07.141 UTC client backend[44671] pg_regress/tsm_system_time DETAIL: view vv depends on function system_time(internal) 2025-11-30 18:45:07.141 UTC client backend[44671] pg_regress/tsm_system_time HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:07.141 UTC client backend[44671] pg_regress/tsm_system_time STATEMENT: DROP EXTENSION tsm_system_time; 2025-11-30 18:45:07.142 UTC client backend[44671] pg_regress/tsm_system_time LOG: disconnection: session time: 0:00:00.032 user=postgres database=regression_tsm_system_time host=[local] 2025-11-30 18:45:07.148 UTC client backend[44636] pg_regress/index_including_gist ERROR: conflicting key value violates exclusion constraint "tbl_gist_c4_c1_c2_c3_excl" 2025-11-30 18:45:07.148 UTC client backend[44636] pg_regress/index_including_gist DETAIL: Key (c4)=((4,5),(2,3)) conflicts with existing key (c4)=((2,3),(1,2)). 2025-11-30 18:45:07.148 UTC client backend[44636] 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-11-30 18:45:07.170 UTC client backend[44636] pg_regress/index_including_gist LOG: disconnection: session time: 0:00:00.353 user=postgres database=regression host=[local] 2025-11-30 18:45:07.172 UTC unrecognized[44676] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.173 UTC client backend[44676] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.173 UTC client backend[44676] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.174 UTC client backend[44676] pg_regress LOG: connection ready: setup total=13.293 ms, fork=11.416 ms, authentication=0.126 ms 2025-11-30 18:45:07.176 UTC client backend[44676] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.178 UTC client backend[44663] isolation/tcn/control connection LOG: disconnection: session time: 0:00:00.115 user=postgres database=isolation_regression_tcn host=[local] 2025-11-30 18:45:07.178 UTC client backend[44667] isolation/tcn/s1 LOG: disconnection: session time: 0:00:00.092 user=postgres database=isolation_regression_tcn host=[local] 2025-11-30 18:45:07.184 UTC client backend[44637] pg_regress/index_including ERROR: access method "brin" does not support included columns 2025-11-30 18:45:07.184 UTC client backend[44637] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING brin(c1, c2) INCLUDE (c3, c4); 2025-11-30 18:45:07.186 UTC unrecognized[44680] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.187 UTC client backend[44680] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.187 UTC client backend[44680] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.188 UTC client backend[44680] pg_regress LOG: connection ready: setup total=3.877 ms, fork=1.539 ms, authentication=0.136 ms 2025-11-30 18:45:07.199 UTC client backend[44637] pg_regress/index_including ERROR: access method "gin" does not support included columns 2025-11-30 18:45:07.199 UTC client backend[44637] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING gin(c1, c2) INCLUDE (c3, c4); 2025-11-30 18:45:07.202 UTC client backend[44680] pg_regress LOG: disconnection: session time: 0:00:00.016 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.203 UTC client backend[44637] pg_regress/index_including ERROR: access method "hash" does not support included columns 2025-11-30 18:45:07.203 UTC client backend[44637] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING hash(c1, c2) INCLUDE (c3, c4); 2025-11-30 18:45:07.223 UTC client backend[44602] postgres_fdw LOG: disconnection: session time: 0:00:00.612 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:07.240 UTC unrecognized[44686] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.240 UTC client backend[44686] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.240 UTC client backend[44686] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:07.241 UTC client backend[44686] postgres_fdw LOG: connection ready: setup total=2.723 ms, fork=1.314 ms, authentication=0.128 ms 2025-11-30 18:45:07.248 UTC client backend[44686] postgres_fdw LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:07.249 UTC unrecognized[44684] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.249 UTC client backend[44684] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.249 UTC client backend[44684] [unknown] LOG: connection authorized: user=postgres database=regression_unaccent application_name=pg_regress/unaccent 2025-11-30 18:45:07.254 UTC client backend[44684] pg_regress/unaccent LOG: connection ready: setup total=18.707 ms, fork=13.576 ms, authentication=0.127 ms 2025-11-30 18:45:07.254 UTC unrecognized[44690] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.255 UTC client backend[44690] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.255 UTC client backend[44690] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.255 UTC client backend[44690] pg_regress LOG: connection ready: setup total=7.011 ms, fork=5.747 ms, authentication=0.113 ms 2025-11-30 18:45:07.256 UTC client backend[44690] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.265 UTC unrecognized[44691] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.265 UTC client backend[44691] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.265 UTC client backend[44691] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:07.265 UTC client backend[44637] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_idx_unique" 2025-11-30 18:45:07.265 UTC client backend[44637] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-11-30 18:45:07.265 UTC client backend[44637] pg_regress/index_including STATEMENT: UPDATE tbl SET c2 = 2 WHERE c1 = 1; 2025-11-30 18:45:07.266 UTC client backend[44691] postgres_fdw LOG: connection ready: setup total=10.541 ms, fork=9.121 ms, authentication=0.125 ms 2025-11-30 18:45:07.280 UTC client backend[44684] pg_regress/unaccent LOG: disconnection: session time: 0:00:00.031 user=postgres database=regression_unaccent host=[local] 2025-11-30 18:45:07.285 UTC unrecognized[44696] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.286 UTC client backend[44696] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.286 UTC client backend[44696] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.287 UTC client backend[44696] pg_regress LOG: connection ready: setup total=1.802 ms, fork=0.514 ms, authentication=0.120 ms 2025-11-30 18:45:07.293 UTC unrecognized[44697] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.293 UTC client backend[44697] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.293 UTC client backend[44697] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.294 UTC client backend[44697] pg_regress LOG: connection ready: setup total=3.871 ms, fork=2.444 ms, authentication=0.124 ms 2025-11-30 18:45:07.294 UTC unrecognized[44698] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.294 UTC client backend[44698] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.294 UTC client backend[44698] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.294 UTC client backend[44697] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.295 UTC client backend[44698] pg_regress LOG: connection ready: setup total=1.533 ms, fork=0.348 ms, authentication=0.115 ms 2025-11-30 18:45:07.295 UTC client backend[44698] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.310 UTC client backend[44640] pg_regress/create_index ERROR: duplicate key value violates unique constraint "unique_idx2" 2025-11-30 18:45:07.310 UTC client backend[44640] pg_regress/create_index DETAIL: Key (i)=(null) already exists. 2025-11-30 18:45:07.310 UTC client backend[44640] pg_regress/create_index STATEMENT: INSERT INTO unique_tbl (t) VALUES ('seven'); 2025-11-30 18:45:07.310 UTC unrecognized[44701] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.311 UTC client backend[44701] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.311 UTC client backend[44701] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.311 UTC client backend[44696] pg_regress LOG: disconnection: session time: 0:00:00.025 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.312 UTC client backend[44701] pg_regress LOG: connection ready: setup total=10.234 ms, fork=8.754 ms, authentication=0.127 ms 2025-11-30 18:45:07.312 UTC unrecognized[44702] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.312 UTC client backend[44702] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.312 UTC client backend[44702] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.313 UTC client backend[44702] pg_regress LOG: connection ready: setup total=9.731 ms, fork=7.130 ms, authentication=0.105 ms 2025-11-30 18:45:07.319 UTC unrecognized[44704] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.320 UTC client backend[44704] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.320 UTC client backend[44704] [unknown] LOG: connection authorized: user=postgres database=regression_uuid-ossp application_name=pg_regress/uuid_ossp 2025-11-30 18:45:07.324 UTC client backend[44704] pg_regress/uuid_ossp LOG: connection ready: setup total=5.679 ms, fork=0.442 ms, authentication=0.165 ms 2025-11-30 18:45:07.352 UTC client backend[44640] pg_regress/create_index ERROR: could not create unique index "unique_idx4" 2025-11-30 18:45:07.352 UTC client backend[44640] pg_regress/create_index DETAIL: Key (i)=(null) is duplicated. 2025-11-30 18:45:07.352 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX unique_idx4 ON unique_tbl (i) NULLS NOT DISTINCT; 2025-11-30 18:45:07.358 UTC client backend[44637] pg_regress/index_including LOG: disconnection: session time: 0:00:00.532 user=postgres database=regression host=[local] 2025-11-30 18:45:07.365 UTC unrecognized[44708] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.366 UTC client backend[44708] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.366 UTC client backend[44708] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.367 UTC client backend[44708] pg_regress LOG: connection ready: setup total=2.630 ms, fork=0.466 ms, authentication=0.125 ms 2025-11-30 18:45:07.371 UTC client backend[44708] pg_regress LOG: disconnection: session time: 0:00:00.005 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.378 UTC client backend[44640] pg_regress/create_index ERROR: duplicate key value violates unique constraint "func_index_index" 2025-11-30 18:45:07.378 UTC client backend[44640] pg_regress/create_index DETAIL: Key (textcat(f1, f2))=(ABCDEF) already exists. 2025-11-30 18:45:07.378 UTC client backend[44640] pg_regress/create_index STATEMENT: INSERT INTO func_index_heap VALUES('ABCD', 'EF'); 2025-11-30 18:45:07.381 UTC unrecognized[44710] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.381 UTC client backend[44710] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.381 UTC client backend[44710] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.382 UTC client backend[44710] pg_regress LOG: connection ready: setup total=1.921 ms, fork=0.657 ms, authentication=0.120 ms 2025-11-30 18:45:07.393 UTC client backend[44710] pg_regress LOG: disconnection: session time: 0:00:00.012 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.395 UTC client backend[44640] pg_regress/create_index ERROR: duplicate key value violates unique constraint "func_index_index" 2025-11-30 18:45:07.395 UTC client backend[44640] pg_regress/create_index DETAIL: Key ((f1 || f2))=(ABCDEF) already exists. 2025-11-30 18:45:07.395 UTC client backend[44640] pg_regress/create_index STATEMENT: INSERT INTO func_index_heap VALUES('ABCD', 'EF'); 2025-11-30 18:45:07.396 UTC client backend[44701] pg_regress LOG: disconnection: session time: 0:00:00.085 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.398 UTC client backend[44702] pg_regress LOG: disconnection: session time: 0:00:00.088 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.403 UTC unrecognized[44715] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.403 UTC unrecognized[44716] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.403 UTC client backend[44715] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.403 UTC client backend[44715] [unknown] LOG: connection authorized: user=postgres database=regression_xml2 application_name=pg_regress/xml2 2025-11-30 18:45:07.403 UTC client backend[44716] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.403 UTC client backend[44716] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_delay_execution application_name=isolation/partition-addition 2025-11-30 18:45:07.408 UTC client backend[44715] pg_regress/xml2 LOG: connection ready: setup total=6.307 ms, fork=0.734 ms, authentication=0.125 ms 2025-11-30 18:45:07.409 UTC client backend[44640] pg_regress/create_index ERROR: column "row" has pseudo-type record 2025-11-30 18:45:07.409 UTC client backend[44640] pg_regress/create_index STATEMENT: create index on func_index_heap ((f1 || f2), (row(f1, f2))); 2025-11-30 18:45:07.414 UTC client backend[44640] pg_regress/create_index ERROR: duplicate key value violates unique constraint "covering_index_index" 2025-11-30 18:45:07.414 UTC client backend[44640] pg_regress/create_index DETAIL: Key (f1, f2)=(1, 2) already exists. 2025-11-30 18:45:07.414 UTC client backend[44640] pg_regress/create_index STATEMENT: INSERT INTO covering_index_heap VALUES(1,2,'BBB'); 2025-11-30 18:45:07.423 UTC unrecognized[44718] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.424 UTC client backend[44718] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.424 UTC client backend[44718] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_brin application_name=isolation/summarization-and-inprogress-insertion 2025-11-30 18:45:07.428 UTC client backend[44716] isolation/partition-addition LOG: connection ready: setup total=26.259 ms, fork=0.567 ms, authentication=0.110 ms 2025-11-30 18:45:07.429 UTC client backend[44718] isolation/summarization-and-inprogress-insertion LOG: connection ready: setup total=6.501 ms, fork=1.005 ms, authentication=0.118 ms 2025-11-30 18:45:07.432 UTC unrecognized[44719] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.434 UTC unrecognized[44720] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.435 UTC client backend[44720] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.435 UTC client backend[44720] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_brin application_name=isolation/summarization-and-inprogress-insertion 2025-11-30 18:45:07.436 UTC client backend[44719] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.436 UTC client backend[44719] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_delay_execution application_name=isolation/partition-addition 2025-11-30 18:45:07.436 UTC client backend[44720] isolation/summarization-and-inprogress-insertion LOG: connection ready: setup total=2.110 ms, fork=0.710 ms, authentication=0.113 ms 2025-11-30 18:45:07.437 UTC client backend[44719] isolation/partition-addition LOG: connection ready: setup total=6.024 ms, fork=1.566 ms, authentication=0.107 ms 2025-11-30 18:45:07.439 UTC client backend[44704] pg_regress/uuid_ossp LOG: disconnection: session time: 0:00:00.119 user=postgres database=regression_uuid-ossp host=[local] 2025-11-30 18:45:07.440 UTC client backend[44640] pg_regress/create_index ERROR: duplicate key value violates unique constraint "concur_index2" 2025-11-30 18:45:07.440 UTC client backend[44640] pg_regress/create_index DETAIL: Key (f1)=(b) already exists. 2025-11-30 18:45:07.440 UTC client backend[44640] pg_regress/create_index STATEMENT: INSERT INTO concur_heap VALUES ('b','x'); 2025-11-30 18:45:07.441 UTC client backend[44640] pg_regress/create_index ERROR: could not create unique index "concur_index3" 2025-11-30 18:45:07.441 UTC client backend[44640] pg_regress/create_index DETAIL: Key (f2)=(b) is duplicated. 2025-11-30 18:45:07.441 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX CONCURRENTLY concur_index3 ON concur_heap(f2); 2025-11-30 18:45:07.442 UTC unrecognized[44722] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.443 UTC client backend[44722] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.443 UTC client backend[44722] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_delay_execution application_name=isolation/partition-addition 2025-11-30 18:45:07.444 UTC client backend[44722] isolation/partition-addition LOG: connection ready: setup total=2.059 ms, fork=0.493 ms, authentication=0.104 ms 2025-11-30 18:45:07.445 UTC unrecognized[44723] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.445 UTC client backend[44723] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.445 UTC client backend[44723] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_brin application_name=isolation/summarization-and-inprogress-insertion 2025-11-30 18:45:07.447 UTC client backend[44723] isolation/summarization-and-inprogress-insertion LOG: connection ready: setup total=3.126 ms, fork=0.696 ms, authentication=0.105 ms 2025-11-30 18:45:07.448 UTC client backend[44640] pg_regress/create_index ERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:07.448 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE INDEX CONCURRENTLY concur_index7 ON concur_heap(f1); runtime error: element output File write for 0wn3d.txt refused runtime error: element output xsltDocumentElem: write rights for 0wn3d.txt denied 2025-11-30 18:45:07.462 UTC client backend[44715] pg_regress/xml2 ERROR: failed to apply stylesheet 2025-11-30 18:45:07.462 UTC client backend[44715] pg_regress/xml2 STATEMENT: SELECT xslt_process('Hello from XML', $$ $$); 2025-11-30 18:45:07.462 UTC client backend[44715] pg_regress/xml2 LOG: disconnection: session time: 0:00:00.059 user=postgres database=regression_xml2 host=[local] 2025-11-30 18:45:07.462 UTC client backend[44633] pg_regress/create_view ERROR: cannot drop column f3 of table tt14t because other objects depend on it 2025-11-30 18:45:07.462 UTC client backend[44633] pg_regress/create_view DETAIL: view tt14v depends on column f3 of table tt14t 2025-11-30 18:45:07.462 UTC client backend[44633] pg_regress/create_view HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:07.462 UTC client backend[44633] pg_regress/create_view STATEMENT: alter table tt14t drop column f3; 2025-11-30 18:45:07.464 UTC client backend[44633] pg_regress/create_view ERROR: attribute 3 of type record has been dropped 2025-11-30 18:45:07.464 UTC client backend[44633] pg_regress/create_view STATEMENT: select * from tt14v; 2025-11-30 18:45:07.465 UTC client backend[44633] pg_regress/create_view ERROR: cannot alter type of a column used by a view or rule 2025-11-30 18:45:07.465 UTC client backend[44633] pg_regress/create_view DETAIL: rule _RETURN on view tt14v depends on column "f4" 2025-11-30 18:45:07.465 UTC client backend[44633] pg_regress/create_view STATEMENT: alter table tt14t alter column f4 type integer using f4::integer; 2025-11-30 18:45:07.474 UTC client backend[44633] pg_regress/create_view ERROR: attribute 4 of type record has wrong type 2025-11-30 18:45:07.474 UTC client backend[44633] pg_regress/create_view DETAIL: Table has type integer, but query expects text. 2025-11-30 18:45:07.474 UTC client backend[44633] pg_regress/create_view STATEMENT: select * from tt14v; 2025-11-30 18:45:07.475 UTC client backend[44634] pg_regress/create_index_spgist LOG: disconnection: session time: 0:00:00.661 user=postgres database=regression host=[local] 2025-11-30 18:45:07.490 UTC client backend[44718] isolation/summarization-and-inprogress-insertion/control connec LOG: disconnection: session time: 0:00:00.066 user=postgres database=isolation_regression_brin host=[local] 2025-11-30 18:45:07.492 UTC client backend[44720] isolation/summarization-and-inprogress-insertion/s1 LOG: disconnection: session time: 0:00:00.057 user=postgres database=isolation_regression_brin host=[local] 2025-11-30 18:45:07.493 UTC client backend[44723] isolation/summarization-and-inprogress-insertion/s2 LOG: disconnection: session time: 0:00:00.048 user=postgres database=isolation_regression_brin host=[local] 2025-11-30 18:45:07.508 UTC client backend[44640] pg_regress/create_index ERROR: could not create unique index "concur_index3" 2025-11-30 18:45:07.508 UTC client backend[44640] pg_regress/create_index DETAIL: Key (f2)=(b) is duplicated. 2025-11-30 18:45:07.508 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE concur_heap; 2025-11-30 18:45:07.508 UTC client backend[44716] isolation/partition-addition/control connection LOG: disconnection: session time: 0:00:00.105 user=postgres database=isolation_regression_delay_execution host=[local] 2025-11-30 18:45:07.511 UTC client backend[44633] pg_regress/create_view ERROR: operator does not exist: text = text[] at character 20 2025-11-30 18:45:07.511 UTC client backend[44633] pg_regress/create_view DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:07.511 UTC client backend[44633] pg_regress/create_view HINT: You might need to add explicit type casts. 2025-11-30 18:45:07.511 UTC client backend[44633] pg_regress/create_view STATEMENT: select 'foo'::text = any((select array['abc','def','foo']::text[])); 2025-11-30 18:45:07.511 UTC client backend[44719] isolation/partition-addition/s1 LOG: disconnection: session time: 0:00:00.078 user=postgres database=isolation_regression_delay_execution host=[local] 2025-11-30 18:45:07.512 UTC client backend[44722] isolation/partition-addition/s2 LOG: disconnection: session time: 0:00:00.070 user=postgres database=isolation_regression_delay_execution host=[local] 2025-11-30 18:45:07.520 UTC unrecognized[44733] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.521 UTC client backend[44733] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.521 UTC client backend[44733] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.521 UTC client backend[44733] pg_regress LOG: connection ready: setup total=2.085 ms, fork=0.754 ms, authentication=0.121 ms 2025-11-30 18:45:07.526 UTC client backend[44733] pg_regress LOG: disconnection: session time: 0:00:00.006 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.539 UTC unrecognized[44737] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.539 UTC client backend[44737] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.539 UTC client backend[44737] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.540 UTC client backend[44737] pg_regress LOG: connection ready: setup total=2.188 ms, fork=0.886 ms, authentication=0.121 ms 2025-11-30 18:45:07.540 UTC client backend[44737] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.549 UTC unrecognized[44742] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.550 UTC client backend[44742] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.550 UTC client backend[44742] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.550 UTC client backend[44640] pg_regress/create_index ERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:07.550 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE INDEX CONCURRENTLY concur_temp_ind ON concur_temp(f1); 2025-11-30 18:45:07.551 UTC client backend[44742] pg_regress LOG: connection ready: setup total=2.361 ms, fork=1.084 ms, authentication=0.112 ms 2025-11-30 18:45:07.556 UTC unrecognized[44744] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.556 UTC client backend[44744] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.556 UTC client backend[44744] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.557 UTC client backend[44633] pg_regress/create_view ERROR: access to non-system view "tt27v" is restricted 2025-11-30 18:45:07.557 UTC client backend[44633] pg_regress/create_view STATEMENT: select a from tt27v where a > 0; 2025-11-30 18:45:07.557 UTC client backend[44633] pg_regress/create_view ERROR: access to non-system view "tt27v" is restricted 2025-11-30 18:45:07.557 UTC client backend[44633] pg_regress/create_view STATEMENT: insert into tt27v values (1); 2025-11-30 18:45:07.557 UTC client backend[44744] pg_regress LOG: connection ready: setup total=1.614 ms, fork=0.354 ms, authentication=0.114 ms 2025-11-30 18:45:07.557 UTC client backend[44744] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.565 UTC unrecognized[44746] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.565 UTC client backend[44746] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.565 UTC client backend[44746] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.566 UTC client backend[44746] pg_regress LOG: connection ready: setup total=1.698 ms, fork=0.375 ms, authentication=0.120 ms 2025-11-30 18:45:07.573 UTC unrecognized[44738] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.573 UTC client backend[44738] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.573 UTC client backend[44738] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_delay_execution application_name=isolation/partition-removal-1 2025-11-30 18:45:07.574 UTC client backend[44738] isolation/partition-removal-1 LOG: connection ready: setup total=36.406 ms, fork=34.708 ms, authentication=0.138 ms 2025-11-30 18:45:07.574 UTC unrecognized[44739] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.575 UTC client backend[44739] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.575 UTC client backend[44739] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.576 UTC client backend[44739] pg_regress LOG: connection ready: setup total=37.466 ms, fork=34.555 ms, authentication=0.118 ms 2025-11-30 18:45:07.584 UTC client backend[44742] pg_regress LOG: disconnection: session time: 0:00:00.034 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.586 UTC client backend[44746] pg_regress LOG: disconnection: session time: 0:00:00.021 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.587 UTC client backend[44640] pg_regress/create_index ERROR: DROP INDEX CONCURRENTLY does not support dropping multiple objects 2025-11-30 18:45:07.587 UTC client backend[44640] pg_regress/create_index STATEMENT: DROP INDEX CONCURRENTLY "concur_index2", "concur_index3"; 2025-11-30 18:45:07.591 UTC client backend[44640] pg_regress/create_index ERROR: DROP INDEX CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:07.591 UTC client backend[44640] pg_regress/create_index STATEMENT: DROP INDEX CONCURRENTLY "concur_index5"; 2025-11-30 18:45:07.591 UTC unrecognized[44747] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.592 UTC client backend[44747] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.592 UTC client backend[44747] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_delay_execution application_name=isolation/partition-removal-1 2025-11-30 18:45:07.593 UTC client backend[44747] isolation/partition-removal-1 LOG: connection ready: setup total=16.234 ms, fork=0.868 ms, authentication=0.123 ms 2025-11-30 18:45:07.594 UTC client backend[44739] pg_regress LOG: disconnection: session time: 0:00:00.021 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.599 UTC unrecognized[44751] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.599 UTC client backend[44751] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.599 UTC client backend[44751] [unknown] LOG: connection authorized: user=postgres database=regression_dummy_seclabel application_name=pg_regress/dummy_seclabel 2025-11-30 18:45:07.602 UTC unrecognized[44749] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.602 UTC client backend[44749] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.602 UTC client backend[44749] [unknown] LOG: connection authorized: user=postgres database=regression_gin application_name=pg_regress/gin_incomplete_splits 2025-11-30 18:45:07.604 UTC client backend[44751] pg_regress/dummy_seclabel LOG: connection ready: setup total=5.723 ms, fork=0.316 ms, authentication=0.111 ms 2025-11-30 18:45:07.604 UTC unrecognized[44753] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.607 UTC client backend[44749] pg_regress/gin_incomplete_splits LOG: connection ready: setup total=16.351 ms, fork=11.251 ms, authentication=0.115 ms 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: column name must be qualified 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON COLUMN dummy_seclabel_tbl1 IS 'unclassified'; 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: '...invalid label...' is not a valid security label 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS '...invalid label...'; 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: security label provider "unknown_seclabel" is not loaded 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL FOR 'unknown_seclabel' ON TABLE dummy_seclabel_tbl1 IS 'classified'; 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: must be owner of table dummy_seclabel_tbl2 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON TABLE dummy_seclabel_tbl2 IS 'unclassified'; 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: only superuser can set 'secret' label 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS 'secret'; 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: relation "dummy_seclabel_tbl3" does not exist 2025-11-30 18:45:07.613 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON TABLE dummy_seclabel_tbl3 IS 'unclassified'; 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: must be owner of table dummy_seclabel_tbl1 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS 'unclassified'; 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: '...invalid label...' is not a valid security label 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON ROLE regress_dummy_seclabel_user3 IS '...invalid label...'; 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: security label provider "unknown_seclabel" is not loaded 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL FOR 'unknown_seclabel' ON ROLE regress_dummy_seclabel_user1 IS 'unclassified'; 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: only superuser can set 'secret' label 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON ROLE regress_dummy_seclabel_user3 IS 'secret'; 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: role "regress_dummy_seclabel_user4" does not exist 2025-11-30 18:45:07.614 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON ROLE regress_dummy_seclabel_user4 IS 'unclassified'; 2025-11-30 18:45:07.615 UTC client backend[44753] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.615 UTC client backend[44753] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_delay_execution application_name=isolation/partition-removal-1 2025-11-30 18:45:07.616 UTC client backend[44753] isolation/partition-removal-1 LOG: connection ready: setup total=13.907 ms, fork=1.764 ms, authentication=0.112 ms 2025-11-30 18:45:07.620 UTC unrecognized[44755] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.621 UTC client backend[44755] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.621 UTC client backend[44755] [unknown] LOG: connection authorized: user=postgres database=regression_dummy_index_am application_name=pg_regress/reloptions 2025-11-30 18:45:07.625 UTC client backend[44755] pg_regress/reloptions LOG: connection ready: setup total=5.985 ms, fork=0.819 ms, authentication=0.105 ms 2025-11-30 18:45:07.635 UTC client backend[44751] pg_regress/dummy_seclabel ERROR: permission denied 2025-11-30 18:45:07.635 UTC client backend[44751] pg_regress/dummy_seclabel DETAIL: The current user must have the CREATEROLE attribute. 2025-11-30 18:45:07.635 UTC client backend[44751] pg_regress/dummy_seclabel STATEMENT: SECURITY LABEL ON ROLE regress_dummy_seclabel_user2 IS 'unclassified'; 2025-11-30 18:45:07.635 UTC unrecognized[44754] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.636 UTC client backend[44754] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.636 UTC client backend[44754] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_delay_execution application_name=isolation/partition-removal-1 2025-11-30 18:45:07.637 UTC client backend[44754] isolation/partition-removal-1 LOG: connection ready: setup total=20.246 ms, fork=18.776 ms, authentication=0.116 ms 2025-11-30 18:45:07.644 UTC client backend[44633] pg_regress/create_view LOG: disconnection: session time: 0:00:00.828 user=postgres database=regression host=[local] 2025-11-30 18:45:07.646 UTC client backend[44751] pg_regress/dummy_seclabel WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:07.646 UTC client backend[44751] pg_regress/dummy_seclabel HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:07.646 UTC client backend[44751] pg_regress/dummy_seclabel WARNING: subscriptions created by regression test cases should have names starting with "regress_" 2025-11-30 18:45:07.647 UTC client backend[44751] pg_regress/dummy_seclabel WARNING: subscription was created, but is not connected 2025-11-30 18:45:07.647 UTC client backend[44751] pg_regress/dummy_seclabel HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:07.647 UTC client backend[44640] pg_regress/create_index ERROR: cannot drop index cwi_replaced_pkey because constraint cwi_replaced_pkey on table cwi_test requires it 2025-11-30 18:45:07.647 UTC client backend[44640] pg_regress/create_index HINT: You can drop constraint cwi_replaced_pkey on table cwi_test instead. 2025-11-30 18:45:07.647 UTC client backend[44640] pg_regress/create_index STATEMENT: DROP INDEX cwi_replaced_pkey; 2025-11-30 18:45:07.648 UTC client backend[44640] pg_regress/create_index ERROR: index "cwi_uniq3_idx" column number 1 does not have default sorting behavior at character 26 2025-11-30 18:45:07.648 UTC client backend[44640] pg_regress/create_index DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-11-30 18:45:07.648 UTC client backend[44640] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq3_idx; 2025-11-30 18:45:07.650 UTC client backend[44640] pg_regress/create_index ERROR: index "cwi_uniq4_idx" column number 1 does not have default sorting behavior at character 26 2025-11-30 18:45:07.650 UTC client backend[44640] pg_regress/create_index DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-11-30 18:45:07.650 UTC client backend[44640] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq4_idx; 2025-11-30 18:45:07.654 UTC client backend[44640] pg_regress/create_index ERROR: ALTER TABLE / ADD CONSTRAINT USING INDEX is not supported on partitioned tables 2025-11-30 18:45:07.654 UTC client backend[44640] pg_regress/create_index STATEMENT: alter table cwi_test add primary key using index cwi_test_a_idx ; 2025-11-30 18:45:07.657 UTC client backend[44640] pg_regress/create_index ERROR: primary keys cannot use NULLS NOT DISTINCT indexes 2025-11-30 18:45:07.657 UTC client backend[44640] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD PRIMARY KEY USING INDEX cwi_a_nnd; 2025-11-30 18:45:07.659 UTC client backend[44640] pg_regress/create_index ERROR: index creation on system columns is not supported 2025-11-30 18:45:07.659 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE INDEX ON syscol_table (ctid); 2025-11-30 18:45:07.659 UTC client backend[44640] pg_regress/create_index ERROR: index creation on system columns is not supported 2025-11-30 18:45:07.659 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE INDEX ON syscol_table ((ctid >= '(1000,0)')); 2025-11-30 18:45:07.660 UTC client backend[44640] pg_regress/create_index ERROR: index creation on system columns is not supported 2025-11-30 18:45:07.660 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE INDEX ON syscol_table (a) WHERE ctid >= '(1000,0)'; 2025-11-30 18:45:07.668 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for enum option "option_enum": three 2025-11-30 18:45:07.668 UTC client backend[44755] pg_regress/reloptions DETAIL: Valid values are "one" and "two". 2025-11-30 18:45:07.668 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_enum = 'three'); 2025-11-30 18:45:07.669 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for integer option "option_int": true 2025-11-30 18:45:07.669 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_int = true); 2025-11-30 18:45:07.669 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for integer option "option_int": val3 2025-11-30 18:45:07.669 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_int = 'val3'); 2025-11-30 18:45:07.670 UTC client backend[44751] pg_regress/dummy_seclabel LOG: disconnection: session time: 0:00:00.070 user=postgres database=regression_dummy_seclabel host=[local] 2025-11-30 18:45:07.670 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for boolean option "option_bool": 4 2025-11-30 18:45:07.670 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_bool = 4); 2025-11-30 18:45:07.670 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for boolean option "option_bool": 3.4 2025-11-30 18:45:07.670 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_bool = 3.4); 2025-11-30 18:45:07.670 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for boolean option "option_bool": val4 2025-11-30 18:45:07.670 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_bool = 'val4'); 2025-11-30 18:45:07.671 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for floating point option "option_real": true 2025-11-30 18:45:07.671 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_real = true); 2025-11-30 18:45:07.671 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for floating point option "option_real": val5 2025-11-30 18:45:07.671 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_real = 'val5'); 2025-11-30 18:45:07.671 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for enum option "option_enum": 0 2025-11-30 18:45:07.671 UTC client backend[44755] pg_regress/reloptions DETAIL: Valid values are "one" and "two". 2025-11-30 18:45:07.671 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_enum = 0); 2025-11-30 18:45:07.672 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for enum option "option_enum": true 2025-11-30 18:45:07.672 UTC client backend[44755] pg_regress/reloptions DETAIL: Valid values are "one" and "two". 2025-11-30 18:45:07.672 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_enum = true); 2025-11-30 18:45:07.672 UTC client backend[44755] pg_regress/reloptions ERROR: invalid value for enum option "option_enum": three 2025-11-30 18:45:07.672 UTC client backend[44755] pg_regress/reloptions DETAIL: Valid values are "one" and "two". 2025-11-30 18:45:07.672 UTC client backend[44755] pg_regress/reloptions STATEMENT: ALTER INDEX dummy_test_idx SET (option_enum = 'three'); 2025-11-30 18:45:07.673 UTC client backend[44755] pg_regress/reloptions LOG: disconnection: session time: 0:00:00.053 user=postgres database=regression_dummy_index_am host=[local] 2025-11-30 18:45:07.725 UTC unrecognized[44763] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.726 UTC client backend[44763] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.726 UTC client backend[44763] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:07.727 UTC client backend[44763] postgres_fdw LOG: connection ready: setup total=2.292 ms, fork=0.815 ms, authentication=0.126 ms 2025-11-30 18:45:07.727 UTC unrecognized[44762] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.727 UTC client backend[44762] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.727 UTC client backend[44762] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.736 UTC client backend[44762] pg_regress LOG: connection ready: setup total=14.755 ms, fork=5.449 ms, authentication=0.116 ms 2025-11-30 18:45:07.738 UTC client backend[44762] pg_regress LOG: disconnection: session time: 0:00:00.011 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.745 UTC unrecognized[44765] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.745 UTC client backend[44765] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.745 UTC client backend[44765] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.746 UTC client backend[44765] pg_regress LOG: connection ready: setup total=4.199 ms, fork=2.903 ms, authentication=0.120 ms 2025-11-30 18:45:07.754 UTC unrecognized[44768] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.754 UTC client backend[44768] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.754 UTC client backend[44768] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.755 UTC client backend[44260] pg_regress/_int LOG: disconnection: session time: 0:00:03.551 user=postgres database=regression_intarray host=[local] 2025-11-30 18:45:07.756 UTC client backend[44768] pg_regress LOG: connection ready: setup total=2.693 ms, fork=0.423 ms, authentication=0.116 ms 2025-11-30 18:45:07.756 UTC client backend[44768] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.760 UTC unrecognized[44771] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.761 UTC client backend[44771] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.761 UTC client backend[44771] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.761 UTC client backend[44771] pg_regress LOG: connection ready: setup total=1.541 ms, fork=0.328 ms, authentication=0.110 ms 2025-11-30 18:45:07.780 UTC client backend[44765] pg_regress LOG: disconnection: session time: 0:00:00.035 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.789 UTC client backend[44771] pg_regress LOG: disconnection: session time: 0:00:00.028 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.810 UTC unrecognized[44778] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.811 UTC client backend[44778] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.811 UTC client backend[44778] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_index application_name=isolation/killtuples 2025-11-30 18:45:07.815 UTC client backend[44778] isolation/killtuples LOG: connection ready: setup total=5.905 ms, fork=0.642 ms, authentication=0.127 ms 2025-11-30 18:45:07.816 UTC unrecognized[44780] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.816 UTC client backend[44780] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.816 UTC client backend[44780] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.817 UTC client backend[44780] pg_regress LOG: connection ready: setup total=1.662 ms, fork=0.379 ms, authentication=0.113 ms 2025-11-30 18:45:07.817 UTC unrecognized[44781] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.817 UTC client backend[44781] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.817 UTC client backend[44781] [unknown] LOG: connection authorized: user=postgres database=isolation_regression_index application_name=isolation/killtuples 2025-11-30 18:45:07.818 UTC client backend[44781] isolation/killtuples LOG: connection ready: setup total=2.011 ms, fork=0.706 ms, authentication=0.104 ms 2025-11-30 18:45:07.819 UTC client backend[44780] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.827 UTC unrecognized[44783] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.827 UTC client backend[44783] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.827 UTC client backend[44783] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.828 UTC client backend[44783] pg_regress LOG: connection ready: setup total=4.737 ms, fork=2.720 ms, authentication=0.106 ms 2025-11-30 18:45:07.829 UTC unrecognized[44774] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.829 UTC client backend[44774] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.829 UTC client backend[44774] [unknown] LOG: connection authorized: user=postgres database=regression_plsample application_name=pg_regress/plsample 2025-11-30 18:45:07.834 UTC client backend[44774] pg_regress/plsample LOG: connection ready: setup total=38.935 ms, fork=33.957 ms, authentication=0.104 ms 2025-11-30 18:45:07.841 UTC client backend[44783] pg_regress LOG: disconnection: session time: 0:00:00.014 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.849 UTC client backend[44774] pg_regress/plsample LOG: disconnection: session time: 0:00:00.020 user=postgres database=regression_plsample host=[local] 2025-11-30 18:45:07.866 UTC client backend[44640] pg_regress/create_index ERROR: concurrent index creation for exclusion constraints is not supported 2025-11-30 18:45:07.866 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_tab3_c2_excl; 2025-11-30 18:45:07.866 UTC client backend[44640] pg_regress/create_index WARNING: cannot reindex exclusion constraint index "public.concur_reindex_tab3_c2_excl" concurrently, skipping 2025-11-30 18:45:07.869 UTC client backend[44640] pg_regress/create_index ERROR: conflicting key value violates exclusion constraint "concur_reindex_tab3_c2_excl" 2025-11-30 18:45:07.869 UTC client backend[44640] pg_regress/create_index DETAIL: Key (c2)=([2,5)) conflicts with existing key (c2)=([1,3)). 2025-11-30 18:45:07.869 UTC client backend[44640] pg_regress/create_index STATEMENT: INSERT INTO concur_reindex_tab3 VALUES (4, '[2,4]'); 2025-11-30 18:45:07.884 UTC unrecognized[44786] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.884 UTC client backend[44786] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.884 UTC client backend[44786] [unknown] LOG: connection authorized: user=postgres database=regression_spgist_name_ops application_name=pg_regress/spgist_name_ops 2025-11-30 18:45:07.889 UTC client backend[44786] pg_regress/spgist_name_ops LOG: connection ready: setup total=24.224 ms, fork=19.035 ms, authentication=0.124 ms 2025-11-30 18:45:07.905 UTC unrecognized[44790] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.906 UTC client backend[44790] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.906 UTC client backend[44790] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.907 UTC client backend[44790] pg_regress LOG: connection ready: setup total=3.236 ms, fork=1.938 ms, authentication=0.123 ms 2025-11-30 18:45:07.907 UTC client backend[44790] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.924 UTC unrecognized[44792] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.924 UTC client backend[44792] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.924 UTC client backend[44792] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:07.925 UTC client backend[44792] pg_regress LOG: connection ready: setup total=1.875 ms, fork=0.548 ms, authentication=0.116 ms 2025-11-30 18:45:07.928 UTC client backend[44749] pg_regress/gin_incomplete_splits LOG: disconnection: session time: 0:00:00.326 user=postgres database=regression_gin host=[local] 2025-11-30 18:45:07.965 UTC client backend[44792] pg_regress LOG: disconnection: session time: 0:00:00.041 user=postgres database=postgres host=[local] 2025-11-30 18:45:07.990 UTC unrecognized[44798] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:07.990 UTC client backend[44798] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:07.990 UTC client backend[44798] [unknown] LOG: connection authorized: user=postgres database=regression_test_binaryheap application_name=pg_regress/test_binaryheap 2025-11-30 18:45:08.000 UTC client backend[44798] pg_regress/test_binaryheap LOG: connection ready: setup total=23.776 ms, fork=2.759 ms, authentication=0.118 ms 2025-11-30 18:45:08.000 UTC unrecognized[44799] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.001 UTC client backend[44799] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.001 UTC client backend[44799] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.001 UTC client backend[44799] pg_regress LOG: connection ready: setup total=14.356 ms, fork=12.353 ms, authentication=0.111 ms 2025-11-30 18:45:08.003 UTC client backend[44786] pg_regress/spgist_name_ops ERROR: index row size 20032 exceeds maximum 8156 for index "t_f1_f2_f3_idx" 2025-11-30 18:45:08.003 UTC client backend[44786] pg_regress/spgist_name_ops HINT: Values larger than a buffer page cannot be indexed. 2025-11-30 18:45:08.003 UTC client backend[44786] pg_regress/spgist_name_ops STATEMENT: insert into t values(repeat('xyzzy', 12), 42, repeat('xyzzy', 4000)); 2025-11-30 18:45:08.006 UTC client backend[44798] pg_regress/test_binaryheap LOG: disconnection: session time: 0:00:00.026 user=postgres database=regression_test_binaryheap host=[local] 2025-11-30 18:45:08.006 UTC client backend[44799] pg_regress LOG: disconnection: session time: 0:00:00.006 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part_index" is not a table or materialized view 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part_index; 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part_index" is not a table or materialized view 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_part_index; 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part_index_10" is not a table or materialized view 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part_index_10; 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part_index_10" is not a table or materialized view 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_part_index_10; 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index ERROR: REINDEX INDEX cannot run inside a transaction block 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index CONTEXT: while reindexing partitioned index "public.concur_reindex_part_index" 2025-11-30 18:45:08.024 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part_index; 2025-11-30 18:45:08.032 UTC client backend[44786] pg_regress/spgist_name_ops ERROR: index row size 20032 exceeds maximum 8156 for index "t_f1_f2_f3_idx" 2025-11-30 18:45:08.032 UTC client backend[44786] pg_regress/spgist_name_ops HINT: Values larger than a buffer page cannot be indexed. 2025-11-30 18:45:08.032 UTC client backend[44786] pg_regress/spgist_name_ops STATEMENT: insert into t values(repeat('xyzzy', 12), 42, repeat('xyzzy', 4000)); 2025-11-30 18:45:08.032 UTC client backend[44786] pg_regress/spgist_name_ops LOG: disconnection: session time: 0:00:00.148 user=postgres database=regression_spgist_name_ops host=[local] 2025-11-30 18:45:08.040 UTC client backend[44691] postgres_fdw LOG: disconnection: session time: 0:00:00.775 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:08.042 UTC client backend[44763] postgres_fdw LOG: disconnection: session time: 0:00:00.316 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:08.055 UTC unrecognized[44805] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.056 UTC client backend[44805] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.056 UTC client backend[44805] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:08.057 UTC client backend[44805] postgres_fdw LOG: connection ready: setup total=8.527 ms, fork=7.071 ms, authentication=0.120 ms 2025-11-30 18:45:08.057 UTC unrecognized[44804] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.057 UTC client backend[44804] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.057 UTC client backend[44804] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.058 UTC client backend[44804] pg_regress LOG: connection ready: setup total=18.472 ms, fork=15.617 ms, authentication=0.110 ms 2025-11-30 18:45:08.073 UTC unrecognized[44809] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.073 UTC client backend[44809] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.073 UTC client backend[44809] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.074 UTC client backend[44809] pg_regress LOG: connection ready: setup total=2.141 ms, fork=0.777 ms, authentication=0.124 ms 2025-11-30 18:45:08.074 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part" is not an index 2025-11-30 18:45:08.074 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part; 2025-11-30 18:45:08.075 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part" is not an index 2025-11-30 18:45:08.075 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_part; 2025-11-30 18:45:08.075 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part_10" is not an index 2025-11-30 18:45:08.075 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part_10; 2025-11-30 18:45:08.075 UTC client backend[44640] pg_regress/create_index ERROR: "concur_reindex_part_10" is not an index 2025-11-30 18:45:08.075 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_part_10; 2025-11-30 18:45:08.075 UTC client backend[44809] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.078 UTC client backend[44640] pg_regress/create_index ERROR: REINDEX TABLE cannot run inside a transaction block 2025-11-30 18:45:08.078 UTC client backend[44640] pg_regress/create_index CONTEXT: while reindexing partitioned table "public.concur_reindex_part" 2025-11-30 18:45:08.078 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part; 2025-11-30 18:45:08.080 UTC unrecognized[44811] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.080 UTC client backend[44811] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.080 UTC client backend[44811] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.082 UTC client backend[44811] pg_regress LOG: connection ready: setup total=3.698 ms, fork=1.703 ms, authentication=0.117 ms 2025-11-30 18:45:08.099 UTC client backend[44811] pg_regress LOG: disconnection: session time: 0:00:00.019 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.099 UTC client backend[44804] pg_regress LOG: disconnection: session time: 0:00:00.044 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.105 UTC unrecognized[44818] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.106 UTC client backend[44818] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.106 UTC client backend[44818] [unknown] LOG: connection authorized: user=postgres database=regression_test_bitmapset application_name=pg_regress/test_bitmapset 2025-11-30 18:45:08.108 UTC unrecognized[44817] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.109 UTC client backend[44817] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.109 UTC client backend[44817] [unknown] LOG: connection authorized: user=postgres database=regression_test_bloomfilter application_name=pg_regress/test_bloomfilter 2025-11-30 18:45:08.110 UTC client backend[44818] pg_regress/test_bitmapset LOG: connection ready: setup total=5.481 ms, fork=0.269 ms, authentication=0.113 ms 2025-11-30 18:45:08.113 UTC unrecognized[44816] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.113 UTC client backend[44816] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.113 UTC client backend[44816] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.113 UTC client backend[44817] pg_regress/test_bloomfilter LOG: connection ready: setup total=9.020 ms, fork=0.833 ms, authentication=0.101 ms 2025-11-30 18:45:08.114 UTC client backend[44816] pg_regress LOG: connection ready: setup total=9.533 ms, fork=8.384 ms, authentication=0.105 ms 2025-11-30 18:45:08.114 UTC client backend[44640] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:08.114 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_tab; 2025-11-30 18:45:08.114 UTC client backend[44816] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.116 UTC client backend[44640] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-11-30 18:45:08.116 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY pg_class; 2025-11-30 18:45:08.118 UTC client backend[44640] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-11-30 18:45:08.118 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY pg_class_oid_index; 2025-11-30 18:45:08.119 UTC client backend[44640] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-11-30 18:45:08.119 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY pg_toast.pg_toast_1262; 2025-11-30 18:45:08.120 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.120 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_make_singleton(-1); 2025-11-30 18:45:08.121 UTC client backend[44640] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-11-30 18:45:08.121 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY pg_toast.pg_toast_1262_index; 2025-11-30 18:45:08.122 UTC client backend[44640] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-11-30 18:45:08.122 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX SYSTEM CONCURRENTLY postgres; 2025-11-30 18:45:08.123 UTC client backend[44640] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-11-30 18:45:08.123 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX (CONCURRENTLY) SYSTEM postgres; 2025-11-30 18:45:08.124 UTC client backend[44640] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-11-30 18:45:08.124 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX (CONCURRENTLY) SYSTEM; 2025-11-30 18:45:08.126 UTC client backend[44640] pg_regress/create_index WARNING: cannot reindex system catalogs concurrently, skipping all 2025-11-30 18:45:08.128 UTC client backend[44640] pg_regress/create_index ERROR: can only reindex the currently open database 2025-11-30 18:45:08.128 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX DATABASE not_current_database; 2025-11-30 18:45:08.131 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.131 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_add_member('(b 1)', -1); 2025-11-30 18:45:08.131 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.131 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_add_member('(b)', -10); 2025-11-30 18:45:08.132 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.132 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_del_member('(b)', -20); 2025-11-30 18:45:08.140 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.140 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_is_member('(b)', -5); 2025-11-30 18:45:08.142 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.142 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_add_range('(b)', -5, 10); 2025-11-30 18:45:08.144 UTC client backend[44818] pg_regress/test_bitmapset ERROR: bitmapset is empty 2025-11-30 18:45:08.144 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_singleton_member('(b)'); 2025-11-30 18:45:08.144 UTC client backend[44818] pg_regress/test_bitmapset ERROR: bitmapset has multiple members 2025-11-30 18:45:08.144 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_singleton_member('(b 1 2)'); 2025-11-30 18:45:08.151 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.151 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_overlap_list('(b 5 10)', ARRAY[-1,5]) AS result; 2025-11-30 18:45:08.151 UTC client backend[44818] pg_regress/test_bitmapset ERROR: negative bitmapset member not allowed 2025-11-30 18:45:08.151 UTC client backend[44818] pg_regress/test_bitmapset STATEMENT: SELECT test_bms_overlap_list('(b 1 2 3)', ARRAY[-5,-1,0]) AS result; 2025-11-30 18:45:08.152 UTC client backend[44640] pg_regress/create_index ERROR: could not create unique index "concur_reindex_ind5" 2025-11-30 18:45:08.152 UTC client backend[44640] pg_regress/create_index DETAIL: Key (c1)=(1) is duplicated. 2025-11-30 18:45:08.152 UTC client backend[44640] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX CONCURRENTLY concur_reindex_ind5 ON concur_reindex_tab4 (c1); 2025-11-30 18:45:08.153 UTC client backend[44640] pg_regress/create_index ERROR: could not create unique index "concur_reindex_ind5_ccnew" 2025-11-30 18:45:08.153 UTC client backend[44640] pg_regress/create_index DETAIL: Key (c1)=(1) is duplicated. 2025-11-30 18:45:08.153 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_ind5; 2025-11-30 18:45:08.158 UTC client backend[44818] pg_regress/test_bitmapset LOG: disconnection: session time: 0:00:00.052 user=postgres database=regression_test_bitmapset host=[local] 2025-11-30 18:45:08.168 UTC unrecognized[44820] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.168 UTC client backend[44820] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.168 UTC client backend[44820] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.169 UTC client backend[44820] pg_regress LOG: connection ready: setup total=47.157 ms, fork=45.769 ms, authentication=0.141 ms 2025-11-30 18:45:08.171 UTC client backend[44640] pg_regress/create_index WARNING: skipping reindex of invalid index "public.concur_reindex_ind5" 2025-11-30 18:45:08.171 UTC client backend[44640] pg_regress/create_index HINT: Use DROP INDEX or REINDEX INDEX. 2025-11-30 18:45:08.215 UTC client backend[44820] pg_regress LOG: disconnection: session time: 0:00:00.046 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.222 UTC unrecognized[44824] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.222 UTC client backend[44824] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.222 UTC client backend[44824] [unknown] LOG: connection authorized: user=postgres database=regression_test_copy_callbacks application_name=pg_regress/test_copy_callbacks 2025-11-30 18:45:08.228 UTC client backend[44824] pg_regress/test_copy_callbacks LOG: connection ready: setup total=8.137 ms, fork=1.923 ms, authentication=0.114 ms 2025-11-30 18:45:08.232 UTC client backend[44824] pg_regress/test_copy_callbacks LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_test_copy_callbacks host=[local] 2025-11-30 18:45:08.270 UTC client backend[44817] pg_regress/test_bloomfilter LOG: disconnection: session time: 0:00:00.164 user=postgres database=regression_test_bloomfilter host=[local] 2025-11-30 18:45:08.300 UTC client backend[44640] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:08.300 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_temp_ind_1; 2025-11-30 18:45:08.303 UTC unrecognized[44831] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.303 UTC client backend[44831] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.303 UTC client backend[44831] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.304 UTC client backend[44831] pg_regress LOG: connection ready: setup total=17.097 ms, fork=15.672 ms, authentication=0.141 ms 2025-11-30 18:45:08.305 UTC client backend[44831] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.308 UTC client backend[44640] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:08.308 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_temp_ind_3; 2025-11-30 18:45:08.309 UTC unrecognized[44835] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.310 UTC client backend[44835] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.310 UTC client backend[44835] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.311 UTC client backend[44835] pg_regress LOG: connection ready: setup total=1.738 ms, fork=0.408 ms, authentication=0.117 ms 2025-11-30 18:45:08.315 UTC unrecognized[44836] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.316 UTC client backend[44836] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.316 UTC client backend[44836] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.317 UTC client backend[44836] pg_regress LOG: connection ready: setup total=5.771 ms, fork=4.407 ms, authentication=0.127 ms 2025-11-30 18:45:08.317 UTC client backend[44836] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.333 UTC unrecognized[44838] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.333 UTC client backend[44838] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.333 UTC client backend[44838] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.334 UTC client backend[44838] pg_regress LOG: connection ready: setup total=3.223 ms, fork=1.845 ms, authentication=0.132 ms 2025-11-30 18:45:08.355 UTC client backend[44835] pg_regress LOG: disconnection: session time: 0:00:00.045 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.362 UTC unrecognized[44842] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.362 UTC unrecognized[44843] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.362 UTC client backend[44842] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.362 UTC client backend[44842] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/test_ddl_deparse 2025-11-30 18:45:08.365 UTC client backend[44838] pg_regress LOG: disconnection: session time: 0:00:00.032 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.367 UTC client backend[44842] pg_regress/test_ddl_deparse LOG: connection ready: setup total=6.108 ms, fork=0.969 ms, authentication=0.122 ms 2025-11-30 18:45:08.367 UTC client backend[44843] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.367 UTC client backend[44843] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.368 UTC client backend[44843] pg_regress LOG: connection ready: setup total=6.749 ms, fork=0.621 ms, authentication=0.121 ms 2025-11-30 18:45:08.371 UTC unrecognized[44845] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.371 UTC client backend[44845] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.371 UTC client backend[44845] [unknown] LOG: connection authorized: user=postgres database=regression_test_dsa application_name=pg_regress/test_dsa 2025-11-30 18:45:08.376 UTC client backend[44845] pg_regress/test_dsa LOG: connection ready: setup total=6.389 ms, fork=0.461 ms, authentication=0.136 ms 2025-11-30 18:45:08.377 UTC client backend[44843] pg_regress LOG: disconnection: session time: 0:00:00.015 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.378 UTC client backend[44842] pg_regress/test_ddl_deparse LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.383 UTC client backend[44845] pg_regress/test_dsa LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression_test_dsa host=[local] 2025-11-30 18:45:08.384 UTC client backend[44805] postgres_fdw LOG: disconnection: session time: 0:00:00.329 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:08.386 UTC unrecognized[44849] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.386 UTC client backend[44849] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.386 UTC client backend[44849] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.387 UTC client backend[44849] pg_regress LOG: connection ready: setup total=2.541 ms, fork=1.300 ms, authentication=0.110 ms 2025-11-30 18:45:08.389 UTC unrecognized[44850] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.389 UTC client backend[44850] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.389 UTC client backend[44850] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_extension 2025-11-30 18:45:08.390 UTC client backend[44850] pg_regress/create_extension LOG: connection ready: setup total=3.422 ms, fork=1.975 ms, authentication=0.110 ms 2025-11-30 18:45:08.395 UTC client backend[44640] pg_regress/create_index ERROR: schema "schema_to_reindex" does not exist 2025-11-30 18:45:08.395 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2025-11-30 18:45:08.398 UTC client backend[44849] pg_regress LOG: disconnection: session time: 0:00:00.012 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.409 UTC unrecognized[44853] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.409 UTC unrecognized[44855] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.410 UTC client backend[44853] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.410 UTC client backend[44853] [unknown] LOG: connection authorized: user=postgres database=regression_test_dsm_registry application_name=pg_regress/test_dsm_registry 2025-11-30 18:45:08.414 UTC client backend[44853] pg_regress/test_dsm_registry LOG: connection ready: setup total=6.044 ms, fork=0.928 ms, authentication=0.118 ms 2025-11-30 18:45:08.419 UTC client backend[44855] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.419 UTC client backend[44855] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:08.420 UTC unrecognized[44856] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.420 UTC client backend[44855] postgres_fdw LOG: connection ready: setup total=11.212 ms, fork=0.625 ms, authentication=0.131 ms 2025-11-30 18:45:08.420 UTC client backend[44856] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.420 UTC client backend[44856] [unknown] LOG: connection authorized: user=postgres database=regression_test_dsm_registry application_name=pg_regress/test_dsm_registry 2025-11-30 18:45:08.421 UTC client backend[44856] pg_regress/test_dsm_registry LOG: connection ready: setup total=2.900 ms, fork=1.100 ms, authentication=0.112 ms 2025-11-30 18:45:08.422 UTC client backend[44853] pg_regress/test_dsm_registry LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_test_dsm_registry host=[local] 2025-11-30 18:45:08.432 UTC client backend[44855] postgres_fdw LOG: disconnection: session time: 0:00:00.022 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:08.440 UTC unrecognized[44857] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.440 UTC client backend[44857] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.440 UTC client backend[44857] [unknown] LOG: connection authorized: user=postgres database=regression_test_dsm_registry application_name=pg_regress/test_dsm_registry 2025-11-30 18:45:08.441 UTC client backend[44857] pg_regress/test_dsm_registry LOG: connection ready: setup total=17.686 ms, fork=16.169 ms, authentication=0.130 ms 2025-11-30 18:45:08.441 UTC client backend[44856] pg_regress/test_dsm_registry LOG: disconnection: session time: 0:00:00.021 user=postgres database=regression_test_dsm_registry host=[local] 2025-11-30 18:45:08.442 UTC client backend[44850] pg_regress/create_extension LOG: disconnection: session time: 0:00:00.053 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.445 UTC unrecognized[44861] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.445 UTC client backend[44857] pg_regress/test_dsm_registry LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_test_dsm_registry host=[local] 2025-11-30 18:45:08.445 UTC client backend[44861] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.445 UTC client backend[44861] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.446 UTC client backend[44861] pg_regress LOG: connection ready: setup total=3.032 ms, fork=1.803 ms, authentication=0.106 ms 2025-11-30 18:45:08.446 UTC client backend[44861] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.454 UTC unrecognized[44865] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.454 UTC client backend[44865] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.454 UTC client backend[44865] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_schema 2025-11-30 18:45:08.454 UTC unrecognized[44866] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.455 UTC client backend[44866] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.455 UTC client backend[44866] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.455 UTC client backend[44865] pg_regress/create_schema LOG: connection ready: setup total=2.100 ms, fork=0.640 ms, authentication=0.114 ms 2025-11-30 18:45:08.455 UTC client backend[44866] pg_regress LOG: connection ready: setup total=2.079 ms, fork=0.947 ms, authentication=0.101 ms 2025-11-30 18:45:08.463 UTC client backend[44865] pg_regress/create_schema LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.471 UTC client backend[44866] pg_regress LOG: disconnection: session time: 0:00:00.016 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.479 UTC unrecognized[44872] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.479 UTC client backend[44872] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.479 UTC client backend[44872] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_type 2025-11-30 18:45:08.480 UTC client backend[44872] pg_regress/create_type LOG: connection ready: setup total=3.054 ms, fork=1.539 ms, authentication=0.120 ms 2025-11-30 18:45:08.481 UTC unrecognized[44871] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.482 UTC client backend[44871] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.482 UTC client backend[44871] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:08.482 UTC client backend[44871] postgres_fdw LOG: connection ready: setup total=5.630 ms, fork=4.267 ms, authentication=0.107 ms 2025-11-30 18:45:08.492 UTC client backend[44640] pg_regress/create_index ERROR: REINDEX SCHEMA cannot run inside a transaction block 2025-11-30 18:45:08.492 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2025-11-30 18:45:08.495 UTC client backend[44872] pg_regress/create_type LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.499 UTC unrecognized[44878] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.500 UTC client backend[44878] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.500 UTC client backend[44878] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:08.501 UTC client backend[44878] postgres_fdw LOG: connection ready: setup total=3.248 ms, fork=1.918 ms, authentication=0.115 ms 2025-11-30 18:45:08.507 UTC client backend[44640] pg_regress/create_index ERROR: must be owner of schema schema_to_reindex 2025-11-30 18:45:08.507 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2025-11-30 18:45:08.507 UTC client backend[44640] pg_regress/create_index ERROR: permission denied for table pg_toast_1262 2025-11-30 18:45:08.507 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX TABLE pg_toast.pg_toast_1262; 2025-11-30 18:45:08.507 UTC client backend[44640] pg_regress/create_index ERROR: permission denied for index pg_toast_1262_index 2025-11-30 18:45:08.507 UTC client backend[44640] pg_regress/create_index STATEMENT: REINDEX INDEX pg_toast.pg_toast_1262_index; 2025-11-30 18:45:08.512 UTC unrecognized[44877] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.513 UTC client backend[44877] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.513 UTC client backend[44877] [unknown] LOG: connection authorized: user=postgres database=regression_test_extensions application_name=pg_regress/test_extensions 2025-11-30 18:45:08.520 UTC client backend[44877] pg_regress/test_extensions LOG: connection ready: setup total=23.038 ms, fork=15.063 ms, authentication=0.113 ms 2025-11-30 18:45:08.520 UTC client backend[44640] pg_regress/create_index LOG: disconnection: session time: 0:00:01.690 user=postgres database=regression host=[local] 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions ERROR: required extension "test_ext2" is not installed 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions HINT: Use CREATE EXTENSION ... CASCADE to install required extensions too. 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext1; 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions ERROR: schema "test_ext1" does not exist 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext1 SCHEMA test_ext1; 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions ERROR: schema "test_ext" does not exist 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext1 SCHEMA test_ext; 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions ERROR: extension "test_ext1" must be installed in schema "test_ext1" 2025-11-30 18:45:08.521 UTC client backend[44877] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext1 SCHEMA has$dollar; 2025-11-30 18:45:08.536 UTC unrecognized[44900] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.537 UTC client backend[44900] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.537 UTC client backend[44900] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_conversion 2025-11-30 18:45:08.538 UTC unrecognized[44902] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.538 UTC client backend[44900] pg_regress/create_conversion LOG: connection ready: setup total=7.929 ms, fork=6.049 ms, authentication=0.125 ms 2025-11-30 18:45:08.538 UTC unrecognized[44901] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.538 UTC client backend[44902] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.538 UTC client backend[44901] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.538 UTC client backend[44902] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_aggregate 2025-11-30 18:45:08.538 UTC client backend[44901] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.539 UTC client backend[44901] pg_regress LOG: connection ready: setup total=8.762 ms, fork=5.770 ms, authentication=0.105 ms 2025-11-30 18:45:08.539 UTC unrecognized[44904] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.539 UTC client backend[44902] pg_regress/create_aggregate LOG: connection ready: setup total=8.703 ms, fork=5.726 ms, authentication=0.114 ms 2025-11-30 18:45:08.539 UTC client backend[44904] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.539 UTC client backend[44904] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_function_sql 2025-11-30 18:45:08.540 UTC client backend[44904] pg_regress/create_function_sql LOG: connection ready: setup total=9.244 ms, fork=4.984 ms, authentication=0.095 ms 2025-11-30 18:45:08.541 UTC unrecognized[44909] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.541 UTC client backend[44909] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.541 UTC client backend[44909] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/triggers 2025-11-30 18:45:08.542 UTC unrecognized[44903] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.542 UTC unrecognized[44907] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.542 UTC client backend[44909] pg_regress/triggers LOG: connection ready: setup total=7.024 ms, fork=1.099 ms, authentication=0.100 ms 2025-11-30 18:45:08.542 UTC client backend[44903] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.542 UTC client backend[44903] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/constraints 2025-11-30 18:45:08.542 UTC client backend[44907] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.542 UTC client backend[44907] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/hash_func 2025-11-30 18:45:08.542 UTC unrecognized[44912] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.543 UTC client backend[44912] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.543 UTC client backend[44912] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/roleattributes 2025-11-30 18:45:08.543 UTC client backend[44903] pg_regress/constraints LOG: connection ready: setup total=12.270 ms, fork=7.398 ms, authentication=0.102 ms 2025-11-30 18:45:08.543 UTC client backend[44907] pg_regress/hash_func LOG: connection ready: setup total=10.847 ms, fork=4.288 ms, authentication=0.105 ms 2025-11-30 18:45:08.543 UTC unrecognized[44906] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.544 UTC client backend[44912] pg_regress/roleattributes LOG: connection ready: setup total=7.349 ms, fork=4.337 ms, authentication=0.100 ms 2025-11-30 18:45:08.544 UTC client backend[44906] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.544 UTC client backend[44906] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/inherit 2025-11-30 18:45:08.544 UTC unrecognized[44905] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.544 UTC client backend[44905] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.544 UTC client backend[44905] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/typed_table 2025-11-30 18:45:08.545 UTC client backend[44906] pg_regress/inherit LOG: connection ready: setup total=12.500 ms, fork=9.190 ms, authentication=0.102 ms 2025-11-30 18:45:08.545 UTC unrecognized[44913] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.545 UTC unrecognized[44915] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.545 UTC client backend[44905] pg_regress/typed_table LOG: connection ready: setup total=13.851 ms, fork=1.368 ms, authentication=0.127 ms 2025-11-30 18:45:08.545 UTC client backend[44901] pg_regress LOG: disconnection: session time: 0:00:00.009 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.546 UTC unrecognized[44908] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.546 UTC client backend[44908] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.546 UTC client backend[44908] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/infinite_recurse 2025-11-30 18:45:08.546 UTC client backend[44913] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.546 UTC client backend[44913] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/vacuum 2025-11-30 18:45:08.547 UTC client backend[44908] pg_regress/infinite_recurse LOG: connection ready: setup total=12.527 ms, fork=6.684 ms, authentication=0.123 ms 2025-11-30 18:45:08.547 UTC client backend[44913] pg_regress/vacuum LOG: connection ready: setup total=7.075 ms, fork=2.079 ms, authentication=0.113 ms 2025-11-30 18:45:08.548 UTC client backend[44915] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.548 UTC client backend[44915] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/updatable_views 2025-11-30 18:45:08.548 UTC client backend[44905] pg_regress/typed_table ERROR: type "nothing" does not exist at character 25 2025-11-30 18:45:08.548 UTC client backend[44905] pg_regress/typed_table STATEMENT: CREATE TABLE ttable1 OF nothing; 2025-11-30 18:45:08.548 UTC unrecognized[44910] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.548 UTC client backend[44910] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.548 UTC client backend[44910] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/drop_if_exists 2025-11-30 18:45:08.549 UTC client backend[44915] pg_regress/updatable_views LOG: connection ready: setup total=7.104 ms, fork=2.405 ms, authentication=0.103 ms 2025-11-30 18:45:08.549 UTC unrecognized[44918] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.549 UTC client backend[44918] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.549 UTC client backend[44918] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select 2025-11-30 18:45:08.549 UTC client backend[44910] pg_regress/drop_if_exists LOG: connection ready: setup total=14.065 ms, fork=10.126 ms, authentication=0.115 ms 2025-11-30 18:45:08.549 UTC client backend[44902] pg_regress/create_aggregate ERROR: aggregate newavg_wrong(integer) does not exist 2025-11-30 18:45:08.549 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: COMMENT ON AGGREGATE newavg_wrong (int4) IS 'an agg comment'; 2025-11-30 18:45:08.550 UTC client backend[44918] pg_regress/select LOG: connection ready: setup total=3.574 ms, fork=2.127 ms, authentication=0.095 ms 2025-11-30 18:45:08.551 UTC client backend[44900] pg_regress/create_conversion LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.552 UTC unrecognized[44914] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.552 UTC client backend[44914] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.552 UTC client backend[44914] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/errors 2025-11-30 18:45:08.553 UTC client backend[44914] pg_regress/errors LOG: connection ready: setup total=12.476 ms, fork=7.279 ms, authentication=0.103 ms 2025-11-30 18:45:08.554 UTC unrecognized[44916] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.554 UTC client backend[44916] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.554 UTC client backend[44916] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_am 2025-11-30 18:45:08.555 UTC client backend[44916] pg_regress/create_am LOG: connection ready: setup total=11.304 ms, fork=7.089 ms, authentication=0.098 ms 2025-11-30 18:45:08.556 UTC client backend[44596] pg_regress/postgres_fdw ERROR: user mapping not found for user "regress_view_owner_another", server "loopback" 2025-11-30 18:45:08.556 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: EXPLAIN (VERBOSE, COSTS OFF) SELECT * FROM v4; 2025-11-30 18:45:08.557 UTC client backend[44877] pg_regress/test_extensions ERROR: cyclic dependency detected between extensions "test_ext_cyclic1" and "test_ext_cyclic2" 2025-11-30 18:45:08.557 UTC client backend[44877] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cyclic1 CASCADE; 2025-11-30 18:45:08.557 UTC client backend[44916] pg_regress/create_am ERROR: function int4in(internal) does not exist 2025-11-30 18:45:08.557 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE INDEX HANDLER int4in; 2025-11-30 18:45:08.558 UTC client backend[44914] pg_regress/errors ERROR: relation "nonesuch" does not exist at character 15 2025-11-30 18:45:08.558 UTC client backend[44914] pg_regress/errors STATEMENT: select * from nonesuch; 2025-11-30 18:45:08.559 UTC client backend[44916] pg_regress/create_am ERROR: function heap_tableam_handler must return type index_am_handler 2025-11-30 18:45:08.559 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE INDEX HANDLER heap_tableam_handler; 2025-11-30 18:45:08.560 UTC unrecognized[44911] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.561 UTC client backend[44911] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.561 UTC client backend[44911] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_cast 2025-11-30 18:45:08.563 UTC client backend[44910] pg_regress/drop_if_exists ERROR: table "test_exists" does not exist 2025-11-30 18:45:08.563 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TABLE test_exists; 2025-11-30 18:45:08.564 UTC client backend[44911] pg_regress/create_cast LOG: connection ready: setup total=28.659 ms, fork=9.950 ms, authentication=0.108 ms 2025-11-30 18:45:08.566 UTC client backend[44914] pg_regress/errors ERROR: column "nonesuch" does not exist at character 8 2025-11-30 18:45:08.566 UTC client backend[44914] pg_regress/errors STATEMENT: select nonesuch from pg_database; 2025-11-30 18:45:08.567 UTC client backend[44916] pg_regress/create_am ERROR: data type box has no default operator class for access method "gist2" 2025-11-30 18:45:08.567 UTC client backend[44916] 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-11-30 18:45:08.567 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE INDEX grect2ind2 ON fast_emp4000 USING gist2 (home_base); 2025-11-30 18:45:08.568 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "from" at character 17 2025-11-30 18:45:08.568 UTC client backend[44914] pg_regress/errors STATEMENT: select distinct from pg_database; 2025-11-30 18:45:08.572 UTC unrecognized[44920] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.573 UTC client backend[44920] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.573 UTC client backend[44920] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.574 UTC client backend[44920] pg_regress LOG: connection ready: setup total=5.395 ms, fork=1.709 ms, authentication=0.132 ms 2025-11-30 18:45:08.574 UTC client backend[44914] pg_regress/errors ERROR: column "nonesuch" does not exist at character 33 2025-11-30 18:45:08.574 UTC client backend[44914] pg_regress/errors STATEMENT: select * from pg_database where nonesuch = pg_database.datname; 2025-11-30 18:45:08.576 UTC client backend[44910] pg_regress/drop_if_exists ERROR: view "test_view_exists" does not exist 2025-11-30 18:45:08.576 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP VIEW test_view_exists; 2025-11-30 18:45:08.577 UTC client backend[44902] pg_regress/create_aggregate ERROR: aggregate nosuchagg(*) does not exist 2025-11-30 18:45:08.577 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: COMMENT ON AGGREGATE nosuchagg (*) IS 'should fail'; 2025-11-30 18:45:08.588 UTC client backend[44914] pg_regress/errors ERROR: column "nonesuch" does not exist at character 55 2025-11-30 18:45:08.588 UTC client backend[44914] pg_regress/errors STATEMENT: select * from pg_database where pg_database.datname = nonesuch; 2025-11-30 18:45:08.588 UTC client backend[44914] pg_regress/errors ERROR: column "foobar" does not exist at character 21 2025-11-30 18:45:08.588 UTC client backend[44914] pg_regress/errors STATEMENT: select distinct on (foobar) * from pg_database; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: FOR UPDATE is not allowed with GROUP BY clause 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: select null from pg_database group by datname for update; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: FOR UPDATE is not allowed with GROUP BY clause 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: select null from pg_database group by grouping sets (()) for update; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 12 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: delete from; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: relation "nonesuch" does not exist at character 13 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: delete from nonesuch; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 11 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: drop table; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: table "nonesuch" does not exist 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: drop table nonesuch; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 19 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: alter table rename; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: relation "nonesuch" does not exist 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: alter table nonesuch rename to newnonesuch; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: relation "nonesuch" does not exist 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: alter table nonesuch rename to stud_emp; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: relation "student" already exists 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: alter table stud_emp rename to student; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: relation "stud_emp" already exists 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: alter table stud_emp rename to stud_emp; 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors ERROR: relation "nonesuchrel" does not exist 2025-11-30 18:45:08.590 UTC client backend[44914] pg_regress/errors STATEMENT: alter table nonesuchrel rename column nonesuchatt to newnonesuchatt; 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors ERROR: column "nonesuchatt" does not exist 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors STATEMENT: alter table emp rename column nonesuchatt to newnonesuchatt; 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors ERROR: column "manager" of relation "stud_emp" already exists 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors STATEMENT: alter table emp rename column salary to manager; 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors ERROR: column name "ctid" conflicts with a system column name 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors STATEMENT: alter table emp rename column salary to ctid; 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors WARNING: there is no transaction in progress 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors WARNING: there is no transaction in progress 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors ERROR: function int2um(integer) does not exist 2025-11-30 18:45:08.591 UTC client backend[44914] pg_regress/errors STATEMENT: create aggregate newavg2 (sfunc = int4pl, basetype = int4, stype = int4, finalfunc = int2um, initcond = '0'); 2025-11-30 18:45:08.592 UTC client backend[44911] pg_regress/create_cast ERROR: function casttestfunc(text) does not exist at character 8 2025-11-30 18:45:08.592 UTC client backend[44911] pg_regress/create_cast DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:08.592 UTC client backend[44911] pg_regress/create_cast HINT: You might need to add explicit type casts. 2025-11-30 18:45:08.592 UTC client backend[44911] pg_regress/create_cast STATEMENT: SELECT casttestfunc('foo'::text); 2025-11-30 18:45:08.592 UTC client backend[44914] pg_regress/errors ERROR: aggregate input type must be specified 2025-11-30 18:45:08.592 UTC client backend[44914] pg_regress/errors STATEMENT: create aggregate newcnt1 (sfunc = int4inc, stype = int4, initcond = '0'); 2025-11-30 18:45:08.592 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 11 2025-11-30 18:45:08.592 UTC client backend[44914] pg_regress/errors STATEMENT: drop index; 2025-11-30 18:45:08.592 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "314159" at character 12 2025-11-30 18:45:08.592 UTC client backend[44914] pg_regress/errors STATEMENT: drop index 314159; 2025-11-30 18:45:08.593 UTC client backend[44914] pg_regress/errors ERROR: index "nonesuch" does not exist 2025-11-30 18:45:08.593 UTC client backend[44914] pg_regress/errors STATEMENT: drop index nonesuch; 2025-11-30 18:45:08.593 UTC client backend[44911] pg_regress/create_cast ERROR: function casttestfunc(text) does not exist at character 8 2025-11-30 18:45:08.593 UTC client backend[44911] pg_regress/create_cast DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:08.593 UTC client backend[44911] pg_regress/create_cast HINT: You might need to add explicit type casts. 2025-11-30 18:45:08.593 UTC client backend[44911] pg_regress/create_cast STATEMENT: SELECT casttestfunc('foo'::text); 2025-11-30 18:45:08.593 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 15 2025-11-30 18:45:08.593 UTC client backend[44914] pg_regress/errors STATEMENT: drop aggregate; 2025-11-30 18:45:08.593 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 23 2025-11-30 18:45:08.593 UTC client backend[44914] pg_regress/errors STATEMENT: drop aggregate newcnt1; 2025-11-30 18:45:08.594 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "314159" at character 16 2025-11-30 18:45:08.594 UTC client backend[44914] pg_regress/errors STATEMENT: drop aggregate 314159 (int); 2025-11-30 18:45:08.594 UTC client backend[44596] pg_regress/postgres_fdw ERROR: user mapping not found for user "regress_view_owner_another", server "loopback" 2025-11-30 18:45:08.594 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: EXPLAIN (VERBOSE, COSTS OFF) SELECT * FROM (SELECT * FROM v4 UNION ALL SELECT * FROM v4); 2025-11-30 18:45:08.594 UTC client backend[44920] pg_regress LOG: disconnection: session time: 0:00:00.023 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.595 UTC client backend[44914] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-11-30 18:45:08.595 UTC client backend[44914] pg_regress/errors STATEMENT: drop aggregate newcnt (nonesuch); 2025-11-30 18:45:08.596 UTC client backend[44914] pg_regress/errors ERROR: aggregate nonesuch(integer) does not exist 2025-11-30 18:45:08.596 UTC client backend[44914] pg_regress/errors STATEMENT: drop aggregate nonesuch (int4); 2025-11-30 18:45:08.596 UTC client backend[44914] pg_regress/errors ERROR: aggregate newcnt(real) does not exist 2025-11-30 18:45:08.596 UTC client backend[44914] pg_regress/errors STATEMENT: drop aggregate newcnt (float4); 2025-11-30 18:45:08.596 UTC client backend[44911] pg_regress/create_cast ERROR: cannot cast type integer to casttesttype at character 18 2025-11-30 18:45:08.596 UTC client backend[44911] pg_regress/create_cast STATEMENT: SELECT 1234::int4::casttesttype; 2025-11-30 18:45:08.599 UTC client backend[44910] pg_regress/drop_if_exists ERROR: view "test_view_exists" does not exist 2025-11-30 18:45:08.599 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP VIEW test_view_exists; 2025-11-30 18:45:08.600 UTC client backend[44910] pg_regress/drop_if_exists ERROR: index "test_index_exists" does not exist 2025-11-30 18:45:08.600 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP INDEX test_index_exists; 2025-11-30 18:45:08.603 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "(" at character 15 2025-11-30 18:45:08.603 UTC client backend[44914] pg_regress/errors STATEMENT: drop function (); 2025-11-30 18:45:08.603 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "314159" at character 15 2025-11-30 18:45:08.603 UTC client backend[44914] pg_regress/errors STATEMENT: drop function 314159(); 2025-11-30 18:45:08.605 UTC client backend[44914] pg_regress/errors ERROR: function nonesuch() does not exist 2025-11-30 18:45:08.605 UTC client backend[44914] pg_regress/errors STATEMENT: drop function nonesuch(); 2025-11-30 18:45:08.605 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 10 2025-11-30 18:45:08.605 UTC client backend[44914] pg_regress/errors STATEMENT: drop type; 2025-11-30 18:45:08.605 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "314159" at character 11 2025-11-30 18:45:08.605 UTC client backend[44914] pg_regress/errors STATEMENT: drop type 314159; 2025-11-30 18:45:08.606 UTC client backend[44914] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-11-30 18:45:08.606 UTC client backend[44914] pg_regress/errors STATEMENT: drop type nonesuch; 2025-11-30 18:45:08.606 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 14 2025-11-30 18:45:08.606 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator; 2025-11-30 18:45:08.607 UTC unrecognized[44923] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.607 UTC client backend[44923] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.607 UTC client backend[44923] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_domain 2025-11-30 18:45:08.608 UTC client backend[44923] pg_regress/create_domain LOG: connection ready: setup total=2.636 ms, fork=0.832 ms, authentication=0.117 ms 2025-11-30 18:45:08.608 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 21 2025-11-30 18:45:08.608 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator equals; 2025-11-30 18:45:08.609 UTC client backend[44902] pg_regress/create_aggregate ERROR: function least_accum(bigint, bigint) requires run-time type coercion 2025-11-30 18:45:08.609 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: create aggregate least_agg(int4) ( stype = int8, sfunc = least_accum ); 2025-11-30 18:45:08.609 UTC client backend[44910] pg_regress/drop_if_exists ERROR: index "test_index_exists" does not exist 2025-11-30 18:45:08.609 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP INDEX test_index_exists; 2025-11-30 18:45:08.612 UTC client backend[44910] pg_regress/drop_if_exists ERROR: sequence "test_sequence_exists" does not exist 2025-11-30 18:45:08.612 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP SEQUENCE test_sequence_exists; 2025-11-30 18:45:08.614 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 18 2025-11-30 18:45:08.614 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator ===; 2025-11-30 18:45:08.615 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "," at character 19 2025-11-30 18:45:08.615 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator int4, int4; 2025-11-30 18:45:08.616 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "(" at character 15 2025-11-30 18:45:08.616 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator (int4, int4); 2025-11-30 18:45:08.621 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ")" at character 20 2025-11-30 18:45:08.621 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator === (); 2025-11-30 18:45:08.622 UTC client backend[44910] pg_regress/drop_if_exists ERROR: sequence "test_sequence_exists" does not exist 2025-11-30 18:45:08.622 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP SEQUENCE test_sequence_exists; 2025-11-30 18:45:08.622 UTC client backend[44923] pg_regress/create_domain LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.622 UTC client backend[44910] pg_regress/drop_if_exists ERROR: schema "test_schema_exists" does not exist 2025-11-30 18:45:08.622 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP SCHEMA test_schema_exists; 2025-11-30 18:45:08.622 UTC client backend[44902] pg_regress/create_aggregate ERROR: function least_accum(bigint, bigint) requires run-time type coercion 2025-11-30 18:45:08.622 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: create aggregate least_agg(int4) ( stype = int8, sfunc = least_accum ); 2025-11-30 18:45:08.623 UTC client backend[44905] pg_regress/typed_table ERROR: cannot add column to typed table 2025-11-30 18:45:08.623 UTC client backend[44905] pg_regress/typed_table STATEMENT: ALTER TABLE persons ADD COLUMN comment text; 2025-11-30 18:45:08.623 UTC client backend[44914] pg_regress/errors ERROR: missing argument at character 24 2025-11-30 18:45:08.623 UTC client backend[44914] pg_regress/errors HINT: Use NONE to denote the missing argument of a unary operator. 2025-11-30 18:45:08.623 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator === (int4); 2025-11-30 18:45:08.624 UTC client backend[44905] pg_regress/typed_table ERROR: cannot drop column from typed table 2025-11-30 18:45:08.624 UTC client backend[44905] pg_regress/typed_table STATEMENT: ALTER TABLE persons DROP COLUMN name; 2025-11-30 18:45:08.624 UTC client backend[44905] pg_regress/typed_table ERROR: cannot rename column of typed table 2025-11-30 18:45:08.624 UTC client backend[44905] pg_regress/typed_table STATEMENT: ALTER TABLE persons RENAME COLUMN id TO num; 2025-11-30 18:45:08.624 UTC client backend[44910] pg_regress/drop_if_exists ERROR: schema "test_schema_exists" does not exist 2025-11-30 18:45:08.624 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP SCHEMA test_schema_exists; 2025-11-30 18:45:08.624 UTC client backend[44914] pg_regress/errors ERROR: operator does not exist: integer === integer 2025-11-30 18:45:08.624 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator === (int4, int4); 2025-11-30 18:45:08.625 UTC client backend[44905] pg_regress/typed_table ERROR: cannot alter column type of typed table at character 34 2025-11-30 18:45:08.625 UTC client backend[44905] pg_regress/typed_table STATEMENT: ALTER TABLE persons ALTER COLUMN name TYPE varchar; 2025-11-30 18:45:08.625 UTC client backend[44910] pg_regress/drop_if_exists ERROR: type "test_type_exists" does not exist 2025-11-30 18:45:08.625 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TYPE test_type_exists; 2025-11-30 18:45:08.627 UTC client backend[44905] pg_regress/typed_table ERROR: cannot change inheritance of typed table 2025-11-30 18:45:08.627 UTC client backend[44905] pg_regress/typed_table STATEMENT: ALTER TABLE persons INHERIT stuff; 2025-11-30 18:45:08.627 UTC client backend[44903] pg_regress/constraints ERROR: syntax error at or near ")" at character 45 2025-11-30 18:45:08.627 UTC client backend[44903] pg_regress/constraints STATEMENT: CREATE TABLE error_tbl (i int DEFAULT (100, )); 2025-11-30 18:45:08.629 UTC client backend[44914] pg_regress/errors ERROR: missing argument at character 26 2025-11-30 18:45:08.629 UTC client backend[44914] pg_regress/errors HINT: Use NONE to denote the missing argument of a unary operator. 2025-11-30 18:45:08.629 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator = (nonesuch); 2025-11-30 18:45:08.629 UTC client backend[44916] pg_regress/create_am ERROR: cannot drop access method gist2 because other objects depend on it 2025-11-30 18:45:08.629 UTC client backend[44916] pg_regress/create_am DETAIL: index grect2ind2 depends on operator class box_ops for access method gist2 2025-11-30 18:45:08.629 UTC client backend[44916] pg_regress/create_am HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:08.629 UTC client backend[44916] pg_regress/create_am STATEMENT: DROP ACCESS METHOD gist2; 2025-11-30 18:45:08.629 UTC client backend[44911] pg_regress/create_cast LOG: disconnection: session time: 0:00:00.083 user=postgres database=regression host=[local] 2025-11-30 18:45:08.631 UTC client backend[44905] pg_regress/typed_table ERROR: column "myname" does not exist 2025-11-30 18:45:08.631 UTC client backend[44905] pg_regress/typed_table STATEMENT: CREATE TABLE personsx OF person_type (myname WITH OPTIONS NOT NULL); 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "," at character 19 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator = ( , int4); 2025-11-30 18:45:08.631 UTC client backend[44903] pg_regress/constraints ERROR: syntax error at or near "IN" at character 43 2025-11-30 18:45:08.631 UTC client backend[44903] pg_regress/constraints STATEMENT: CREATE TABLE error_tbl (b1 bool DEFAULT 1 IN (1, 2)); 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator = (nonesuch, int4); 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator = (int4, nonesuch); 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ")" at character 24 2025-11-30 18:45:08.631 UTC client backend[44914] pg_regress/errors STATEMENT: drop operator = (int4, ); 2025-11-30 18:45:08.633 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 10 2025-11-30 18:45:08.633 UTC client backend[44914] pg_regress/errors STATEMENT: drop rule; 2025-11-30 18:45:08.633 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "314159" at character 11 2025-11-30 18:45:08.633 UTC client backend[44914] pg_regress/errors STATEMENT: drop rule 314159; 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors ERROR: relation "noplace" does not exist 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors STATEMENT: drop rule nonesuch on noplace; 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "tuple" at character 6 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors STATEMENT: drop tuple rule nonesuch; 2025-11-30 18:45:08.634 UTC client backend[44904] pg_regress/create_function_sql ERROR: only superuser can define a leakproof function 2025-11-30 18:45:08.634 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: ALTER FUNCTION functest_E_2(int) LEAKPROOF; 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "instance" at character 6 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors STATEMENT: drop instance rule nonesuch on noplace; 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "rewrite" at character 6 2025-11-30 18:45:08.634 UTC client backend[44914] pg_regress/errors STATEMENT: drop rewrite rule nonesuch; 2025-11-30 18:45:08.635 UTC client backend[44904] pg_regress/create_function_sql ERROR: only superuser can define a leakproof function 2025-11-30 18:45:08.635 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_E_3(int) RETURNS bool LANGUAGE 'sql' LEAKPROOF AS 'SELECT $1 < 200'; 2025-11-30 18:45:08.635 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.635 UTC client backend[44914] pg_regress/errors STATEMENT: select 1/0; 2025-11-30 18:45:08.635 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.635 UTC client backend[44914] pg_regress/errors STATEMENT: select 1::int8/0; 2025-11-30 18:45:08.635 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.635 UTC client backend[44914] pg_regress/errors STATEMENT: select 1/0::int8; 2025-11-30 18:45:08.636 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.636 UTC client backend[44914] pg_regress/errors STATEMENT: select 1::int2/0; 2025-11-30 18:45:08.637 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.637 UTC client backend[44914] pg_regress/errors STATEMENT: select 1/0::int2; 2025-11-30 18:45:08.637 UTC client backend[43726] isolation/receipt-report/s1 LOG: disconnection: session time: 0:00:07.007 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:08.637 UTC client backend[43731] isolation/receipt-report/s3 LOG: disconnection: session time: 0:00:06.997 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:08.637 UTC client backend[43728] isolation/receipt-report/s2 LOG: disconnection: session time: 0:00:07.003 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:08.639 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.639 UTC client backend[44914] pg_regress/errors STATEMENT: select 1::numeric/0; 2025-11-30 18:45:08.640 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.640 UTC client backend[44914] pg_regress/errors STATEMENT: select 1/0::numeric; 2025-11-30 18:45:08.641 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.641 UTC client backend[44914] pg_regress/errors STATEMENT: select 1::float8/0; 2025-11-30 18:45:08.641 UTC client backend[44877] pg_regress/test_extensions ERROR: syntax error at or near "FUNCTIN" at character 8 2025-11-30 18:45:08.641 UTC client backend[44877] pg_regress/test_extensions QUERY: CREATE FUNCTIN my_erroneous_func(int) RETURNS int LANGUAGE SQL AS $$ SELECT $1 + 1 $$; 2025-11-30 18:45:08.641 UTC client backend[44877] pg_regress/test_extensions CONTEXT: extension script file "test_ext7--2.0--2.1bad.sql", near line 10 2025-11-30 18:45:08.641 UTC client backend[44877] pg_regress/test_extensions STATEMENT: alter extension test_ext7 update to '2.1bad'; 2025-11-30 18:45:08.642 UTC unrecognized[44925] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.642 UTC client backend[44925] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.642 UTC client backend[44925] [unknown] LOG: connection authorized: user=postgres database=regression_test_ginpostinglist application_name=pg_regress/test_ginpostinglist 2025-11-30 18:45:08.645 UTC client backend[44910] pg_regress/drop_if_exists ERROR: type "test_type_exists" does not exist 2025-11-30 18:45:08.645 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TYPE test_type_exists; 2025-11-30 18:45:08.646 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.646 UTC client backend[44914] pg_regress/errors STATEMENT: select 1/0::float8; 2025-11-30 18:45:08.647 UTC client backend[44925] pg_regress/test_ginpostinglist LOG: connection ready: setup total=27.567 ms, fork=11.415 ms, authentication=0.122 ms 2025-11-30 18:45:08.647 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.647 UTC client backend[44914] pg_regress/errors STATEMENT: select 1::float4/0; 2025-11-30 18:45:08.647 UTC client backend[44916] pg_regress/create_am ERROR: invalid value for parameter "default_table_access_method": "" 2025-11-30 18:45:08.647 UTC client backend[44916] pg_regress/create_am DETAIL: "default_table_access_method" cannot be empty. 2025-11-30 18:45:08.647 UTC client backend[44916] pg_regress/create_am STATEMENT: SET default_table_access_method = ''; 2025-11-30 18:45:08.647 UTC client backend[44914] pg_regress/errors ERROR: division by zero 2025-11-30 18:45:08.647 UTC client backend[44914] pg_regress/errors STATEMENT: select 1/0::float4; 2025-11-30 18:45:08.648 UTC client backend[44916] pg_regress/create_am ERROR: invalid value for parameter "default_table_access_method": "I do not exist AM" 2025-11-30 18:45:08.648 UTC client backend[44916] pg_regress/create_am DETAIL: Table access method "I do not exist AM" does not exist. 2025-11-30 18:45:08.648 UTC client backend[44916] pg_regress/create_am STATEMENT: SET default_table_access_method = 'I do not exist AM'; 2025-11-30 18:45:08.648 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "xxx" at character 1 2025-11-30 18:45:08.648 UTC client backend[44914] pg_regress/errors STATEMENT: xxx; 2025-11-30 18:45:08.648 UTC client backend[44916] pg_regress/create_am ERROR: access method "btree" is not of type TABLE 2025-11-30 18:45:08.648 UTC client backend[44916] pg_regress/create_am STATEMENT: SET default_table_access_method = 'btree'; 2025-11-30 18:45:08.649 UTC client backend[44877] pg_regress/test_extensions ERROR: syntax error at or near "," at character 14 2025-11-30 18:45:08.649 UTC client backend[44877] pg_regress/test_extensions QUERY: SELECT $1 + , 1 2025-11-30 18:45:08.649 UTC client backend[44877] pg_regress/test_extensions CONTEXT: SQL statement "CREATE FUNCTION my_erroneous_func(int) RETURNS int LANGUAGE SQL AS $$ SELECT $1 + , 1 $$" extension script file "test_ext7--2.0--2.2bad.sql", near line 9 2025-11-30 18:45:08.649 UTC client backend[44877] pg_regress/test_extensions STATEMENT: alter extension test_ext7 update to '2.2bad'; 2025-11-30 18:45:08.649 UTC client backend[44738] isolation/partition-removal-1/control connection LOG: disconnection: session time: 0:00:01.076 user=postgres database=isolation_regression_delay_execution host=[local] 2025-11-30 18:45:08.650 UTC unrecognized[44928] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.650 UTC client backend[44928] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.650 UTC client backend[44928] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/temporal-range-integrity 2025-11-30 18:45:08.651 UTC client backend[44910] pg_regress/drop_if_exists ERROR: type "test_domain_exists" does not exist 2025-11-30 18:45:08.651 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP DOMAIN test_domain_exists; 2025-11-30 18:45:08.651 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "foo" at character 8 2025-11-30 18:45:08.651 UTC client backend[44914] pg_regress/errors STATEMENT: CREATE foo; 2025-11-30 18:45:08.651 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near ";" at character 14 2025-11-30 18:45:08.651 UTC client backend[44914] pg_regress/errors STATEMENT: CREATE TABLE ; 2025-11-30 18:45:08.652 UTC client backend[44916] pg_regress/create_am ERROR: function int4in(internal) does not exist 2025-11-30 18:45:08.652 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE TABLE HANDLER int4in; 2025-11-30 18:45:08.652 UTC client backend[44914] pg_regress/errors ERROR: syntax error at end of input at character 13 2025-11-30 18:45:08.652 UTC client backend[44914] pg_regress/errors STATEMENT: CREATE TABLE 2025-11-30 18:45:08.652 UTC client backend[44916] pg_regress/create_am ERROR: function bthandler must return type table_am_handler 2025-11-30 18:45:08.652 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE TABLE HANDLER bthandler; 2025-11-30 18:45:08.652 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "foo" at character 29 2025-11-30 18:45:08.652 UTC client backend[44914] pg_regress/errors STATEMENT: INSERT INTO foo VALUES(123) foo; 2025-11-30 18:45:08.655 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "123" at character 13 2025-11-30 18:45:08.655 UTC client backend[44914] pg_regress/errors STATEMENT: INSERT INTO 123 VALUES(123); 2025-11-30 18:45:08.655 UTC client backend[44902] pg_regress/create_aggregate ERROR: must specify both or neither of serialization and deserialization functions 2025-11-30 18:45:08.655 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_serialize ); 2025-11-30 18:45:08.656 UTC client backend[44928] isolation/temporal-range-integrity LOG: connection ready: setup total=10.533 ms, fork=2.692 ms, authentication=0.108 ms 2025-11-30 18:45:08.656 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2025-11-30 18:45:08.656 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (3). 2025-11-30 18:45:08.656 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (3); 2025-11-30 18:45:08.657 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "123" at character 29 2025-11-30 18:45:08.657 UTC client backend[44914] pg_regress/errors STATEMENT: INSERT INTO foo VALUES(123) 123 ; 2025-11-30 18:45:08.658 UTC client backend[44902] pg_regress/create_aggregate ERROR: function numeric_avg_deserialize(internal) does not exist 2025-11-30 18:45:08.658 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_deserialize, deserialfunc = numeric_avg_deserialize ); 2025-11-30 18:45:08.659 UTC unrecognized[44930] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.659 UTC client backend[44930] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.659 UTC client backend[44930] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/temporal-range-integrity 2025-11-30 18:45:08.659 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2025-11-30 18:45:08.659 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (2). 2025-11-30 18:45:08.659 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (2); 2025-11-30 18:45:08.660 UTC client backend[44930] isolation/temporal-range-integrity LOG: connection ready: setup total=2.097 ms, fork=0.612 ms, authentication=0.122 ms 2025-11-30 18:45:08.660 UTC client backend[44902] pg_regress/create_aggregate ERROR: function numeric_avg_serialize(bytea, internal) does not exist 2025-11-30 18:45:08.660 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_serialize, deserialfunc = numeric_avg_serialize ); 2025-11-30 18:45:08.660 UTC unrecognized[44931] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.661 UTC client backend[44753] isolation/partition-removal-1/s2 LOG: disconnection: session time: 0:00:01.057 user=postgres database=isolation_regression_delay_execution host=[local] 2025-11-30 18:45:08.661 UTC client backend[44747] isolation/partition-removal-1/s1 LOG: disconnection: session time: 0:00:01.083 user=postgres database=isolation_regression_delay_execution host=[local] 2025-11-30 18:45:08.661 UTC client backend[44931] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.661 UTC client backend[44931] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:08.661 UTC client backend[44931] postgres_fdw LOG: connection ready: setup total=3.029 ms, fork=0.363 ms, authentication=0.098 ms 2025-11-30 18:45:08.662 UTC client backend[44902] pg_regress/create_aggregate ERROR: function int4larger(internal, internal) does not exist 2025-11-30 18:45:08.662 UTC client backend[44902] 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-11-30 18:45:08.664 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 94 2025-11-30 18:45:08.664 UTC client backend[44914] 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-11-30 18:45:08.665 UTC client backend[44754] isolation/partition-removal-1/s3 LOG: disconnection: session time: 0:00:01.029 user=postgres database=isolation_regression_delay_execution host=[local] 2025-11-30 18:45:08.665 UTC client backend[43725] isolation/receipt-report/control connection LOG: disconnection: session time: 0:00:07.041 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:08.666 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 90 2025-11-30 18:45:08.666 UTC client backend[44914] 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-11-30 18:45:08.667 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 35 2025-11-30 18:45:08.667 UTC client backend[44914] 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-11-30 18:45:08.667 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 90 2025-11-30 18:45:08.667 UTC client backend[44914] 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-11-30 18:45:08.667 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 100 2025-11-30 18:45:08.667 UTC client backend[44914] 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-11-30 18:45:08.667 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 45 2025-11-30 18:45:08.667 UTC client backend[44914] 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-11-30 18:45:08.667 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 153 2025-11-30 18:45:08.667 UTC client backend[44914] 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-11-30 18:45:08.668 UTC client backend[44914] pg_regress/errors ERROR: syntax error at or near "NUL" at character 180 2025-11-30 18:45:08.668 UTC client backend[44914] 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-11-30 18:45:08.668 UTC client backend[44914] pg_regress/errors LOG: disconnection: session time: 0:00:00.119 user=postgres database=regression host=[local] 2025-11-30 18:45:08.668 UTC client backend[44907] pg_regress/hash_func ERROR: could not identify a hash function for type bit varying 2025-11-30 18:45:08.668 UTC client backend[44907] pg_regress/hash_func STATEMENT: SELECT v as value, hash_array(v)::bit(32) as standard FROM (VALUES ('{101}'::varbit[])) x(v); 2025-11-30 18:45:08.668 UTC client backend[44907] pg_regress/hash_func ERROR: could not identify an extended hash function for type bit varying 2025-11-30 18:45:08.668 UTC client backend[44907] 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-11-30 18:45:08.676 UTC client backend[44908] pg_regress/infinite_recurse ERROR: stack depth limit exceeded 2025-11-30 18:45:08.676 UTC client backend[44908] 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-11-30 18:45:08.676 UTC client backend[44908] pg_regress/infinite_recurse CONTEXT: SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 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-11-30 18:45:08.676 UTC client backend[44908] pg_regress/infinite_recurse STATEMENT: select infinite_recurse(); 2025-11-30 18:45:08.677 UTC unrecognized[44933] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.678 UTC client backend[44933] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.678 UTC client backend[44933] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/temporal-range-integrity 2025-11-30 18:45:08.679 UTC client backend[44933] isolation/temporal-range-integrity LOG: connection ready: setup total=2.617 ms, fork=1.034 ms, authentication=0.129 ms 2025-11-30 18:45:08.681 UTC unrecognized[44934] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.682 UTC client backend[44934] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.682 UTC client backend[44934] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_sequence 2025-11-30 18:45:08.683 UTC client backend[44934] pg_regress/create_sequence LOG: connection ready: setup total=6.080 ms, fork=2.970 ms, authentication=0.125 ms 2025-11-30 18:45:08.684 UTC client backend[44910] pg_regress/drop_if_exists ERROR: type "test_domain_exists" does not exist 2025-11-30 18:45:08.684 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP DOMAIN test_domain_exists; 2025-11-30 18:45:08.684 UTC client backend[44908] pg_regress/infinite_recurse LOG: disconnection: session time: 0:00:00.142 user=postgres database=regression host=[local] 2025-11-30 18:45:08.684 UTC client backend[44916] pg_regress/create_am ERROR: syntax error at or near "USING" at character 41 2025-11-30 18:45:08.684 UTC client backend[44916] pg_regress/create_am STATEMENT: SELECT INTO tableam_tblselectinto_heap2 USING heap2 FROM tableam_tbl_heap2; 2025-11-30 18:45:08.684 UTC client backend[44916] pg_regress/create_am ERROR: syntax error at or near "USING" at character 32 2025-11-30 18:45:08.684 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE VIEW tableam_view_heap2 USING heap2 AS SELECT * FROM tableam_tbl_heap2; 2025-11-30 18:45:08.684 UTC client backend[44910] pg_regress/drop_if_exists ERROR: role "regress_test_u2" does not exist 2025-11-30 18:45:08.684 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP USER regress_test_u2; 2025-11-30 18:45:08.685 UTC client backend[44916] pg_regress/create_am ERROR: syntax error at or near "USING" at character 35 2025-11-30 18:45:08.685 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE SEQUENCE tableam_seq_heap2 USING heap2; 2025-11-30 18:45:08.685 UTC client backend[44910] pg_regress/drop_if_exists ERROR: role "regress_test_u1" does not exist 2025-11-30 18:45:08.685 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP USER regress_test_u1; 2025-11-30 18:45:08.685 UTC client backend[44910] pg_regress/drop_if_exists ERROR: role "regress_test_r2" does not exist 2025-11-30 18:45:08.685 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP ROLE regress_test_r2; 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists ERROR: role "regress_test_r1" does not exist 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP ROLE regress_test_r1; 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists ERROR: role "regress_test_g2" does not exist 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP GROUP regress_test_g2; 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists ERROR: role "regress_test_g1" does not exist 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP GROUP regress_test_g1; 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists ERROR: conversion "test_conversion_exists" does not exist 2025-11-30 18:45:08.689 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP CONVERSION test_conversion_exists; 2025-11-30 18:45:08.690 UTC client backend[44934] pg_regress/create_sequence LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.691 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2025-11-30 18:45:08.691 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (1). 2025-11-30 18:45:08.691 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (1); 2025-11-30 18:45:08.692 UTC client backend[44910] pg_regress/drop_if_exists ERROR: text search parser "test_tsparser_exists" does not exist 2025-11-30 18:45:08.692 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH PARSER test_tsparser_exists; 2025-11-30 18:45:08.693 UTC client backend[44910] pg_regress/drop_if_exists ERROR: text search dictionary "test_tsdict_exists" does not exist 2025-11-30 18:45:08.693 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH DICTIONARY test_tsdict_exists; 2025-11-30 18:45:08.693 UTC client backend[44902] pg_regress/create_aggregate ERROR: cannot change return type of existing function 2025-11-30 18:45:08.693 UTC client backend[44902] pg_regress/create_aggregate HINT: Use DROP AGGREGATE myavg(numeric) first. 2025-11-30 18:45:08.693 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE myavg (numeric) ( stype = numeric, sfunc = numeric_add, finalfunc = numeric_out ); 2025-11-30 18:45:08.693 UTC client backend[44902] pg_regress/create_aggregate ERROR: cannot change routine kind 2025-11-30 18:45:08.693 UTC client backend[44902] pg_regress/create_aggregate DETAIL: "myavg" is an ordinary aggregate function. 2025-11-30 18:45:08.693 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE myavg (order by numeric) ( stype = numeric, sfunc = numeric_add ); 2025-11-30 18:45:08.695 UTC client backend[44902] pg_regress/create_aggregate ERROR: cannot change routine kind 2025-11-30 18:45:08.695 UTC client backend[44902] pg_regress/create_aggregate DETAIL: "sum3" is a function. 2025-11-30 18:45:08.695 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE sum3 (int8,int8,int8) ( stype = int8, sfunc = sum4 ); 2025-11-30 18:45:08.695 UTC client backend[44910] pg_regress/drop_if_exists ERROR: text search template "test_tstemplate_exists" does not exist 2025-11-30 18:45:08.695 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH TEMPLATE test_tstemplate_exists; 2025-11-30 18:45:08.696 UTC client backend[44910] pg_regress/drop_if_exists ERROR: text search configuration "test_tsconfig_exists" does not exist 2025-11-30 18:45:08.696 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH CONFIGURATION test_tsconfig_exists; 2025-11-30 18:45:08.697 UTC client backend[44902] pg_regress/create_aggregate ERROR: parameter "parallel" must be SAFE, RESTRICTED, or UNSAFE 2025-11-30 18:45:08.697 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE mysum (int) ( stype = int, sfunc = int4pl, parallel = pear ); 2025-11-30 18:45:08.697 UTC client backend[44907] pg_regress/hash_func ERROR: could not identify a hash function for type bit varying 2025-11-30 18:45:08.697 UTC client backend[44907] 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-11-30 18:45:08.699 UTC client backend[44902] pg_regress/create_aggregate ERROR: strictness of aggregate's forward and inverse transition functions must match 2025-11-30 18:45:08.699 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE invalidsumdouble (float8) ( stype = float8, sfunc = float8pl, mstype = float8, msfunc = float8pl, minvfunc = float8mi_n ); 2025-11-30 18:45:08.700 UTC client backend[44907] pg_regress/hash_func ERROR: could not identify an extended hash function for type bit varying 2025-11-30 18:45:08.700 UTC client backend[44907] 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-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate ERROR: return type of inverse transition function float8mi_int is not double precision 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE wrongreturntype (float8) ( stype = float8, sfunc = float8pl, mstype = float8, msfunc = float8pl, minvfunc = float8mi_int ); 2025-11-30 18:45:08.700 UTC client backend[44910] pg_regress/drop_if_exists ERROR: extension "test_extension_exists" does not exist 2025-11-30 18:45:08.700 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP EXTENSION test_extension_exists; 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Sfunc1" not recognized 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Basetype" not recognized 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Stype1" not recognized 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Initcond1" not recognized 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Parallel" not recognized 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate ERROR: aggregate stype must be specified 2025-11-30 18:45:08.700 UTC client backend[44902] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE case_agg ( -- old syntax "Sfunc1" = int4pl, "Basetype" = int4, "Stype1" = int4, "Initcond1" = '0', "Parallel" = safe ); 2025-11-30 18:45:08.701 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Stype" not recognized 2025-11-30 18:45:08.701 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Sfunc" not recognized 2025-11-30 18:45:08.701 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc" not recognized 2025-11-30 18:45:08.701 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc_extra" not recognized 2025-11-30 18:45:08.701 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc_modify" not recognized 2025-11-30 18:45:08.701 UTC client backend[44902] pg_regress/create_aggregate WARNING: aggregate attribute "Parallel" not recognized 2025-11-30 18:45:08.701 UTC client backend[44902] pg_regress/create_aggregate ERROR: aggregate stype must be specified 2025-11-30 18:45:08.701 UTC client backend[44902] 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-11-30 18:45:08.702 UTC client backend[44902] pg_regress/create_aggregate LOG: disconnection: session time: 0:00:00.165 user=postgres database=regression host=[local] 2025-11-30 18:45:08.703 UTC client backend[44931] postgres_fdw LOG: disconnection: session time: 0:00:00.043 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:08.707 UTC client backend[44910] pg_regress/drop_if_exists ERROR: function test_function_exists() does not exist 2025-11-30 18:45:08.707 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_function_exists(); 2025-11-30 18:45:08.708 UTC client backend[44910] pg_regress/drop_if_exists ERROR: function test_function_exists(integer, text, integer[]) does not exist 2025-11-30 18:45:08.708 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_function_exists(int, text, int[]); 2025-11-30 18:45:08.711 UTC client backend[44904] pg_regress/create_function_sql ERROR: duplicate function body specified 2025-11-30 18:45:08.711 UTC client backend[44904] 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-11-30 18:45:08.712 UTC client backend[44904] pg_regress/create_function_sql ERROR: SQL function with unquoted function body cannot have polymorphic arguments 2025-11-30 18:45:08.712 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_S_xx(x anyarray) RETURNS anyelement LANGUAGE SQL RETURN x[1]; 2025-11-30 18:45:08.713 UTC client backend[44910] pg_regress/drop_if_exists ERROR: aggregate test_aggregate_exists(*) does not exist 2025-11-30 18:45:08.713 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP AGGREGATE test_aggregate_exists(*); 2025-11-30 18:45:08.718 UTC client backend[44904] pg_regress/create_function_sql ERROR: operator does not exist: date > integer at character 85 2025-11-30 18:45:08.718 UTC client backend[44904] pg_regress/create_function_sql DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:08.718 UTC client backend[44904] pg_regress/create_function_sql HINT: You might need to add explicit type casts. 2025-11-30 18:45:08.718 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_S_xx(x date) RETURNS boolean LANGUAGE SQL RETURN x > 1; 2025-11-30 18:45:08.718 UTC client backend[44912] pg_regress/roleattributes LOG: disconnection: session time: 0:00:00.177 user=postgres database=regression host=[local] 2025-11-30 18:45:08.721 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-11-30 18:45:08.721 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (1, x check failed, -2). 2025-11-30 18:45:08.721 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (1, 'x check failed', -2); 2025-11-30 18:45:08.722 UTC client backend[44910] pg_regress/drop_if_exists ERROR: aggregate test_aggregate_exists(integer) does not exist 2025-11-30 18:45:08.722 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP AGGREGATE test_aggregate_exists(int); 2025-11-30 18:45:08.724 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-11-30 18:45:08.724 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (5, z check failed, 10). 2025-11-30 18:45:08.724 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (5, 'z check failed', 10); 2025-11-30 18:45:08.725 UTC client backend[44925] pg_regress/test_ginpostinglist LOG: disconnection: session time: 0:00:00.094 user=postgres database=regression_test_ginpostinglist host=[local] 2025-11-30 18:45:08.727 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-11-30 18:45:08.727 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (0, check failed, -2). 2025-11-30 18:45:08.727 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (0, 'check failed', -2); 2025-11-30 18:45:08.728 UTC client backend[44910] pg_regress/drop_if_exists ERROR: operator does not exist: integer @#@ integer 2025-11-30 18:45:08.728 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR @#@ (int, int); 2025-11-30 18:45:08.729 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-11-30 18:45:08.729 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (6, check failed, 11). 2025-11-30 18:45:08.729 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (6, 'check failed', 11); 2025-11-30 18:45:08.730 UTC client backend[44905] pg_regress/typed_table ERROR: column "name" specified more than once 2025-11-30 18:45:08.730 UTC client backend[44905] 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-11-30 18:45:08.731 UTC client backend[44907] pg_regress/hash_func LOG: disconnection: session time: 0:00:00.194 user=postgres database=regression host=[local] 2025-11-30 18:45:08.732 UTC client backend[44905] pg_regress/typed_table ERROR: cannot drop type person_type because other objects depend on it 2025-11-30 18:45:08.732 UTC client backend[44905] 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-11-30 18:45:08.732 UTC client backend[44905] pg_regress/typed_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:08.732 UTC client backend[44905] pg_regress/typed_table STATEMENT: DROP TYPE person_type RESTRICT; 2025-11-30 18:45:08.739 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:08.739 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:08.739 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:08.739 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: DELETE FROM statute WHERE statute_cite = '123.45(1)a' AND eff_date = DATE '2008-01-01'; 2025-11-30 18:45:08.742 UTC unrecognized[44940] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.743 UTC client backend[44905] pg_regress/typed_table ERROR: type stuff is the row type of another table 2025-11-30 18:45:08.743 UTC client backend[44905] pg_regress/typed_table DETAIL: A typed table must use a stand-alone composite type created with CREATE TYPE. 2025-11-30 18:45:08.743 UTC client backend[44905] pg_regress/typed_table STATEMENT: CREATE TABLE persons5 OF stuff; 2025-11-30 18:45:08.743 UTC client backend[44910] pg_regress/drop_if_exists ERROR: language "test_language_exists" does not exist 2025-11-30 18:45:08.743 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP LANGUAGE test_language_exists; 2025-11-30 18:45:08.743 UTC client backend[44940] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.743 UTC client backend[44940] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_table 2025-11-30 18:45:08.744 UTC client backend[44940] pg_regress/create_table LOG: connection ready: setup total=5.935 ms, fork=2.071 ms, authentication=0.133 ms 2025-11-30 18:45:08.747 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.747 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (2, -NULL-, -2). 2025-11-30 18:45:08.747 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,z) VALUES (2, -2); 2025-11-30 18:45:08.749 UTC client backend[44913] pg_regress/vacuum ERROR: ANALYZE cannot be executed from VACUUM or ANALYZE 2025-11-30 18:45:08.749 UTC client backend[44913] pg_regress/vacuum CONTEXT: SQL function "do_analyze" statement 1 SQL function "wrap_do_analyze" statement 1 2025-11-30 18:45:08.749 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE vaccluster; 2025-11-30 18:45:08.749 UTC client backend[44905] pg_regress/typed_table ERROR: type tt_enum_type is not a composite type 2025-11-30 18:45:08.749 UTC client backend[44905] pg_regress/typed_table STATEMENT: CREATE TABLE of_tt_enum_type OF tt_enum_type; 2025-11-30 18:45:08.750 UTC client backend[44910] pg_regress/drop_if_exists ERROR: cast from type text to type text does not exist 2025-11-30 18:45:08.750 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP CAST (text AS text); 2025-11-30 18:45:08.750 UTC unrecognized[44941] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.750 UTC client backend[44941] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.750 UTC client backend[44941] [unknown] LOG: connection authorized: user=postgres database=regression_test_extensions application_name=pg_regress/test_extensions 2025-11-30 18:45:08.751 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.751 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (2, Y, -2). 2025-11-30 18:45:08.751 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y) VALUES ('Y'); 2025-11-30 18:45:08.754 UTC client backend[44941] pg_regress/test_extensions LOG: connection ready: setup total=7.076 ms, fork=1.717 ms, authentication=0.132 ms 2025-11-30 18:45:08.755 UTC client backend[44877] pg_regress/test_extensions LOG: disconnection: session time: 0:00:00.242 user=postgres database=regression_test_extensions host=[local] 2025-11-30 18:45:08.756 UTC client backend[44910] pg_regress/drop_if_exists ERROR: trigger "test_trigger_exists" for table "test_exists" does not exist 2025-11-30 18:45:08.756 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON test_exists; 2025-11-30 18:45:08.756 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_check" 2025-11-30 18:45:08.756 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (1, -NULL-, -2). 2025-11-30 18:45:08.756 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,z) VALUES (1, -2); 2025-11-30 18:45:08.763 UTC client backend[44941] pg_regress/test_extensions LOG: test_extensions looped 0 times 2025-11-30 18:45:08.763 UTC client backend[44941] pg_regress/test_extensions CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE 2025-11-30 18:45:08.763 UTC client backend[44941] pg_regress/test_extensions STATEMENT: do 'declare c int = 0; begin while (select count(*) from pg_stat_activity where pid = ' '44877' ') > 0 loop c := c + 1; perform pg_stat_clear_snapshot(); end loop; raise log ''test_extensions looped % times'', c; end'; 2025-11-30 18:45:08.763 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.763 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (5, check failed, -5). 2025-11-30 18:45:08.763 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL VALUES (5, 'check failed', -5); 2025-11-30 18:45:08.765 UTC client backend[44910] pg_regress/drop_if_exists ERROR: relation "no_such_table" does not exist 2025-11-30 18:45:08.765 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON no_such_table; 2025-11-30 18:45:08.770 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_check" 2025-11-30 18:45:08.770 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (5, check failed, 4). 2025-11-30 18:45:08.770 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y,z) VALUES ('check failed', 4); 2025-11-30 18:45:08.771 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view1" 2025-11-30 18:45:08.771 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing DISTINCT are not automatically updatable. 2025-11-30 18:45:08.771 UTC client backend[44915] 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-11-30 18:45:08.771 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view1; 2025-11-30 18:45:08.771 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.771 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (5, check failed, -5). 2025-11-30 18:45:08.771 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,y) VALUES (5, 'check failed'); 2025-11-30 18:45:08.774 UTC client backend[44910] pg_regress/drop_if_exists ERROR: schema "no_such_schema" does not exist 2025-11-30 18:45:08.774 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON no_such_schema.no_such_table; 2025-11-30 18:45:08.778 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.778 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (8, Y, -8). 2025-11-30 18:45:08.778 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y) VALUES ('Y'); 2025-11-30 18:45:08.785 UTC client backend[44878] postgres_fdw LOG: disconnection: session time: 0:00:00.285 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:08.786 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view2" 2025-11-30 18:45:08.786 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing GROUP BY are not automatically updatable. 2025-11-30 18:45:08.786 UTC client backend[44915] 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-11-30 18:45:08.786 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view2; 2025-11-30 18:45:08.786 UTC client backend[44910] pg_regress/drop_if_exists ERROR: rule "test_rule_exists" for relation "test_exists" does not exist 2025-11-30 18:45:08.786 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON test_exists; 2025-11-30 18:45:08.790 UTC client backend[44918] pg_regress/select LOG: disconnection: session time: 0:00:00.241 user=postgres database=regression host=[local] 2025-11-30 18:45:08.792 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "sys_col_check_tbl" violates check constraint "sys_col_check_tbl_check" 2025-11-30 18:45:08.792 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (Olympia, Washington, t, 100). 2025-11-30 18:45:08.792 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO SYS_COL_CHECK_TBL VALUES ('Olympia', 'Washington', true, 100); 2025-11-30 18:45:08.792 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:08.792 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:08.792 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:08.792 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:08.793 UTC unrecognized[44943] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.793 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view3" 2025-11-30 18:45:08.793 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing HAVING are not automatically updatable. 2025-11-30 18:45:08.793 UTC client backend[44915] 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-11-30 18:45:08.793 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view3; 2025-11-30 18:45:08.795 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view4" 2025-11-30 18:45:08.795 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that return aggregate functions are not automatically updatable. 2025-11-30 18:45:08.795 UTC client backend[44915] 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-11-30 18:45:08.795 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view4; 2025-11-30 18:45:08.796 UTC client backend[44943] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.796 UTC client backend[44943] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.796 UTC client backend[44943] pg_regress LOG: connection ready: setup total=10.690 ms, fork=4.401 ms, authentication=0.127 ms 2025-11-30 18:45:08.797 UTC client backend[44903] pg_regress/constraints ERROR: system column "ctid" reference in check constraint is invalid at character 138 2025-11-30 18:45:08.797 UTC client backend[44903] 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-11-30 18:45:08.798 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view5" 2025-11-30 18:45:08.798 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that return window functions are not automatically updatable. 2025-11-30 18:45:08.798 UTC client backend[44915] 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-11-30 18:45:08.798 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view5; 2025-11-30 18:45:08.804 UTC client backend[44909] pg_regress/triggers ERROR: trigger "no_such_trigger" for table "main_table" does not exist 2025-11-30 18:45:08.804 UTC client backend[44909] pg_regress/triggers STATEMENT: COMMENT ON TRIGGER no_such_trigger ON main_table IS 'wrong'; 2025-11-30 18:45:08.805 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view6" 2025-11-30 18:45:08.805 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable. 2025-11-30 18:45:08.805 UTC client backend[44915] 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-11-30 18:45:08.805 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view6; 2025-11-30 18:45:08.805 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_child_check" 2025-11-30 18:45:08.805 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (7, -NULL-, -7, 42, 6). 2025-11-30 18:45:08.805 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,6); 2025-11-30 18:45:08.807 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_tbl_check" 2025-11-30 18:45:08.807 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (6, -NULL-, -7, 42, 7). 2025-11-30 18:45:08.807 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,z,cy) VALUES (6,-7,7); 2025-11-30 18:45:08.808 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.808 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (6, check failed, -6, 42, 7). 2025-11-30 18:45:08.808 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,y,z,cy) VALUES (6,'check failed',-6,7); 2025-11-30 18:45:08.808 UTC client backend[44916] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2025-11-30 18:45:08.808 UTC client backend[44916] pg_regress/create_am STATEMENT: ALTER TABLE heaptable SET ACCESS METHOD heap, SET ACCESS METHOD heap2; 2025-11-30 18:45:08.809 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view7" 2025-11-30 18:45:08.809 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing WITH are not automatically updatable. 2025-11-30 18:45:08.809 UTC client backend[44915] 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-11-30 18:45:08.809 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view7 SET a=a+1; 2025-11-30 18:45:08.809 UTC client backend[44916] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2025-11-30 18:45:08.809 UTC client backend[44916] pg_regress/create_am STATEMENT: ALTER TABLE heaptable SET ACCESS METHOD DEFAULT, SET ACCESS METHOD heap2; 2025-11-30 18:45:08.810 UTC client backend[44916] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2025-11-30 18:45:08.810 UTC client backend[44916] pg_regress/create_am STATEMENT: ALTER MATERIALIZED VIEW heapmv SET ACCESS METHOD heap, SET ACCESS METHOD heap2; 2025-11-30 18:45:08.810 UTC client backend[44910] pg_regress/drop_if_exists ERROR: relation "no_such_table" does not exist 2025-11-30 18:45:08.810 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON no_such_table; 2025-11-30 18:45:08.810 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view8" 2025-11-30 18:45:08.810 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-11-30 18:45:08.810 UTC client backend[44915] 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-11-30 18:45:08.810 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view8 SET a=a+1; 2025-11-30 18:45:08.813 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view9" 2025-11-30 18:45:08.813 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-11-30 18:45:08.813 UTC client backend[44915] 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-11-30 18:45:08.813 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view9 SET a=a+1; 2025-11-30 18:45:08.814 UTC client backend[44943] pg_regress LOG: disconnection: session time: 0:00:00.023 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.817 UTC client backend[44910] pg_regress/drop_if_exists ERROR: schema "no_such_schema" does not exist 2025-11-30 18:45:08.817 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON no_such_schema.no_such_table; 2025-11-30 18:45:08.820 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test_check" 2025-11-30 18:45:08.820 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (-3). 2025-11-30 18:45:08.820 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST) VALUES (-3); 2025-11-30 18:45:08.821 UTC client backend[44910] pg_regress/drop_if_exists ERROR: foreign-data wrapper "test_fdw_exists" does not exist 2025-11-30 18:45:08.821 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP FOREIGN DATA WRAPPER test_fdw_exists; 2025-11-30 18:45:08.823 UTC client backend[44910] pg_regress/drop_if_exists ERROR: server "test_server_exists" does not exist 2025-11-30 18:45:08.823 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP SERVER test_server_exists; 2025-11-30 18:45:08.825 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:08.825 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:08.825 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:08.825 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:08.827 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view10" 2025-11-30 18:45:08.827 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.827 UTC client backend[44915] 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-11-30 18:45:08.827 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view10 SET a=a+1; 2025-11-30 18:45:08.829 UTC client backend[44941] pg_regress/test_extensions ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:08.829 UTC client backend[44941] pg_regress/test_extensions STATEMENT: PREPARE TRANSACTION 'twophase_extension'; 2025-11-30 18:45:08.833 UTC unrecognized[44946] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.833 UTC client backend[44946] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.833 UTC client backend[44946] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.837 UTC client backend[44946] pg_regress LOG: connection ready: setup total=11.208 ms, fork=6.409 ms, authentication=0.117 ms 2025-11-30 18:45:08.844 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view11" 2025-11-30 18:45:08.844 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.844 UTC client backend[44915] 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-11-30 18:45:08.844 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view11 SET a=a+1; 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view12" 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.845 UTC client backend[44915] 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-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view12 SET a=a+1; 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into view "ro_view13" 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.845 UTC client backend[44915] 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-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO ro_view13 VALUES (3, 'Row 3'); 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view13" 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views HINT: To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger. 2025-11-30 18:45:08.845 UTC client backend[44915] 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-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view13" 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.845 UTC client backend[44915] pg_regress/updatable_views HINT: To enable updating the view using MERGE, provide an INSTEAD OF UPDATE trigger. 2025-11-30 18:45:08.845 UTC client backend[44915] 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-11-30 18:45:08.846 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into view "ro_view13" 2025-11-30 18:45:08.846 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.846 UTC client backend[44915] pg_regress/updatable_views HINT: To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger. 2025-11-30 18:45:08.846 UTC client backend[44915] 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-11-30 18:45:08.848 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "ctid" of view "rw_view14" 2025-11-30 18:45:08.848 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-11-30 18:45:08.848 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view14 VALUES (null, 3, 'Row 3'); 2025-11-30 18:45:08.851 UTC client backend[44910] pg_regress/drop_if_exists ERROR: operator class "test_operator_class" does not exist for access method "btree" 2025-11-30 18:45:08.851 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS test_operator_class USING btree; 2025-11-30 18:45:08.852 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update column "ctid" of view "rw_view14" 2025-11-30 18:45:08.852 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-11-30 18:45:08.852 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view14 SET ctid=null WHERE a=3; 2025-11-30 18:45:08.852 UTC client backend[44946] pg_regress LOG: disconnection: session time: 0:00:00.019 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.853 UTC client backend[44906] pg_regress/inherit ERROR: null value in column "aa" of relation "z" violates not-null constraint 2025-11-30 18:45:08.853 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (null, text). 2025-11-30 18:45:08.853 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO z VALUES (NULL, 'text'); 2025-11-30 18:45:08.855 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "atacc2" violates check constraint "atacc1_test_check" 2025-11-30 18:45:08.855 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (-3, null). 2025-11-30 18:45:08.855 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO ATACC2 (TEST) VALUES (-3); 2025-11-30 18:45:08.856 UTC client backend[44910] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-11-30 18:45:08.856 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS test_operator_class USING no_such_am; 2025-11-30 18:45:08.856 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test_check" 2025-11-30 18:45:08.856 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (-3, null). 2025-11-30 18:45:08.856 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST) VALUES (-3); 2025-11-30 18:45:08.857 UTC client backend[44910] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-11-30 18:45:08.857 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS IF EXISTS test_operator_class USING no_such_am; 2025-11-30 18:45:08.857 UTC client backend[44910] pg_regress/drop_if_exists ERROR: operator family "test_operator_family" does not exist for access method "btree" 2025-11-30 18:45:08.857 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY test_operator_family USING btree; 2025-11-30 18:45:08.857 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:08.857 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:08.857 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:08.857 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: DELETE FROM statute WHERE statute_cite = '123.45(1)a' AND eff_date = DATE '2008-01-01'; 2025-11-30 18:45:08.858 UTC client backend[44910] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-11-30 18:45:08.858 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY test_operator_family USING no_such_am; 2025-11-30 18:45:08.858 UTC client backend[44941] pg_regress/test_extensions ERROR: function ext_cor_func() is not a member of extension "test_ext_cor" 2025-11-30 18:45:08.858 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension is not allowed to replace an object that it does not own. 2025-11-30 18:45:08.858 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE OR REPLACE FUNCTION ext_cor_func() RETURNS text AS $$ SELECT 'ext_cor_func: from extension'::text $$ LANGUAGE sql" extension script file "test_ext_cor--1.0.sql", near line 8 2025-11-30 18:45:08.858 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cor; 2025-11-30 18:45:08.860 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot merge into column "ctid" of view "rw_view14" 2025-11-30 18:45:08.860 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-11-30 18:45:08.860 UTC client backend[44915] 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-11-30 18:45:08.860 UTC client backend[44910] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-11-30 18:45:08.860 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY IF EXISTS test_operator_family USING no_such_am; 2025-11-30 18:45:08.861 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test2_check" 2025-11-30 18:45:08.861 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (null, 3). 2025-11-30 18:45:08.861 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST2) VALUES (3); 2025-11-30 18:45:08.862 UTC client backend[44940] pg_regress/create_table LOG: disconnection: session time: 0:00:00.121 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.863 UTC client backend[44905] pg_regress/typed_table LOG: disconnection: session time: 0:00:00.330 user=postgres database=regression host=[local] 2025-11-30 18:45:08.864 UTC client backend[44910] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-11-30 18:45:08.864 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP ACCESS METHOD no_such_am; 2025-11-30 18:45:08.866 UTC unrecognized[44950] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.868 UTC client backend[44910] pg_regress/drop_if_exists ERROR: table "test_exists" does not exist 2025-11-30 18:45:08.868 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP TABLE test_exists; 2025-11-30 18:45:08.868 UTC client backend[44913] pg_regress/vacuum ERROR: ANALYZE cannot be executed from VACUUM or ANALYZE 2025-11-30 18:45:08.868 UTC client backend[44913] pg_regress/vacuum CONTEXT: SQL function "do_analyze" statement 1 SQL function "wrap_do_analyze" statement 1 2025-11-30 18:45:08.868 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM FULL vaccluster; 2025-11-30 18:45:08.871 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2025-11-30 18:45:08.871 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:08.871 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 VALUES (3, 'ROW 3'); 2025-11-30 18:45:08.872 UTC client backend[44950] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.872 UTC client backend[44950] [unknown] LOG: connection authorized: user=postgres database=regression_test_integerset application_name=pg_regress/test_integerset 2025-11-30 18:45:08.877 UTC client backend[44950] pg_regress/test_integerset LOG: connection ready: setup total=13.505 ms, fork=1.442 ms, authentication=0.119 ms 2025-11-30 18:45:08.881 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.881 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (8, try again, -8). 2025-11-30 18:45:08.881 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y,z) SELECT yd, -8 FROM tmp WHERE yd = 'try again'; 2025-11-30 18:45:08.882 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2025-11-30 18:45:08.882 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:08.882 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 (a) VALUES (3) ON CONFLICT (a) DO UPDATE set upper = 'blarg'; 2025-11-30 18:45:08.886 UTC client backend[44941] pg_regress/test_extensions ERROR: view ext_cor_view is not a member of extension "test_ext_cor" 2025-11-30 18:45:08.886 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension is not allowed to replace an object that it does not own. 2025-11-30 18:45:08.886 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE OR REPLACE VIEW ext_cor_view AS SELECT 'ext_cor_view: from extension'::text AS col" extension script file "test_ext_cor--1.0.sql", near line 11 2025-11-30 18:45:08.886 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cor; 2025-11-30 18:45:08.887 UTC client backend[44941] pg_regress/test_extensions ERROR: function ext_cor_func() does not exist at character 8 2025-11-30 18:45:08.887 UTC client backend[44941] pg_regress/test_extensions DETAIL: There is no function of that name. 2025-11-30 18:45:08.887 UTC client backend[44941] pg_regress/test_extensions STATEMENT: SELECT ext_cor_func(); 2025-11-30 18:45:08.889 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2025-11-30 18:45:08.889 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:08.889 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 (a) VALUES (4); 2025-11-30 18:45:08.889 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-11-30 18:45:08.889 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (-4, Y, 4). 2025-11-30 18:45:08.889 UTC client backend[44903] pg_regress/constraints STATEMENT: UPDATE INSERT_TBL SET x = z, z = x; 2025-11-30 18:45:08.892 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update column "upper" of view "rw_view15" 2025-11-30 18:45:08.892 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:08.892 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view15 SET upper='ROW 3' WHERE a=3; 2025-11-30 18:45:08.892 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:08.892 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:08.892 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:08.892 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:08.893 UTC client backend[44903] pg_regress/constraints ERROR: new row for relation "copy_tbl" violates check constraint "copy_con" 2025-11-30 18:45:08.893 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (7, check failed, 6). 2025-11-30 18:45:08.893 UTC client backend[44903] pg_regress/constraints CONTEXT: COPY copy_tbl, line 2: "7 check failed 6" 2025-11-30 18:45:08.893 UTC client backend[44903] pg_regress/constraints STATEMENT: COPY COPY_TBL FROM '/tmp/cirrus-ci-build/src/test/regress/data/constrf.data'; 2025-11-30 18:45:08.901 UTC unrecognized[44953] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.902 UTC client backend[44953] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.902 UTC client backend[44953] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.903 UTC client backend[44953] pg_regress LOG: connection ready: setup total=2.841 ms, fork=1.497 ms, authentication=0.120 ms 2025-11-30 18:45:08.903 UTC client backend[44953] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.906 UTC client backend[44941] pg_regress/test_extensions ERROR: type test_ext_type is not a member of extension "test_ext_cor" 2025-11-30 18:45:08.906 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension is not allowed to replace an object that it does not own. 2025-11-30 18:45:08.906 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE TYPE test_ext_type AS ENUM('x', 'y')" extension script file "test_ext_cor--1.0.sql", near line 17 2025-11-30 18:45:08.906 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cor; 2025-11-30 18:45:08.907 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update column "upper" of view "rw_view15" 2025-11-30 18:45:08.907 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:08.907 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view15 SET upper=DEFAULT WHERE a=3; 2025-11-30 18:45:08.909 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "primary_tbl_pkey" 2025-11-30 18:45:08.909 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-11-30 18:45:08.909 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL VALUES (1, 'three'); 2025-11-30 18:45:08.909 UTC client backend[44941] pg_regress/test_extensions ERROR: operator <<@@(point,polygon) is not a member of extension "test_ext_cor" 2025-11-30 18:45:08.909 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension is not allowed to replace an object that it does not own. 2025-11-30 18:45:08.909 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE OPERATOR <<@@ ( PROCEDURE = pt_contained_poly, LEFTARG = point, RIGHTARG = polygon )" extension script file "test_ext_cor--1.0.sql", near line 19 2025-11-30 18:45:08.909 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cor; 2025-11-30 18:45:08.910 UTC client backend[44910] pg_regress/drop_if_exists ERROR: function name "test_ambiguous_funcname" is not unique 2025-11-30 18:45:08.910 UTC client backend[44910] pg_regress/drop_if_exists HINT: Specify the argument list to select the function unambiguously. 2025-11-30 18:45:08.910 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_ambiguous_funcname; 2025-11-30 18:45:08.910 UTC client backend[44910] pg_regress/drop_if_exists ERROR: function name "test_ambiguous_funcname" is not unique 2025-11-30 18:45:08.910 UTC client backend[44910] pg_regress/drop_if_exists HINT: Specify the argument list to select the function unambiguously. 2025-11-30 18:45:08.910 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION IF EXISTS test_ambiguous_funcname; 2025-11-30 18:45:08.910 UTC client backend[44903] pg_regress/constraints ERROR: null value in column "i" of relation "primary_tbl" violates not-null constraint 2025-11-30 18:45:08.910 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (null, six). 2025-11-30 18:45:08.910 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL (t) VALUES ('six'); 2025-11-30 18:45:08.914 UTC client backend[44910] pg_regress/drop_if_exists ERROR: procedure name "test_ambiguous_procname" is not unique 2025-11-30 18:45:08.914 UTC client backend[44910] pg_regress/drop_if_exists HINT: Specify the argument list to select the procedure unambiguously. 2025-11-30 18:45:08.914 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP PROCEDURE test_ambiguous_procname; 2025-11-30 18:45:08.917 UTC client backend[44910] pg_regress/drop_if_exists ERROR: procedure name "test_ambiguous_procname" is not unique 2025-11-30 18:45:08.917 UTC client backend[44910] pg_regress/drop_if_exists HINT: Specify the argument list to select the procedure unambiguously. 2025-11-30 18:45:08.917 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP PROCEDURE IF EXISTS test_ambiguous_procname; 2025-11-30 18:45:08.920 UTC client backend[44915] pg_regress/updatable_views ERROR: multiple assignments to same column "a" 2025-11-30 18:45:08.920 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view16 VALUES (3, 'Row 3', 3); 2025-11-30 18:45:08.921 UTC client backend[44910] pg_regress/drop_if_exists ERROR: routine name "test_ambiguous_procname" is not unique 2025-11-30 18:45:08.921 UTC client backend[44910] pg_regress/drop_if_exists HINT: Specify the argument list to select the routine unambiguously. 2025-11-30 18:45:08.921 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: DROP ROUTINE IF EXISTS test_ambiguous_procname; 2025-11-30 18:45:08.921 UTC unrecognized[44955] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.922 UTC client backend[44955] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.922 UTC client backend[44955] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:08.922 UTC client backend[44955] pg_regress LOG: connection ready: setup total=4.652 ms, fork=3.060 ms, authentication=0.125 ms 2025-11-30 18:45:08.923 UTC client backend[44909] pg_regress/triggers ERROR: duplicate trigger events specified at or near "ON" at character 63 2025-11-30 18:45:08.923 UTC client backend[44909] 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-11-30 18:45:08.923 UTC client backend[44909] pg_regress/triggers ERROR: column "a" specified more than once 2025-11-30 18:45:08.923 UTC client backend[44909] 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-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers ERROR: syntax error at or near "OF" at character 42 2025-11-30 18:45:08.924 UTC client backend[44909] 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-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers ERROR: INSERT trigger's WHEN condition cannot reference OLD values at character 88 2025-11-30 18:45:08.924 UTC client backend[44909] 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-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers ERROR: DELETE trigger's WHEN condition cannot reference NEW values at character 97 2025-11-30 18:45:08.924 UTC client backend[44909] 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-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers ERROR: BEFORE trigger's WHEN condition cannot reference NEW system columns at character 88 2025-11-30 18:45:08.924 UTC client backend[44909] 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-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers ERROR: statement trigger's WHEN condition cannot reference column values at character 90 2025-11-30 18:45:08.924 UTC client backend[44909] 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-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers ERROR: cannot drop column b of table main_table because other objects depend on it 2025-11-30 18:45:08.924 UTC client backend[44909] 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-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:08.924 UTC client backend[44909] pg_regress/triggers STATEMENT: ALTER TABLE main_table DROP COLUMN b; 2025-11-30 18:45:08.926 UTC client backend[44915] pg_regress/updatable_views ERROR: multiple assignments to same column "a" 2025-11-30 18:45:08.926 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view16 SET a=3, aa=-3 WHERE a=3; 2025-11-30 18:45:08.929 UTC unrecognized[44956] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.929 UTC client backend[44956] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.929 UTC client backend[44956] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_transform 2025-11-30 18:45:08.931 UTC client backend[44956] pg_regress/create_transform LOG: connection ready: setup total=2.665 ms, fork=0.604 ms, authentication=0.118 ms 2025-11-30 18:45:08.932 UTC client backend[44910] pg_regress/drop_if_exists ERROR: database "test_database_exists" does not exist 2025-11-30 18:45:08.932 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: drop database test_database_exists (force); 2025-11-30 18:45:08.934 UTC client backend[44910] pg_regress/drop_if_exists ERROR: database "test_database_exists" does not exist 2025-11-30 18:45:08.934 UTC client backend[44910] pg_regress/drop_if_exists STATEMENT: drop database test_database_exists with (force); 2025-11-30 18:45:08.936 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into view "ro_view1" 2025-11-30 18:45:08.936 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing DISTINCT are not automatically updatable. 2025-11-30 18:45:08.936 UTC client backend[44915] 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-11-30 18:45:08.936 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO ro_view17 VALUES (3, 'ROW 3'); 2025-11-30 18:45:08.936 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "ro_view18" 2025-11-30 18:45:08.936 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.936 UTC client backend[44915] 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-11-30 18:45:08.936 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view18; 2025-11-30 18:45:08.936 UTC client backend[44910] pg_regress/drop_if_exists LOG: disconnection: session time: 0:00:00.391 user=postgres database=regression host=[local] 2025-11-30 18:45:08.938 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view19" 2025-11-30 18:45:08.938 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-11-30 18:45:08.938 UTC client backend[44915] 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-11-30 18:45:08.938 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view19 SET last_value=1000; 2025-11-30 18:45:08.939 UTC client backend[44955] pg_regress LOG: disconnection: session time: 0:00:00.018 user=postgres database=postgres host=[local] 2025-11-30 18:45:08.940 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "ro_view20" 2025-11-30 18:45:08.940 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views that return set-returning functions are not automatically updatable. 2025-11-30 18:45:08.940 UTC client backend[44915] 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-11-30 18:45:08.940 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE ro_view20 SET b=upper(b); 2025-11-30 18:45:08.943 UTC client backend[44956] pg_regress/create_transform LOG: disconnection: session time: 0:00:00.014 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:08.947 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:08.947 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:08.947 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:08.947 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:08.948 UTC client backend[44904] pg_regress/create_function_sql ERROR: could not find a function named "functest_b_1" 2025-11-30 18:45:08.948 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: DROP FUNCTION functest_b_1; 2025-11-30 18:45:08.950 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into view "rw_view16" 2025-11-30 18:45:08.950 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2025-11-30 18:45:08.950 UTC client backend[44915] 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-11-30 18:45:08.950 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view16 (a, b) VALUES (3, 'Row 3'); 2025-11-30 18:45:08.951 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update view "rw_view16" 2025-11-30 18:45:08.951 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2025-11-30 18:45:08.951 UTC client backend[44915] 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-11-30 18:45:08.951 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view16 SET b='ROW 2' WHERE a=2; 2025-11-30 18:45:08.953 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "rw_view16" 2025-11-30 18:45:08.953 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2025-11-30 18:45:08.953 UTC client backend[44915] 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-11-30 18:45:08.953 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view16 WHERE a=2; 2025-11-30 18:45:08.953 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot execute MERGE on relation "rw_view16" 2025-11-30 18:45:08.953 UTC client backend[44915] pg_regress/updatable_views DETAIL: MERGE is not supported for relations with rules. 2025-11-30 18:45:08.953 UTC client backend[44915] 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-11-30 18:45:08.960 UTC client backend[44941] pg_regress/test_extensions ERROR: collation ext_cine_coll is not a member of extension "test_ext_cine" 2025-11-30 18:45:08.960 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension may only use CREATE ... IF NOT EXISTS to skip object creation if the conflicting object is one that it already owns. 2025-11-30 18:45:08.960 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE COLLATION IF NOT EXISTS ext_cine_coll ( LC_COLLATE = "POSIX", LC_CTYPE = "POSIX" )" extension script file "test_ext_cine--1.0.sql", near line 10 2025-11-30 18:45:08.960 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cine; 2025-11-30 18:45:08.978 UTC client backend[44904] pg_regress/create_function_sql ERROR: function name "functest_b_2" is not unique 2025-11-30 18:45:08.978 UTC client backend[44904] pg_regress/create_function_sql HINT: Specify the argument list to select the function unambiguously. 2025-11-30 18:45:08.978 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: DROP FUNCTION functest_b_2; 2025-11-30 18:45:08.983 UTC unrecognized[44962] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.983 UTC client backend[44962] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.983 UTC client backend[44962] [unknown] LOG: connection authorized: user=postgres database=regression_test_lfind application_name=pg_regress/test_lfind 2025-11-30 18:45:08.988 UTC client backend[44962] pg_regress/test_lfind LOG: connection ready: setup total=12.455 ms, fork=2.400 ms, authentication=0.118 ms 2025-11-30 18:45:08.990 UTC client backend[44941] pg_regress/test_extensions ERROR: materialized view ext_cine_mv is not a member of extension "test_ext_cine" 2025-11-30 18:45:08.990 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension may only use CREATE ... IF NOT EXISTS to skip object creation if the conflicting object is one that it already owns. 2025-11-30 18:45:08.990 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE MATERIALIZED VIEW IF NOT EXISTS ext_cine_mv AS SELECT 42 AS f1" extension script file "test_ext_cine--1.0.sql", near line 13 2025-11-30 18:45:08.990 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cine; 2025-11-30 18:45:08.995 UTC unrecognized[44964] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:08.995 UTC client backend[44964] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:08.995 UTC client backend[44964] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/alter_table 2025-11-30 18:45:08.996 UTC client backend[44964] pg_regress/alter_table LOG: connection ready: setup total=11.310 ms, fork=4.753 ms, authentication=0.128 ms 2025-11-30 18:45:08.998 UTC client backend[44941] pg_regress/test_extensions ERROR: server ext_cine_srv is not a member of extension "test_ext_cine" 2025-11-30 18:45:08.998 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension may only use CREATE ... IF NOT EXISTS to skip object creation if the conflicting object is one that it already owns. 2025-11-30 18:45:08.998 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE SERVER IF NOT EXISTS ext_cine_srv FOREIGN DATA WRAPPER ext_cine_fdw" extension script file "test_ext_cine--1.0.sql", near line 17 2025-11-30 18:45:08.998 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cine; 2025-11-30 18:45:09.003 UTC client backend[44903] pg_regress/constraints ERROR: null value in column "i" of relation "primary_tbl" violates not-null constraint 2025-11-30 18:45:09.003 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (null, six). 2025-11-30 18:45:09.003 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL (t) VALUES ('six'); 2025-11-30 18:45:09.004 UTC client backend[44904] pg_regress/create_function_sql ERROR: cannot change routine kind 2025-11-30 18:45:09.004 UTC client backend[44904] pg_regress/create_function_sql DETAIL: "functest1" is a function. 2025-11-30 18:45:09.004 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE OR REPLACE FUNCTION functest1(a int) RETURNS int LANGUAGE SQL WINDOW AS 'SELECT $1'; 2025-11-30 18:45:09.016 UTC client backend[44916] pg_regress/create_am ERROR: zero-length delimited identifier at or near """" at character 37 2025-11-30 18:45:09.016 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING ""; 2025-11-30 18:45:09.017 UTC client backend[44916] pg_regress/create_am ERROR: access method "i_do_not_exist_am" does not exist 2025-11-30 18:45:09.017 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING i_do_not_exist_am; 2025-11-30 18:45:09.017 UTC client backend[44916] pg_regress/create_am ERROR: access method "I do not exist AM" does not exist 2025-11-30 18:45:09.017 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING "I do not exist AM"; 2025-11-30 18:45:09.017 UTC client backend[44916] pg_regress/create_am ERROR: access method "btree" is not of type TABLE 2025-11-30 18:45:09.017 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING "btree"; 2025-11-30 18:45:09.025 UTC client backend[44962] pg_regress/test_lfind LOG: disconnection: session time: 0:00:00.047 user=postgres database=regression_test_lfind host=[local] 2025-11-30 18:45:09.026 UTC client backend[44913] pg_regress/vacuum ERROR: PARALLEL option must be between 0 and 1024 at character 9 2025-11-30 18:45:09.026 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL -1) pvactst; 2025-11-30 18:45:09.027 UTC client backend[44916] pg_regress/create_am ERROR: "tableam_parted_a_heap2" is not partitioned 2025-11-30 18:45:09.027 UTC client backend[44916] pg_regress/create_am STATEMENT: CREATE FOREIGN TABLE fp PARTITION OF tableam_parted_a_heap2 DEFAULT SERVER x; 2025-11-30 18:45:09.028 UTC client backend[44916] pg_regress/create_am ERROR: cannot drop access method heap2 because other objects depend on it 2025-11-30 18:45:09.028 UTC client backend[44916] 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-11-30 18:45:09.028 UTC client backend[44916] pg_regress/create_am HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:09.028 UTC client backend[44916] pg_regress/create_am STATEMENT: DROP ACCESS METHOD heap2; 2025-11-30 18:45:09.030 UTC client backend[44916] pg_regress/create_am LOG: disconnection: session time: 0:00:00.479 user=postgres database=regression host=[local] 2025-11-30 18:45:09.032 UTC client backend[44913] pg_regress/vacuum ERROR: VACUUM FULL cannot be performed in parallel 2025-11-30 18:45:09.032 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL 2, FULL TRUE) pvactst; 2025-11-30 18:45:09.032 UTC client backend[44913] pg_regress/vacuum ERROR: parallel requires an integer value 2025-11-30 18:45:09.032 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL) pvactst; 2025-11-30 18:45:09.034 UTC client backend[44904] pg_regress/create_function_sql ERROR: cannot change routine kind 2025-11-30 18:45:09.034 UTC client backend[44904] pg_regress/create_function_sql DETAIL: "functest1" is a function. 2025-11-30 18:45:09.034 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE OR REPLACE PROCEDURE functest1(a int) LANGUAGE SQL AS 'SELECT $1'; 2025-11-30 18:45:09.036 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.036 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.036 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.036 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:09.040 UTC client backend[44941] pg_regress/test_extensions ERROR: schema ext_cine_schema is not a member of extension "test_ext_cine" 2025-11-30 18:45:09.040 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension may only use CREATE ... IF NOT EXISTS to skip object creation if the conflicting object is one that it already owns. 2025-11-30 18:45:09.040 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE SCHEMA IF NOT EXISTS ext_cine_schema" extension script file "test_ext_cine--1.0.sql", near line 19 2025-11-30 18:45:09.040 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cine; 2025-11-30 18:45:09.046 UTC client backend[44941] pg_regress/test_extensions ERROR: sequence ext_cine_seq is not a member of extension "test_ext_cine" 2025-11-30 18:45:09.046 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension may only use CREATE ... IF NOT EXISTS to skip object creation if the conflicting object is one that it already owns. 2025-11-30 18:45:09.046 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE SEQUENCE IF NOT EXISTS ext_cine_seq" extension script file "test_ext_cine--1.0.sql", near line 21 2025-11-30 18:45:09.046 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cine; 2025-11-30 18:45:09.054 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.054 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-11-30 18:45:09.054 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'three'); 2025-11-30 18:45:09.077 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.077 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-11-30 18:45:09.077 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE INSERT ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row'); 2025-11-30 18:45:09.078 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.078 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-11-30 18:45:09.078 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE UPDATE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row'); 2025-11-30 18:45:09.078 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.078 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-11-30 18:45:09.078 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE DELETE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row'); 2025-11-30 18:45:09.080 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.080 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-11-30 18:45:09.080 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER INSERT ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row'); 2025-11-30 18:45:09.083 UTC client backend[44903] pg_regress/constraints ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-11-30 18:45:09.083 UTC client backend[44903] pg_regress/constraints HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-11-30 18:45:09.083 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'a'), (2, 'b'), (2, 'b') ON CONFLICT (i) DO UPDATE SET t = 'fails'; 2025-11-30 18:45:09.084 UTC client backend[44941] pg_regress/test_extensions ERROR: table ext_cine_tab1 is not a member of extension "test_ext_cine" 2025-11-30 18:45:09.084 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension may only use CREATE ... IF NOT EXISTS to skip object creation if the conflicting object is one that it already owns. 2025-11-30 18:45:09.084 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE TABLE IF NOT EXISTS ext_cine_tab1 (x int)" extension script file "test_ext_cine--1.0.sql", near line 23 2025-11-30 18:45:09.084 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cine; 2025-11-30 18:45:09.088 UTC client backend[44906] pg_regress/inherit ERROR: column "tomorrow" inherits conflicting default values 2025-11-30 18:45:09.088 UTC client backend[44906] pg_regress/inherit HINT: To resolve the conflict, specify a default explicitly. 2025-11-30 18:45:09.088 UTC client backend[44906] pg_regress/inherit STATEMENT: CREATE TABLE otherchild () INHERITS (firstparent, thirdparent); 2025-11-30 18:45:09.089 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.089 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-11-30 18:45:09.089 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'three'); 2025-11-30 18:45:09.089 UTC client backend[44913] pg_regress/vacuum WARNING: disabling parallel option of vacuum on "tmp" --- cannot vacuum temporary tables in parallel 2025-11-30 18:45:09.093 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.093 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(null) already exists. 2025-11-30 18:45:09.093 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL (t) VALUES ('seven'); 2025-11-30 18:45:09.100 UTC client backend[44904] pg_regress/create_function_sql ERROR: division by zero 2025-11-30 18:45:09.100 UTC client backend[44904] pg_regress/create_function_sql CONTEXT: SQL function "part_hashint4_error" statement 1 2025-11-30 18:45:09.100 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: INSERT INTO pt VALUES (1); 2025-11-30 18:45:09.100 UTC client backend[44904] pg_regress/create_function_sql ERROR: division by zero 2025-11-30 18:45:09.100 UTC client backend[44904] pg_regress/create_function_sql CONTEXT: SQL function "part_hashint4_error" statement 1 2025-11-30 18:45:09.100 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: INSERT INTO pt VALUES (1); 2025-11-30 18:45:09.101 UTC client backend[44904] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2025-11-30 18:45:09.101 UTC client backend[44904] pg_regress/create_function_sql DETAIL: Actual return type is text. 2025-11-30 18:45:09.101 UTC client backend[44904] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2025-11-30 18:45:09.101 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT ''not an integer'';'; 2025-11-30 18:45:09.102 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.102 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-11-30 18:45:09.102 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER UPDATE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row'); 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql ERROR: syntax error at or near "not" at character 62 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'not even SQL'; 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql DETAIL: Final statement must return exactly one column. 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT 1, 2, 3;'; 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql ERROR: there is no parameter $2 at character 69 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT $2;'; 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql ERROR: only one AS item needed for language "sql" 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'a', 'b'; 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql DETAIL: Function's final statement must be SELECT or INSERT/UPDATE/DELETE/MERGE RETURNING. 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2025-11-30 18:45:09.103 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS ''; 2025-11-30 18:45:09.104 UTC client backend[44904] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer[] 2025-11-30 18:45:09.104 UTC client backend[44904] pg_regress/create_function_sql DETAIL: Function's final statement must be SELECT or INSERT/UPDATE/DELETE/MERGE RETURNING. 2025-11-30 18:45:09.104 UTC client backend[44904] pg_regress/create_function_sql CONTEXT: SQL function "test1" during startup 2025-11-30 18:45:09.104 UTC client backend[44904] pg_regress/create_function_sql STATEMENT: SELECT test1(0); 2025-11-30 18:45:09.111 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.111 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-11-30 18:45:09.111 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER DELETE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row'); 2025-11-30 18:45:09.114 UTC client backend[44904] pg_regress/create_function_sql LOG: disconnection: session time: 0:00:00.578 user=postgres database=regression host=[local] 2025-11-30 18:45:09.121 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.121 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.121 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.121 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:09.122 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_t_key" 2025-11-30 18:45:09.122 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i, t)=(1, one) already exists. 2025-11-30 18:45:09.122 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'one'); 2025-11-30 18:45:09.123 UTC client backend[44906] pg_regress/inherit ERROR: cannot alter inherited column "f1" of relation "childtab" 2025-11-30 18:45:09.123 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table parent1 alter column f1 type bigint; 2025-11-30 18:45:09.126 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.126 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have TRUNCATE triggers. 2025-11-30 18:45:09.126 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE TRUNCATE ON main_view EXECUTE PROCEDURE trigger_func('before_tru_row'); 2025-11-30 18:45:09.127 UTC client backend[44941] pg_regress/test_extensions ERROR: table ext_cine_tab2 is not a member of extension "test_ext_cine" 2025-11-30 18:45:09.127 UTC client backend[44941] pg_regress/test_extensions DETAIL: An extension may only use CREATE ... IF NOT EXISTS to skip object creation if the conflicting object is one that it already owns. 2025-11-30 18:45:09.127 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL statement "CREATE TABLE IF NOT EXISTS ext_cine_tab2 AS SELECT 42 AS y" extension script file "test_ext_cine--1.0.sql", near line 25 2025-11-30 18:45:09.127 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_cine; 2025-11-30 18:45:09.143 UTC client backend[44909] pg_regress/triggers ERROR: "main_view" is a view 2025-11-30 18:45:09.143 UTC client backend[44909] pg_regress/triggers DETAIL: Views cannot have TRUNCATE triggers. 2025-11-30 18:45:09.143 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER TRUNCATE ON main_view EXECUTE PROCEDURE trigger_func('before_tru_row'); 2025-11-30 18:45:09.145 UTC client backend[44909] pg_regress/triggers ERROR: "main_table" is a table 2025-11-30 18:45:09.145 UTC client backend[44909] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-11-30 18:45:09.145 UTC client backend[44909] 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-11-30 18:45:09.146 UTC client backend[44909] pg_regress/triggers ERROR: "main_table" is a table 2025-11-30 18:45:09.146 UTC client backend[44909] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-11-30 18:45:09.146 UTC client backend[44909] 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-11-30 18:45:09.148 UTC client backend[44909] pg_regress/triggers ERROR: "main_table" is a table 2025-11-30 18:45:09.148 UTC client backend[44909] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-11-30 18:45:09.148 UTC client backend[44909] 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-11-30 18:45:09.149 UTC client backend[44909] pg_regress/triggers ERROR: INSTEAD OF triggers cannot have WHEN conditions 2025-11-30 18:45:09.149 UTC client backend[44909] 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-11-30 18:45:09.160 UTC client backend[44906] pg_regress/inherit ERROR: constraint "p2chk" conflicts with inherited constraint on relation "c2" 2025-11-30 18:45:09.160 UTC client backend[44906] pg_regress/inherit STATEMENT: create table c2 (constraint p2chk check (ff1 > 10) no inherit) inherits (p1); 2025-11-30 18:45:09.169 UTC client backend[44909] pg_regress/triggers ERROR: INSTEAD OF triggers cannot have column lists 2025-11-30 18:45:09.169 UTC client backend[44909] 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-11-30 18:45:09.172 UTC client backend[44871] postgres_fdw LOG: disconnection: session time: 0:00:00.691 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:09.173 UTC client backend[44909] pg_regress/triggers ERROR: INSTEAD OF triggers must be FOR EACH ROW 2025-11-30 18:45:09.173 UTC client backend[44909] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_view EXECUTE PROCEDURE view_trigger('instead_of_upd'); 2025-11-30 18:45:09.174 UTC unrecognized[44972] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.174 UTC client backend[44972] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.174 UTC client backend[44972] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.175 UTC client backend[44972] pg_regress LOG: connection ready: setup total=2.782 ms, fork=1.531 ms, authentication=0.113 ms 2025-11-30 18:45:09.176 UTC client backend[44972] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.181 UTC client backend[44941] pg_regress/test_extensions ERROR: invalid character in extension "test_ext_extschema" schema: must not contain any of ""$'\" 2025-11-30 18:45:09.181 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_extschema SCHEMA has$dollar; 2025-11-30 18:45:09.194 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.194 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-11-30 18:45:09.194 UTC client backend[44903] pg_regress/constraints STATEMENT: UPDATE unique_tbl SET i = 1 WHERE i = 0; 2025-11-30 18:45:09.197 UTC client backend[44964] pg_regress/alter_table LOG: disconnection: session time: 0:00:00.207 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.200 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.200 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:09.200 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.200 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: INSERT INTO offense VALUES (1, '123.45(1)a', DATE '2009-05-15'); 2025-11-30 18:45:09.200 UTC unrecognized[44975] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.201 UTC client backend[44975] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.201 UTC client backend[44975] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.201 UTC client backend[44975] pg_regress LOG: connection ready: setup total=2.520 ms, fork=1.193 ms, authentication=0.118 ms 2025-11-30 18:45:09.202 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.202 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-11-30 18:45:09.202 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMIT; 2025-11-30 18:45:09.202 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.202 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-11-30 18:45:09.202 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO unique_tbl VALUES (3, 'Three'); 2025-11-30 18:45:09.208 UTC unrecognized[44977] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.208 UTC client backend[44977] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.208 UTC client backend[44977] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:09.209 UTC client backend[44977] postgres_fdw LOG: connection ready: setup total=4.973 ms, fork=2.841 ms, authentication=0.132 ms 2025-11-30 18:45:09.215 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.215 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-11-30 18:45:09.215 UTC client backend[44903] pg_regress/constraints STATEMENT: SET CONSTRAINTS ALL IMMEDIATE; 2025-11-30 18:45:09.218 UTC client backend[44975] pg_regress LOG: disconnection: session time: 0:00:00.018 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.225 UTC unrecognized[44979] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.225 UTC client backend[44979] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.225 UTC client backend[44979] [unknown] LOG: connection authorized: user=postgres database=regression_test_parser application_name=pg_regress/test_parser 2025-11-30 18:45:09.230 UTC client backend[44979] pg_regress/test_parser LOG: connection ready: setup total=6.087 ms, fork=1.032 ms, authentication=0.119 ms 2025-11-30 18:45:09.230 UTC client backend[44913] pg_regress/vacuum ERROR: null value in column "i" of relation "vac_truncate_test" violates not-null constraint 2025-11-30 18:45:09.230 UTC client backend[44913] pg_regress/vacuum DETAIL: Failing row contains (null, null). 2025-11-30 18:45:09.230 UTC client backend[44913] pg_regress/vacuum STATEMENT: INSERT INTO vac_truncate_test VALUES (1, NULL), (NULL, NULL); 2025-11-30 18:45:09.232 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key" 2025-11-30 18:45:09.232 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-11-30 18:45:09.232 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO parted_uniq_tbl VALUES (1); 2025-11-30 18:45:09.233 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key" 2025-11-30 18:45:09.233 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-11-30 18:45:09.233 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMIT; 2025-11-30 18:45:09.236 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.236 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:09.236 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.236 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: DELETE FROM statute WHERE statute_cite = '123.45(1)a' AND eff_date = DATE '2008-01-01'; 2025-11-30 18:45:09.241 UTC client backend[44913] pg_regress/vacuum ERROR: null value in column "i" of relation "vac_truncate_test" violates not-null constraint 2025-11-30 18:45:09.241 UTC client backend[44913] pg_regress/vacuum DETAIL: Failing row contains (null, null). 2025-11-30 18:45:09.241 UTC client backend[44913] pg_regress/vacuum STATEMENT: INSERT INTO vac_truncate_test VALUES (1, NULL), (NULL, NULL); 2025-11-30 18:45:09.243 UTC client backend[44979] pg_regress/test_parser LOG: disconnection: session time: 0:00:00.018 user=postgres database=regression_test_parser host=[local] 2025-11-30 18:45:09.254 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.254 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.254 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.254 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:09.260 UTC client backend[44941] pg_regress/test_extensions ERROR: extension "test_ext_req_schema1" does not support SET SCHEMA 2025-11-30 18:45:09.260 UTC client backend[44941] pg_regress/test_extensions DETAIL: function test_func_dep2.dep_req1() is not in the extension's schema "test_func_dep1" 2025-11-30 18:45:09.260 UTC client backend[44941] pg_regress/test_extensions STATEMENT: ALTER EXTENSION test_ext_req_schema1 SET SCHEMA test_func_dep3; 2025-11-30 18:45:09.264 UTC client backend[44941] pg_regress/test_extensions ERROR: invalid character in extension "test_ext_req_schema1" schema: must not contain any of ""$'\" 2025-11-30 18:45:09.264 UTC client backend[44941] pg_regress/test_extensions STATEMENT: CREATE EXTENSION test_ext_req_schema3 CASCADE; 2025-11-30 18:45:09.268 UTC client backend[44941] pg_regress/test_extensions ERROR: cannot SET SCHEMA of extension "test_ext_req_schema1" because other extensions prevent it 2025-11-30 18:45:09.268 UTC client backend[44941] pg_regress/test_extensions DETAIL: Extension "test_ext_req_schema3" requests no relocation of extension "test_ext_req_schema1". 2025-11-30 18:45:09.268 UTC client backend[44941] pg_regress/test_extensions STATEMENT: ALTER EXTENSION test_ext_req_schema1 SET SCHEMA test_s_dep2; 2025-11-30 18:45:09.269 UTC client backend[44913] pg_regress/vacuum ERROR: column "a" of relation "vacparted" appears more than once 2025-11-30 18:45:09.269 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM ANALYZE vacparted(a,b,a); 2025-11-30 18:45:09.275 UTC client backend[44913] pg_regress/vacuum ERROR: column "b" of relation "vacparted" appears more than once 2025-11-30 18:45:09.275 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE vacparted(a,b,b); 2025-11-30 18:45:09.279 UTC client backend[44941] pg_regress/test_extensions ERROR: function public.dep_req2() does not exist at character 9 2025-11-30 18:45:09.279 UTC client backend[44941] pg_regress/test_extensions QUERY: SELECT public.dep_req2() || ' req3b' 2025-11-30 18:45:09.279 UTC client backend[44941] pg_regress/test_extensions CONTEXT: SQL function "dep_req3b" statement 1 2025-11-30 18:45:09.279 UTC client backend[44941] pg_regress/test_extensions STATEMENT: SELECT dep_req3b(); 2025-11-30 18:45:09.281 UTC unrecognized[44981] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.282 UTC client backend[44981] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.282 UTC client backend[44981] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_view 2025-11-30 18:45:09.283 UTC client backend[44981] pg_regress/create_view LOG: connection ready: setup total=2.049 ms, fork=0.561 ms, authentication=0.116 ms 2025-11-30 18:45:09.292 UTC client backend[44981] pg_regress/create_view LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.294 UTC client backend[44941] pg_regress/test_extensions LOG: disconnection: session time: 0:00:00.545 user=postgres database=regression_test_extensions host=[local] 2025-11-30 18:45:09.306 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.306 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.306 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.306 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:09.323 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "ac" violates check constraint "ac_check" 2025-11-30 18:45:09.323 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (null). 2025-11-30 18:45:09.323 UTC client backend[44906] pg_regress/inherit STATEMENT: insert into ac (aa) values (NULL); 2025-11-30 18:45:09.324 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "bc" violates check constraint "ac_check" 2025-11-30 18:45:09.324 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (null, null). 2025-11-30 18:45:09.324 UTC client backend[44906] pg_regress/inherit STATEMENT: insert into bc (aa) values (NULL); 2025-11-30 18:45:09.324 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "ac_check" of relation "bc" 2025-11-30 18:45:09.324 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table bc drop constraint ac_check; 2025-11-30 18:45:09.324 UTC unrecognized[44988] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.325 UTC client backend[44988] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.325 UTC client backend[44988] [unknown] LOG: connection authorized: user=postgres database=regression_test_extensions application_name=pg_regress/test_extdepend 2025-11-30 18:45:09.327 UTC client backend[44988] pg_regress/test_extdepend LOG: connection ready: setup total=4.298 ms, fork=0.949 ms, authentication=0.117 ms 2025-11-30 18:45:09.333 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "ac" violates check constraint "ac_aa_check" 2025-11-30 18:45:09.333 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (null). 2025-11-30 18:45:09.333 UTC client backend[44906] pg_regress/inherit STATEMENT: insert into ac (aa) values (NULL); 2025-11-30 18:45:09.335 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "bc" violates check constraint "ac_aa_check" 2025-11-30 18:45:09.335 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (null, null). 2025-11-30 18:45:09.335 UTC client backend[44906] pg_regress/inherit STATEMENT: insert into bc (aa) values (NULL); 2025-11-30 18:45:09.336 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "ac_aa_check" of relation "bc" 2025-11-30 18:45:09.336 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table bc drop constraint ac_aa_check; 2025-11-30 18:45:09.341 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.341 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.341 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.341 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:09.341 UTC unrecognized[44989] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.342 UTC client backend[44989] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.342 UTC client backend[44989] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_trigger 2025-11-30 18:45:09.343 UTC client backend[44989] pg_regress/create_trigger LOG: connection ready: setup total=13.902 ms, fork=11.053 ms, authentication=0.120 ms 2025-11-30 18:45:09.348 UTC client backend[44913] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-11-30 18:45:09.348 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM vacparted, does_not_exist; 2025-11-30 18:45:09.356 UTC client backend[44913] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-11-30 18:45:09.356 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (FREEZE) does_not_exist, vaccluster; 2025-11-30 18:45:09.362 UTC client backend[44913] pg_regress/vacuum ERROR: column "does_not_exist" of relation "vactst" does not exist 2025-11-30 18:45:09.362 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM ANALYZE vactst (does_not_exist), vacparted (b); 2025-11-30 18:45:09.365 UTC client backend[44989] pg_regress/create_trigger LOG: disconnection: session time: 0:00:00.024 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.367 UTC unrecognized[44991] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.367 UTC client backend[44991] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.367 UTC client backend[44991] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.368 UTC client backend[44991] pg_regress LOG: connection ready: setup total=7.190 ms, fork=5.845 ms, authentication=0.123 ms 2025-11-30 18:45:09.369 UTC client backend[44991] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.369 UTC client backend[44913] pg_regress/vacuum ERROR: ANALYZE option must be specified when a column list is provided 2025-11-30 18:45:09.369 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM FULL vactst, vacparted (a, b), vaccluster (i); 2025-11-30 18:45:09.374 UTC client backend[44778] isolation/killtuples/control connection LOG: disconnection: session time: 0:00:01.563 user=postgres database=isolation_regression_index host=[local] 2025-11-30 18:45:09.381 UTC client backend[44781] isolation/killtuples LOG: disconnection: session time: 0:00:01.564 user=postgres database=isolation_regression_index host=[local] 2025-11-30 18:45:09.382 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.382 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.382 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.382 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:09.384 UTC client backend[44906] pg_regress/inherit ERROR: check constraint "cc" of relation "c1" is violated by some row 2025-11-30 18:45:09.384 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p2 add constraint cc check (f2>0); 2025-11-30 18:45:09.386 UTC unrecognized[44996] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.386 UTC client backend[44996] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.386 UTC client backend[44996] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.386 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot execute MERGE on relation "rw_view1" 2025-11-30 18:45:09.386 UTC client backend[44915] pg_regress/updatable_views DETAIL: MERGE is not supported for relations with rules. 2025-11-30 18:45:09.386 UTC client backend[44915] 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-11-30 18:45:09.386 UTC client backend[44913] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-11-30 18:45:09.386 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE vactst, does_not_exist, vacparted; 2025-11-30 18:45:09.387 UTC client backend[44996] pg_regress LOG: connection ready: setup total=3.679 ms, fork=2.313 ms, authentication=0.122 ms 2025-11-30 18:45:09.387 UTC unrecognized[44997] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.387 UTC client backend[44906] pg_regress/inherit ERROR: check constraint "p2_f2_check" of relation "c1" is violated by some row 2025-11-30 18:45:09.387 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p2 add check (f2>0); 2025-11-30 18:45:09.387 UTC client backend[44997] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.387 UTC client backend[44997] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/create_rule 2025-11-30 18:45:09.389 UTC client backend[44903] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-11-30 18:45:09.389 UTC client backend[44903] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-11-30 18:45:09.389 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMIT; 2025-11-30 18:45:09.390 UTC client backend[44913] pg_regress/vacuum ERROR: column "does_not_exist" of relation "vacparted" does not exist 2025-11-30 18:45:09.390 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE vactst (i), vacparted (does_not_exist); 2025-11-30 18:45:09.392 UTC client backend[44909] pg_regress/triggers ERROR: No such country: "Japon" 2025-11-30 18:45:09.392 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function city_update() line 9 at RAISE 2025-11-30 18:45:09.392 UTC client backend[44909] pg_regress/triggers STATEMENT: UPDATE city_view SET country_name = 'Japon' WHERE city_name = 'Tokyo'; 2025-11-30 18:45:09.396 UTC client backend[44997] pg_regress/create_rule LOG: connection ready: setup total=12.097 ms, fork=3.239 ms, authentication=0.119 ms 2025-11-30 18:45:09.397 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "c1" violates check constraint "p2_f2_check" 2025-11-30 18:45:09.397 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (1, -1, 2). 2025-11-30 18:45:09.397 UTC client backend[44906] pg_regress/inherit STATEMENT: insert into c1 values(1,-1,2); 2025-11-30 18:45:09.400 UTC client backend[44996] pg_regress LOG: disconnection: session time: 0:00:00.014 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.403 UTC client backend[44997] pg_regress/create_rule LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.406 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.406 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:09.406 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.406 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: INSERT INTO offense VALUES (1, '123.45(1)a', DATE '2009-05-15'); 2025-11-30 18:45:09.418 UTC unrecognized[45001] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.419 UTC client backend[45001] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.419 UTC client backend[45001] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/comment_on 2025-11-30 18:45:09.420 UTC client backend[45001] pg_regress/comment_on LOG: connection ready: setup total=2.014 ms, fork=0.536 ms, authentication=0.116 ms 2025-11-30 18:45:09.427 UTC client backend[45001] pg_regress/comment_on ERROR: function c_function_test() does not exist 2025-11-30 18:45:09.427 UTC client backend[45001] pg_regress/comment_on STATEMENT: COMMENT ON FUNCTION c_function_test() IS 'FUNCTION test'; 2025-11-30 18:45:09.431 UTC client backend[44988] pg_regress/test_extdepend ERROR: cannot drop table test_ext.a because other objects depend on it 2025-11-30 18:45:09.431 UTC client backend[44988] pg_regress/test_extdepend DETAIL: materialized view test_ext.d depends on table test_ext.a 2025-11-30 18:45:09.431 UTC client backend[44988] pg_regress/test_extdepend HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:09.431 UTC client backend[44988] pg_regress/test_extdepend STATEMENT: DROP TABLE test_ext.a; 2025-11-30 18:45:09.431 UTC client backend[44903] pg_regress/constraints ERROR: misplaced ENFORCED clause at character 41 2025-11-30 18:45:09.431 UTC client backend[44903] pg_regress/constraints STATEMENT: CREATE TABLE UNIQUE_EN_TBL(i int UNIQUE ENFORCED); 2025-11-30 18:45:09.433 UTC client backend[44903] pg_regress/constraints ERROR: misplaced NOT ENFORCED clause at character 44 2025-11-30 18:45:09.433 UTC client backend[44903] pg_regress/constraints STATEMENT: CREATE TABLE UNIQUE_NOTEN_TBL(i int UNIQUE NOT ENFORCED); 2025-11-30 18:45:09.433 UTC client backend[44933] isolation/temporal-range-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.433 UTC client backend[44933] isolation/temporal-range-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.433 UTC client backend[44933] isolation/temporal-range-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.433 UTC client backend[44933] isolation/temporal-range-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:09.434 UTC client backend[45001] pg_regress/comment_on LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.434 UTC client backend[44903] pg_regress/constraints ERROR: cannot alter enforceability of constraint "unique_tbl_i_key" of relation "unique_tbl" 2025-11-30 18:45:09.434 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key ENFORCED; 2025-11-30 18:45:09.435 UTC client backend[44903] pg_regress/constraints ERROR: cannot alter enforceability of constraint "unique_tbl_i_key" of relation "unique_tbl" 2025-11-30 18:45:09.435 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key NOT ENFORCED; 2025-11-30 18:45:09.436 UTC client backend[44903] pg_regress/constraints ERROR: constraints cannot be altered to be NOT VALID at character 58 2025-11-30 18:45:09.436 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key NOT VALID; 2025-11-30 18:45:09.436 UTC client backend[44913] pg_regress/vacuum WARNING: VACUUM ONLY of partitioned table "vacparted" has no effect 2025-11-30 18:45:09.438 UTC unrecognized[45004] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.439 UTC client backend[45004] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.439 UTC client backend[45004] [unknown] LOG: connection authorized: user=postgres database=regression_test_pg_dump application_name=pg_regress/test_pg_dump 2025-11-30 18:45:09.443 UTC client backend[45004] pg_regress/test_pg_dump LOG: connection ready: setup total=6.170 ms, fork=1.082 ms, authentication=0.113 ms 2025-11-30 18:45:09.453 UTC client backend[44903] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "circles_c1_c2_excl" 2025-11-30 18:45:09.453 UTC client backend[44903] 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-11-30 18:45:09.453 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO circles VALUES('<(20,20), 10>', '<(0,0), 4>'); 2025-11-30 18:45:09.454 UTC client backend[44903] pg_regress/constraints ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:09.454 UTC client backend[44903] 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-11-30 18:45:09.455 UTC client backend[44903] pg_regress/constraints ERROR: could not create exclusion constraint "circles_c1_c2_excl1" 2025-11-30 18:45:09.455 UTC client backend[44903] 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-11-30 18:45:09.455 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE circles ADD EXCLUDE USING gist (c1 WITH &&, (c2::circle) WITH &&); 2025-11-30 18:45:09.459 UTC client backend[45004] pg_regress/test_pg_dump ERROR: cannot add an object of this type to an extension 2025-11-30 18:45:09.459 UTC client backend[45004] pg_regress/test_pg_dump STATEMENT: ALTER EXTENSION test_pg_dump ADD DATABASE postgres; 2025-11-30 18:45:09.462 UTC client backend[44903] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2025-11-30 18:45:09.462 UTC client backend[44903] pg_regress/constraints DETAIL: Key (f1)=(1) conflicts with existing key (f1)=(1). 2025-11-30 18:45:09.462 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO deferred_excl VALUES(1); 2025-11-30 18:45:09.462 UTC client backend[44903] pg_regress/constraints ERROR: ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters 2025-11-30 18:45:09.462 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO deferred_excl VALUES(1) ON CONFLICT ON CONSTRAINT deferred_excl_con DO NOTHING; 2025-11-30 18:45:09.463 UTC client backend[44903] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2025-11-30 18:45:09.463 UTC client backend[44903] pg_regress/constraints DETAIL: Key (f1)=(2) conflicts with existing key (f1)=(2). 2025-11-30 18:45:09.463 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMIT; 2025-11-30 18:45:09.463 UTC client backend[44903] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2025-11-30 18:45:09.463 UTC client backend[44903] pg_regress/constraints DETAIL: Key (f1)=(3) conflicts with existing key (f1)=(3). 2025-11-30 18:45:09.463 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMIT; 2025-11-30 18:45:09.466 UTC unrecognized[45006] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.468 UTC client backend[44903] pg_regress/constraints ERROR: could not create exclusion constraint "deferred_excl_f1_excl" 2025-11-30 18:45:09.468 UTC client backend[44903] pg_regress/constraints DETAIL: Key (f1)=(3) conflicts with key (f1)=(3). 2025-11-30 18:45:09.468 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE deferred_excl ADD EXCLUDE (f1 WITH =); 2025-11-30 18:45:09.470 UTC client backend[45006] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.470 UTC client backend[45006] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/alter_function 2025-11-30 18:45:09.471 UTC client backend[45006] pg_regress/alter_function LOG: connection ready: setup total=6.386 ms, fork=1.135 ms, authentication=0.134 ms 2025-11-30 18:45:09.474 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.474 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.474 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.474 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:09.491 UTC client backend[45006] pg_regress/alter_function ERROR: function plpgsql_function_trigger_2() does not exist 2025-11-30 18:45:09.491 UTC client backend[45006] pg_regress/alter_function STATEMENT: ALTER FUNCTION plpgsql_function_trigger_2() OWNER TO regress_alter_function_role; 2025-11-30 18:45:09.494 UTC client backend[45006] pg_regress/alter_function LOG: disconnection: session time: 0:00:00.027 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.496 UTC client backend[44930] isolation/temporal-range-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.496 UTC client backend[44930] isolation/temporal-range-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:09.496 UTC client backend[44930] isolation/temporal-range-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.496 UTC client backend[44930] isolation/temporal-range-integrity/s1 STATEMENT: INSERT INTO offense VALUES (1, '123.45(1)a', DATE '2009-05-15'); 2025-11-30 18:45:09.516 UTC client backend[44903] pg_regress/constraints ERROR: constraint "notnull_tbl1_a_not_null" for relation "notnull_tbl1" already exists 2025-11-30 18:45:09.516 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD COLUMN b INT CONSTRAINT notnull_tbl1_a_not_null NOT NULL; 2025-11-30 18:45:09.518 UTC unrecognized[45010] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.518 UTC client backend[45010] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.518 UTC client backend[45010] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/alter_sequence 2025-11-30 18:45:09.519 UTC client backend[45010] pg_regress/alter_sequence LOG: connection ready: setup total=7.332 ms, fork=5.829 ms, authentication=0.129 ms 2025-11-30 18:45:09.521 UTC client backend[44988] pg_regress/test_extdepend LOG: disconnection: session time: 0:00:00.196 user=postgres database=regression_test_extensions host=[local] 2025-11-30 18:45:09.521 UTC client backend[44930] isolation/temporal-range-integrity/s1 LOG: disconnection: session time: 0:00:00.862 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:09.526 UTC client backend[45010] pg_regress/alter_sequence LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.526 UTC client backend[44933] isolation/temporal-range-integrity/s2 LOG: disconnection: session time: 0:00:00.848 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:09.526 UTC client backend[44928] isolation/temporal-range-integrity/control connection LOG: disconnection: session time: 0:00:00.878 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:09.538 UTC unrecognized[45017] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.538 UTC client backend[45017] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.538 UTC client backend[45017] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/alter_ts_config 2025-11-30 18:45:09.539 UTC client backend[45017] pg_regress/alter_ts_config LOG: connection ready: setup total=2.887 ms, fork=1.027 ms, authentication=0.120 ms 2025-11-30 18:45:09.543 UTC client backend[45017] pg_regress/alter_ts_config LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.550 UTC unrecognized[45013] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.551 UTC client backend[45013] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.551 UTC client backend[45013] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/project-manager 2025-11-30 18:45:09.552 UTC client backend[45013] isolation/project-manager LOG: connection ready: setup total=26.543 ms, fork=20.151 ms, authentication=0.120 ms 2025-11-30 18:45:09.556 UTC unrecognized[45022] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.556 UTC client backend[45022] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.556 UTC client backend[45022] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/project-manager 2025-11-30 18:45:09.557 UTC client backend[45022] isolation/project-manager LOG: connection ready: setup total=4.308 ms, fork=2.511 ms, authentication=0.115 ms 2025-11-30 18:45:09.558 UTC unrecognized[45024] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.563 UTC unrecognized[45023] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.563 UTC client backend[45024] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.563 UTC client backend[45024] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/alter_type_enum 2025-11-30 18:45:09.564 UTC client backend[45023] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.564 UTC client backend[45023] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.564 UTC client backend[45023] pg_regress LOG: connection ready: setup total=9.504 ms, fork=6.849 ms, authentication=0.102 ms 2025-11-30 18:45:09.564 UTC client backend[45024] pg_regress/alter_type_enum LOG: connection ready: setup total=8.614 ms, fork=1.225 ms, authentication=0.119 ms 2025-11-30 18:45:09.565 UTC client backend[45023] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.568 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot delete from view "rw_view1" 2025-11-30 18:45:09.568 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-11-30 18:45:09.568 UTC client backend[44915] pg_regress/updatable_views HINT: To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger. 2025-11-30 18:45:09.568 UTC client backend[44915] 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-11-30 18:45:09.571 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into view "rw_view1" 2025-11-30 18:45:09.571 UTC client backend[44915] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-11-30 18:45:09.571 UTC client backend[44915] pg_regress/updatable_views HINT: To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger. 2025-11-30 18:45:09.571 UTC client backend[44915] 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-11-30 18:45:09.573 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot merge into view "rw_view2" 2025-11-30 18:45:09.573 UTC client backend[44915] pg_regress/updatable_views DETAIL: MERGE is not supported for views with INSTEAD OF triggers for some actions but not all. 2025-11-30 18:45:09.573 UTC client backend[44915] 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-11-30 18:45:09.573 UTC client backend[44915] 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-11-30 18:45:09.586 UTC unrecognized[45027] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.586 UTC client backend[45027] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.586 UTC client backend[45027] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/project-manager 2025-11-30 18:45:09.587 UTC client backend[45024] pg_regress/alter_type_enum LOG: disconnection: session time: 0:00:00.029 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.587 UTC client backend[45027] isolation/project-manager LOG: connection ready: setup total=2.630 ms, fork=1.124 ms, authentication=0.118 ms 2025-11-30 18:45:09.591 UTC unrecognized[45028] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.591 UTC client backend[45028] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.591 UTC client backend[45028] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.592 UTC client backend[45028] pg_regress LOG: connection ready: setup total=6.559 ms, fork=2.389 ms, authentication=0.110 ms 2025-11-30 18:45:09.601 UTC client backend[44909] pg_regress/triggers ERROR: U9999 2025-11-30 18:45:09.601 UTC client backend[44909] 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-11-30 18:45:09.601 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into depth_a values (1); 2025-11-30 18:45:09.605 UTC unrecognized[45031] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.605 UTC client backend[45031] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.605 UTC client backend[45031] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.606 UTC client backend[45031] pg_regress LOG: connection ready: setup total=6.610 ms, fork=1.862 ms, authentication=0.127 ms 2025-11-30 18:45:09.606 UTC client backend[44913] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-11-30 18:45:09.606 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE (VERBOSE) does_not_exist; 2025-11-30 18:45:09.607 UTC client backend[45031] pg_regress LOG: disconnection: session time: 0:00:00.005 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.609 UTC client backend[45028] pg_regress LOG: disconnection: session time: 0:00:00.021 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.613 UTC unrecognized[45035] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.613 UTC client backend[45035] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.613 UTC client backend[45035] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/opfamily 2025-11-30 18:45:09.614 UTC client backend[45035] pg_regress/opfamily LOG: connection ready: setup total=2.092 ms, fork=0.653 ms, authentication=0.110 ms 2025-11-30 18:45:09.619 UTC unrecognized[45036] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.619 UTC client backend[45036] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.619 UTC client backend[45036] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.620 UTC client backend[45036] pg_regress LOG: connection ready: setup total=1.733 ms, fork=0.480 ms, authentication=0.121 ms 2025-11-30 18:45:09.632 UTC client backend[45036] pg_regress LOG: disconnection: session time: 0:00:00.012 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.640 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.640 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl VALUES (3, 'Row 3', 3.0); 2025-11-30 18:45:09.640 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.640 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 3', 3.0, 3); 2025-11-30 18:45:09.641 UTC client backend[44913] pg_regress/vacuum ERROR: syntax error at or near "arg" at character 22 2025-11-30 18:45:09.641 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE (nonexistent-arg) does_not_exist; 2025-11-30 18:45:09.641 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.641 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES ('Row 3', 3.0, 3); 2025-11-30 18:45:09.641 UTC unrecognized[45037] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.641 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.641 UTC client backend[44915] 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-11-30 18:45:09.641 UTC client backend[45037] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.641 UTC client backend[45037] [unknown] LOG: connection authorized: user=postgres database=regression_test_predtest application_name=pg_regress/test_predtest 2025-11-30 18:45:09.642 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.642 UTC client backend[44915] 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-11-30 18:45:09.642 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.642 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE base_tbl SET b=b; 2025-11-30 18:45:09.643 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.643 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-11-30 18:45:09.644 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.644 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bb=bb; 2025-11-30 18:45:09.644 UTC unrecognized[45039] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.644 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.644 UTC client backend[44915] 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-11-30 18:45:09.645 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.645 UTC client backend[44915] 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-11-30 18:45:09.645 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.645 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM base_tbl; 2025-11-30 18:45:09.645 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.645 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1; 2025-11-30 18:45:09.646 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.646 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view2; 2025-11-30 18:45:09.646 UTC client backend[45037] pg_regress/test_predtest LOG: connection ready: setup total=27.241 ms, fork=21.991 ms, authentication=0.136 ms 2025-11-30 18:45:09.646 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.646 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4); 2025-11-30 18:45:09.647 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.647 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:09.647 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.647 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: UPDATE person SET is_project_manager = false WHERE person_id = 1; 2025-11-30 18:45:09.647 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.647 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1 WHERE aa=2; 2025-11-30 18:45:09.648 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.648 UTC client backend[44915] 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-11-30 18:45:09.648 UTC client backend[45039] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.648 UTC client backend[45039] [unknown] LOG: connection authorized: user=postgres database=regression_test_radixtree application_name=pg_regress/test_radixtree 2025-11-30 18:45:09.650 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.650 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl VALUES (5, 'Row 5', 5.0); 2025-11-30 18:45:09.651 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.651 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES ('Row 6', 6.0, 6); 2025-11-30 18:45:09.651 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.651 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM base_tbl WHERE a=3; 2025-11-30 18:45:09.652 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.652 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view2 WHERE aa=4; 2025-11-30 18:45:09.652 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.652 UTC client backend[44915] 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-11-30 18:45:09.653 UTC client backend[45039] pg_regress/test_radixtree LOG: connection ready: setup total=9.357 ms, fork=0.903 ms, authentication=0.116 ms 2025-11-30 18:45:09.653 UTC client backend[45035] pg_regress/opfamily LOG: disconnection: session time: 0:00:00.039 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.655 UTC client backend[44906] pg_regress/inherit ERROR: cannot rename inherited column "b" 2025-11-30 18:45:09.655 UTC client backend[44906] pg_regress/inherit STATEMENT: ALTER TABLE inht1 RENAME b TO bb; max_val = 255 num_keys = 2 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 2 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 2 height = 1, n4 = 3, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 2 height = 1, n4 = 3, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 2 height = 7, n4 = 15, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 2 height = 7, n4 = 15, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 15 height = 0, n4 = 0, n16 = 1, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 15 height = 0, n4 = 0, n16 = 1, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 15 height = 1, n4 = 15, n16 = 1, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 15 height = 1, n4 = 15, n16 = 1, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 15 height = 7, n4 = 105, n16 = 1, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 15 height = 7, n4 = 105, n16 = 1, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 30 height = 0, n4 = 0, n16 = 0, n32 = 1, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 30 height = 0, n4 = 0, n16 = 0, n32 = 1, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 30 height = 1, n4 = 30, n16 = 0, n32 = 1, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 30 height = 1, n4 = 30, n16 = 0, n32 = 1, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 30 height = 7, n4 = 210, n16 = 0, n32 = 1, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 30 height = 7, n4 = 210, n16 = 0, n32 = 1, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 60 height = 0, n4 = 0, n16 = 0, n32 = 0, n64 = 1, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 60 height = 0, n4 = 0, n16 = 0, n32 = 0, n64 = 1, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 60 height = 1, n4 = 60, n16 = 0, n32 = 0, n64 = 1, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 60 height = 1, n4 = 60, n16 = 0, n32 = 0, n64 = 1, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 60 height = 7, n4 = 420, n16 = 0, n32 = 0, n64 = 1, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 60 height = 7, n4 = 420, n16 = 0, n32 = 0, n64 = 1, n256 = 0, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 256 height = 0, n4 = 0, n16 = 0, n32 = 0, n64 = 0, n256 = 1, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 255 num_keys = 256 height = 0, n4 = 0, n16 = 0, n32 = 0, n64 = 0, n256 = 1, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 256 height = 1, n4 = 256, n16 = 0, n32 = 0, n64 = 0, n256 = 1, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 65535 num_keys = 256 height = 1, n4 = 256, n16 = 0, n32 = 0, n64 = 0, n256 = 1, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 256 height = 7, n4 = 1792, n16 = 0, n32 = 0, n64 = 0, n256 = 1, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 max_val = 18446744073709551615 num_keys = 256 height = 7, n4 = 1792, n16 = 0, n32 = 0, n64 = 0, n256 = 1, leaves = 0 max_val = 255 num_keys = 0 height = 0, n4 = 1, n16 = 0, n32 = 0, n64 = 0, n256 = 0, leaves = 0 2025-11-30 18:45:09.661 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.661 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-11-30 18:45:09.661 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.661 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1 FOR UPDATE; 2025-11-30 18:45:09.662 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.662 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = 'foo' WHERE a = 1; 2025-11-30 18:45:09.662 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.662 UTC client backend[44915] 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-11-30 18:45:09.663 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.663 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.663 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.663 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-11-30 18:45:09.664 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.664 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-11-30 18:45:09.664 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.664 UTC client backend[44915] 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-11-30 18:45:09.672 UTC unrecognized[45042] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.672 UTC client backend[45042] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.672 UTC client backend[45042] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/defprivs 2025-11-30 18:45:09.673 UTC client backend[45042] pg_regress/defprivs LOG: connection ready: setup total=7.349 ms, fork=5.069 ms, authentication=0.120 ms 2025-11-30 18:45:09.676 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.676 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1 FOR UPDATE; 2025-11-30 18:45:09.676 UTC client backend[45042] pg_regress/defprivs LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.678 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.678 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = 'foo' WHERE a = 1; 2025-11-30 18:45:09.678 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.678 UTC client backend[44915] 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-11-30 18:45:09.678 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.678 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.679 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.679 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; max_val = 4294967295 num_keys = 90795 height = 3, n4 = 2048, n16 = 1, n32 = 44, n64 = 2003, n256 = 9, leaves = 0 2025-11-30 18:45:09.679 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.679 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-11-30 18:45:09.679 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.679 UTC client backend[44915] 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-11-30 18:45:09.680 UTC client backend[44906] pg_regress/inherit ERROR: cannot rename inherited column "aa" 2025-11-30 18:45:09.680 UTC client backend[44906] pg_regress/inherit STATEMENT: ALTER TABLE inhts RENAME aa TO aaa; 2025-11-30 18:45:09.681 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.681 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-11-30 18:45:09.682 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.682 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-11-30 18:45:09.683 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.683 UTC client backend[44915] 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-11-30 18:45:09.684 UTC client backend[45004] pg_regress/test_pg_dump LOG: disconnection: session time: 0:00:00.245 user=postgres database=regression_test_pg_dump host=[local] 2025-11-30 18:45:09.687 UTC client backend[44913] pg_regress/vacuum ERROR: unrecognized ANALYZE option "nonexistentarg" at character 10 2025-11-30 18:45:09.687 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE (nonexistentarg) does_not_exit; 2025-11-30 18:45:09.688 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.688 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-11-30 18:45:09.688 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.688 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-11-30 18:45:09.688 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.688 UTC client backend[44915] 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-11-30 18:45:09.691 UTC client backend[44909] pg_regress/triggers ERROR: tuple to be updated was already modified by an operation triggered by the current command 2025-11-30 18:45:09.691 UTC client backend[44909] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-11-30 18:45:09.691 UTC client backend[44909] pg_regress/triggers STATEMENT: update parent set val1 = 'b' where aid = 1; 2025-11-30 18:45:09.692 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.692 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.692 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.692 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: COMMIT; 2025-11-30 18:45:09.693 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.693 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1 FOR UPDATE; 2025-11-30 18:45:09.693 UTC client backend[44909] pg_regress/triggers ERROR: tuple to be updated or deleted was already modified by an operation triggered by the current command 2025-11-30 18:45:09.693 UTC client backend[44909] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-11-30 18:45:09.693 UTC client backend[44909] 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-11-30 18:45:09.693 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.693 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = 'foo' WHERE a = 1; 2025-11-30 18:45:09.693 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.693 UTC client backend[44915] 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-11-30 18:45:09.694 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.694 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-11-30 18:45:09.694 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.694 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-11-30 18:45:09.695 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.695 UTC client backend[44915] 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-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM base_tbl; 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl VALUES (3, 'Row 3', 3.0); 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 3', 3.0, 3); 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.702 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE base_tbl SET a=a; 2025-11-30 18:45:09.703 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.703 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET bb=bb, cc=cc; 2025-11-30 18:45:09.703 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.703 UTC client backend[44915] 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-11-30 18:45:09.703 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.703 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM base_tbl; 2025-11-30 18:45:09.703 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.703 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1; 2025-11-30 18:45:09.704 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.704 UTC client backend[44915] 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-11-30 18:45:09.705 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.705 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE base_tbl SET b=b; 2025-11-30 18:45:09.706 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.706 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-11-30 18:45:09.707 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.707 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET bb=bb; 2025-11-30 18:45:09.707 UTC client backend[45039] pg_regress/test_radixtree LOG: disconnection: session time: 0:00:00.062 user=postgres database=regression_test_radixtree host=[local] 2025-11-30 18:45:09.707 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.707 UTC client backend[44915] 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-11-30 18:45:09.707 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.707 UTC client backend[44915] 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-11-30 18:45:09.708 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.708 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4); 2025-11-30 18:45:09.708 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.708 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1 WHERE aa=2; 2025-11-30 18:45:09.708 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.708 UTC client backend[44915] 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-11-30 18:45:09.709 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.709 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4); 2025-11-30 18:45:09.709 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.709 UTC client backend[44915] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1 WHERE aa=2; 2025-11-30 18:45:09.710 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.710 UTC client backend[44915] 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-11-30 18:45:09.713 UTC unrecognized[45047] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.713 UTC client backend[45047] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.713 UTC client backend[45047] [unknown] LOG: connection authorized: user=postgres database=regression_test_ddl_deparse application_name=pg_regress/matviews 2025-11-30 18:45:09.714 UTC client backend[45047] pg_regress/matviews LOG: connection ready: setup total=2.883 ms, fork=1.376 ms, authentication=0.114 ms 2025-11-30 18:45:09.716 UTC client backend[44909] pg_regress/triggers ERROR: tuple to be deleted was already modified by an operation triggered by the current command 2025-11-30 18:45:09.716 UTC client backend[44909] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-11-30 18:45:09.716 UTC client backend[44909] pg_regress/triggers STATEMENT: delete from parent where aid = 1; 2025-11-30 18:45:09.717 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.717 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.717 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.717 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: COMMIT; 2025-11-30 18:45:09.719 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.719 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-11-30 18:45:09.719 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.719 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-11-30 18:45:09.720 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.720 UTC client backend[44915] 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-11-30 18:45:09.720 UTC client backend[44909] pg_regress/triggers ERROR: tuple to be updated or deleted was already modified by an operation triggered by the current command 2025-11-30 18:45:09.720 UTC client backend[44909] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-11-30 18:45:09.720 UTC client backend[44909] pg_regress/triggers STATEMENT: merge into parent p using (values (1)) as v(id) on p.aid = v.id when matched then delete; 2025-11-30 18:45:09.721 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.721 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.721 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.721 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.722 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.722 UTC client backend[44915] 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-11-30 18:45:09.723 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.723 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET cc=cc; 2025-11-30 18:45:09.724 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.724 UTC client backend[44915] 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-11-30 18:45:09.724 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.724 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.725 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.725 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.725 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.725 UTC client backend[44915] 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-11-30 18:45:09.725 UTC client backend[45037] pg_regress/test_predtest LOG: disconnection: session time: 0:00:00.084 user=postgres database=regression_test_predtest host=[local] 2025-11-30 18:45:09.725 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.725 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.725 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.725 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.726 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.726 UTC client backend[44915] 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-11-30 18:45:09.726 UTC client backend[44913] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-11-30 18:45:09.726 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE (SKIP_LOCKED, VERBOSE) does_not_exist; 2025-11-30 18:45:09.727 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.727 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.727 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.727 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.728 UTC client backend[44913] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-11-30 18:45:09.728 UTC client backend[44913] pg_regress/vacuum STATEMENT: ANALYZE (VERBOSE, SKIP_LOCKED) does_not_exist; 2025-11-30 18:45:09.728 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.728 UTC client backend[44915] 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-11-30 18:45:09.728 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.728 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.728 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.728 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.729 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.729 UTC client backend[44915] 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-11-30 18:45:09.730 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.730 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.730 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.730 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.731 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.731 UTC client backend[44915] 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-11-30 18:45:09.732 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.732 UTC client backend[44915] 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-11-30 18:45:09.734 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.734 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.735 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.735 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.737 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.737 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.738 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.738 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET ccc=ccc; 2025-11-30 18:45:09.739 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.739 UTC client backend[44915] 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-11-30 18:45:09.741 UTC client backend[45047] pg_regress/matviews LOG: disconnection: session time: 0:00:00.027 user=postgres database=regression_test_ddl_deparse host=[local] 2025-11-30 18:45:09.741 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.741 UTC client backend[44915] 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-11-30 18:45:09.742 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.742 UTC client backend[44915] 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-11-30 18:45:09.749 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.749 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.750 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.750 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.753 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.753 UTC client backend[44915] 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-11-30 18:45:09.754 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.754 UTC client backend[44915] 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-11-30 18:45:09.758 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.758 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-11-30 18:45:09.758 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.758 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-11-30 18:45:09.760 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.760 UTC client backend[44915] 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-11-30 18:45:09.760 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.760 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.761 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.761 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.762 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.762 UTC client backend[44915] 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-11-30 18:45:09.766 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.766 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:09.766 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.766 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: UPDATE person SET is_project_manager = false WHERE person_id = 1; 2025-11-30 18:45:09.769 UTC unrecognized[45053] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.769 UTC client backend[45053] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.769 UTC client backend[45053] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.770 UTC client backend[45053] pg_regress LOG: connection ready: setup total=14.273 ms, fork=3.158 ms, authentication=0.123 ms 2025-11-30 18:45:09.770 UTC client backend[45053] pg_regress LOG: disconnection: session time: 0:00:00.011 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.780 UTC client backend[44913] pg_regress/vacuum ERROR: PROCESS_TOAST required with VACUUM FULL 2025-11-30 18:45:09.780 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (PROCESS_TOAST FALSE, FULL) vac_option_tab; 2025-11-30 18:45:09.782 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.782 UTC client backend[44915] 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-11-30 18:45:09.785 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.785 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.785 UTC unrecognized[45057] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.785 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.785 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.785 UTC client backend[45057] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.785 UTC client backend[45057] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.786 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.786 UTC client backend[44915] 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-11-30 18:45:09.786 UTC client backend[45057] pg_regress LOG: connection ready: setup total=2.314 ms, fork=1.020 ms, authentication=0.126 ms 2025-11-30 18:45:09.786 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.786 UTC client backend[44915] 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-11-30 18:45:09.788 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.788 UTC client backend[44915] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-11-30 18:45:09.788 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.788 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.788 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.788 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.789 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.789 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET ccc=ccc; 2025-11-30 18:45:09.789 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.789 UTC client backend[44915] 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-11-30 18:45:09.789 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.789 UTC client backend[44915] 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-11-30 18:45:09.794 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.794 UTC client backend[44915] 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-11-30 18:45:09.796 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.796 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-11-30 18:45:09.797 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.797 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-11-30 18:45:09.798 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:09.798 UTC client backend[44915] 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-11-30 18:45:09.798 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:09.798 UTC client backend[44915] 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-11-30 18:45:09.813 UTC client backend[45057] pg_regress LOG: disconnection: session time: 0:00:00.028 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.833 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.833 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.833 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.833 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: COMMIT; 2025-11-30 18:45:09.836 UTC client backend[44909] pg_regress/triggers ERROR: tuple to be updated was already modified by an operation triggered by the current command 2025-11-30 18:45:09.836 UTC client backend[44909] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-11-30 18:45:09.836 UTC client backend[44909] pg_regress/triggers STATEMENT: delete from self_ref_trigger; 2025-11-30 18:45:09.844 UTC unrecognized[45062] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.845 UTC client backend[45062] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.845 UTC client backend[45062] [unknown] LOG: connection authorized: user=postgres database=regression_test_rbtree application_name=pg_regress/test_rbtree 2025-11-30 18:45:09.847 UTC client backend[44913] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2025-11-30 18:45:09.847 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 16777220) vac_option_tab; 2025-11-30 18:45:09.853 UTC client backend[44903] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "bar" 2025-11-30 18:45:09.853 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial constraint foo not null constraint bar not null); 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 120) vac_option_tab; 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum HINT: Value exceeds integer range. 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 10000000000) vac_option_tab; 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT cannot be specified for VACUUM FULL 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT '512 kB', FULL) vac_option_tab; 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum ERROR: ONLY_DATABASE_STATS cannot be specified with a list of tables 2025-11-30 18:45:09.853 UTC client backend[44913] pg_regress/vacuum STATEMENT: VACUUM (ONLY_DATABASE_STATS) vactst; 2025-11-30 18:45:09.853 UTC unrecognized[45068] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.854 UTC client backend[45068] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.854 UTC client backend[45068] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.855 UTC client backend[45068] pg_regress LOG: connection ready: setup total=2.377 ms, fork=1.058 ms, authentication=0.115 ms 2025-11-30 18:45:09.855 UTC client backend[45068] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.865 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-11-30 18:45:09.865 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial constraint foo not null no inherit constraint foo not null); 2025-11-30 18:45:09.865 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:09.865 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int constraint foo not null, constraint foo not null a no inherit); 2025-11-30 18:45:09.866 UTC unrecognized[45070] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.867 UTC client backend[44903] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "bar" 2025-11-30 18:45:09.867 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial constraint foo not null, constraint bar not null a); 2025-11-30 18:45:09.868 UTC client backend[45070] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.868 UTC client backend[45070] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.869 UTC client backend[44903] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "bar" 2025-11-30 18:45:09.869 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial, constraint foo not null a, constraint bar not null a); 2025-11-30 18:45:09.869 UTC client backend[45070] pg_regress LOG: connection ready: setup total=4.303 ms, fork=0.679 ms, authentication=0.143 ms 2025-11-30 18:45:09.870 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:09.870 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial, constraint foo not null a no inherit); 2025-11-30 18:45:09.871 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-11-30 18:45:09.871 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial not null no inherit); 2025-11-30 18:45:09.873 UTC client backend[44903] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "foo2" 2025-11-30 18:45:09.873 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (like notnull_tbl1, constraint foo2 not null a); 2025-11-30 18:45:09.873 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned", skipping it 2025-11-30 18:45:09.873 UTC unrecognized[45071] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.873 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-11-30 18:45:09.873 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int primary key constraint foo not null no inherit); 2025-11-30 18:45:09.873 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-11-30 18:45:09.873 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int not null no inherit primary key); 2025-11-30 18:45:09.873 UTC client backend[45071] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.873 UTC client backend[45071] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.874 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:09.874 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int primary key, not null a no inherit); 2025-11-30 18:45:09.874 UTC unrecognized[45067] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.874 UTC client backend[45071] pg_regress LOG: connection ready: setup total=2.571 ms, fork=1.324 ms, authentication=0.124 ms 2025-11-30 18:45:09.874 UTC client backend[45067] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.874 UTC client backend[45067] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.874 UTC client backend[45071] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.875 UTC client backend[45067] pg_regress LOG: connection ready: setup total=28.253 ms, fork=26.920 ms, authentication=0.107 ms 2025-11-30 18:45:09.875 UTC client backend[45067] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.876 UTC client backend[45062] pg_regress/test_rbtree LOG: connection ready: setup total=57.231 ms, fork=25.435 ms, authentication=0.121 ms 2025-11-30 18:45:09.881 UTC unrecognized[45074] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.882 UTC client backend[45074] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.882 UTC client backend[45074] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.882 UTC client backend[45074] pg_regress LOG: connection ready: setup total=1.645 ms, fork=0.379 ms, authentication=0.115 ms 2025-11-30 18:45:09.884 UTC client backend[45070] pg_regress LOG: disconnection: session time: 0:00:00.018 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.891 UTC client backend[45062] pg_regress/test_rbtree LOG: disconnection: session time: 0:00:00.047 user=postgres database=regression_test_rbtree host=[local] 2025-11-30 18:45:09.893 UTC unrecognized[45076] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.893 UTC client backend[45076] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.893 UTC client backend[45076] [unknown] LOG: connection authorized: user=postgres database=regression_test_resowner application_name=pg_regress/test_resowner 2025-11-30 18:45:09.897 UTC client backend[44909] pg_regress/triggers ERROR: cannot ALTER TABLE "trigger_ddl_table" because it is being used by active queries in this session 2025-11-30 18:45:09.897 UTC client backend[44909] 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-11-30 18:45:09.897 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into trigger_ddl_table values (1, 42); 2025-11-30 18:45:09.898 UTC client backend[45076] pg_regress/test_resowner LOG: connection ready: setup total=6.404 ms, fork=1.312 ms, authentication=0.117 ms 2025-11-30 18:45:09.898 UTC client backend[45074] pg_regress LOG: disconnection: session time: 0:00:00.016 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.900 UTC client backend[44909] pg_regress/triggers ERROR: cannot CREATE INDEX "trigger_ddl_table" because it is being used by active queries in this session 2025-11-30 18:45:09.900 UTC client backend[44909] 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-11-30 18:45:09.900 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into trigger_ddl_table values (1, 42); 2025-11-30 18:45:09.900 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:09.900 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int, primary key(a), not null a no inherit); 2025-11-30 18:45:09.903 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:09.903 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int generated by default as identity, constraint foo not null a no inherit); 2025-11-30 18:45:09.903 UTC client backend[44903] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-11-30 18:45:09.903 UTC client backend[44903] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int generated by default as identity not null no inherit); 2025-11-30 18:45:09.905 UTC unrecognized[45079] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.906 UTC client backend[45079] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.906 UTC client backend[45079] [unknown] LOG: connection authorized: user=postgres database=regression_test_regex application_name=pg_regress/test_regex 2025-11-30 18:45:09.908 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.908 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.908 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.908 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: COMMIT; 2025-11-30 18:45:09.908 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned", skipping it 2025-11-30 18:45:09.912 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned", skipping it 2025-11-30 18:45:09.914 UTC client backend[45079] pg_regress/test_regex LOG: connection ready: setup total=9.241 ms, fork=0.572 ms, authentication=0.116 ms 2025-11-30 18:45:09.916 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.916 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('(*)', '', ''); 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid argument to regex function 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a', '', 'qe'); 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid argument to regex function 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a', '', 'qa'); 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid argument to regex function 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a', '', 'qx'); 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid argument to regex function 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a', '', 'qn'); 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid argument to regex function 2025-11-30 18:45:09.917 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a', '', 'ba'); 2025-11-30 18:45:09.918 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "pg_class", skipping it 2025-11-30 18:45:09.918 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "ctid" of view "rw_view1" 2025-11-30 18:45:09.918 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-11-30 18:45:09.918 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (null, null, 1.1, null); 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: parentheses () not balanced 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a(b', '', '-'); 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: parentheses () not balanced 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\(b', '', 'b'); 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: parentheses () not balanced 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a)b', '', '-'); 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: parentheses () not balanced 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\)b', '', 'b'); 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.919 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a(?:b)c', '', 'e'); 2025-11-30 18:45:09.920 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "pg_class", skipping it 2025-11-30 18:45:09.921 UTC client backend[44906] pg_regress/inherit ERROR: cannot rename inherited column "b" 2025-11-30 18:45:09.921 UTC client backend[44906] pg_regress/inherit STATEMENT: ALTER TABLE inht1 RENAME b TO bb; 2025-11-30 18:45:09.921 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "pg_class", skipping it 2025-11-30 18:45:09.921 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.921 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('*', '', '-'); 2025-11-30 18:45:09.922 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.922 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('(*)', '', '-'); 2025-11-30 18:45:09.922 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.922 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('^*', '', '-'); 2025-11-30 18:45:09.922 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "pg_authid", skipping it 2025-11-30 18:45:09.923 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.923 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('+', '', '-'); 2025-11-30 18:45:09.923 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.923 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('?', '', '-'); 2025-11-30 18:45:09.923 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:09.923 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('x(\w)(?=(\1))', '', '-'); 2025-11-30 18:45:09.924 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "pg_authid", skipping it 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('**', '', '-'); 2025-11-30 18:45:09.925 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "pg_authid", skipping it 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a**', '', ''); 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a**', '', 'b'); 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.925 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a**b', '', ''); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a**b', '', 'b'); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***', '', ''); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***', '', 'b'); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a++', '', '-'); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a?+', '', '-'); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a?*', '', '-'); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a+*', '', '-'); 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a*+', '', '-'); 2025-11-30 18:45:09.926 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid repetition count(s) 2025-11-30 18:45:09.926 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a{1,0}', '', '-'); 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid repetition count(s) 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a{1,2,3}', '', '-'); 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid repetition count(s) 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a{257}', '', '-'); 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid repetition count(s) 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a{1000}', '', '-'); 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: braces {} not balanced 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a{1', '', '-'); 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid repetition count(s) 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a{1n}', '', '-'); 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: braces {} not balanced 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\{0,1', '', 'b'); 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid repetition count(s) 2025-11-30 18:45:09.927 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a{0,1\', '', '-'); 2025-11-30 18:45:09.928 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.929 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.930 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.932 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (1,black) 2025-11-30 18:45:09.932 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.933 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-11-30 18:45:09.933 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:09.933 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 (s, c, a) VALUES (null, null, 1.1); 2025-11-30 18:45:09.933 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.933 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_parted", skipping it 2025-11-30 18:45:09.933 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.933 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[0-[=x=]]', '', ''); 2025-11-30 18:45:09.933 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-11-30 18:45:09.933 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.933 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[0-[=x=]]', '', 'b'); 2025-11-30 18:45:09.933 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character class 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[:woopsie:]]', '', ''); 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character class 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[:woopsie:]]', '', 'b'); 2025-11-30 18:45:09.934 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[0-[:digit:]]', '', ''); 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.934 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[0-[:digit:]]', '', 'b'); 2025-11-30 18:45:09.934 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid collating element 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[..]]b', '', ''); 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid collating element 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[..]]b', '', 'b'); 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid collating element 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[==]]b', '', ''); 2025-11-30 18:45:09.935 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-11-30 18:45:09.935 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.935 UTC client backend[44909] pg_regress/triggers WARNING: after insert (new): (1,black) 2025-11-30 18:45:09.935 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid collating element 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[==]]b', '', 'b'); 2025-11-30 18:45:09.935 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character class 2025-11-30 18:45:09.935 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[::]]b', '', ''); 2025-11-30 18:45:09.936 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.936 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.936 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character class 2025-11-30 18:45:09.936 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[::]]b', '', 'b'); 2025-11-30 18:45:09.937 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (2,red) 2025-11-30 18:45:09.937 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[.a', '', ''); 2025-11-30 18:45:09.937 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new, modified): (3,"red trig modified") 2025-11-30 18:45:09.937 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[.a', '', 'b'); 2025-11-30 18:45:09.937 UTC client backend[44909] pg_regress/triggers WARNING: after insert (new): (3,"red trig modified") 2025-11-30 18:45:09.937 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[=a', '', ''); 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.937 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[=a', '', 'b'); 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (3,orange) 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.938 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.938 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[:a', '', ''); 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers WARNING: before update (old): (3,"red trig modified") 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2025-11-30 18:45:09.938 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.938 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[[:a', '', 'b'); 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers WARNING: before update (new): (3,"updated red trig modified") 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2025-11-30 18:45:09.938 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.938 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[', '', ''); 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers WARNING: after update (old): (3,"red trig modified") 2025-11-30 18:45:09.938 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2025-11-30 18:45:09.939 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.939 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[', '', 'b'); 2025-11-30 18:45:09.939 UTC client backend[44909] pg_regress/triggers WARNING: after update (new): (3,"updated red trig modified") 2025-11-30 18:45:09.939 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2025-11-30 18:45:09.939 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.939 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[b', '', ''); 2025-11-30 18:45:09.939 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.939 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[b', '', 'b'); 2025-11-30 18:45:09.940 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (4,green) 2025-11-30 18:45:09.940 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[b-', '', ''); 2025-11-30 18:45:09.940 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new, modified): (5,"green trig modified") 2025-11-30 18:45:09.940 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[b-', '', 'b'); 2025-11-30 18:45:09.940 UTC client backend[44909] pg_regress/triggers WARNING: after insert (new): (5,"green trig modified") 2025-11-30 18:45:09.940 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[b-c', '', ''); 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: brackets [] not balanced 2025-11-30 18:45:09.940 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[b-c', '', 'b'); 2025-11-30 18:45:09.941 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (5,purple) 2025-11-30 18:45:09.941 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.941 UTC client backend[44909] pg_regress/triggers WARNING: before update (old): (5,"green trig modified") 2025-11-30 18:45:09.941 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2025-11-30 18:45:09.941 UTC client backend[44909] pg_regress/triggers WARNING: before update (new): (5,"updated green trig modified") 2025-11-30 18:45:09.941 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2025-11-30 18:45:09.942 UTC unrecognized[45081] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.942 UTC client backend[44909] pg_regress/triggers WARNING: after update (old): (5,"green trig modified") 2025-11-30 18:45:09.942 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2025-11-30 18:45:09.942 UTC client backend[44909] pg_regress/triggers WARNING: after update (new): (5,"updated green trig modified") 2025-11-30 18:45:09.942 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2025-11-30 18:45:09.942 UTC client backend[45081] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.942 UTC client backend[45081] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:09.942 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.942 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[c-b]', '', ''); 2025-11-30 18:45:09.943 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (6,white) 2025-11-30 18:45:09.943 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.943 UTC client backend[45081] pg_regress LOG: connection ready: setup total=32.002 ms, fork=28.333 ms, authentication=0.128 ms 2025-11-30 18:45:09.943 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.943 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[c-b]', '', 'b'); 2025-11-30 18:45:09.943 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new, modified): (7,"white trig modified") 2025-11-30 18:45:09.943 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-11-30 18:45:09.943 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.943 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[a-b-c]', '', ''); 2025-11-30 18:45:09.943 UTC client backend[44909] pg_regress/triggers WARNING: after insert (new): (7,"white trig modified") 2025-11-30 18:45:09.943 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-11-30 18:45:09.943 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.943 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[a-b-c]', '', 'b'); 2025-11-30 18:45:09.944 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (7,pink) 2025-11-30 18:45:09.944 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.944 UTC client backend[44909] pg_regress/triggers WARNING: before update (old): (7,"white trig modified") 2025-11-30 18:45:09.944 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2025-11-30 18:45:09.945 UTC client backend[44909] pg_regress/triggers WARNING: before update (new): (7,"updated white trig modified") 2025-11-30 18:45:09.945 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2025-11-30 18:45:09.945 UTC client backend[44909] pg_regress/triggers WARNING: after update (old): (7,"white trig modified") 2025-11-30 18:45:09.945 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2025-11-30 18:45:09.945 UTC client backend[44909] pg_regress/triggers WARNING: after update (new): (7,"updated white trig modified") 2025-11-30 18:45:09.945 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2025-11-30 18:45:09.945 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.946 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new): (8,yellow) 2025-11-30 18:45:09.946 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-11-30 18:45:09.946 UTC client backend[44909] pg_regress/triggers WARNING: before insert (new, modified): (9,"yellow trig modified") 2025-11-30 18:45:09.946 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-11-30 18:45:09.946 UTC client backend[44909] pg_regress/triggers WARNING: after insert (new): (9,"yellow trig modified") 2025-11-30 18:45:09.946 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-11-30 18:45:09.946 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.946 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.946 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.946 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: COMMIT; 2025-11-30 18:45:09.953 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.953 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:09.953 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a[\Z]b', '', '-'); 2025-11-30 18:45:09.954 UTC client backend[44909] pg_regress/triggers ERROR: "my_view" is a view 2025-11-30 18:45:09.954 UTC client backend[44909] pg_regress/triggers DETAIL: Triggers on views cannot have transition tables. 2025-11-30 18:45:09.954 UTC client backend[44909] 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-11-30 18:45:09.957 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-11-30 18:45:09.957 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:09.957 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 (s, c, a) VALUES (default, default, 1.1); 2025-11-30 18:45:09.957 UTC client backend[45076] pg_regress/test_resowner WARNING: resource was not closed: test string "my string" 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('^*', '', '-'); 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('$*', '', '-'); 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('\A*', '', '-'); 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.961 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('\Z*', '', '-'); 2025-11-30 18:45:09.961 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.963 UTC client backend[45076] pg_regress/test_resowner ERROR: ResourceOwnerEnlarge called after release started 2025-11-30 18:45:09.963 UTC client backend[45076] pg_regress/test_resowner STATEMENT: SELECT test_resowner_remember_between_phases(); 2025-11-30 18:45:09.963 UTC client backend[44909] pg_regress/triggers ERROR: "parted_trig" is a table 2025-11-30 18:45:09.963 UTC client backend[44909] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-11-30 18:45:09.963 UTC client backend[44909] pg_regress/triggers STATEMENT: create trigger failed instead of update on parted_trig for each row execute procedure trigger_nothing(); 2025-11-30 18:45:09.964 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.964 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('[[:<:]]*', '', '-'); 2025-11-30 18:45:09.964 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.964 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('[[:>:]]*', '', '-'); 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('\<*', '', 'b'); 2025-11-30 18:45:09.965 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.965 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:09.965 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.965 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: COMMIT; 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('\>*', '', 'b'); 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('\y*', '', '-'); 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:09.965 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('\Y*', '', '-'); 2025-11-30 18:45:09.965 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update column "s" of view "rw_view1" 2025-11-30 18:45:09.965 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:09.965 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET s = s WHERE a = 1.1; 2025-11-30 18:45:09.966 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.966 UTC client backend[44909] pg_regress/triggers ERROR: "parted_trig" is a partitioned table 2025-11-30 18:45:09.966 UTC client backend[44909] pg_regress/triggers DETAIL: ROW triggers with transition tables are not supported on partitioned tables. 2025-11-30 18:45:09.966 UTC client backend[44909] 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-11-30 18:45:09.966 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.967 UTC client backend[45081] pg_regress LOG: disconnection: session time: 0:00:00.027 user=postgres database=postgres host=[local] 2025-11-30 18:45:09.970 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.972 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-11-30 18:45:09.972 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.973 UTC unrecognized[45085] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.973 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.973 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_parted", skipping it 2025-11-30 18:45:09.973 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.973 UTC client backend[45085] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:09.973 UTC client backend[45085] [unknown] LOG: connection authorized: user=postgres database=regression_test_rls_hooks application_name=pg_regress/test_rls_hooks 2025-11-30 18:45:09.974 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.974 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-11-30 18:45:09.974 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.974 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.975 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.975 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.975 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.976 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.976 UTC client backend[45076] pg_regress/test_resowner ERROR: ResourceOwnerForget called for test resource after release started 2025-11-30 18:45:09.976 UTC client backend[45076] pg_regress/test_resowner STATEMENT: SELECT test_resowner_forget_between_phases(); 2025-11-30 18:45:09.976 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-11-30 18:45:09.976 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.976 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-11-30 18:45:09.976 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-11-30 18:45:09.976 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.976 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.977 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-11-30 18:45:09.977 UTC client backend[44913] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-11-30 18:45:09.978 UTC client backend[45085] pg_regress/test_rls_hooks LOG: connection ready: setup total=5.832 ms, fork=0.455 ms, authentication=0.117 ms 2025-11-30 18:45:09.981 UTC unrecognized[45086] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:09.984 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:09.984 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:09.984 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:09.984 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: INSERT INTO project VALUES (101, 'Build Great Wall', 1); 2025-11-30 18:45:09.984 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.984 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('[\w-~]*', 'ab01_~-`**', 'LNPSE'); 2025-11-30 18:45:09.985 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.985 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('[~-\w]*', 'ab01_~-`**', 'LNPSE'); 2025-11-30 18:45:09.985 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.985 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('[[:alnum:]-~]*', 'ab01~-`**', 'LNS'); 2025-11-30 18:45:09.985 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid character range 2025-11-30 18:45:09.985 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('[~-[:alnum:]]*', 'ab01~-`**', 'LNS'); 2025-11-30 18:45:09.990 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_permissive" 2025-11-30 18:45:09.990 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_permissive VALUES ('regress_r4','regress_s4',10); 2025-11-30 18:45:09.993 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy "extension policy" for table "rls_test_restrictive" 2025-11-30 18:45:09.993 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_restrictive VALUES ('regress_r4','regress_s4',10); 2025-11-30 18:45:09.994 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_both" 2025-11-30 18:45:09.994 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_both VALUES ('regress_r1','regress_s1',10); 2025-11-30 18:45:09.995 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_both" 2025-11-30 18:45:09.995 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_both VALUES ('regress_r4','regress_s1',10); 2025-11-30 18:45:09.995 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_both" 2025-11-30 18:45:09.995 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_both VALUES ('regress_r4','regress_s4',10); 2025-11-30 18:45:10.000 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_permissive" 2025-11-30 18:45:10.000 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_permissive VALUES ('regress_r4','regress_s4',7); 2025-11-30 18:45:10.000 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.000 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\', '', ''); 2025-11-30 18:45:10.000 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.000 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\', '', 'b'); 2025-11-30 18:45:10.001 UTC client backend[44913] pg_regress/vacuum LOG: disconnection: session time: 0:00:01.458 user=postgres database=regression host=[local] 2025-11-30 18:45:10.002 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy "extension policy" for table "rls_test_restrictive" 2025-11-30 18:45:10.002 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_restrictive VALUES ('regress_r3','regress_s3',10); 2025-11-30 18:45:10.003 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_restrictive" 2025-11-30 18:45:10.003 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_restrictive VALUES ('regress_r1','regress_s1',7); 2025-11-30 18:45:10.003 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_restrictive" 2025-11-30 18:45:10.003 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_restrictive VALUES ('regress_r4','regress_s4',7); 2025-11-30 18:45:10.005 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy "extension policy" for table "rls_test_both" 2025-11-30 18:45:10.005 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_both VALUES ('regress_r3','regress_s3',10); 2025-11-30 18:45:10.006 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_both" 2025-11-30 18:45:10.006 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_both VALUES ('regress_r1','regress_s1',7); 2025-11-30 18:45:10.006 UTC client backend[45076] pg_regress/test_resowner LOG: disconnection: session time: 0:00:00.113 user=postgres database=regression_test_resowner host=[local] 2025-11-30 18:45:10.006 UTC client backend[45085] pg_regress/test_rls_hooks ERROR: new row violates row-level security policy for table "rls_test_both" 2025-11-30 18:45:10.006 UTC client backend[45085] pg_regress/test_rls_hooks STATEMENT: INSERT INTO rls_test_both VALUES ('regress_r4','regress_s4',7); 2025-11-30 18:45:10.006 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "t" of view "rw_view2" 2025-11-30 18:45:10.006 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:10.006 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (null, null, null, 1.1, null); 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\u008x', E'a\bx', 'P'); 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\U0000008x', E'a\bx', 'P'); 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\xq', '', '-'); 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.009 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\z', '', '-'); 2025-11-30 18:45:10.010 UTC client backend[45085] pg_regress/test_rls_hooks LOG: disconnection: session time: 0:00:00.037 user=postgres database=regression_test_rls_hooks host=[local] 2025-11-30 18:45:10.010 UTC client backend[45086] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.010 UTC client backend[45086] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.011 UTC client backend[45086] pg_regress LOG: connection ready: setup total=30.516 ms, fork=0.392 ms, authentication=0.127 ms 2025-11-30 18:45:10.012 UTC client backend[45086] pg_regress LOG: disconnection: session time: 0:00:00.030 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.012 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.012 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.012 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.012 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: UPDATE person SET is_project_manager = false WHERE person_id = 1; 2025-11-30 18:45:10.013 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:10.013 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a((b)\1)', '', '-'); 2025-11-30 18:45:10.013 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:10.013 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a(b)c\2', '', '-'); 2025-11-30 18:45:10.017 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-11-30 18:45:10.017 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:10.017 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2(s, c, base_a) VALUES (null, null, 1.1); 2025-11-30 18:45:10.017 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:10.017 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\7b', '', '-'); 2025-11-30 18:45:10.018 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:10.018 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a((((((((((b\10))))))))))c', '', '-'); 2025-11-30 18:45:10.018 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid backreference number 2025-11-30 18:45:10.018 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('a\12b', '', 'b'); 2025-11-30 18:45:10.022 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid regexp (reg version 0.8) 2025-11-30 18:45:10.022 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***?', '', ''); 2025-11-30 18:45:10.022 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid regexp (reg version 0.8) 2025-11-30 18:45:10.022 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***?', '', 'b'); 2025-11-30 18:45:10.023 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:10.023 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***:***=a*b', '', ''); 2025-11-30 18:45:10.023 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:10.023 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***:***=a*b', '', 'b'); 2025-11-30 18:45:10.023 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:10.023 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('(?b)\w+', '', 'e'); 2025-11-30 18:45:10.024 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update column "s" of view "rw_view1" 2025-11-30 18:45:10.024 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:10.024 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET s = s WHERE base_a = 1.1; 2025-11-30 18:45:10.024 UTC client backend[44909] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart1 because trigger trg1 on table trigpart requires it 2025-11-30 18:45:10.024 UTC client backend[44909] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2025-11-30 18:45:10.024 UTC client backend[44909] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart1; 2025-11-30 18:45:10.025 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: invalid embedded option 2025-11-30 18:45:10.025 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('(?z)ab', '', '-'); 2025-11-30 18:45:10.025 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:10.025 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('(?i)(?q)a+', '', 'P'); 2025-11-30 18:45:10.026 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update column "t" of view "rw_view2" 2025-11-30 18:45:10.026 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:10.026 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET t = t WHERE base_a = 1.1; 2025-11-30 18:45:10.026 UTC client backend[44909] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart2 because trigger trg1 on table trigpart requires it 2025-11-30 18:45:10.026 UTC client backend[44909] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2025-11-30 18:45:10.026 UTC client backend[44909] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart2; 2025-11-30 18:45:10.028 UTC client backend[44909] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart3 because trigger trg1 on table trigpart requires it 2025-11-30 18:45:10.028 UTC client backend[44909] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2025-11-30 18:45:10.028 UTC client backend[44909] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart3; 2025-11-30 18:45:10.030 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.030 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.030 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.030 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.032 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "t" of view "rw_view3" 2025-11-30 18:45:10.032 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:10.032 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view3 VALUES (null, null, null, null); 2025-11-30 18:45:10.034 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-11-30 18:45:10.034 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:10.034 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view3(s) VALUES (null); 2025-11-30 18:45:10.037 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot update column "s" of view "rw_view1" 2025-11-30 18:45:10.037 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:10.037 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view3 SET s = s; 2025-11-30 18:45:10.048 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.048 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.048 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.048 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.063 UTC unrecognized[45092] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.064 UTC client backend[45092] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.064 UTC client backend[45092] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.065 UTC client backend[45092] pg_regress LOG: connection ready: setup total=4.795 ms, fork=2.880 ms, authentication=0.123 ms 2025-11-30 18:45:10.066 UTC unrecognized[45094] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.067 UTC client backend[45094] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.067 UTC client backend[45094] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.067 UTC client backend[45094] pg_regress LOG: connection ready: setup total=2.941 ms, fork=1.189 ms, authentication=0.117 ms 2025-11-30 18:45:10.069 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.069 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.069 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.069 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.069 UTC client backend[45094] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.082 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:10.082 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***', '', ''); 2025-11-30 18:45:10.082 UTC client backend[45079] pg_regress/test_regex ERROR: invalid regular expression: quantifier operand invalid 2025-11-30 18:45:10.082 UTC client backend[45079] pg_regress/test_regex STATEMENT: select * from test_regex('***', '', 'b'); 2025-11-30 18:45:10.082 UTC unrecognized[45097] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.083 UTC client backend[45097] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.083 UTC client backend[45097] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.084 UTC client backend[45097] pg_regress LOG: connection ready: setup total=2.757 ms, fork=0.673 ms, authentication=0.117 ms 2025-11-30 18:45:10.098 UTC client backend[44909] pg_regress/triggers ERROR: trigger "trg1" for table "trigpart3" does not exist 2025-11-30 18:45:10.098 UTC client backend[44909] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart3; 2025-11-30 18:45:10.101 UTC client backend[45097] pg_regress LOG: disconnection: session time: 0:00:00.019 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.103 UTC client backend[45092] pg_regress LOG: disconnection: session time: 0:00:00.040 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.105 UTC client backend[44909] pg_regress/triggers ERROR: trigger "trg1" for table "trigpart41" does not exist 2025-11-30 18:45:10.105 UTC client backend[44909] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart41; 2025-11-30 18:45:10.109 UTC unrecognized[45101] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.109 UTC client backend[45101] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.109 UTC client backend[45101] [unknown] LOG: connection authorized: user=postgres database=regression_test_tidstore application_name=pg_regress/test_tidstore 2025-11-30 18:45:10.110 UTC unrecognized[45103] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.114 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert a non-DEFAULT value into column "idplus1" 2025-11-30 18:45:10.114 UTC client backend[44915] pg_regress/updatable_views DETAIL: Column "idplus1" is a generated column. 2025-11-30 18:45:10.114 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl (id, idplus1) VALUES (5, 6); 2025-11-30 18:45:10.114 UTC client backend[45101] pg_regress/test_tidstore LOG: connection ready: setup total=8.064 ms, fork=2.915 ms, authentication=0.118 ms 2025-11-30 18:45:10.114 UTC client backend[45103] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.114 UTC client backend[45103] [unknown] LOG: connection authorized: user=postgres database=regression_test_shm_mq application_name=pg_regress/test_shm_mq 2025-11-30 18:45:10.119 UTC client backend[45103] pg_regress/test_shm_mq LOG: connection ready: setup total=10.459 ms, fork=1.645 ms, authentication=0.126 ms 2025-11-30 18:45:10.119 UTC unrecognized[45104] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.119 UTC client backend[45104] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.119 UTC client backend[45104] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.120 UTC client backend[45104] pg_regress LOG: connection ready: setup total=10.016 ms, fork=3.925 ms, authentication=0.121 ms 2025-11-30 18:45:10.120 UTC client backend[45104] pg_regress LOG: disconnection: session time: 0:00:00.006 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.125 UTC unrecognized[45106] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.125 UTC client backend[45106] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.125 UTC client backend[45106] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.125 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.125 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.125 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.125 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.126 UTC client backend[45106] pg_regress LOG: connection ready: setup total=1.561 ms, fork=0.357 ms, authentication=0.109 ms 2025-11-30 18:45:10.129 UTC client backend[45101] pg_regress/test_tidstore ERROR: tuple offset out of range: 0 2025-11-30 18:45:10.129 UTC client backend[45101] pg_regress/test_tidstore STATEMENT: SELECT do_set_block_offsets(1, ARRAY[0]::int2[]); 2025-11-30 18:45:10.130 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert a non-DEFAULT value into column "idplus1" 2025-11-30 18:45:10.130 UTC client backend[44915] pg_regress/updatable_views DETAIL: Column "idplus1" is a generated column. 2025-11-30 18:45:10.130 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 (id, idplus1) VALUES (6, 7); 2025-11-30 18:45:10.139 UTC client backend[45106] pg_regress LOG: disconnection: session time: 0:00:00.013 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.139 UTC postmaster[43401] LOG: background worker "test_shm_mq" (PID 45107) exited with exit code 1 2025-11-30 18:45:10.143 UTC unrecognized[45110] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.144 UTC client backend[45110] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.144 UTC client backend[45110] [unknown] LOG: connection authorized: user=postgres database=regression_typcache application_name=pg_regress/typcache_rel_type_cache 2025-11-30 18:45:10.149 UTC client backend[45110] pg_regress/typcache_rel_type_cache LOG: connection ready: setup total=6.046 ms, fork=0.504 ms, authentication=0.114 ms 2025-11-30 18:45:10.161 UTC postmaster[43401] LOG: background worker "test_shm_mq" (PID 45109) exited with exit code 1 2025-11-30 18:45:10.162 UTC client backend[45110] pg_regress/typcache_rel_type_cache ERROR: error triggered for injection point typecache-before-rel-type-cache-insert at character 8 2025-11-30 18:45:10.162 UTC client backend[45110] pg_regress/typcache_rel_type_cache STATEMENT: SELECT '(1)'::t; 2025-11-30 18:45:10.163 UTC client backend[45110] pg_regress/typcache_rel_type_cache LOG: disconnection: session time: 0:00:00.019 user=postgres database=regression_typcache host=[local] 2025-11-30 18:45:10.179 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.179 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.179 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.179 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: INSERT INTO project VALUES (101, 'Build Great Wall', 1); 2025-11-30 18:45:10.179 UTC client backend[44903] pg_regress/constraints ERROR: not-null constraints on partitioned tables cannot be NO INHERIT 2025-11-30 18:45:10.179 UTC client backend[44903] pg_regress/constraints STATEMENT: CREATE TABLE ATACC1 (a int NOT NULL NO INHERIT) PARTITION BY LIST (a); 2025-11-30 18:45:10.181 UTC client backend[44903] pg_regress/constraints ERROR: not-null constraints on partitioned tables cannot be NO INHERIT 2025-11-30 18:45:10.181 UTC client backend[44903] pg_regress/constraints STATEMENT: CREATE TABLE ATACC1 (a int, NOT NULL a NO INHERIT) PARTITION BY LIST (a); 2025-11-30 18:45:10.192 UTC client backend[45027] isolation/project-manager/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.192 UTC client backend[45027] isolation/project-manager/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.192 UTC client backend[45027] isolation/project-manager/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.192 UTC client backend[45027] isolation/project-manager/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.208 UTC client backend[45101] pg_regress/test_tidstore LOG: disconnection: session time: 0:00:00.099 user=postgres database=regression_test_tidstore host=[local] 2025-11-30 18:45:10.209 UTC postmaster[43401] LOG: background worker "test_shm_mq" (PID 45111) exited with exit code 1 2025-11-30 18:45:10.221 UTC client backend[44903] pg_regress/constraints ERROR: cannot change NO INHERIT status of NOT NULL constraint "a_is_not_null" on relation "atacc2" 2025-11-30 18:45:10.221 UTC client backend[44903] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-11-30 18:45:10.221 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE ATACC1 ADD CONSTRAINT ditto NOT NULL a; 2025-11-30 18:45:10.224 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.224 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.224 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.224 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.244 UTC client backend[44909] pg_regress/triggers ERROR: trigger "trg1" for relation "trigpart3" already exists 2025-11-30 18:45:10.244 UTC client backend[44909] pg_regress/triggers STATEMENT: alter table trigpart attach partition trigpart3 FOR VALUES FROM (2000) to (3000); 2025-11-30 18:45:10.246 UTC client backend[45022] isolation/project-manager/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.246 UTC client backend[45022] isolation/project-manager/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.246 UTC client backend[45022] isolation/project-manager/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.246 UTC client backend[45022] isolation/project-manager/s1 STATEMENT: INSERT INTO project VALUES (101, 'Build Great Wall', 1); 2025-11-30 18:45:10.250 UTC unrecognized[45118] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.251 UTC client backend[45118] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.251 UTC client backend[45118] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.252 UTC client backend[45118] pg_regress LOG: connection ready: setup total=2.606 ms, fork=1.097 ms, authentication=0.123 ms 2025-11-30 18:45:10.252 UTC client backend[45118] pg_regress LOG: disconnection: session time: 0:00:00.001 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.258 UTC unrecognized[45120] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.259 UTC client backend[45120] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.259 UTC client backend[45120] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.259 UTC client backend[45120] pg_regress LOG: connection ready: setup total=1.958 ms, fork=0.426 ms, authentication=0.119 ms 2025-11-30 18:45:10.260 UTC client backend[45120] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.264 UTC unrecognized[45122] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.266 UTC client backend[45122] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.266 UTC client backend[45122] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.267 UTC client backend[45122] pg_regress LOG: connection ready: setup total=3.665 ms, fork=0.730 ms, authentication=0.117 ms 2025-11-30 18:45:10.267 UTC client backend[45122] pg_regress LOG: disconnection: session time: 0:00:00.003 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.270 UTC client backend[45013] isolation/project-manager/control connection LOG: disconnection: session time: 0:00:00.724 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:10.271 UTC client backend[45022] isolation/project-manager/s1 LOG: disconnection: session time: 0:00:00.715 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:10.271 UTC client backend[45027] isolation/project-manager/s2 LOG: disconnection: session time: 0:00:00.685 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:10.274 UTC unrecognized[45126] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.275 UTC client backend[45126] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.275 UTC client backend[45126] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/classroom-scheduling 2025-11-30 18:45:10.276 UTC client backend[45126] isolation/classroom-scheduling LOG: connection ready: setup total=1.969 ms, fork=0.508 ms, authentication=0.110 ms 2025-11-30 18:45:10.279 UTC unrecognized[45127] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.279 UTC client backend[45127] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.279 UTC client backend[45127] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.280 UTC client backend[45127] pg_regress LOG: connection ready: setup total=6.235 ms, fork=0.702 ms, authentication=0.106 ms 2025-11-30 18:45:10.281 UTC client backend[45127] pg_regress LOG: disconnection: session time: 0:00:00.005 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.285 UTC unrecognized[45130] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.286 UTC client backend[45130] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.286 UTC client backend[45130] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.286 UTC client backend[45130] pg_regress LOG: connection ready: setup total=2.314 ms, fork=1.111 ms, authentication=0.116 ms 2025-11-30 18:45:10.297 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.297 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (4, 3). 2025-11-30 18:45:10.297 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES(4,3); 2025-11-30 18:45:10.298 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.298 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (5, null). 2025-11-30 18:45:10.298 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES(5,null); 2025-11-30 18:45:10.298 UTC client backend[44903] pg_regress/constraints ERROR: constraint "blah" for relation "notnull_tbl2" already exists 2025-11-30 18:45:10.298 UTC client backend[44903] pg_regress/constraints STATEMENT: CREATE TABLE notnull_tbl2 (a INTEGER CONSTRAINT blah NOT NULL, b INTEGER CONSTRAINT blah NOT NULL); 2025-11-30 18:45:10.299 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.299 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (3, -5). 2025-11-30 18:45:10.299 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = -5 WHERE a = 3; 2025-11-30 18:45:10.300 UTC client backend[45130] pg_regress LOG: disconnection: session time: 0:00:00.014 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.301 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.301 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (10, 10). 2025-11-30 18:45:10.301 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1(a) VALUES (10); 2025-11-30 18:45:10.303 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.303 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (11, 10). 2025-11-30 18:45:10.303 UTC client backend[44915] 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-11-30 18:45:10.304 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.304 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (3, 3). 2025-11-30 18:45:10.304 UTC client backend[44915] 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-11-30 18:45:10.304 UTC client backend[44903] pg_regress/constraints ERROR: column "a" is in a primary key 2025-11-30 18:45:10.304 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl2 ALTER a DROP NOT NULL; 2025-11-30 18:45:10.316 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.316 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-11-30 18:45:10.316 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (-5); 2025-11-30 18:45:10.317 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.317 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-11-30 18:45:10.317 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (15); 2025-11-30 18:45:10.318 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.318 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-11-30 18:45:10.318 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET a = a - 10; 2025-11-30 18:45:10.319 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.319 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-11-30 18:45:10.319 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET a = a + 10; 2025-11-30 18:45:10.321 UTC unrecognized[45132] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.324 UTC client backend[45132] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.324 UTC client backend[45132] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.325 UTC client backend[45132] pg_regress LOG: connection ready: setup total=4.421 ms, fork=0.970 ms, authentication=0.124 ms 2025-11-30 18:45:10.327 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.327 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (20). 2025-11-30 18:45:10.327 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (20); 2025-11-30 18:45:10.328 UTC client backend[44915] pg_regress/updatable_views ERROR: invalid value for enum option "check_option": here 2025-11-30 18:45:10.328 UTC client backend[44915] pg_regress/updatable_views DETAIL: Valid values are "local" and "cascaded". 2025-11-30 18:45:10.328 UTC client backend[44915] pg_regress/updatable_views STATEMENT: ALTER VIEW rw_view1 SET (check_option=here); 2025-11-30 18:45:10.329 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.329 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-20). 2025-11-30 18:45:10.329 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (-20); 2025-11-30 18:45:10.330 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.330 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (30). 2025-11-30 18:45:10.330 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (30); 2025-11-30 18:45:10.337 UTC client backend[45132] pg_regress LOG: disconnection: session time: 0:00:00.015 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.344 UTC unrecognized[45134] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.345 UTC client backend[45134] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.345 UTC client backend[45134] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.346 UTC client backend[45134] pg_regress LOG: connection ready: setup total=1.923 ms, fork=0.587 ms, authentication=0.120 ms 2025-11-30 18:45:10.347 UTC client backend[45134] pg_regress LOG: disconnection: session time: 0:00:00.002 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.352 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.352 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-3). 2025-11-30 18:45:10.352 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view3 VALUES (-3); 2025-11-30 18:45:10.357 UTC unrecognized[45128] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.357 UTC client backend[45128] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.357 UTC client backend[45128] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/classroom-scheduling 2025-11-30 18:45:10.358 UTC client backend[45128] isolation/classroom-scheduling LOG: connection ready: setup total=78.739 ms, fork=45.800 ms, authentication=0.119 ms 2025-11-30 18:45:10.361 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_check_constraint7" conflicts with NOT ENFORCED constraint on relation "p1_c1" 2025-11-30 18:45:10.361 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p1 add constraint inh_check_constraint7 check (f1 < 10) enforced; 2025-11-30 18:45:10.362 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.362 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (10, {4,5}). 2025-11-30 18:45:10.362 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (10, ARRAY[4,5]); 2025-11-30 18:45:10.366 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_check_constraint8" conflicts with NOT ENFORCED constraint on relation "p1_c1" 2025-11-30 18:45:10.366 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p1_c1 add constraint inh_check_constraint8 check (f1 < 10) not enforced; 2025-11-30 18:45:10.367 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.367 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (1, {-1,-2,3}). 2025-11-30 18:45:10.367 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b[1] = -b[1] WHERE a = 1; 2025-11-30 18:45:10.368 UTC client backend[44977] postgres_fdw LOG: disconnection: session time: 0:00:01.160 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:10.374 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_check_constraint2" conflicts with NOT ENFORCED constraint on relation "p1_fail" 2025-11-30 18:45:10.374 UTC client backend[44906] pg_regress/inherit STATEMENT: create table p1_fail(f1 int constraint inh_check_constraint2 check (f1 < 10) not enforced) inherits(p1); 2025-11-30 18:45:10.376 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.376 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (10, {4,5}). 2025-11-30 18:45:10.376 UTC client backend[44915] pg_regress/updatable_views STATEMENT: EXECUTE ins(10, ARRAY[4,5]); 2025-11-30 18:45:10.380 UTC unrecognized[45136] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.381 UTC client backend[45136] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.381 UTC client backend[45136] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:10.381 UTC client backend[45136] postgres_fdw LOG: connection ready: setup total=2.984 ms, fork=1.187 ms, authentication=0.123 ms 2025-11-30 18:45:10.385 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.385 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-11-30 18:45:10.385 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (15); 2025-11-30 18:45:10.395 UTC client backend[45136] postgres_fdw LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:10.395 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_check_constraint6" conflicts with NOT ENFORCED constraint on relation "p1_fail" 2025-11-30 18:45:10.395 UTC client backend[44906] pg_regress/inherit STATEMENT: create table p1_fail(f1 int constraint inh_check_constraint6 check (f1 < 10) not enforced) inherits(p1, p1_c1); 2025-11-30 18:45:10.396 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.396 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-11-30 18:45:10.396 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET a = a + 5; 2025-11-30 18:45:10.398 UTC unrecognized[45137] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.399 UTC client backend[45137] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.399 UTC client backend[45137] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/classroom-scheduling 2025-11-30 18:45:10.400 UTC client backend[45137] isolation/classroom-scheduling LOG: connection ready: setup total=4.121 ms, fork=2.055 ms, authentication=0.118 ms 2025-11-30 18:45:10.409 UTC unrecognized[45139] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.409 UTC client backend[45139] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.409 UTC client backend[45139] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-30 18:45:10.410 UTC client backend[45139] pg_regress LOG: connection ready: setup total=8.140 ms, fork=2.742 ms, authentication=0.121 ms 2025-11-30 18:45:10.416 UTC client backend[45139] pg_regress LOG: disconnection: session time: 0:00:00.011 user=postgres database=postgres host=[local] 2025-11-30 18:45:10.428 UTC unrecognized[45138] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.428 UTC client backend[45138] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.428 UTC client backend[45138] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:10.429 UTC client backend[45138] postgres_fdw LOG: connection ready: setup total=31.201 ms, fork=29.589 ms, authentication=0.126 ms 2025-11-30 18:45:10.430 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.430 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.430 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.430 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: UPDATE room_reservation SET start_time = TIMESTAMP WITH TIME ZONE '2010-04-01 13:30', end_time = TIMESTAMP WITH TIME ZONE '2010-04-01 14:30' WHERE room_id = '101' AND start_time = TIMESTAMP WITH TIME ZONE '2010-04-01 10:00'; 2025-11-30 18:45:10.439 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.439 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (15, 10). 2025-11-30 18:45:10.439 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (15, 20); 2025-11-30 18:45:10.440 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-11-30 18:45:10.440 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (20, 10). 2025-11-30 18:45:10.440 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET a = 20, b = 30; 2025-11-30 18:45:10.443 UTC client backend[44906] pg_regress/inherit ERROR: constraint "p1_a_check" conflicts with NOT ENFORCED constraint on child table "p1_c1" 2025-11-30 18:45:10.443 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p1_c1 inherit p1; 2025-11-30 18:45:10.444 UTC client backend[45138] postgres_fdw LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:10.444 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.444 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.444 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.444 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.453 UTC client backend[45079] pg_regress/test_regex LOG: disconnection: session time: 0:00:00.547 user=postgres database=regression_test_regex host=[local] 2025-11-30 18:45:10.457 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.457 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.457 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.457 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.468 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.468 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-11-30 18:45:10.468 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (-5); 2025-11-30 18:45:10.469 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.469 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.469 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.469 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: UPDATE room_reservation SET start_time = TIMESTAMP WITH TIME ZONE '2010-04-01 13:30', end_time = TIMESTAMP WITH TIME ZONE '2010-04-01 14:30' WHERE room_id = '101' AND start_time = TIMESTAMP WITH TIME ZONE '2010-04-01 10:00'; 2025-11-30 18:45:10.470 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.470 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-11-30 18:45:10.470 UTC client backend[44915] 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-11-30 18:45:10.476 UTC unrecognized[45147] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.477 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c1" 2025-11-30 18:45:10.477 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p1_c1 drop constraint f1_pos; 2025-11-30 18:45:10.477 UTC client backend[45147] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.477 UTC client backend[45147] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:10.478 UTC client backend[45147] postgres_fdw LOG: connection ready: setup total=2.720 ms, fork=0.585 ms, authentication=0.126 ms 2025-11-30 18:45:10.479 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.479 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-11-30 18:45:10.479 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET a = a - 10; 2025-11-30 18:45:10.480 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-11-30 18:45:10.480 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-4). 2025-11-30 18:45:10.480 UTC client backend[44915] 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-11-30 18:45:10.480 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.480 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.480 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.480 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.490 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.490 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.490 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.490 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.503 UTC unrecognized[45150] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.503 UTC client backend[45150] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.503 UTC client backend[45150] [unknown] LOG: connection authorized: user=postgres database=regression_test_regex application_name=pg_regress/test_regex_utf8 2025-11-30 18:45:10.504 UTC client backend[45150] pg_regress/test_regex_utf8 LOG: connection ready: setup total=1.956 ms, fork=0.423 ms, authentication=0.119 ms 2025-11-30 18:45:10.506 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.506 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.506 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.506 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.512 UTC client backend[45150] pg_regress/test_regex_utf8 ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.512 UTC client backend[45150] pg_regress/test_regex_utf8 STATEMENT: select * from test_regex('a\U0001234x', E'a\u1234x', 'P'); 2025-11-30 18:45:10.512 UTC client backend[45150] pg_regress/test_regex_utf8 ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.512 UTC client backend[45150] pg_regress/test_regex_utf8 STATEMENT: select * from test_regex('a\U0001234x', E'a\u1234x', 'P'); 2025-11-30 18:45:10.513 UTC client backend[45150] pg_regress/test_regex_utf8 ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.513 UTC client backend[45150] pg_regress/test_regex_utf8 STATEMENT: select * from test_regex('a\U1000000x', E'a\ufffd0x', 'P'); 2025-11-30 18:45:10.513 UTC client backend[45150] pg_regress/test_regex_utf8 ERROR: invalid regular expression: invalid escape \ sequence 2025-11-30 18:45:10.513 UTC client backend[45150] pg_regress/test_regex_utf8 STATEMENT: select * from test_regex('a\U1000000x', E'a\ufffd0x', 'P'); 2025-11-30 18:45:10.516 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.516 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.516 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.516 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.529 UTC postmaster[43401] LOG: background worker "test_shm_mq" (PID 45114) exited with exit code 1 2025-11-30 18:45:10.532 UTC client backend[45150] pg_regress/test_regex_utf8 LOG: disconnection: session time: 0:00:00.028 user=postgres database=regression_test_regex host=[local] 2025-11-30 18:45:10.533 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.533 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.533 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.533 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: INSERT INTO room_reservation VALUES ('101', TIMESTAMP WITH TIME ZONE '2010-04-01 13:00', TIMESTAMP WITH TIME ZONE '2010-04-01 14:00', 'Carol'); 2025-11-30 18:45:10.545 UTC client backend[45147] postgres_fdw LOG: disconnection: session time: 0:00:00.069 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:10.546 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.546 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.546 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.546 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: UPDATE room_reservation SET start_time = TIMESTAMP WITH TIME ZONE '2010-04-01 13:30', end_time = TIMESTAMP WITH TIME ZONE '2010-04-01 14:30' WHERE room_id = '101' AND start_time = TIMESTAMP WITH TIME ZONE '2010-04-01 10:00'; 2025-11-30 18:45:10.555 UTC unrecognized[45155] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.556 UTC client backend[45155] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.556 UTC client backend[45155] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:10.556 UTC client backend[45155] postgres_fdw LOG: connection ready: setup total=8.348 ms, fork=6.460 ms, authentication=0.123 ms 2025-11-30 18:45:10.586 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.586 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.586 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.586 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.610 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.610 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.610 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.610 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.617 UTC client backend[45155] postgres_fdw LOG: disconnection: session time: 0:00:00.062 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:10.619 UTC unrecognized[45166] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.620 UTC client backend[45166] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.620 UTC client backend[45166] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:10.620 UTC client backend[45166] postgres_fdw LOG: connection ready: setup total=2.185 ms, fork=0.726 ms, authentication=0.119 ms 2025-11-30 18:45:10.624 UTC client backend[44903] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-11-30 18:45:10.624 UTC client backend[44903] pg_regress/constraints DETAIL: The constraint "cnn_pk_a_not_null" on column "a" of table "cnn_pk", marked NO INHERIT, is incompatible with a primary key. 2025-11-30 18:45:10.624 UTC client backend[44903] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-11-30 18:45:10.624 UTC client backend[44903] pg_regress/constraints STATEMENT: alter table cnn_pk add primary key (a); 2025-11-30 18:45:10.625 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.625 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.625 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.625 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.630 UTC unrecognized[45167] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.630 UTC client backend[45167] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.630 UTC client backend[45167] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/compat_informix-rnull 2025-11-30 18:45:10.635 UTC client backend[45167] ecpg/compat_informix-rnull LOG: connection ready: setup total=6.811 ms, fork=1.535 ms, authentication=0.124 ms 2025-11-30 18:45:10.637 UTC client backend[45166] postgres_fdw LOG: disconnection: session time: 0:00:00.017 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:10.642 UTC unrecognized[45168] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.644 UTC client backend[45168] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.644 UTC client backend[45168] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:10.644 UTC client backend[45168] postgres_fdw LOG: connection ready: setup total=2.977 ms, fork=0.837 ms, authentication=0.121 ms 2025-11-30 18:45:10.645 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c2" 2025-11-30 18:45:10.645 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p1_c2 drop constraint f1_pos; 2025-11-30 18:45:10.646 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c1c2" 2025-11-30 18:45:10.646 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table p1_c1c2 drop constraint f1_pos; 2025-11-30 18:45:10.648 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.648 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.648 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.648 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.658 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_check_constraint" conflicts with NOT VALID constraint on relation "invalid_check_con_child" 2025-11-30 18:45:10.658 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table invalid_check_con add constraint inh_check_constraint check(f1 > 0); 2025-11-30 18:45:10.661 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "invalid_check_con" violates check constraint "inh_check_constraint" 2025-11-30 18:45:10.661 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (0). 2025-11-30 18:45:10.661 UTC client backend[44906] pg_regress/inherit STATEMENT: insert into invalid_check_con values(0); 2025-11-30 18:45:10.661 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "invalid_check_con_child" violates check constraint "inh_check_constraint" 2025-11-30 18:45:10.661 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (0). 2025-11-30 18:45:10.661 UTC client backend[44906] pg_regress/inherit STATEMENT: insert into invalid_check_con_child values(0); 2025-11-30 18:45:10.669 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.669 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.669 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.669 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: INSERT INTO room_reservation VALUES ('101', TIMESTAMP WITH TIME ZONE '2010-04-01 13:00', TIMESTAMP WITH TIME ZONE '2010-04-01 14:00', 'Carol'); 2025-11-30 18:45:10.671 UTC client backend[45167] ecpg/compat_informix-rnull LOG: disconnection: session time: 0:00:00.041 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.672 UTC client backend[44903] pg_regress/constraints ERROR: column "a" of relation "cnn_part1" contains null values 2025-11-30 18:45:10.672 UTC client backend[44903] pg_regress/constraints STATEMENT: alter table cnn2_parted add primary key (a); 2025-11-30 18:45:10.682 UTC unrecognized[45173] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.684 UTC client backend[45173] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.684 UTC client backend[45173] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/compat_informix-sqlda 2025-11-30 18:45:10.685 UTC client backend[45173] ecpg/compat_informix-sqlda LOG: connection ready: setup total=4.038 ms, fork=0.505 ms, authentication=0.127 ms 2025-11-30 18:45:10.686 UTC client backend[45137] isolation/classroom-scheduling/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.686 UTC client backend[45137] isolation/classroom-scheduling/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.686 UTC client backend[45137] isolation/classroom-scheduling/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.686 UTC client backend[45137] isolation/classroom-scheduling/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.699 UTC unrecognized[45174] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.700 UTC client backend[45174] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.700 UTC client backend[45174] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/compat_informix-sqlda 2025-11-30 18:45:10.701 UTC client backend[45174] ecpg/compat_informix-sqlda LOG: connection ready: setup total=7.426 ms, fork=5.102 ms, authentication=0.132 ms 2025-11-30 18:45:10.701 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.701 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.701 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.701 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.704 UTC client backend[45174] ecpg/compat_informix-sqlda LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.707 UTC client backend[45173] ecpg/compat_informix-sqlda LOG: disconnection: session time: 0:00:00.025 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.714 UTC client backend[45128] isolation/classroom-scheduling/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.714 UTC client backend[45128] isolation/classroom-scheduling/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:10.714 UTC client backend[45128] isolation/classroom-scheduling/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.714 UTC client backend[45128] isolation/classroom-scheduling/s1 STATEMENT: INSERT INTO room_reservation VALUES ('101', TIMESTAMP WITH TIME ZONE '2010-04-01 13:00', TIMESTAMP WITH TIME ZONE '2010-04-01 14:00', 'Carol'); 2025-11-30 18:45:10.721 UTC unrecognized[45179] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.721 UTC client backend[45179] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.721 UTC client backend[45179] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/compat_informix-describe 2025-11-30 18:45:10.722 UTC client backend[45179] ecpg/compat_informix-describe LOG: connection ready: setup total=2.139 ms, fork=0.569 ms, authentication=0.119 ms 2025-11-30 18:45:10.737 UTC client backend[44909] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-11-30 18:45:10.737 UTC client backend[44909] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_1_1". 2025-11-30 18:45:10.737 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into parted values (1, 1, 'uno uno v2'); 2025-11-30 18:45:10.737 UTC client backend[44909] pg_regress/triggers ERROR: no partition of relation "parted" found for row 2025-11-30 18:45:10.737 UTC client backend[44909] pg_regress/triggers DETAIL: Partition key of the failing row contains (a) = (2). 2025-11-30 18:45:10.737 UTC client backend[44909] pg_regress/triggers STATEMENT: update parted set c = c || 'v3'; 2025-11-30 18:45:10.739 UTC client backend[44909] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-11-30 18:45:10.739 UTC client backend[44909] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_1_1". 2025-11-30 18:45:10.739 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into parted values (1, 1, 'uno uno v4'); 2025-11-30 18:45:10.739 UTC client backend[44909] pg_regress/triggers ERROR: no partition of relation "parted_1" found for row 2025-11-30 18:45:10.739 UTC client backend[44909] pg_regress/triggers DETAIL: Partition key of the failing row contains (b) = (2). 2025-11-30 18:45:10.739 UTC client backend[44909] pg_regress/triggers STATEMENT: update parted set c = c || 'v5'; 2025-11-30 18:45:10.762 UTC client backend[45179] ecpg/compat_informix-describe LOG: disconnection: session time: 0:00:00.041 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.776 UTC unrecognized[45184] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.777 UTC client backend[45184] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.777 UTC client backend[45184] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/compat_informix-test_informix 2025-11-30 18:45:10.778 UTC client backend[45184] ecpg/compat_informix-test_informix LOG: connection ready: setup total=2.838 ms, fork=1.239 ms, authentication=0.119 ms 2025-11-30 18:45:10.783 UTC client backend[45184] ecpg/compat_informix-test_informix ERROR: duplicate key value violates unique constraint "test_pkey" 2025-11-30 18:45:10.783 UTC client backend[45184] ecpg/compat_informix-test_informix DETAIL: Key (i)=(7) already exists. 2025-11-30 18:45:10.783 UTC client backend[45184] ecpg/compat_informix-test_informix STATEMENT: insert into test ( i , j , c ) values ( 7 , 12 , 'a' ) 2025-11-30 18:45:10.785 UTC client backend[45184] ecpg/compat_informix-test_informix ERROR: more than one row returned by a subquery used as an expression 2025-11-30 18:45:10.785 UTC client backend[45184] ecpg/compat_informix-test_informix STATEMENT: select i from test where j = ( select j from test ) 2025-11-30 18:45:10.791 UTC client backend[45184] ecpg/compat_informix-test_informix LOG: disconnection: session time: 0:00:00.014 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.801 UTC client backend[45128] isolation/classroom-scheduling/s1 LOG: disconnection: session time: 0:00:00.475 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:10.805 UTC client backend[45137] isolation/classroom-scheduling/s2 LOG: disconnection: session time: 0:00:00.407 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:10.805 UTC client backend[45126] isolation/classroom-scheduling/control connection LOG: disconnection: session time: 0:00:00.531 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:10.846 UTC unrecognized[45192] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.847 UTC client backend[45192] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.847 UTC client backend[45192] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/total-cash 2025-11-30 18:45:10.847 UTC unrecognized[45191] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.847 UTC client backend[45191] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.848 UTC client backend[45191] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/compat_informix-test_informix2 2025-11-30 18:45:10.848 UTC client backend[45192] isolation/total-cash LOG: connection ready: setup total=1.921 ms, fork=0.298 ms, authentication=0.135 ms 2025-11-30 18:45:10.848 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "v1" 2025-11-30 18:45:10.848 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-2, minus two, 20). 2025-11-30 18:45:10.848 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO v2 VALUES (-2, 'minus two', 20); 2025-11-30 18:45:10.848 UTC client backend[45191] ecpg/compat_informix-test_informix2 LOG: connection ready: setup total=2.999 ms, fork=1.583 ms, authentication=0.105 ms 2025-11-30 18:45:10.849 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "v2" 2025-11-30 18:45:10.849 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (3, three, 30). 2025-11-30 18:45:10.849 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO v2 VALUES (3, 'three', 30); 2025-11-30 18:45:10.849 UTC unrecognized[45193] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.850 UTC client backend[45193] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.850 UTC client backend[45193] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/total-cash 2025-11-30 18:45:10.851 UTC client backend[45193] isolation/total-cash LOG: connection ready: setup total=1.825 ms, fork=0.519 ms, authentication=0.097 ms 2025-11-30 18:45:10.851 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "v1" 2025-11-30 18:45:10.851 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-1, ONE, 10). 2025-11-30 18:45:10.851 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE v2 SET a = -1 WHERE a = 1; 2025-11-30 18:45:10.851 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "v2" 2025-11-30 18:45:10.851 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (1, ONE, 30). 2025-11-30 18:45:10.851 UTC client backend[44915] pg_regress/updatable_views STATEMENT: UPDATE v2 SET c = 30 WHERE a = 1; 2025-11-30 18:45:10.853 UTC unrecognized[45194] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.853 UTC client backend[45191] ecpg/compat_informix-test_informix2 LOG: disconnection: session time: 0:00:00.006 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.854 UTC client backend[45194] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.854 UTC client backend[45194] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/total-cash 2025-11-30 18:45:10.854 UTC client backend[45194] isolation/total-cash LOG: connection ready: setup total=2.869 ms, fork=1.532 ms, authentication=0.100 ms 2025-11-30 18:45:10.873 UTC client backend[44909] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-11-30 18:45:10.873 UTC client backend[44909] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_1". 2025-11-30 18:45:10.873 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into parted values (1, 1, 'one fail'); 2025-11-30 18:45:10.873 UTC unrecognized[45203] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.874 UTC client backend[45203] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.874 UTC client backend[45203] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/compat_oracle-char_array 2025-11-30 18:45:10.875 UTC client backend[45203] ecpg/compat_oracle-char_array LOG: connection ready: setup total=2.489 ms, fork=0.665 ms, authentication=0.124 ms 2025-11-30 18:45:10.879 UTC client backend[45203] ecpg/compat_oracle-char_array LOG: disconnection: session time: 0:00:00.006 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.883 UTC client backend[45168] postgres_fdw LOG: disconnection: session time: 0:00:00.240 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:10.884 UTC client backend[44909] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-11-30 18:45:10.884 UTC client backend[44909] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_2". 2025-11-30 18:45:10.884 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into parted values (1, 2, 'two fail'); 2025-11-30 18:45:10.886 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.886 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on conflict out to pivot 11889, during read. 2025-11-30 18:45:10.886 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.886 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: SELECT SUM(balance) FROM accounts; 2025-11-30 18:45:10.888 UTC unrecognized[45209] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.889 UTC client backend[45209] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.889 UTC client backend[45209] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test2 2025-11-30 18:45:10.889 UTC unrecognized[45208] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.893 UTC client backend[45209] ecpg/connect-test2 LOG: connection ready: setup total=5.321 ms, fork=0.258 ms, authentication=0.112 ms 2025-11-30 18:45:10.894 UTC client backend[45208] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.894 UTC client backend[45208] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:10.894 UTC client backend[44909] pg_regress/triggers ERROR: constraint triggers cannot be marked NOT VALID at character 54 2025-11-30 18:45:10.894 UTC client backend[44909] pg_regress/triggers STATEMENT: create constraint trigger crtr after insert on foo not valid for each row execute procedure foo (); 2025-11-30 18:45:10.894 UTC client backend[45208] postgres_fdw LOG: connection ready: setup total=6.908 ms, fork=1.716 ms, authentication=0.111 ms 2025-11-30 18:45:10.897 UTC unrecognized[45210] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.898 UTC client backend[45210] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.898 UTC client backend[45210] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/connect-test2 2025-11-30 18:45:10.899 UTC client backend[45210] ecpg/connect-test2 LOG: connection ready: setup total=4.917 ms, fork=3.395 ms, authentication=0.105 ms 2025-11-30 18:45:10.899 UTC client backend[44909] pg_regress/triggers ERROR: constraint triggers cannot be marked NO INHERIT at character 54 2025-11-30 18:45:10.899 UTC client backend[44909] pg_regress/triggers STATEMENT: create constraint trigger crtr after insert on foo no inherit for each row execute procedure foo (); 2025-11-30 18:45:10.899 UTC client backend[44909] pg_regress/triggers ERROR: constraint triggers cannot be marked NOT ENFORCED at character 54 2025-11-30 18:45:10.899 UTC client backend[44909] pg_regress/triggers STATEMENT: create constraint trigger crtr after insert on foo not enforced for each row execute procedure foo (); 2025-11-30 18:45:10.901 UTC client backend[45209] ecpg/connect-test2 LOG: disconnection: session time: 0:00:00.012 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:10.902 UTC client backend[45210] ecpg/connect-test2 LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.907 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.907 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.907 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.907 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: COMMIT; 2025-11-30 18:45:10.919 UTC unrecognized[45215] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.919 UTC client backend[45215] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.919 UTC client backend[45215] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test3 2025-11-30 18:45:10.920 UTC client backend[45215] ecpg/connect-test3 LOG: connection ready: setup total=1.973 ms, fork=0.425 ms, authentication=0.117 ms 2025-11-30 18:45:10.921 UTC unrecognized[45216] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.921 UTC client backend[45216] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.921 UTC client backend[45216] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/connect-test3 2025-11-30 18:45:10.922 UTC client backend[45216] ecpg/connect-test3 LOG: connection ready: setup total=2.145 ms, fork=0.751 ms, authentication=0.117 ms 2025-11-30 18:45:10.924 UTC client backend[45216] ecpg/connect-test3 LOG: disconnection: session time: 0:00:00.003 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.927 UTC unrecognized[45217] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.927 UTC client backend[45217] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.927 UTC client backend[45217] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/connect-test3 2025-11-30 18:45:10.928 UTC client backend[45217] ecpg/connect-test3 LOG: connection ready: setup total=2.559 ms, fork=1.161 ms, authentication=0.105 ms 2025-11-30 18:45:10.928 UTC client backend[45217] ecpg/connect-test3 LOG: disconnection: session time: 0:00:00.001 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.929 UTC client backend[45215] ecpg/connect-test3 LOG: disconnection: session time: 0:00:00.010 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:10.940 UTC unrecognized[45222] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.940 UTC client backend[45222] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.940 UTC client backend[45222] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/connect-test4 2025-11-30 18:45:10.941 UTC client backend[45222] ecpg/connect-test4 LOG: connection ready: setup total=5.105 ms, fork=1.557 ms, authentication=0.120 ms 2025-11-30 18:45:10.942 UTC client backend[45222] ecpg/connect-test4 LOG: disconnection: session time: 0:00:00.003 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:10.953 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "v1" 2025-11-30 18:45:10.953 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (-1, invalid). 2025-11-30 18:45:10.953 UTC client backend[44915] pg_regress/updatable_views STATEMENT: INSERT INTO v1 VALUES (-1, 'invalid'); 2025-11-30 18:45:10.957 UTC unrecognized[45227] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.958 UTC client backend[45227] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.958 UTC client backend[45227] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:10.959 UTC client backend[45227] ecpg/connect-test5 LOG: connection ready: setup total=3.532 ms, fork=0.954 ms, authentication=0.132 ms 2025-11-30 18:45:10.961 UTC postmaster[43401] LOG: background worker "test_shm_mq" (PID 45159) exited with exit code 1 2025-11-30 18:45:10.961 UTC postmaster[43401] LOG: background worker "test_shm_mq" (PID 45161) exited with exit code 1 2025-11-30 18:45:10.962 UTC postmaster[43401] LOG: background worker "test_shm_mq" (PID 45160) exited with exit code 1 2025-11-30 18:45:10.963 UTC client backend[45103] pg_regress/test_shm_mq LOG: disconnection: session time: 0:00:00.853 user=postgres database=regression_test_shm_mq host=[local] 2025-11-30 18:45:10.970 UTC client backend[45227] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.013 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:10.975 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.975 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:10.975 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.975 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: COMMIT; 2025-11-30 18:45:10.975 UTC unrecognized[45229] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.975 UTC client backend[45229] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.975 UTC client backend[45229] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:10.976 UTC client backend[45229] ecpg/connect-test5 LOG: connection ready: setup total=5.164 ms, fork=3.549 ms, authentication=0.133 ms 2025-11-30 18:45:10.977 UTC client backend[45229] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.001 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:10.982 UTC unrecognized[45230] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.982 UTC client backend[45230] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.982 UTC client backend[45230] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:10.983 UTC client backend[45230] ecpg/connect-test5 LOG: connection ready: setup total=6.388 ms, fork=4.866 ms, authentication=0.113 ms 2025-11-30 18:45:10.984 UTC client backend[45230] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.002 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:10.985 UTC unrecognized[45231] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.986 UTC client backend[45231] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.986 UTC client backend[45231] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:10.987 UTC client backend[45231] ecpg/connect-test5 LOG: connection ready: setup total=3.249 ms, fork=1.312 ms, authentication=0.110 ms 2025-11-30 18:45:10.987 UTC client backend[45231] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.002 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:10.990 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:10.990 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on conflict out to pivot 11976, during read. 2025-11-30 18:45:10.990 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:10.990 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: SELECT SUM(balance) FROM accounts; 2025-11-30 18:45:10.992 UTC unrecognized[45232] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.992 UTC client backend[45232] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.992 UTC client backend[45232] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:10.993 UTC client backend[45232] ecpg/connect-test5 LOG: connection ready: setup total=5.542 ms, fork=2.852 ms, authentication=0.109 ms 2025-11-30 18:45:10.995 UTC client backend[45232] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.004 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:10.996 UTC client backend[44903] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1" contains null values 2025-11-30 18:45:10.996 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD CONSTRAINT nn NOT NULL a; 2025-11-30 18:45:10.999 UTC unrecognized[45233] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:10.999 UTC client backend[45233] [unknown] LOG: connection authenticated: user="regress_ecpg_user1" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:10.999 UTC client backend[45233] [unknown] LOG: connection authorized: user=regress_ecpg_user1 database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:11.000 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "uv_ptv_wco" 2025-11-30 18:45:11.000 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (1, 2, null). 2025-11-30 18:45:11.000 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into uv_ptv_wco values (1, 2); 2025-11-30 18:45:11.000 UTC client backend[45233] ecpg/connect-test5 LOG: connection ready: setup total=3.847 ms, fork=0.989 ms, authentication=0.111 ms 2025-11-30 18:45:11.000 UTC client backend[45233] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.003 user=regress_ecpg_user1 database=ecpg2_regression host=[local] 2025-11-30 18:45:11.000 UTC client backend[44915] pg_regress/updatable_views ERROR: MERGE command cannot affect row a second time 2025-11-30 18:45:11.000 UTC client backend[44915] pg_regress/updatable_views HINT: Ensure that not more than one source row matches any one target row. 2025-11-30 18:45:11.000 UTC client backend[44915] 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-11-30 18:45:11.002 UTC client backend[44915] pg_regress/updatable_views ERROR: no partition of relation "uv_pt1" found for row 2025-11-30 18:45:11.002 UTC client backend[44915] pg_regress/updatable_views DETAIL: Partition key of the failing row contains (b) = (5). 2025-11-30 18:45:11.002 UTC client backend[44915] 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-11-30 18:45:11.002 UTC client backend[44903] pg_regress/constraints ERROR: null value in column "a" of relation "notnull_tbl1" violates not-null constraint 2025-11-30 18:45:11.002 UTC client backend[44903] pg_regress/constraints DETAIL: Failing row contains (null, 4). 2025-11-30 18:45:11.002 UTC client backend[44903] pg_regress/constraints STATEMENT: INSERT INTO notnull_tbl1 VALUES (NULL, 4); 2025-11-30 18:45:11.005 UTC unrecognized[45234] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.006 UTC client backend[45234] [unknown] LOG: connection authenticated: user="regress_ecpg_user1" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.006 UTC client backend[45234] [unknown] LOG: connection authorized: user=regress_ecpg_user1 database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:11.007 UTC client backend[45234] ecpg/connect-test5 LOG: connection ready: setup total=6.071 ms, fork=4.684 ms, authentication=0.106 ms 2025-11-30 18:45:11.008 UTC client backend[45234] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.002 user=regress_ecpg_user1 database=ecpg2_regression host=[local] 2025-11-30 18:45:11.011 UTC unrecognized[45235] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.012 UTC client backend[45235] [unknown] LOG: connection authenticated: user="regress_ecpg_user1" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.012 UTC client backend[45235] [unknown] LOG: connection authorized: user=regress_ecpg_user1 database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:11.013 UTC client backend[45235] ecpg/connect-test5 LOG: connection ready: setup total=3.816 ms, fork=1.049 ms, authentication=0.100 ms 2025-11-30 18:45:11.014 UTC unrecognized[45236] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.014 UTC client backend[45236] [unknown] LOG: connection authenticated: user="regress_ecpg_user1" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.014 UTC client backend[45236] [unknown] LOG: connection authorized: user=regress_ecpg_user1 database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:11.015 UTC client backend[45235] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.004 user=regress_ecpg_user1 database=ecpg2_regression host=[local] 2025-11-30 18:45:11.015 UTC client backend[45236] ecpg/connect-test5 LOG: connection ready: setup total=2.361 ms, fork=1.027 ms, authentication=0.106 ms 2025-11-30 18:45:11.015 UTC client backend[45236] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.001 user=regress_ecpg_user1 database=ecpg2_regression host=[local] 2025-11-30 18:45:11.016 UTC unrecognized[45237] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.017 UTC client backend[45237] [unknown] LOG: connection authenticated: user="regress_ecpg_user1" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.017 UTC client backend[45237] [unknown] LOG: connection authorized: user=regress_ecpg_user1 database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:11.017 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "wcowrtest_v" 2025-11-30 18:45:11.017 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (1). 2025-11-30 18:45:11.017 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into wcowrtest_v values (1); 2025-11-30 18:45:11.018 UTC client backend[45237] ecpg/connect-test5 LOG: connection ready: setup total=1.731 ms, fork=0.440 ms, authentication=0.109 ms 2025-11-30 18:45:11.018 UTC client backend[45237] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.001 user=regress_ecpg_user1 database=ecpg2_regression host=[local] 2025-11-30 18:45:11.019 UTC unrecognized[45238] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.019 UTC client backend[45238] [unknown] LOG: connection authenticated: user="regress_ecpg_user2" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.019 UTC client backend[45238] [unknown] LOG: connection authorized: user=regress_ecpg_user2 database=regress_ecpg_user2 application_name=ecpg/connect-test5 2025-11-30 18:45:11.019 UTC client backend[45238] [unknown] FATAL: database "regress_ecpg_user2" does not exist 2025-11-30 18:45:11.023 UTC unrecognized[45239] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.023 UTC client backend[45239] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.023 UTC client backend[45239] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/connect-test5 2025-11-30 18:45:11.024 UTC client backend[45239] ecpg/connect-test5 LOG: connection ready: setup total=3.364 ms, fork=0.686 ms, authentication=0.100 ms 2025-11-30 18:45:11.025 UTC client backend[45239] ecpg/connect-test5 LOG: disconnection: session time: 0:00:00.003 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:11.030 UTC client backend[44915] pg_regress/updatable_views ERROR: new row violates check option for view "wcowrtest_v2" 2025-11-30 18:45:11.030 UTC client backend[44915] pg_regress/updatable_views DETAIL: Failing row contains (2, no such row in sometable). 2025-11-30 18:45:11.030 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into wcowrtest_v2 values (2, 'no such row in sometable'); 2025-11-30 18:45:11.030 UTC client backend[44903] pg_regress/constraints ERROR: cannot change NO INHERIT status of NOT NULL constraint "nn" on relation "notnull_tbl1" 2025-11-30 18:45:11.030 UTC client backend[44903] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-11-30 18:45:11.030 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD CONSTRAINT nn1 NOT NULL a NOT VALID NO INHERIT; 2025-11-30 18:45:11.033 UTC client backend[44903] pg_regress/constraints ERROR: incompatible NOT VALID constraint "nn" on relation "notnull_tbl1" 2025-11-30 18:45:11.033 UTC client backend[44903] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-11-30 18:45:11.033 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD CONSTRAINT nn NOT NULL a; 2025-11-30 18:45:11.039 UTC client backend[44906] pg_regress/inherit ERROR: cannot define not-null constraint with NO INHERIT on column "a2" 2025-11-30 18:45:11.039 UTC client backend[44906] pg_regress/inherit DETAIL: The column has an inherited not-null constraint. 2025-11-30 18:45:11.039 UTC client backend[44906] pg_regress/inherit STATEMENT: create table cc3 (a2 int not null no inherit) inherits (cc1); 2025-11-30 18:45:11.040 UTC client backend[44906] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "nn" on relation "cc2" 2025-11-30 18:45:11.040 UTC client backend[44906] pg_regress/inherit HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-11-30 18:45:11.040 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table cc2 add not null a2 no inherit; 2025-11-30 18:45:11.041 UTC client backend[44903] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-11-30 18:45:11.041 UTC client backend[44903] pg_regress/constraints DETAIL: The constraint "nn" on column "a" of table "notnull_tbl1", marked NOT VALID, is incompatible with a primary key. 2025-11-30 18:45:11.041 UTC client backend[44903] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-11-30 18:45:11.041 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD PRIMARY KEY (a); 2025-11-30 18:45:11.041 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "nn" of relation "cc2" 2025-11-30 18:45:11.041 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table cc2 alter column a2 drop not null; 2025-11-30 18:45:11.046 UTC unrecognized[45244] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.047 UTC client backend[45244] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.047 UTC client backend[45244] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/pgtypeslib-dt_test 2025-11-30 18:45:11.048 UTC client backend[45244] ecpg/pgtypeslib-dt_test LOG: connection ready: setup total=2.127 ms, fork=0.550 ms, authentication=0.124 ms 2025-11-30 18:45:11.051 UTC client backend[45244] ecpg/pgtypeslib-dt_test LOG: disconnection: session time: 0:00:00.004 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.051 UTC client backend[44903] pg_regress/constraints ERROR: incompatible NOT VALID constraint "nn" on relation "notnull_tbl1" 2025-11-30 18:45:11.051 UTC client backend[44903] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-11-30 18:45:11.051 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:11.056 UTC client backend[44903] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1" contains null values 2025-11-30 18:45:11.056 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ALTER a SET NOT NULL; 2025-11-30 18:45:11.063 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "pp1_f1_not_null" of relation "cc2" 2025-11-30 18:45:11.063 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table cc2 alter column f1 drop not null; 2025-11-30 18:45:11.071 UTC client backend[44906] pg_regress/inherit ERROR: cannot drop inherited constraint "pp1_f1_not_null" of relation "cc1" 2025-11-30 18:45:11.071 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table cc1 alter column f1 drop not null; 2025-11-30 18:45:11.080 UTC client backend[44903] pg_regress/constraints ERROR: column "a" in child table "notnull_tbl1_child2" must be marked NOT NULL 2025-11-30 18:45:11.080 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1_child2 INHERIT notnull_tbl1; 2025-11-30 18:45:11.091 UTC client backend[44903] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1" contains null values 2025-11-30 18:45:11.091 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 VALIDATE CONSTRAINT nn; 2025-11-30 18:45:11.103 UTC unrecognized[45253] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.104 UTC client backend[45253] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.104 UTC client backend[45253] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/pgtypeslib-num_test 2025-11-30 18:45:11.106 UTC client backend[44915] pg_regress/updatable_views ERROR: cannot insert into column "cc" of view "uv_iocu_view" 2025-11-30 18:45:11.106 UTC client backend[44915] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-11-30 18:45:11.106 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into uv_iocu_view (aa) values (1) on conflict (aa) do update set cc = 'XXX'; 2025-11-30 18:45:11.109 UTC client backend[45253] ecpg/pgtypeslib-num_test LOG: connection ready: setup total=9.752 ms, fork=2.391 ms, authentication=0.127 ms 2025-11-30 18:45:11.112 UTC client backend[45253] ecpg/pgtypeslib-num_test LOG: disconnection: session time: 0:00:00.010 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.116 UTC client backend[44903] pg_regress/constraints ERROR: constraint "nn_parent" conflicts with NOT VALID constraint on child table "notnull_tbl1" 2025-11-30 18:45:11.116 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 INHERIT notnull_chld0; 2025-11-30 18:45:11.128 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:11.128 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into rw_view1 values ('yyy',2.0,1) on conflict (aa) do update set bb = excluded.cc; 2025-11-30 18:45:11.130 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:11.130 UTC client backend[44915] 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-11-30 18:45:11.132 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:11.132 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into rw_view1 values ('zzz',2.0,1) on conflict (aa) do update set cc = 3.0; 2025-11-30 18:45:11.134 UTC client backend[44903] pg_regress/constraints ERROR: incompatible NOT VALID constraint "nn" on relation "notnull_inhchild" 2025-11-30 18:45:11.134 UTC client backend[44903] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-11-30 18:45:11.134 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_inhchild ADD CONSTRAINT nn1 NOT NULL i; 2025-11-30 18:45:11.134 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-11-30 18:45:11.134 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into rw_view2 (aa,bb) values (1,'xxx') on conflict (aa) do update set bb = excluded.bb; 2025-11-30 18:45:11.138 UTC client backend[44915] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-11-30 18:45:11.138 UTC client backend[44915] pg_regress/updatable_views STATEMENT: insert into rw_view4 (aa,bb) values (1,'yyy') on conflict (aa) do update set bb = excluded.bb; 2025-11-30 18:45:11.141 UTC client backend[44903] pg_regress/constraints ERROR: table "notnull_tbl1" does not exist 2025-11-30 18:45:11.141 UTC client backend[44903] pg_regress/constraints STATEMENT: DROP TABLE notnull_tbl1; 2025-11-30 18:45:11.154 UTC unrecognized[45262] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.155 UTC client backend[45262] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.155 UTC client backend[45262] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/pgtypeslib-nan_test 2025-11-30 18:45:11.156 UTC client backend[45262] ecpg/pgtypeslib-nan_test LOG: connection ready: setup total=2.496 ms, fork=0.933 ms, authentication=0.122 ms 2025-11-30 18:45:11.159 UTC client backend[44903] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1_3" contains null values 2025-11-30 18:45:11.159 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ALTER COLUMN a SET NOT NULL; 2025-11-30 18:45:11.160 UTC client backend[44903] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1_3" contains null values 2025-11-30 18:45:11.160 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1_3 VALIDATE CONSTRAINT nn3; 2025-11-30 18:45:11.162 UTC client backend[45262] ecpg/pgtypeslib-nan_test LOG: disconnection: session time: 0:00:00.008 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.163 UTC client backend[45208] postgres_fdw LOG: disconnection: session time: 0:00:00.274 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:11.166 UTC unrecognized[45265] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.166 UTC client backend[45265] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.166 UTC client backend[45265] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:11.167 UTC client backend[45265] postgres_fdw LOG: connection ready: setup total=1.604 ms, fork=0.324 ms, authentication=0.109 ms 2025-11-30 18:45:11.174 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.174 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.174 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.174 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.175 UTC client backend[44903] pg_regress/constraints ERROR: constraint "nn1" conflicts with NOT VALID constraint on child table "pp_nn_1" 2025-11-30 18:45:11.175 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE pp_nn ATTACH PARTITION pp_nn_1 FOR VALUES IN (NULL,5); 2025-11-30 18:45:11.176 UTC client backend[45265] postgres_fdw LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:11.180 UTC unrecognized[45268] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.181 UTC client backend[45268] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.181 UTC client backend[45268] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:11.182 UTC client backend[45268] postgres_fdw LOG: connection ready: setup total=1.660 ms, fork=0.348 ms, authentication=0.113 ms 2025-11-30 18:45:11.185 UTC unrecognized[45269] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.185 UTC client backend[45269] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.185 UTC client backend[45269] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-array_of_struct 2025-11-30 18:45:11.186 UTC client backend[45269] ecpg/preproc-array_of_struct LOG: connection ready: setup total=2.880 ms, fork=1.460 ms, authentication=0.109 ms 2025-11-30 18:45:11.187 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.187 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.187 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.187 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.187 UTC client backend[44903] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-11-30 18:45:11.187 UTC client backend[44903] pg_regress/constraints DETAIL: The constraint "nn" on column "a" of table "pp_nn_1", marked NOT VALID, is incompatible with a primary key. 2025-11-30 18:45:11.187 UTC client backend[44903] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-11-30 18:45:11.187 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE ONLY pp_nn ADD PRIMARY KEY (a); 2025-11-30 18:45:11.195 UTC client backend[44903] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-11-30 18:45:11.195 UTC client backend[44903] pg_regress/constraints DETAIL: The constraint "nn" on column "a" of table "pp_nn_1", marked NO INHERIT, is incompatible with a primary key. 2025-11-30 18:45:11.195 UTC client backend[44903] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-11-30 18:45:11.195 UTC client backend[44903] pg_regress/constraints STATEMENT: ALTER TABLE ONLY pp_nn ADD PRIMARY KEY (a); 2025-11-30 18:45:11.197 UTC client backend[45269] ecpg/preproc-array_of_struct LOG: disconnection: session time: 0:00:00.012 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.199 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.199 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.199 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.199 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.213 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.213 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.213 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.213 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.222 UTC unrecognized[45274] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.222 UTC client backend[45274] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.222 UTC client backend[45274] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-pointer_to_struct 2025-11-30 18:45:11.223 UTC client backend[45274] ecpg/preproc-pointer_to_struct LOG: connection ready: setup total=3.905 ms, fork=0.784 ms, authentication=0.124 ms 2025-11-30 18:45:11.226 UTC client backend[45274] ecpg/preproc-pointer_to_struct LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.230 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.230 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on conflict out to pivot 12313, during read. 2025-11-30 18:45:11.230 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.230 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: SELECT SUM(balance) FROM accounts; 2025-11-30 18:45:11.240 UTC client backend[44909] pg_regress/triggers ERROR: except 2025-11-30 18:45:11.240 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-11-30 18:45:11.240 UTC client backend[44909] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (1); 2025-11-30 18:45:11.240 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.240 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on conflict out to pivot 12336, during read. 2025-11-30 18:45:11.240 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.240 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: SELECT SUM(balance) FROM accounts; 2025-11-30 18:45:11.246 UTC unrecognized[45279] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.246 UTC client backend[45279] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.246 UTC client backend[45279] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-autoprep 2025-11-30 18:45:11.247 UTC client backend[45279] ecpg/preproc-autoprep LOG: connection ready: setup total=2.182 ms, fork=0.438 ms, authentication=0.149 ms 2025-11-30 18:45:11.251 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.251 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.251 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.251 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.259 UTC client backend[45279] ecpg/preproc-autoprep LOG: disconnection: session time: 0:00:00.013 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.262 UTC unrecognized[45280] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.263 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.263 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.263 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.263 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.263 UTC client backend[45280] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.263 UTC client backend[45280] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-autoprep 2025-11-30 18:45:11.264 UTC client backend[45280] ecpg/preproc-autoprep LOG: connection ready: setup total=3.775 ms, fork=0.566 ms, authentication=0.116 ms 2025-11-30 18:45:11.268 UTC client backend[44915] pg_regress/updatable_views LOG: disconnection: session time: 0:00:02.723 user=postgres database=regression host=[local] 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints ERROR: constraint "no_constraint" for table "constraint_comments_tbl" does not exist 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT no_constraint ON constraint_comments_tbl IS 'yes, the comment'; 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints ERROR: constraint "no_constraint" for domain constraint_comments_dom does not exist 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT no_constraint ON DOMAIN constraint_comments_dom IS 'yes, another comment'; 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints ERROR: relation "no_comments_tbl" does not exist 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON no_comments_tbl IS 'bad comment'; 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints ERROR: type "no_comments_dom" does not exist 2025-11-30 18:45:11.269 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON DOMAIN no_comments_dom IS 'another bad comment'; 2025-11-30 18:45:11.269 UTC client backend[45280] ecpg/preproc-autoprep LOG: disconnection: session time: 0:00:00.008 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.270 UTC client backend[44903] pg_regress/constraints ERROR: must be owner of relation constraint_comments_tbl 2025-11-30 18:45:11.270 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON constraint_comments_tbl IS 'no, the comment'; 2025-11-30 18:45:11.270 UTC client backend[44903] pg_regress/constraints ERROR: must be owner of type constraint_comments_dom 2025-11-30 18:45:11.270 UTC client backend[44903] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON DOMAIN constraint_comments_dom IS 'no, another comment'; 2025-11-30 18:45:11.274 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.274 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.274 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.274 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.279 UTC unrecognized[45285] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.279 UTC client backend[45285] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.279 UTC client backend[45285] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-comment 2025-11-30 18:45:11.280 UTC client backend[45285] ecpg/preproc-comment LOG: connection ready: setup total=2.280 ms, fork=0.788 ms, authentication=0.115 ms 2025-11-30 18:45:11.280 UTC client backend[45285] ecpg/preproc-comment LOG: disconnection: session time: 0:00:00.001 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.282 UTC client backend[44909] pg_regress/triggers ERROR: except 2025-11-30 18:45:11.282 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-11-30 18:45:11.282 UTC client backend[44909] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (1); 2025-11-30 18:45:11.282 UTC client backend[44903] pg_regress/constraints LOG: disconnection: session time: 0:00:02.744 user=postgres database=regression host=[local] 2025-11-30 18:45:11.283 UTC client backend[44909] pg_regress/triggers ERROR: except 2025-11-30 18:45:11.283 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-11-30 18:45:11.283 UTC client backend[44909] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (11); 2025-11-30 18:45:11.287 UTC client backend[44596] pg_regress/postgres_fdw ERROR: "reindex_foreign" is not a table or materialized view 2025-11-30 18:45:11.287 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: REINDEX TABLE reindex_foreign; 2025-11-30 18:45:11.287 UTC client backend[44596] pg_regress/postgres_fdw ERROR: "reindex_foreign" is not a table or materialized view 2025-11-30 18:45:11.287 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: REINDEX TABLE CONCURRENTLY reindex_foreign; 2025-11-30 18:45:11.289 UTC client backend[44909] pg_regress/triggers ERROR: except 2025-11-30 18:45:11.289 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-11-30 18:45:11.289 UTC client backend[44909] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (21); 2025-11-30 18:45:11.290 UTC client backend[44909] pg_regress/triggers ERROR: except 2025-11-30 18:45:11.290 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-11-30 18:45:11.290 UTC client backend[44909] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (30); 2025-11-30 18:45:11.290 UTC client backend[44909] pg_regress/triggers ERROR: except 2025-11-30 18:45:11.290 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-11-30 18:45:11.290 UTC client backend[44909] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (40); 2025-11-30 18:45:11.295 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-11-30 18:45:11.295 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: column "x8" of foreign table "ftx" 2025-11-30 18:45:11.295 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 ftx(x1,x2,x3,x4,x5,x6,x7,x8) WHERE x1 = 1; 2025-11-30 18:45:11.298 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-11-30 18:45:11.298 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: column "x8" of foreign table "ftx" 2025-11-30 18:45:11.298 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT ftx.x1, ft2.c2, ftx.x8 FROM ft1 ftx(x1,x2,x3,x4,x5,x6,x7,x8), ft2 WHERE ftx.x1 = ft2.c1 AND ftx.x1 = 1; 2025-11-30 18:45:11.302 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-11-30 18:45:11.302 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: whole-row reference to foreign table "ftx" 2025-11-30 18:45:11.302 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT ftx.x1, ft2.c2, ftx FROM ft1 ftx(x1,x2,x3,x4,x5,x6,x7,x8), ft2 WHERE ftx.x1 = ft2.c1 AND ftx.x1 = 1; 2025-11-30 18:45:11.302 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.302 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.302 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.302 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.305 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-11-30 18:45:11.305 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: processing expression at position 2 in select list 2025-11-30 18:45:11.305 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT sum(c2), array_agg(c8) FROM ft1 GROUP BY c8; 2025-11-30 18:45:11.309 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-11-30 18:45:11.309 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: column "c8" of foreign table "ft1" 2025-11-30 18:45:11.309 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ANALYZE ft1; 2025-11-30 18:45:11.314 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.314 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on conflict out to pivot 12439, during read. 2025-11-30 18:45:11.314 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.314 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: SELECT SUM(balance) FROM accounts; 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw ERROR: operator does not exist: public.user_enum ~~ unknown at character 92 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw HINT: You might need to add explicit type casts. 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw STATEMENT: DECLARE c1 CURSOR FOR SELECT "C 1", c2, c3, c4, c5, c6, c7, c8 FROM "S 1"."T 1" WHERE ((c8 ~~ 'foo')) LIMIT 1::bigint 2025-11-30 18:45:11.315 UTC client backend[44596] pg_regress/postgres_fdw ERROR: operator does not exist: public.user_enum ~~ unknown 2025-11-30 18:45:11.315 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:11.315 UTC client backend[44596] pg_regress/postgres_fdw HINT: You might need to add explicit type casts. 2025-11-30 18:45:11.315 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: SELECT "C 1", c2, c3, c4, c5, c6, c7, c8 FROM "S 1"."T 1" WHERE ((c8 ~~ 'foo')) LIMIT 1::bigint 2025-11-30 18:45:11.315 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 WHERE c8 LIKE 'foo' LIMIT 1; 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw ERROR: operator does not exist: public.user_enum ~~ unknown at character 92 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw HINT: You might need to add explicit type casts. 2025-11-30 18:45:11.315 UTC client backend[45268] postgres_fdw STATEMENT: DECLARE c1 CURSOR FOR SELECT "C 1", c2, c3, c4, c5, c6, c7, c8 FROM "S 1"."T 1" WHERE ((c8 ~~ 'foo')) LIMIT 1::bigint 2025-11-30 18:45:11.316 UTC client backend[44596] pg_regress/postgres_fdw ERROR: operator does not exist: public.user_enum ~~ unknown 2025-11-30 18:45:11.316 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:11.316 UTC client backend[44596] pg_regress/postgres_fdw HINT: You might need to add explicit type casts. 2025-11-30 18:45:11.316 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: SELECT "C 1", c2, c3, c4, c5, c6, c7, c8 FROM "S 1"."T 1" WHERE ((c8 ~~ 'foo')) LIMIT 1::bigint 2025-11-30 18:45:11.316 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 WHERE c8::text LIKE 'foo' LIMIT 1; 2025-11-30 18:45:11.318 UTC client backend[44596] pg_regress/postgres_fdw ERROR: syntax error at or near "ERROR" at character 1 2025-11-30 18:45:11.318 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ERROR OUT; 2025-11-30 18:45:11.319 UTC client backend[45268] postgres_fdw ERROR: division by zero 2025-11-30 18:45:11.319 UTC client backend[45268] postgres_fdw STATEMENT: FETCH 100 FROM c2 2025-11-30 18:45:11.319 UTC client backend[44596] pg_regress/postgres_fdw ERROR: division by zero 2025-11-30 18:45:11.319 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: SELECT "C 1", c2, c3, c4, c5, c6, c7, c8 FROM "S 1"."T 1" WHERE (((1 / ("C 1" - 1)) > 0)) 2025-11-30 18:45:11.319 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 WHERE 1 / (c1 - 1) > 0; 2025-11-30 18:45:11.328 UTC client backend[45194] isolation/total-cash/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.328 UTC client backend[45194] isolation/total-cash/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.328 UTC client backend[45194] isolation/total-cash/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.328 UTC client backend[45194] isolation/total-cash/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.337 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.337 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.337 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.337 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.348 UTC client backend[45193] isolation/total-cash/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.348 UTC client backend[45193] isolation/total-cash/s1 DETAIL: Reason code: Canceled on conflict out to pivot 12478, during read. 2025-11-30 18:45:11.348 UTC client backend[45193] isolation/total-cash/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.348 UTC client backend[45193] isolation/total-cash/s1 STATEMENT: SELECT SUM(balance) FROM accounts; 2025-11-30 18:45:11.359 UTC client backend[45194] isolation/total-cash/s2 LOG: disconnection: session time: 0:00:00.506 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:11.360 UTC client backend[45193] isolation/total-cash/s1 LOG: disconnection: session time: 0:00:00.510 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:11.361 UTC client backend[45192] isolation/total-cash/control connection LOG: disconnection: session time: 0:00:00.514 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:11.364 UTC unrecognized[45293] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.364 UTC unrecognized[45290] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.365 UTC client backend[45293] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.365 UTC client backend[45293] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/referential-integrity 2025-11-30 18:45:11.365 UTC client backend[45290] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.365 UTC client backend[45290] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-cursor 2025-11-30 18:45:11.366 UTC client backend[45293] isolation/referential-integrity LOG: connection ready: setup total=1.919 ms, fork=0.379 ms, authentication=0.116 ms 2025-11-30 18:45:11.366 UTC client backend[45290] ecpg/preproc-cursor LOG: connection ready: setup total=24.044 ms, fork=22.691 ms, authentication=0.097 ms 2025-11-30 18:45:11.367 UTC unrecognized[45295] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.368 UTC client backend[45295] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.368 UTC client backend[45295] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/referential-integrity 2025-11-30 18:45:11.368 UTC client backend[45295] isolation/referential-integrity LOG: connection ready: setup total=1.643 ms, fork=0.292 ms, authentication=0.101 ms 2025-11-30 18:45:11.369 UTC client backend[44906] 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-11-30 18:45:11.369 UTC client backend[44906] pg_regress/inherit HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-11-30 18:45:11.369 UTC client backend[44906] pg_regress/inherit STATEMENT: ALTER TABLE inh_nn_parent ADD CONSTRAINT nna NOT NULL a; 2025-11-30 18:45:11.369 UTC unrecognized[45294] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.370 UTC client backend[45294] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.370 UTC client backend[45294] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/preproc-cursor 2025-11-30 18:45:11.371 UTC client backend[45294] ecpg/preproc-cursor LOG: connection ready: setup total=4.262 ms, fork=2.878 ms, authentication=0.109 ms 2025-11-30 18:45:11.372 UTC unrecognized[45296] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.373 UTC client backend[45296] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.373 UTC client backend[45296] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/referential-integrity 2025-11-30 18:45:11.374 UTC client backend[45296] isolation/referential-integrity LOG: connection ready: setup total=3.996 ms, fork=2.618 ms, authentication=0.109 ms 2025-11-30 18:45:11.374 UTC client backend[44906] 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-11-30 18:45:11.374 UTC client backend[44906] pg_regress/inherit STATEMENT: ALTER TABLE inh_nn_parent ALTER a SET NOT NULL; 2025-11-30 18:45:11.384 UTC client backend[44906] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "foo" on relation "inh_nn_lvl3" 2025-11-30 18:45:11.384 UTC client backend[44906] pg_regress/inherit HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-11-30 18:45:11.384 UTC client backend[44906] pg_regress/inherit STATEMENT: ALTER TABLE inh_nn_lvl1 ADD PRIMARY KEY (a); 2025-11-30 18:45:11.386 UTC client backend[44909] pg_regress/triggers ERROR: ROW triggers with transition tables are not supported on partitions 2025-11-30 18:45:11.386 UTC client backend[44909] 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-11-30 18:45:11.388 UTC client backend[44909] pg_regress/triggers ERROR: trigger "child_row_trig" prevents table "child" from becoming a partition 2025-11-30 18:45:11.388 UTC client backend[44909] pg_regress/triggers DETAIL: ROW triggers with transition tables are not supported on partitions. 2025-11-30 18:45:11.388 UTC client backend[44909] pg_regress/triggers STATEMENT: alter table parent attach partition child for values in ('AAA'); 2025-11-30 18:45:11.391 UTC client backend[44906] pg_regress/inherit ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:11.391 UTC client backend[44906] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn1 (a int primary key, b int, not null a no inherit); 2025-11-30 18:45:11.393 UTC client backend[44906] pg_regress/inherit ERROR: cannot define not-null constraint with NO INHERIT on column "a" 2025-11-30 18:45:11.393 UTC client backend[44906] pg_regress/inherit DETAIL: The column has an inherited not-null constraint. 2025-11-30 18:45:11.393 UTC client backend[44906] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn2 (a int not null no inherit) INHERITS (inh_nn1); 2025-11-30 18:45:11.404 UTC client backend[45294] ecpg/preproc-cursor LOG: disconnection: session time: 0:00:00.034 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:11.405 UTC client backend[44906] pg_regress/inherit ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:11.405 UTC client backend[44906] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn3 (a int not null, b int, not null a no inherit); 2025-11-30 18:45:11.406 UTC client backend[45290] ecpg/preproc-cursor LOG: disconnection: session time: 0:00:00.041 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.408 UTC client backend[44906] pg_regress/inherit ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-11-30 18:45:11.408 UTC client backend[44906] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn4 (a int not null no inherit, b int, not null a); 2025-11-30 18:45:11.413 UTC client backend[44906] pg_regress/inherit ERROR: column "f1" in child table "inh_child2" must be marked NOT NULL 2025-11-30 18:45:11.413 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_child2 inherit inh_child1; 2025-11-30 18:45:11.417 UTC unrecognized[45301] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.417 UTC client backend[45301] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.417 UTC client backend[45301] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-define 2025-11-30 18:45:11.418 UTC client backend[45301] ecpg/preproc-define LOG: connection ready: setup total=2.142 ms, fork=0.602 ms, authentication=0.121 ms 2025-11-30 18:45:11.422 UTC client backend[45301] ecpg/preproc-define LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.440 UTC unrecognized[45310] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.441 UTC client backend[45310] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.441 UTC client backend[45310] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-strings 2025-11-30 18:45:11.441 UTC client backend[45310] ecpg/preproc-strings LOG: connection ready: setup total=2.225 ms, fork=0.710 ms, authentication=0.115 ms 2025-11-30 18:45:11.442 UTC client backend[45310] ecpg/preproc-strings LOG: disconnection: session time: 0:00:00.002 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.456 UTC unrecognized[45315] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.456 UTC client backend[45315] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.456 UTC client backend[45315] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-type 2025-11-30 18:45:11.457 UTC client backend[45315] ecpg/preproc-type LOG: connection ready: setup total=1.920 ms, fork=0.429 ms, authentication=0.114 ms 2025-11-30 18:45:11.460 UTC client backend[45315] ecpg/preproc-type LOG: disconnection: session time: 0:00:00.004 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.469 UTC unrecognized[45320] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.470 UTC client backend[45320] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.470 UTC client backend[45320] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-variable 2025-11-30 18:45:11.471 UTC client backend[45320] ecpg/preproc-variable LOG: connection ready: setup total=2.191 ms, fork=0.683 ms, authentication=0.116 ms 2025-11-30 18:45:11.475 UTC client backend[45320] ecpg/preproc-variable LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.486 UTC unrecognized[45325] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.486 UTC client backend[45325] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.486 UTC client backend[45325] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-outofscope 2025-11-30 18:45:11.487 UTC client backend[45325] ecpg/preproc-outofscope LOG: connection ready: setup total=2.622 ms, fork=1.049 ms, authentication=0.123 ms 2025-11-30 18:45:11.497 UTC client backend[45325] ecpg/preproc-outofscope LOG: disconnection: session time: 0:00:00.011 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.514 UTC client backend[44906] pg_regress/inherit ERROR: column "a" in child table "inh_child" must be marked NOT NULL 2025-11-30 18:45:11.514 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_child inherit inh_parent; 2025-11-30 18:45:11.516 UTC unrecognized[45330] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.516 UTC client backend[45330] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.516 UTC client backend[45330] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-whenever 2025-11-30 18:45:11.517 UTC client backend[45330] ecpg/preproc-whenever LOG: connection ready: setup total=3.225 ms, fork=1.667 ms, authentication=0.123 ms 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever ERROR: relation "nonexistent" does not exist at character 15 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever STATEMENT: select * from nonexistent 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever ERROR: relation "nonexistent" does not exist at character 15 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever STATEMENT: select * from nonexistent 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever ERROR: relation "nonexistent" does not exist at character 15 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever STATEMENT: select * from nonexistent 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever ERROR: relation "nonexistent" does not exist at character 15 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever STATEMENT: select * from nonexistent 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever ERROR: relation "nonexistent" does not exist at character 15 2025-11-30 18:45:11.520 UTC client backend[45330] ecpg/preproc-whenever STATEMENT: select * from nonexistent 2025-11-30 18:45:11.521 UTC client backend[45330] ecpg/preproc-whenever LOG: disconnection: session time: 0:00:00.004 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.523 UTC client backend[44909] pg_regress/triggers ERROR: ROW triggers with transition tables are not supported on inheritance children 2025-11-30 18:45:11.523 UTC client backend[44909] 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-11-30 18:45:11.525 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_child_a_not_null" conflicts with non-inherited constraint on child table "inh_child" 2025-11-30 18:45:11.525 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_child inherit inh_parent; 2025-11-30 18:45:11.531 UTC unrecognized[45335] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.531 UTC client backend[45335] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.531 UTC client backend[45335] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/preproc-whenever_do_continue 2025-11-30 18:45:11.532 UTC client backend[44909] pg_regress/triggers ERROR: trigger "child_row_trig" prevents table "child" from becoming an inheritance child 2025-11-30 18:45:11.532 UTC client backend[44909] pg_regress/triggers DETAIL: ROW triggers with transition tables are not supported in inheritance hierarchies. 2025-11-30 18:45:11.532 UTC client backend[44909] pg_regress/triggers STATEMENT: alter table child inherit parent; 2025-11-30 18:45:11.532 UTC client backend[45335] ecpg/preproc-whenever_do_continue LOG: connection ready: setup total=3.494 ms, fork=1.930 ms, authentication=0.126 ms 2025-11-30 18:45:11.539 UTC client backend[45335] ecpg/preproc-whenever_do_continue LOG: unexpected EOF on client connection with an open transaction 2025-11-30 18:45:11.539 UTC client backend[45335] ecpg/preproc-whenever_do_continue LOG: disconnection: session time: 0:00:00.008 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.547 UTC unrecognized[45340] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.548 UTC client backend[45340] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.548 UTC client backend[45340] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-array 2025-11-30 18:45:11.549 UTC client backend[45340] ecpg/sql-array LOG: connection ready: setup total=1.963 ms, fork=0.490 ms, authentication=0.117 ms 2025-11-30 18:45:11.554 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.554 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.554 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.554 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.563 UTC client backend[45340] ecpg/sql-array LOG: disconnection: session time: 0:00:00.015 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.576 UTC unrecognized[45345] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.576 UTC client backend[45345] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.576 UTC client backend[45345] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-binary 2025-11-30 18:45:11.577 UTC client backend[45345] ecpg/sql-binary LOG: connection ready: setup total=2.790 ms, fork=1.203 ms, authentication=0.120 ms 2025-11-30 18:45:11.582 UTC client backend[45345] ecpg/sql-binary LOG: disconnection: session time: 0:00:00.006 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.590 UTC client backend[44950] pg_regress/test_integerset LOG: disconnection: session time: 0:00:02.725 user=postgres database=regression_test_integerset host=[local] 2025-11-30 18:45:11.600 UTC unrecognized[45351] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.602 UTC client backend[45351] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.602 UTC client backend[45351] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-bytea 2025-11-30 18:45:11.603 UTC client backend[45351] ecpg/sql-bytea LOG: connection ready: setup total=3.962 ms, fork=1.163 ms, authentication=0.129 ms 2025-11-30 18:45:11.604 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.604 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.604 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.604 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.613 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.613 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.613 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.613 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.613 UTC client backend[45351] ecpg/sql-bytea LOG: disconnection: session time: 0:00:00.013 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.624 UTC unrecognized[45356] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.624 UTC client backend[45356] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.624 UTC client backend[45356] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-code100 2025-11-30 18:45:11.625 UTC client backend[44909] pg_regress/triggers ERROR: transition tables cannot be specified for triggers with more than one event 2025-11-30 18:45:11.625 UTC client backend[44909] 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-11-30 18:45:11.625 UTC client backend[44909] pg_regress/triggers ERROR: transition tables cannot be specified for triggers with column lists 2025-11-30 18:45:11.625 UTC client backend[44909] 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-11-30 18:45:11.625 UTC client backend[45356] ecpg/sql-code100 LOG: connection ready: setup total=1.933 ms, fork=0.412 ms, authentication=0.119 ms 2025-11-30 18:45:11.630 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.630 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.630 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.630 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.633 UTC client backend[44906] pg_regress/inherit ERROR: column "f1" of relation "inh_nn2" contains null values 2025-11-30 18:45:11.633 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_not_null inherit; 2025-11-30 18:45:11.634 UTC client backend[44909] pg_regress/triggers ERROR: transition table "new_table" cannot be referenced in a persistent object 2025-11-30 18:45:11.634 UTC client backend[44909] 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-11-30 18:45:11.634 UTC client backend[44909] pg_regress/triggers STATEMENT: insert into my_table values (42); 2025-11-30 18:45:11.641 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.641 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.641 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.641 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.643 UTC client backend[45356] ecpg/sql-code100 LOG: disconnection: session time: 0:00:00.018 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.652 UTC client backend[44906] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "nn3_f1" on relation "inh_nn3" 2025-11-30 18:45:11.652 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_not_null inherit; 2025-11-30 18:45:11.653 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.653 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.653 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.653 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.654 UTC unrecognized[45361] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.654 UTC client backend[45361] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.654 UTC client backend[45361] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-copystdout 2025-11-30 18:45:11.655 UTC client backend[45361] ecpg/sql-copystdout LOG: connection ready: setup total=2.733 ms, fork=1.243 ms, authentication=0.120 ms 2025-11-30 18:45:11.659 UTC client backend[45361] ecpg/sql-copystdout LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.664 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_nn1_f1_check" of relation "inh_nn1" is not a not-null constraint 2025-11-30 18:45:11.664 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_check inherit; 2025-11-30 18:45:11.665 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_nn1_pkey" of relation "inh_nn1" is not a not-null constraint 2025-11-30 18:45:11.665 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_pkey inherit; 2025-11-30 18:45:11.665 UTC client backend[44906] pg_regress/inherit ERROR: constraint "inh_nn1_f1_fkey" of relation "inh_nn1" is not a not-null constraint 2025-11-30 18:45:11.665 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_fkey inherit; 2025-11-30 18:45:11.665 UTC client backend[44906] pg_regress/inherit ERROR: constraint "foo" of relation "inh_nn1" does not exist 2025-11-30 18:45:11.665 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint foo inherit; 2025-11-30 18:45:11.667 UTC client backend[44906] pg_regress/inherit ERROR: cannot alter inherited constraint "inh_nn1_f2_not_null" on relation "inh_nn2" 2025-11-30 18:45:11.667 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_nn2 alter constraint inh_nn1_f2_not_null no inherit; 2025-11-30 18:45:11.668 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.668 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.668 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.668 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.668 UTC unrecognized[45366] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.668 UTC client backend[45366] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.668 UTC client backend[45366] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-createtableas 2025-11-30 18:45:11.672 UTC client backend[45366] ecpg/sql-createtableas LOG: connection ready: setup total=4.447 ms, fork=0.486 ms, authentication=0.114 ms 2025-11-30 18:45:11.676 UTC client backend[44906] pg_regress/inherit ERROR: must be owner of table inh_child 2025-11-30 18:45:11.676 UTC client backend[44906] pg_regress/inherit STATEMENT: alter table inh_parent alter a drop not null; 2025-11-30 18:45:11.679 UTC client backend[45366] ecpg/sql-createtableas LOG: disconnection: session time: 0:00:00.011 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.680 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.680 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.680 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.680 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.681 UTC client backend[44906] pg_regress/inherit ERROR: cannot inherit from temporary relation "inh_temp_parent" 2025-11-30 18:45:11.681 UTC client backend[44906] pg_regress/inherit STATEMENT: create table inh_perm_child () inherits (inh_temp_parent); 2025-11-30 18:45:11.687 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.687 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.687 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.687 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.692 UTC unrecognized[45371] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.692 UTC client backend[45371] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.692 UTC client backend[45371] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-define 2025-11-30 18:45:11.693 UTC client backend[45371] ecpg/sql-define LOG: connection ready: setup total=2.565 ms, fork=1.094 ms, authentication=0.127 ms 2025-11-30 18:45:11.697 UTC client backend[45371] ecpg/sql-define LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.699 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.699 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.699 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.699 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.708 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.708 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.708 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.708 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.708 UTC unrecognized[45376] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.709 UTC client backend[45376] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.709 UTC client backend[45376] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-desc 2025-11-30 18:45:11.710 UTC client backend[45376] ecpg/sql-desc LOG: connection ready: setup total=2.612 ms, fork=1.138 ms, authentication=0.116 ms 2025-11-30 18:45:11.717 UTC client backend[45376] ecpg/sql-desc LOG: disconnection: session time: 0:00:00.009 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.721 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.721 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.721 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.721 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.725 UTC unrecognized[45381] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.725 UTC client backend[45381] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.725 UTC client backend[45381] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-sqlda 2025-11-30 18:45:11.726 UTC client backend[45381] ecpg/sql-sqlda LOG: connection ready: setup total=1.829 ms, fork=0.374 ms, authentication=0.114 ms 2025-11-30 18:45:11.731 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.731 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.731 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.731 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.733 UTC unrecognized[45382] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.733 UTC client backend[45382] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.733 UTC client backend[45382] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-sqlda 2025-11-30 18:45:11.734 UTC client backend[45382] ecpg/sql-sqlda LOG: connection ready: setup total=1.816 ms, fork=0.399 ms, authentication=0.121 ms 2025-11-30 18:45:11.736 UTC client backend[44909] pg_regress/triggers ERROR: trigger "my_trig" for relation "my_table" already exists 2025-11-30 18:45:11.736 UTC client backend[44909] pg_regress/triggers STATEMENT: create trigger my_trig before insert on my_table for each row execute procedure funcB(); 2025-11-30 18:45:11.737 UTC client backend[45382] ecpg/sql-sqlda LOG: disconnection: session time: 0:00:00.004 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.738 UTC client backend[45381] ecpg/sql-sqlda LOG: disconnection: session time: 0:00:00.013 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.742 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.742 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.742 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.742 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: INSERT INTO b VALUES (1); 2025-11-30 18:45:11.748 UTC unrecognized[45387] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.748 UTC client backend[45387] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.748 UTC client backend[45387] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-describe 2025-11-30 18:45:11.749 UTC client backend[45387] ecpg/sql-describe LOG: connection ready: setup total=2.006 ms, fork=0.432 ms, authentication=0.123 ms 2025-11-30 18:45:11.750 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.750 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.750 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.750 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.758 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.758 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.758 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.758 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.760 UTC client backend[45387] ecpg/sql-describe LOG: disconnection: session time: 0:00:00.012 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.771 UTC unrecognized[45392] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.771 UTC client backend[45392] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.771 UTC client backend[45392] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-dynalloc 2025-11-30 18:45:11.771 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.771 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.771 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.771 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.772 UTC client backend[45392] ecpg/sql-dynalloc LOG: connection ready: setup total=2.008 ms, fork=0.464 ms, authentication=0.119 ms 2025-11-30 18:45:11.772 UTC client backend[44909] pg_regress/triggers ERROR: trigger "my_trig" for relation "parted_trig_1" is an internal or a child trigger 2025-11-30 18:45:11.772 UTC client backend[44909] pg_regress/triggers STATEMENT: create or replace trigger my_trig after insert on parted_trig_1 for each row execute procedure funcB(); 2025-11-30 18:45:11.779 UTC client backend[44909] pg_regress/triggers ERROR: trigger "my_trig" for relation "parted_trig_1" already exists 2025-11-30 18:45:11.779 UTC client backend[44909] pg_regress/triggers STATEMENT: create trigger my_trig after insert on parted_trig for each row execute procedure funcB(); 2025-11-30 18:45:11.779 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.779 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.779 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.779 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.779 UTC client backend[45392] ecpg/sql-dynalloc LOG: disconnection: session time: 0:00:00.008 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.786 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.786 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.786 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.786 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.789 UTC unrecognized[45397] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.789 UTC client backend[45397] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.789 UTC client backend[45397] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-dynalloc2 2025-11-30 18:45:11.790 UTC client backend[45397] ecpg/sql-dynalloc2 LOG: connection ready: setup total=2.073 ms, fork=0.475 ms, authentication=0.121 ms 2025-11-30 18:45:11.794 UTC client backend[45397] ecpg/sql-dynalloc2 LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.796 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.796 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.796 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.796 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.804 UTC unrecognized[45402] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.804 UTC client backend[45402] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.804 UTC client backend[45402] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-dyntest 2025-11-30 18:45:11.805 UTC client backend[45402] ecpg/sql-dyntest LOG: connection ready: setup total=2.190 ms, fork=0.613 ms, authentication=0.126 ms 2025-11-30 18:45:11.805 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.805 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.805 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.805 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.810 UTC client backend[45402] ecpg/sql-dyntest LOG: unexpected EOF on client connection with an open transaction 2025-11-30 18:45:11.810 UTC client backend[45402] ecpg/sql-dyntest LOG: disconnection: session time: 0:00:00.006 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.815 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.815 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.815 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.815 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.818 UTC unrecognized[45407] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.819 UTC client backend[45407] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.819 UTC client backend[45407] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-execute 2025-11-30 18:45:11.820 UTC client backend[45407] ecpg/sql-execute LOG: connection ready: setup total=2.005 ms, fork=0.444 ms, authentication=0.125 ms 2025-11-30 18:45:11.827 UTC client backend[45407] ecpg/sql-execute LOG: disconnection: session time: 0:00:00.008 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.828 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.828 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.828 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.828 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.837 UTC unrecognized[45412] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.837 UTC client backend[45412] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.837 UTC client backend[45412] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-fetch 2025-11-30 18:45:11.837 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.837 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.837 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.837 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: INSERT INTO b VALUES (1); 2025-11-30 18:45:11.840 UTC client backend[45412] ecpg/sql-fetch LOG: connection ready: setup total=3.786 ms, fork=0.519 ms, authentication=0.137 ms 2025-11-30 18:45:11.845 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.845 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.845 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.845 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: DELETE FROM a WHERE i = 1; 2025-11-30 18:45:11.848 UTC client backend[45412] ecpg/sql-fetch LOG: disconnection: session time: 0:00:00.011 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.856 UTC unrecognized[45417] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.856 UTC client backend[45417] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.856 UTC client backend[45417] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-func 2025-11-30 18:45:11.857 UTC client backend[45417] ecpg/sql-func LOG: connection ready: setup total=1.998 ms, fork=0.404 ms, authentication=0.140 ms 2025-11-30 18:45:11.864 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.864 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.864 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.864 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.868 UTC client backend[45417] ecpg/sql-func LOG: disconnection: session time: 0:00:00.012 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.872 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.872 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.872 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.872 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.876 UTC client backend[44909] pg_regress/triggers ERROR: BOOM! 2025-11-30 18:45:11.876 UTC client backend[44909] pg_regress/triggers CONTEXT: PL/pgSQL function convslot_trig4() line 1 at RAISE 2025-11-30 18:45:11.876 UTC client backend[44909] pg_regress/triggers STATEMENT: update convslot_test_parent set val = 3; 2025-11-30 18:45:11.880 UTC unrecognized[45422] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.880 UTC client backend[45422] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.880 UTC client backend[45422] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-indicators 2025-11-30 18:45:11.881 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.881 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.881 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.881 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.881 UTC client backend[45422] ecpg/sql-indicators LOG: connection ready: setup total=1.992 ms, fork=0.418 ms, authentication=0.132 ms 2025-11-30 18:45:11.891 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.891 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.891 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.891 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.896 UTC client backend[45422] ecpg/sql-indicators LOG: disconnection: session time: 0:00:00.016 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.900 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.900 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.900 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.900 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: INSERT INTO b VALUES (1); 2025-11-30 18:45:11.906 UTC unrecognized[45427] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.906 UTC client backend[45427] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.906 UTC client backend[45427] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-oldexec 2025-11-30 18:45:11.907 UTC client backend[45427] ecpg/sql-oldexec LOG: connection ready: setup total=1.889 ms, fork=0.406 ms, authentication=0.114 ms 2025-11-30 18:45:11.910 UTC client backend[45296] isolation/referential-integrity/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.910 UTC client backend[45296] isolation/referential-integrity/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.910 UTC client backend[45296] isolation/referential-integrity/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.910 UTC client backend[45296] isolation/referential-integrity/s2 STATEMENT: COMMIT; 2025-11-30 18:45:11.913 UTC client backend[45427] ecpg/sql-oldexec LOG: disconnection: session time: 0:00:00.007 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.914 UTC client backend[44909] pg_regress/triggers ERROR: syntax error at or near "only" at character 20 2025-11-30 18:45:11.914 UTC client backend[44909] pg_regress/triggers STATEMENT: alter trigger a on only grandparent rename to b; 2025-11-30 18:45:11.915 UTC client backend[44909] pg_regress/triggers ERROR: cannot rename trigger "b" on table "middle" 2025-11-30 18:45:11.915 UTC client backend[44909] pg_regress/triggers HINT: Rename the trigger on the partitioned table "grandparent" instead. 2025-11-30 18:45:11.915 UTC client backend[44909] pg_regress/triggers STATEMENT: alter trigger b on middle rename to c; 2025-11-30 18:45:11.917 UTC client backend[44909] pg_regress/triggers ERROR: trigger "c" for relation "middle" already exists 2025-11-30 18:45:11.917 UTC client backend[44909] pg_regress/triggers STATEMENT: alter trigger b on grandparent rename to c; 2025-11-30 18:45:11.922 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.922 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:11.922 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.922 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: COMMIT; 2025-11-30 18:45:11.927 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check" 2025-11-30 18:45:11.927 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (0, 1, 10). 2025-11-30 18:45:11.927 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', '10'); 2025-11-30 18:45:11.928 UTC unrecognized[45432] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.928 UTC client backend[45432] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.928 UTC client backend[45432] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-quote 2025-11-30 18:45:11.929 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check" 2025-11-30 18:45:11.929 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (10, 1, 10). 2025-11-30 18:45:11.929 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', '10'); 2025-11-30 18:45:11.929 UTC client backend[45432] ecpg/sql-quote LOG: connection ready: setup total=2.365 ms, fork=0.828 ms, authentication=0.120 ms 2025-11-30 18:45:11.929 UTC client backend[45295] isolation/referential-integrity/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.929 UTC client backend[45295] isolation/referential-integrity/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.929 UTC client backend[45295] isolation/referential-integrity/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.929 UTC client backend[45295] isolation/referential-integrity/s1 STATEMENT: INSERT INTO b VALUES (1); 2025-11-30 18:45:11.932 UTC client backend[45432] ecpg/sql-quote WARNING: nonstandard use of \\ in a string literal at character 37 2025-11-30 18:45:11.932 UTC client backend[45432] ecpg/sql-quote HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:11.933 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check" 2025-11-30 18:45:11.933 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (20, 1, 10). 2025-11-30 18:45:11.933 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', '10'); 2025-11-30 18:45:11.934 UTC client backend[44906] pg_regress/inherit ERROR: null value in column "data" of relation "errtst_child_fastdef" violates not-null constraint 2025-11-30 18:45:11.934 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (0, 1, null). 2025-11-30 18:45:11.934 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', NULL); 2025-11-30 18:45:11.934 UTC client backend[44906] pg_regress/inherit ERROR: null value in column "data" of relation "errtst_child_plaindef" violates not-null constraint 2025-11-30 18:45:11.934 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (10, 1, null). 2025-11-30 18:45:11.934 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', NULL); 2025-11-30 18:45:11.935 UTC client backend[45432] ecpg/sql-quote LOG: disconnection: session time: 0:00:00.007 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.935 UTC client backend[44906] pg_regress/inherit ERROR: null value in column "data" of relation "errtst_child_reorder" violates not-null constraint 2025-11-30 18:45:11.935 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (20, 1, null). 2025-11-30 18:45:11.935 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', NULL); 2025-11-30 18:45:11.935 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "shdata_small" 2025-11-30 18:45:11.935 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (0, 5, 5). 2025-11-30 18:45:11.935 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '5', '5'); 2025-11-30 18:45:11.936 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "shdata_small" 2025-11-30 18:45:11.936 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (10, 5, 5). 2025-11-30 18:45:11.936 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '5', '5'); 2025-11-30 18:45:11.937 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "shdata_small" 2025-11-30 18:45:11.937 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (20, 5, 5). 2025-11-30 18:45:11.937 UTC client backend[44906] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '5', '5'); 2025-11-30 18:45:11.941 UTC client backend[45293] isolation/referential-integrity/control connection LOG: disconnection: session time: 0:00:00.576 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:11.941 UTC client backend[45296] isolation/referential-integrity/s2 LOG: disconnection: session time: 0:00:00.568 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:11.941 UTC client backend[45295] isolation/referential-integrity/s1 LOG: disconnection: session time: 0:00:00.573 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:11.943 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check" 2025-11-30 18:45:11.943 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (0, 1, 15). 2025-11-30 18:45:11.943 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET data = data + 10 WHERE partid = 0; 2025-11-30 18:45:11.944 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check" 2025-11-30 18:45:11.944 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (10, 1, 15). 2025-11-30 18:45:11.944 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET data = data + 10 WHERE partid = 10; 2025-11-30 18:45:11.945 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check" 2025-11-30 18:45:11.945 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (20, 1, 15). 2025-11-30 18:45:11.945 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET data = data + 10 WHERE partid = 20; 2025-11-30 18:45:11.945 UTC unrecognized[45440] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.946 UTC client backend[45440] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.946 UTC client backend[45440] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/ri-trigger 2025-11-30 18:45:11.946 UTC unrecognized[45439] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.946 UTC client backend[45439] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.946 UTC client backend[45439] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-show 2025-11-30 18:45:11.947 UTC client backend[45440] isolation/ri-trigger LOG: connection ready: setup total=1.796 ms, fork=0.305 ms, authentication=0.114 ms 2025-11-30 18:45:11.947 UTC client backend[45439] ecpg/sql-show LOG: connection ready: setup total=2.432 ms, fork=1.088 ms, authentication=0.098 ms 2025-11-30 18:45:11.948 UTC client backend[45439] ecpg/sql-show LOG: disconnection: session time: 0:00:00.002 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.948 UTC unrecognized[45441] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.948 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates partition constraint 2025-11-30 18:45:11.948 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (10, 1, 5). 2025-11-30 18:45:11.948 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_child_fastdef SET partid = partid + 10 WHERE partid = 0; 2025-11-30 18:45:11.949 UTC client backend[45441] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.949 UTC client backend[45441] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/ri-trigger 2025-11-30 18:45:11.949 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates partition constraint 2025-11-30 18:45:11.949 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (20, 1, 5). 2025-11-30 18:45:11.949 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_child_plaindef SET partid = partid + 10 WHERE partid = 10; 2025-11-30 18:45:11.950 UTC client backend[45441] isolation/ri-trigger LOG: connection ready: setup total=2.005 ms, fork=0.664 ms, authentication=0.099 ms 2025-11-30 18:45:11.950 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates partition constraint 2025-11-30 18:45:11.950 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (5, 1, 30). 2025-11-30 18:45:11.950 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_child_reorder SET partid = partid + 10 WHERE partid = 20; 2025-11-30 18:45:11.952 UTC unrecognized[45445] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.952 UTC client backend[45445] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.952 UTC client backend[45445] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/ri-trigger 2025-11-30 18:45:11.953 UTC client backend[45445] isolation/ri-trigger LOG: connection ready: setup total=1.865 ms, fork=0.521 ms, authentication=0.104 ms 2025-11-30 18:45:11.955 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check" 2025-11-30 18:45:11.955 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (10, 1, 15). 2025-11-30 18:45:11.955 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 10, data = data + 10 WHERE partid = 0; 2025-11-30 18:45:11.956 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check" 2025-11-30 18:45:11.956 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (20, 1, 15). 2025-11-30 18:45:11.956 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 20, data = data + 10 WHERE partid = 10; 2025-11-30 18:45:11.956 UTC unrecognized[45447] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.956 UTC client backend[45447] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.957 UTC client backend[45447] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-sqljson 2025-11-30 18:45:11.957 UTC client backend[44906] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check" 2025-11-30 18:45:11.957 UTC client backend[44906] pg_regress/inherit DETAIL: Failing row contains (0, 1, 15). 2025-11-30 18:45:11.957 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 0, data = data + 10 WHERE partid = 20; 2025-11-30 18:45:11.957 UTC client backend[45447] ecpg/sql-sqljson LOG: connection ready: setup total=1.785 ms, fork=0.371 ms, authentication=0.108 ms 2025-11-30 18:45:11.957 UTC client backend[44906] pg_regress/inherit ERROR: no partition of relation "errtst_parent" found for row 2025-11-30 18:45:11.957 UTC client backend[44906] pg_regress/inherit DETAIL: Partition key of the failing row contains (partid) = (30). 2025-11-30 18:45:11.957 UTC client backend[44906] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 30, data = data + 10 WHERE partid = 20; 2025-11-30 18:45:11.960 UTC client backend[45268] postgres_fdw LOG: disconnection: session time: 0:00:00.779 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:11.961 UTC client backend[45447] ecpg/sql-sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:11.961 UTC client backend[45447] ecpg/sql-sqljson STATEMENT: select json_object ( 1 : 1 , '1' : null with unique ) 2025-11-30 18:45:11.961 UTC client backend[45447] ecpg/sql-sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 30 2025-11-30 18:45:11.961 UTC client backend[45447] ecpg/sql-sqljson STATEMENT: select json ( '{ "a" : 1 } ' format json encoding UTF8 ) 2025-11-30 18:45:11.961 UTC client backend[45447] ecpg/sql-sqljson ERROR: cannot use non-string types with WITH UNIQUE KEYS clause at character 8 2025-11-30 18:45:11.961 UTC client backend[45447] ecpg/sql-sqljson STATEMENT: select json ( ' 1 ' :: json with unique keys ) into json 2025-11-30 18:45:11.962 UTC client backend[45447] ecpg/sql-sqljson ERROR: duplicate JSON object key value 2025-11-30 18:45:11.962 UTC client backend[45447] ecpg/sql-sqljson STATEMENT: select json ( '{"a": 1, "a": 2}' with unique keys ) 2025-11-30 18:45:11.962 UTC client backend[45447] ecpg/sql-sqljson ERROR: cannot use type jsonb in RETURNING clause of JSON_SERIALIZE() 2025-11-30 18:45:11.962 UTC client backend[45447] ecpg/sql-sqljson HINT: Try returning a string type or bytea. 2025-11-30 18:45:11.962 UTC client backend[45447] ecpg/sql-sqljson STATEMENT: select json_serialize ( '{ "a" : 1 } ' returning jsonb ) 2025-11-30 18:45:11.963 UTC client backend[45447] ecpg/sql-sqljson LOG: disconnection: session time: 0:00:00.006 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.964 UTC unrecognized[45448] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.964 UTC client backend[45448] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.964 UTC client backend[45448] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:11.965 UTC client backend[45448] postgres_fdw LOG: connection ready: setup total=2.830 ms, fork=1.607 ms, authentication=0.105 ms 2025-11-30 18:45:11.971 UTC client backend[45445] isolation/ri-trigger/s2 ERROR: child row exists 2025-11-30 18:45:11.971 UTC client backend[45445] isolation/ri-trigger/s2 CONTEXT: PL/pgSQL function ri_parent() line 5 at RAISE 2025-11-30 18:45:11.971 UTC client backend[45445] isolation/ri-trigger/s2 STATEMENT: DELETE FROM parent WHERE parent_id = 0; 2025-11-30 18:45:11.975 UTC unrecognized[45453] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.975 UTC client backend[45453] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.975 UTC client backend[45453] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-sqljson_jsontable 2025-11-30 18:45:11.976 UTC client backend[45453] ecpg/sql-sqljson_jsontable LOG: connection ready: setup total=2.839 ms, fork=1.336 ms, authentication=0.118 ms 2025-11-30 18:45:11.977 UTC client backend[45453] ecpg/sql-sqljson_jsontable LOG: disconnection: session time: 0:00:00.002 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.987 UTC client backend[45445] isolation/ri-trigger/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:11.987 UTC client backend[45445] isolation/ri-trigger/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:11.987 UTC client backend[45445] isolation/ri-trigger/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:11.987 UTC client backend[45445] isolation/ri-trigger/s2 STATEMENT: DELETE FROM parent WHERE parent_id = 0; 2025-11-30 18:45:11.989 UTC unrecognized[45458] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:11.989 UTC client backend[44909] pg_regress/triggers ERROR: division by zero 2025-11-30 18:45:11.989 UTC client backend[44909] pg_regress/triggers CONTEXT: SQL statement "SELECT 1 / 0" PL/pgSQL function whoami() line 4 at PERFORM 2025-11-30 18:45:11.989 UTC client backend[44909] pg_regress/triggers STATEMENT: commit; 2025-11-30 18:45:11.989 UTC client backend[45458] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:11.989 UTC client backend[45458] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-insupd 2025-11-30 18:45:11.990 UTC client backend[45458] ecpg/sql-insupd LOG: connection ready: setup total=1.967 ms, fork=0.441 ms, authentication=0.121 ms 2025-11-30 18:45:11.993 UTC client backend[44909] pg_regress/triggers LOG: disconnection: session time: 0:00:03.457 user=postgres database=regression host=[local] 2025-11-30 18:45:11.995 UTC client backend[45458] ecpg/sql-insupd LOG: disconnection: session time: 0:00:00.005 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:11.996 UTC client backend[44906] pg_regress/inherit LOG: disconnection: session time: 0:00:03.455 user=postgres database=regression host=[local] 2025-11-30 18:45:12.002 UTC unrecognized[45468] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.003 UTC client backend[45468] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.003 UTC client backend[45468] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-parser 2025-11-30 18:45:12.003 UTC client backend[45468] ecpg/sql-parser LOG: connection ready: setup total=1.932 ms, fork=0.335 ms, authentication=0.115 ms 2025-11-30 18:45:12.006 UTC client backend[45445] isolation/ri-trigger/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.006 UTC client backend[45445] isolation/ri-trigger/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.006 UTC client backend[45445] isolation/ri-trigger/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.006 UTC client backend[45445] isolation/ri-trigger/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.012 UTC client backend[45468] ecpg/sql-parser LOG: disconnection: session time: 0:00:00.009 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.016 UTC client backend[45448] postgres_fdw LOG: disconnection: session time: 0:00:00.052 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:12.017 UTC unrecognized[45485] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.017 UTC client backend[45485] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.017 UTC client backend[45485] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sanity_check 2025-11-30 18:45:12.018 UTC client backend[45485] pg_regress/sanity_check LOG: connection ready: setup total=1.954 ms, fork=0.448 ms, authentication=0.123 ms 2025-11-30 18:45:12.019 UTC unrecognized[45486] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.019 UTC client backend[45486] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.019 UTC client backend[45486] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:12.019 UTC unrecognized[45487] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.020 UTC client backend[45487] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.020 UTC client backend[45487] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-prepareas 2025-11-30 18:45:12.020 UTC client backend[45486] postgres_fdw LOG: connection ready: setup total=1.590 ms, fork=0.328 ms, authentication=0.112 ms 2025-11-30 18:45:12.021 UTC client backend[45487] ecpg/sql-prepareas LOG: connection ready: setup total=1.682 ms, fork=0.329 ms, authentication=0.096 ms 2025-11-30 18:45:12.021 UTC client backend[45441] isolation/ri-trigger/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.021 UTC client backend[45441] isolation/ri-trigger/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.021 UTC client backend[45441] isolation/ri-trigger/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.021 UTC client backend[45441] isolation/ri-trigger/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.029 UTC client backend[45487] ecpg/sql-prepareas LOG: disconnection: session time: 0:00:00.009 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.033 UTC client backend[45486] postgres_fdw ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-11-30 18:45:12.033 UTC client backend[45486] postgres_fdw DETAIL: Key ("C 1")=(11) already exists. 2025-11-30 18:45:12.033 UTC client backend[45486] postgres_fdw STATEMENT: INSERT INTO "S 1"."T 1"("C 1", c2, c3, c4, c5, c6, c7, c8) VALUES ($1, $2, $3, $4, $5, $6, $7, $8) 2025-11-30 18:45:12.033 UTC client backend[44596] pg_regress/postgres_fdw ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-11-30 18:45:12.033 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Key ("C 1")=(11) already exists. 2025-11-30 18:45:12.033 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: INSERT INTO "S 1"."T 1"("C 1", c2, c3, c4, c5, c6, c7, c8) VALUES ($1, $2, $3, $4, $5, $6, $7, $8) 2025-11-30 18:45:12.033 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(11, 12); 2025-11-30 18:45:12.035 UTC client backend[44596] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:12.035 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(11, 12) ON CONFLICT (c1, c2) DO NOTHING; 2025-11-30 18:45:12.035 UTC client backend[44596] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:12.035 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(11, 12) ON CONFLICT (c1, c2) DO UPDATE SET c3 = 'ffg'; 2025-11-30 18:45:12.036 UTC unrecognized[45492] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.036 UTC client backend[45492] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.036 UTC client backend[45492] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-declare 2025-11-30 18:45:12.036 UTC client backend[45445] isolation/ri-trigger/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.036 UTC client backend[45445] isolation/ri-trigger/s2 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:12.036 UTC client backend[45445] isolation/ri-trigger/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.036 UTC client backend[45445] isolation/ri-trigger/s2 STATEMENT: DELETE FROM parent WHERE parent_id = 0; 2025-11-30 18:45:12.036 UTC client backend[45486] postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.036 UTC client backend[45486] postgres_fdw DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-11-30 18:45:12.036 UTC client backend[45486] postgres_fdw STATEMENT: INSERT INTO "S 1"."T 1"("C 1", c2, c3, c4, c5, c6, c7, c8) VALUES ($1, $2, $3, $4, $5, $6, $7, $8) 2025-11-30 18:45:12.036 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.036 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-11-30 18:45:12.036 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: INSERT INTO "S 1"."T 1"("C 1", c2, c3, c4, c5, c6, c7, c8) VALUES ($1, $2, $3, $4, $5, $6, $7, $8) 2025-11-30 18:45:12.036 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(1111, -2); 2025-11-30 18:45:12.038 UTC client backend[45486] postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.038 UTC client backend[45486] postgres_fdw DETAIL: Failing row contains (1, -1, 00001_trig_update, 1970-01-02 08:00:00+00, 1970-01-02 00:00:00, 1, 1 , foo). 2025-11-30 18:45:12.038 UTC client backend[45486] postgres_fdw STATEMENT: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-11-30 18:45:12.038 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.038 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (1, -1, 00001_trig_update, 1970-01-02 08:00:00+00, 1970-01-02 00:00:00, 1, 1 , foo). 2025-11-30 18:45:12.038 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-11-30 18:45:12.038 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: UPDATE ft1 SET c2 = -c2 WHERE c1 = 1; 2025-11-30 18:45:12.040 UTC client backend[45492] ecpg/sql-declare LOG: connection ready: setup total=4.958 ms, fork=0.422 ms, authentication=0.102 ms 2025-11-30 18:45:12.041 UTC unrecognized[45493] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.041 UTC client backend[45493] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.041 UTC client backend[45493] [unknown] LOG: connection authorized: user=postgres database=ecpg2_regression application_name=ecpg/sql-declare 2025-11-30 18:45:12.045 UTC client backend[45493] ecpg/sql-declare LOG: connection ready: setup total=4.866 ms, fork=0.412 ms, authentication=0.102 ms 2025-11-30 18:45:12.052 UTC client backend[45445] isolation/ri-trigger/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.052 UTC client backend[45445] isolation/ri-trigger/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.052 UTC client backend[45445] isolation/ri-trigger/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.052 UTC client backend[45445] isolation/ri-trigger/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.053 UTC client backend[45493] ecpg/sql-declare LOG: disconnection: session time: 0:00:00.012 user=postgres database=ecpg2_regression host=[local] 2025-11-30 18:45:12.054 UTC client backend[45492] ecpg/sql-declare LOG: disconnection: session time: 0:00:00.018 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.062 UTC unrecognized[45498] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.063 UTC client backend[45498] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.063 UTC client backend[45498] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.067 UTC client backend[45441] isolation/ri-trigger/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.067 UTC client backend[45441] isolation/ri-trigger/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.067 UTC client backend[45441] isolation/ri-trigger/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.067 UTC client backend[45441] isolation/ri-trigger/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.067 UTC client backend[45498] ecpg/thread-thread LOG: connection ready: setup total=5.059 ms, fork=0.410 ms, authentication=0.110 ms 2025-11-30 18:45:12.067 UTC client backend[45498] ecpg/thread-thread ERROR: table "test_thread" does not exist 2025-11-30 18:45:12.067 UTC client backend[45498] ecpg/thread-thread STATEMENT: drop table test_thread 2025-11-30 18:45:12.073 UTC client backend[45498] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.010 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.074 UTC unrecognized[45499] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.074 UTC client backend[45499] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.074 UTC client backend[45499] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.075 UTC client backend[45499] ecpg/thread-thread LOG: connection ready: setup total=2.097 ms, fork=0.673 ms, authentication=0.122 ms 2025-11-30 18:45:12.076 UTC unrecognized[45500] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.076 UTC client backend[45500] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.076 UTC client backend[45500] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.077 UTC client backend[45500] ecpg/thread-thread LOG: connection ready: setup total=1.709 ms, fork=0.400 ms, authentication=0.115 ms 2025-11-30 18:45:12.078 UTC unrecognized[45501] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.078 UTC client backend[45501] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.078 UTC client backend[45501] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.079 UTC client backend[45501] ecpg/thread-thread LOG: connection ready: setup total=1.568 ms, fork=0.298 ms, authentication=0.100 ms 2025-11-30 18:45:12.079 UTC unrecognized[45502] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.080 UTC client backend[45502] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.080 UTC client backend[45502] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.080 UTC client backend[45486] postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.080 UTC client backend[45486] postgres_fdw DETAIL: Failing row contains (10, -2, 00010_trig_update_trig_update, 1970-01-11 08:00:00+00, 1970-01-11 00:00:00, 0, 0 , foo). 2025-11-30 18:45:12.080 UTC client backend[45486] postgres_fdw STATEMENT: UPDATE "S 1"."T 1" SET c2 = (-2) WHERE ((c2 = 42)) AND (("C 1" = 10)) 2025-11-30 18:45:12.080 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.080 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (10, -2, 00010_trig_update_trig_update, 1970-01-11 08:00:00+00, 1970-01-11 00:00:00, 0, 0 , foo). 2025-11-30 18:45:12.080 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE "S 1"."T 1" SET c2 = (-2) WHERE ((c2 = 42)) AND (("C 1" = 10)) 2025-11-30 18:45:12.080 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update ft2 set c2 = -2 where c2 = 42 and c1 = 10; 2025-11-30 18:45:12.081 UTC client backend[45502] ecpg/thread-thread LOG: connection ready: setup total=1.563 ms, fork=0.309 ms, authentication=0.095 ms 2025-11-30 18:45:12.081 UTC unrecognized[45503] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.082 UTC client backend[45503] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.082 UTC client backend[45503] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.082 UTC client backend[45445] isolation/ri-trigger/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.082 UTC client backend[45445] isolation/ri-trigger/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.082 UTC client backend[45445] isolation/ri-trigger/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.082 UTC client backend[45445] isolation/ri-trigger/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.083 UTC client backend[45503] ecpg/thread-thread LOG: connection ready: setup total=1.663 ms, fork=0.311 ms, authentication=0.097 ms 2025-11-30 18:45:12.083 UTC unrecognized[45504] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.084 UTC client backend[45504] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.084 UTC client backend[45504] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.084 UTC client backend[45504] ecpg/thread-thread LOG: connection ready: setup total=1.632 ms, fork=0.321 ms, authentication=0.102 ms 2025-11-30 18:45:12.085 UTC unrecognized[45505] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.085 UTC client backend[45505] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.085 UTC client backend[45505] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.086 UTC client backend[45505] ecpg/thread-thread LOG: connection ready: setup total=1.579 ms, fork=0.312 ms, authentication=0.100 ms 2025-11-30 18:45:12.087 UTC unrecognized[45506] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.087 UTC client backend[45506] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.087 UTC client backend[45506] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.088 UTC client backend[45506] ecpg/thread-thread LOG: connection ready: setup total=1.592 ms, fork=0.342 ms, authentication=0.097 ms 2025-11-30 18:45:12.089 UTC unrecognized[45507] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.089 UTC client backend[45507] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.089 UTC client backend[45507] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.090 UTC client backend[45507] ecpg/thread-thread LOG: connection ready: setup total=1.571 ms, fork=0.312 ms, authentication=0.094 ms 2025-11-30 18:45:12.091 UTC unrecognized[45508] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.091 UTC client backend[45508] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.091 UTC client backend[45508] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.092 UTC client backend[45508] ecpg/thread-thread LOG: connection ready: setup total=1.775 ms, fork=0.526 ms, authentication=0.091 ms 2025-11-30 18:45:12.105 UTC client backend[45441] isolation/ri-trigger/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.105 UTC client backend[45441] isolation/ri-trigger/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.105 UTC client backend[45441] isolation/ri-trigger/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.105 UTC client backend[45441] isolation/ri-trigger/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.114 UTC client backend[45485] pg_regress/sanity_check LOG: disconnection: session time: 0:00:00.097 user=postgres database=regression host=[local] 2025-11-30 18:45:12.127 UTC client backend[45441] isolation/ri-trigger/s1 ERROR: parent row missing 2025-11-30 18:45:12.127 UTC client backend[45441] isolation/ri-trigger/s1 CONTEXT: PL/pgSQL function ri_child() line 5 at RAISE 2025-11-30 18:45:12.127 UTC client backend[45441] isolation/ri-trigger/s1 STATEMENT: INSERT INTO child (parent_id) VALUES (0); 2025-11-30 18:45:12.142 UTC client backend[45508] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.051 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.144 UTC unrecognized[45533] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.144 UTC client backend[45533] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.144 UTC client backend[45533] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_distinct 2025-11-30 18:45:12.145 UTC unrecognized[45532] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.146 UTC client backend[45532] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.146 UTC client backend[45532] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/subselect 2025-11-30 18:45:12.146 UTC unrecognized[45538] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.147 UTC client backend[45538] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.147 UTC client backend[45538] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/join 2025-11-30 18:45:12.149 UTC client backend[45533] pg_regress/select_distinct LOG: connection ready: setup total=16.003 ms, fork=8.680 ms, authentication=0.137 ms 2025-11-30 18:45:12.149 UTC unrecognized[45537] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.150 UTC client backend[45537] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.150 UTC client backend[45537] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/case 2025-11-30 18:45:12.150 UTC client backend[45537] pg_regress/case LOG: connection ready: setup total=14.194 ms, fork=7.133 ms, authentication=0.103 ms 2025-11-30 18:45:12.150 UTC client backend[45532] pg_regress/subselect LOG: connection ready: setup total=17.640 ms, fork=10.392 ms, authentication=0.100 ms 2025-11-30 18:45:12.151 UTC unrecognized[45539] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.151 UTC unrecognized[45530] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.151 UTC client backend[45539] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.151 UTC client backend[45539] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/aggregates 2025-11-30 18:45:12.151 UTC client backend[45530] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.151 UTC client backend[45530] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/union 2025-11-30 18:45:12.152 UTC client backend[45538] pg_regress/join LOG: connection ready: setup total=15.271 ms, fork=9.607 ms, authentication=0.109 ms 2025-11-30 18:45:12.152 UTC client backend[45539] pg_regress/aggregates LOG: connection ready: setup total=14.276 ms, fork=5.737 ms, authentication=0.101 ms 2025-11-30 18:45:12.152 UTC client backend[45530] pg_regress/union LOG: connection ready: setup total=19.873 ms, fork=12.883 ms, authentication=0.128 ms 2025-11-30 18:45:12.152 UTC client backend[45441] isolation/ri-trigger/s1 LOG: disconnection: session time: 0:00:00.204 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:12.153 UTC unrecognized[45531] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.153 UTC unrecognized[45540] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.153 UTC client backend[45531] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.153 UTC client backend[45531] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_implicit 2025-11-30 18:45:12.153 UTC client backend[45540] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.153 UTC client backend[45540] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/arrays 2025-11-30 18:45:12.153 UTC unrecognized[45535] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.154 UTC client backend[45535] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.154 UTC client backend[45535] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_having 2025-11-30 18:45:12.154 UTC client backend[45531] pg_regress/select_implicit LOG: connection ready: setup total=21.277 ms, fork=12.621 ms, authentication=0.102 ms 2025-11-30 18:45:12.154 UTC client backend[45540] pg_regress/arrays LOG: connection ready: setup total=15.063 ms, fork=4.656 ms, authentication=0.100 ms 2025-11-30 18:45:12.154 UTC unrecognized[45534] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.154 UTC client backend[45506] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.067 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.154 UTC client backend[45534] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.154 UTC client backend[45534] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_into 2025-11-30 18:45:12.155 UTC client backend[45535] pg_regress/select_having LOG: connection ready: setup total=19.978 ms, fork=8.633 ms, authentication=0.100 ms 2025-11-30 18:45:12.155 UTC client backend[45534] pg_regress/select_into LOG: connection ready: setup total=21.726 ms, fork=11.864 ms, authentication=0.101 ms 2025-11-30 18:45:12.155 UTC unrecognized[45541] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.156 UTC client backend[45541] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.156 UTC client backend[45541] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/portals 2025-11-30 18:45:12.157 UTC client backend[45541] pg_regress/portals LOG: connection ready: setup total=17.450 ms, fork=6.323 ms, authentication=0.097 ms 2025-11-30 18:45:12.157 UTC client backend[45440] isolation/ri-trigger/control connection LOG: disconnection: session time: 0:00:00.211 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:12.157 UTC unrecognized[45536] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.157 UTC client backend[45536] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.157 UTC client backend[45536] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/transactions 2025-11-30 18:45:12.158 UTC client backend[45445] isolation/ri-trigger/s2 LOG: disconnection: session time: 0:00:00.206 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:12.158 UTC client backend[45536] pg_regress/transactions LOG: connection ready: setup total=22.238 ms, fork=7.569 ms, authentication=0.107 ms 2025-11-30 18:45:12.159 UTC unrecognized[45545] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.159 UTC unrecognized[45542] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.159 UTC client backend[45545] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.159 UTC client backend[45545] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/namespace 2025-11-30 18:45:12.159 UTC unrecognized[45548] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.159 UTC client backend[45542] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.159 UTC client backend[45542] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/btree_index 2025-11-30 18:45:12.160 UTC client backend[45548] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.160 UTC client backend[45548] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_distinct_on 2025-11-30 18:45:12.160 UTC unrecognized[45543] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.160 UTC client backend[45545] pg_regress/namespace LOG: connection ready: setup total=15.798 ms, fork=10.930 ms, authentication=0.105 ms 2025-11-30 18:45:12.160 UTC client backend[45543] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.160 UTC client backend[45542] pg_regress/btree_index LOG: connection ready: setup total=20.804 ms, fork=6.843 ms, authentication=0.117 ms 2025-11-30 18:45:12.160 UTC client backend[45543] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/random 2025-11-30 18:45:12.160 UTC client backend[45548] pg_regress/select_distinct_on LOG: connection ready: setup total=15.460 ms, fork=7.570 ms, authentication=0.103 ms 2025-11-30 18:45:12.160 UTC unrecognized[45547] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.161 UTC client backend[45547] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.161 UTC client backend[45547] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/delete 2025-11-30 18:45:12.161 UTC client backend[45543] pg_regress/random LOG: connection ready: setup total=17.324 ms, fork=14.722 ms, authentication=0.100 ms 2025-11-30 18:45:12.161 UTC unrecognized[45544] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.162 UTC client backend[45544] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.162 UTC client backend[45547] pg_regress/delete LOG: connection ready: setup total=16.878 ms, fork=1.568 ms, authentication=0.097 ms 2025-11-30 18:45:12.162 UTC client backend[45544] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/hash_index 2025-11-30 18:45:12.162 UTC unrecognized[45546] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.162 UTC client backend[45546] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.162 UTC client backend[45546] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/update 2025-11-30 18:45:12.162 UTC client backend[45544] pg_regress/hash_index LOG: connection ready: setup total=18.472 ms, fork=14.524 ms, authentication=0.104 ms 2025-11-30 18:45:12.163 UTC client backend[45546] pg_regress/update LOG: connection ready: setup total=18.441 ms, fork=14.106 ms, authentication=0.098 ms 2025-11-30 18:45:12.164 UTC unrecognized[45549] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.164 UTC client backend[45549] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.164 UTC client backend[45549] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/prepared_xacts 2025-11-30 18:45:12.165 UTC client backend[45505] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.080 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.171 UTC client backend[45549] pg_regress/prepared_xacts LOG: connection ready: setup total=20.575 ms, fork=6.263 ms, authentication=0.112 ms 2025-11-30 18:45:12.172 UTC unrecognized[45552] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.172 UTC client backend[45552] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.172 UTC client backend[45552] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/partial-index 2025-11-30 18:45:12.173 UTC client backend[45552] isolation/partial-index LOG: connection ready: setup total=16.741 ms, fork=9.216 ms, authentication=0.107 ms 2025-11-30 18:45:12.173 UTC client backend[45501] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.095 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.174 UTC client backend[45503] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.092 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.185 UTC client backend[45540] pg_regress/arrays ERROR: value too long for type character(5) 2025-11-30 18:45:12.185 UTC client backend[45540] pg_regress/arrays STATEMENT: INSERT INTO arrtest (f) VALUES ('{"too long"}'); 2025-11-30 18:45:12.186 UTC client backend[45499] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.112 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.186 UTC client backend[45507] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.097 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.188 UTC unrecognized[45553] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.188 UTC client backend[45553] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.188 UTC client backend[45553] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/partial-index 2025-11-30 18:45:12.189 UTC client backend[45553] isolation/partial-index LOG: connection ready: setup total=9.356 ms, fork=7.410 ms, authentication=0.112 ms 2025-11-30 18:45:12.194 UTC client backend[45504] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.110 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.195 UTC client backend[45545] pg_regress/namespace ERROR: column "c" does not exist at character 70 2025-11-30 18:45:12.195 UTC client backend[45545] pg_regress/namespace STATEMENT: CREATE SCHEMA test_ns_schema_2 CREATE VIEW abc_view AS SELECT c FROM abc; 2025-11-30 18:45:12.195 UTC client backend[45548] pg_regress/select_distinct_on ERROR: SELECT DISTINCT ON expressions must match initial ORDER BY expressions at character 30 2025-11-30 18:45:12.195 UTC client backend[45548] 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-11-30 18:45:12.197 UTC unrecognized[45554] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.197 UTC client backend[45554] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.197 UTC client backend[45554] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/partial-index 2025-11-30 18:45:12.198 UTC client backend[45554] isolation/partial-index LOG: connection ready: setup total=5.066 ms, fork=1.928 ms, authentication=0.123 ms 2025-11-30 18:45:12.201 UTC client backend[45500] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.125 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.204 UTC client backend[45543] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-11-30 18:45:12.204 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random(1, 0); 2025-11-30 18:45:12.204 UTC client backend[45536] pg_regress/transactions ERROR: parameter "transaction_isolation" cannot be reset 2025-11-30 18:45:12.204 UTC client backend[45536] pg_regress/transactions STATEMENT: RESET transaction_isolation; 2025-11-30 18:45:12.205 UTC client backend[45540] pg_regress/arrays ERROR: subscripted assignment to "b" requires type integer but expression is of type timestamp with time zone at character 22 2025-11-30 18:45:12.205 UTC client backend[45540] pg_regress/arrays HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:12.205 UTC client backend[45540] pg_regress/arrays STATEMENT: INSERT INTO arrtest (b[2]) VALUES(now()); 2025-11-30 18:45:12.208 UTC client backend[45540] pg_regress/arrays ERROR: subscripted assignment to "b" requires type integer[] but expression is of type timestamp with time zone at character 22 2025-11-30 18:45:12.208 UTC client backend[45540] pg_regress/arrays HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:12.208 UTC client backend[45540] pg_regress/arrays STATEMENT: INSERT INTO arrtest (b[1:2]) VALUES(now()); 2025-11-30 18:45:12.211 UTC client backend[45543] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-11-30 18:45:12.211 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random(1000000000001, 1000000000000); 2025-11-30 18:45:12.211 UTC client backend[45546] pg_regress/update ERROR: column "t" of relation "update_test" does not exist at character 26 2025-11-30 18:45:12.211 UTC client backend[45546] pg_regress/update HINT: SET target columns cannot be qualified with the relation name. 2025-11-30 18:45:12.211 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE update_test t SET t.b = t.b + 10 WHERE t.a = 10; 2025-11-30 18:45:12.212 UTC client backend[45543] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-11-30 18:45:12.212 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random(-2.0, -3.0); 2025-11-30 18:45:12.213 UTC client backend[45543] pg_regress/random ERROR: lower bound cannot be NaN 2025-11-30 18:45:12.213 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('NaN'::numeric, 10); 2025-11-30 18:45:12.214 UTC client backend[45543] pg_regress/random ERROR: lower bound cannot be infinity 2025-11-30 18:45:12.214 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('-Inf'::numeric, 0); 2025-11-30 18:45:12.214 UTC client backend[45536] pg_regress/transactions ERROR: parameter "transaction_read_only" cannot be reset 2025-11-30 18:45:12.214 UTC client backend[45536] pg_regress/transactions STATEMENT: RESET transaction_read_only; 2025-11-30 18:45:12.218 UTC client backend[45537] pg_regress/case ERROR: division by zero 2025-11-30 18:45:12.218 UTC client backend[45537] pg_regress/case STATEMENT: SELECT CASE WHEN i > 100 THEN 1/0 ELSE 0 END FROM case_tbl; 2025-11-30 18:45:12.220 UTC client backend[45543] pg_regress/random ERROR: upper bound cannot be NaN 2025-11-30 18:45:12.220 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random(0, 'NaN'::numeric); 2025-11-30 18:45:12.221 UTC client backend[45543] pg_regress/random ERROR: upper bound cannot be infinity 2025-11-30 18:45:12.221 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random(0, 'Inf'::numeric); 2025-11-30 18:45:12.221 UTC client backend[45547] pg_regress/delete ERROR: invalid reference to FROM-clause entry for table "delete_test" at character 34 2025-11-30 18:45:12.221 UTC client backend[45547] pg_regress/delete HINT: Perhaps you meant to reference the table alias "dt". 2025-11-30 18:45:12.221 UTC client backend[45547] pg_regress/delete STATEMENT: DELETE FROM delete_test dt WHERE delete_test.a > 25; 2025-11-30 18:45:12.222 UTC client backend[45536] pg_regress/transactions ERROR: parameter "transaction_deferrable" cannot be reset 2025-11-30 18:45:12.222 UTC client backend[45536] pg_regress/transactions STATEMENT: RESET transaction_deferrable; 2025-11-30 18:45:12.223 UTC client backend[45534] pg_regress/select_into ERROR: permission denied for table tbl_withdata1 2025-11-30 18:45:12.223 UTC client backend[45534] pg_regress/select_into STATEMENT: INSERT INTO selinto_schema.tbl_withdata1 VALUES (4); 2025-11-30 18:45:12.224 UTC client backend[45546] pg_regress/update ERROR: column "a" is of type integer but expression is of type record at character 28 2025-11-30 18:45:12.224 UTC client backend[45546] pg_regress/update HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:12.224 UTC client backend[45546] 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-11-30 18:45:12.226 UTC client backend[45535] 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-11-30 18:45:12.226 UTC client backend[45535] pg_regress/select_having STATEMENT: SELECT a FROM test_having HAVING min(a) < max(a); 2025-11-30 18:45:12.227 UTC client backend[45535] 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-11-30 18:45:12.227 UTC client backend[45535] pg_regress/select_having STATEMENT: SELECT 1 AS one FROM test_having HAVING a > 1; 2025-11-30 18:45:12.228 UTC client backend[45536] pg_regress/transactions ERROR: parameter "transaction_read_only" cannot be set locally in functions 2025-11-30 18:45:12.228 UTC client backend[45536] pg_regress/transactions STATEMENT: CREATE FUNCTION errfunc() RETURNS int LANGUAGE SQL AS 'SELECT 1' SET transaction_read_only = on; 2025-11-30 18:45:12.237 UTC client backend[45531] 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-11-30 18:45:12.237 UTC client backend[45531] pg_regress/select_implicit STATEMENT: SELECT count(*) FROM test_missing_target GROUP BY a ORDER BY b; 2025-11-30 18:45:12.237 UTC client backend[45549] pg_regress/prepared_xacts ERROR: transaction identifier "regress_foo3" is already in use 2025-11-30 18:45:12.237 UTC client backend[45549] pg_regress/prepared_xacts STATEMENT: PREPARE TRANSACTION 'regress_foo3'; 2025-11-30 18:45:12.244 UTC client backend[45536] pg_regress/transactions ERROR: transaction read-write mode must be set before any query 2025-11-30 18:45:12.244 UTC client backend[45536] pg_regress/transactions STATEMENT: SET TRANSACTION READ WRITE; 2025-11-30 18:45:12.246 UTC client backend[45538] pg_regress/join ERROR: column reference "i" is ambiguous at character 8 2025-11-30 18:45:12.246 UTC client backend[45538] pg_regress/join STATEMENT: SELECT i, k, t FROM J1_TBL CROSS JOIN J2_TBL; 2025-11-30 18:45:12.247 UTC client backend[45531] pg_regress/select_implicit ERROR: GROUP BY position 3 is not in select list at character 54 2025-11-30 18:45:12.247 UTC client backend[45531] pg_regress/select_implicit STATEMENT: SELECT c, count(*) FROM test_missing_target GROUP BY 3; 2025-11-30 18:45:12.250 UTC unrecognized[45555] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.250 UTC client backend[45531] pg_regress/select_implicit ERROR: column reference "b" is ambiguous at character 105 2025-11-30 18:45:12.250 UTC client backend[45531] 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-11-30 18:45:12.253 UTC client backend[45502] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.174 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.255 UTC client backend[45549] pg_regress/prepared_xacts ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.255 UTC client backend[45549] pg_regress/prepared_xacts DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:12.255 UTC client backend[45549] pg_regress/prepared_xacts HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.255 UTC client backend[45549] pg_regress/prepared_xacts STATEMENT: INSERT INTO pxtest1 VALUES ('fff'); 2025-11-30 18:45:12.255 UTC client backend[45535] pg_regress/select_having LOG: disconnection: session time: 0:00:00.112 user=postgres database=regression host=[local] 2025-11-30 18:45:12.256 UTC client backend[45547] pg_regress/delete LOG: disconnection: session time: 0:00:00.109 user=postgres database=regression host=[local] 2025-11-30 18:45:12.258 UTC client backend[45555] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.258 UTC client backend[45555] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread 2025-11-30 18:45:12.258 UTC client backend[45555] ecpg/thread-thread LOG: connection ready: setup total=12.018 ms, fork=1.377 ms, authentication=0.115 ms 2025-11-30 18:45:12.259 UTC client backend[45548] pg_regress/select_distinct_on LOG: disconnection: session time: 0:00:00.106 user=postgres database=regression host=[local] 2025-11-30 18:45:12.259 UTC client backend[45546] pg_regress/update ERROR: multiple assignments to same column "b" 2025-11-30 18:45:12.259 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE update_test SET (c,b) = ('car', a+b), b = a + 1 WHERE a = 10; 2025-11-30 18:45:12.262 UTC client backend[45536] pg_regress/transactions ERROR: cannot set transaction read-write mode inside a read-only transaction 2025-11-30 18:45:12.262 UTC client backend[45536] pg_regress/transactions STATEMENT: SET TRANSACTION READ WRITE; 2025-11-30 18:45:12.264 UTC client backend[45545] pg_regress/namespace ERROR: schema "test_ns_schema_renamed" already exists 2025-11-30 18:45:12.264 UTC client backend[45545] pg_regress/namespace STATEMENT: CREATE SCHEMA test_ns_schema_renamed; 2025-11-30 18:45:12.266 UTC client backend[45546] pg_regress/update ERROR: more than one row returned by a subquery used as an expression 2025-11-30 18:45:12.266 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE update_test SET (b,a) = (select a+1,b from update_test); 2025-11-30 18:45:12.267 UTC client backend[45545] pg_regress/namespace ERROR: CREATE SCHEMA IF NOT EXISTS cannot include schema elements at character 79 2025-11-30 18:45:12.267 UTC client backend[45545] pg_regress/namespace STATEMENT: CREATE SCHEMA IF NOT EXISTS test_ns_schema_renamed -- fail, disallowed CREATE TABLE abc ( a serial, b int UNIQUE ); 2025-11-30 18:45:12.269 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "j1_tbl" at character 57 2025-11-30 18:45:12.269 UTC client backend[45538] pg_regress/join DETAIL: There is an entry for table "j1_tbl", but it cannot be referenced from this part of the query. 2025-11-30 18:45:12.269 UTC client backend[45538] pg_regress/join STATEMENT: SELECT * FROM (J1_TBL JOIN J2_TBL USING (i)) AS x WHERE J1_TBL.t = 'one'; 2025-11-30 18:45:12.269 UTC client backend[45531] 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-11-30 18:45:12.269 UTC client backend[45531] pg_regress/select_implicit STATEMENT: SELECT count(a) FROM test_missing_target GROUP BY a ORDER BY b; 2025-11-30 18:45:12.271 UTC client backend[45549] pg_regress/prepared_xacts ERROR: cannot PREPARE while holding both session-level and transaction-level locks on the same object 2025-11-30 18:45:12.271 UTC client backend[45549] pg_regress/prepared_xacts STATEMENT: PREPARE TRANSACTION 'regress_foo6'; 2025-11-30 18:45:12.272 UTC client backend[45538] pg_regress/join ERROR: column x.t does not exist at character 55 2025-11-30 18:45:12.272 UTC client backend[45538] pg_regress/join STATEMENT: SELECT * FROM J1_TBL JOIN J2_TBL USING (i) AS x WHERE x.t = 'one'; 2025-11-30 18:45:12.272 UTC client backend[45546] pg_regress/update ERROR: source for a multiple-column UPDATE item must be a sub-SELECT or ROW() expression at character 33 2025-11-30 18:45:12.272 UTC client backend[45546] 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-11-30 18:45:12.273 UTC client backend[45538] pg_regress/join ERROR: missing FROM-clause entry for table "x" at character 63 2025-11-30 18:45:12.273 UTC client backend[45538] pg_regress/join STATEMENT: SELECT * FROM (J1_TBL JOIN J2_TBL USING (i) AS x) AS xx WHERE x.i = 1; 2025-11-30 18:45:12.273 UTC client backend[45530] pg_regress/union ERROR: FOR NO KEY UPDATE is not allowed with UNION/INTERSECT/EXCEPT 2025-11-30 18:45:12.273 UTC client backend[45530] pg_regress/union STATEMENT: SELECT q1 FROM int8_tbl EXCEPT ALL SELECT q1 FROM int8_tbl FOR NO KEY UPDATE; 2025-11-30 18:45:12.274 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.274 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on conflict out to pivot 13512, during read. 2025-11-30 18:45:12.274 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.274 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: select * from test_t where val2 = 1; 2025-11-30 18:45:12.274 UTC client backend[45536] pg_regress/transactions ERROR: cannot set transaction read-write mode inside a read-only transaction 2025-11-30 18:45:12.274 UTC client backend[45536] pg_regress/transactions STATEMENT: SET TRANSACTION READ WRITE; 2025-11-30 18:45:12.275 UTC client backend[45531] pg_regress/select_implicit ERROR: column reference "b" is ambiguous at character 109 2025-11-30 18:45:12.275 UTC client backend[45531] 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-11-30 18:45:12.275 UTC client backend[45538] pg_regress/join ERROR: table name "a1" specified more than once 2025-11-30 18:45:12.275 UTC client backend[45538] pg_regress/join STATEMENT: SELECT * FROM J1_TBL a1 JOIN J2_TBL a2 USING (i) AS a1; 2025-11-30 18:45:12.277 UTC client backend[45531] pg_regress/select_implicit ERROR: column reference "b" is ambiguous at character 14 2025-11-30 18:45:12.277 UTC client backend[45531] 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-11-30 18:45:12.277 UTC client backend[45546] pg_regress/update ERROR: invalid reference to FROM-clause entry for table "update_test" at character 33 2025-11-30 18:45:12.277 UTC client backend[45546] pg_regress/update HINT: Perhaps you meant to reference the table alias "t". 2025-11-30 18:45:12.277 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE update_test AS t SET b = update_test.b + 10 WHERE t.a = 10; 2025-11-30 18:45:12.287 UTC client backend[45555] ecpg/thread-thread LOG: disconnection: session time: 0:00:00.039 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.302 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.302 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.302 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.302 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.303 UTC client backend[45537] pg_regress/case LOG: disconnection: session time: 0:00:00.159 user=postgres database=regression host=[local] 2025-11-30 18:45:12.305 UTC client backend[45536] pg_regress/transactions ERROR: cannot execute DROP TABLE in a read-only transaction 2025-11-30 18:45:12.305 UTC client backend[45536] pg_regress/transactions STATEMENT: DROP TABLE writetest; 2025-11-30 18:45:12.312 UTC client backend[45531] pg_regress/select_implicit LOG: disconnection: session time: 0:00:00.166 user=postgres database=regression host=[local] 2025-11-30 18:45:12.314 UTC client backend[45536] pg_regress/transactions ERROR: cannot execute INSERT in a read-only transaction 2025-11-30 18:45:12.314 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO writetest VALUES (1); 2025-11-30 18:45:12.323 UTC client backend[45536] pg_regress/transactions ERROR: cannot execute UPDATE in a read-only transaction 2025-11-30 18:45:12.323 UTC client backend[45536] pg_regress/transactions STATEMENT: EXECUTE test; 2025-11-30 18:45:12.329 UTC client backend[45541] pg_regress/portals ERROR: cursor can only scan forward 2025-11-30 18:45:12.329 UTC client backend[45541] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-11-30 18:45:12.329 UTC client backend[45541] pg_regress/portals STATEMENT: FETCH BACKWARD 1 FROM foo24; 2025-11-30 18:45:12.330 UTC client backend[45536] pg_regress/transactions ERROR: cannot execute CREATE TABLE AS in a read-only transaction 2025-11-30 18:45:12.330 UTC client backend[45536] pg_regress/transactions STATEMENT: CREATE TABLE test AS SELECT * FROM writetest; 2025-11-30 18:45:12.331 UTC client backend[45549] pg_regress/prepared_xacts ERROR: cursor "foo" does not exist 2025-11-30 18:45:12.331 UTC client backend[45549] pg_regress/prepared_xacts STATEMENT: FETCH 1 FROM foo; 2025-11-30 18:45:12.334 UTC client backend[45541] pg_regress/portals ERROR: cursor can only scan forward 2025-11-30 18:45:12.334 UTC client backend[45541] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-11-30 18:45:12.334 UTC client backend[45541] pg_regress/portals STATEMENT: FETCH ABSOLUTE 1 FROM foo24; 2025-11-30 18:45:12.341 UTC client backend[45549] pg_regress/prepared_xacts ERROR: relation "pxtest2" does not exist at character 15 2025-11-30 18:45:12.341 UTC client backend[45549] pg_regress/prepared_xacts STATEMENT: SELECT * FROM pxtest2; 2025-11-30 18:45:12.341 UTC client backend[45532] pg_regress/subselect ERROR: more than one row returned by a subquery used as an expression 2025-11-30 18:45:12.341 UTC client backend[45532] pg_regress/subselect STATEMENT: SELECT ROW(1, 2) = (SELECT f1, f2 FROM SUBSELECT_TBL); 2025-11-30 18:45:12.346 UTC client backend[45545] pg_regress/namespace LOG: disconnection: session time: 0:00:00.190 user=postgres database=regression host=[local] 2025-11-30 18:45:12.348 UTC client backend[45549] pg_regress/prepared_xacts ERROR: could not obtain lock on relation "pxtest3" 2025-11-30 18:45:12.348 UTC client backend[45549] pg_regress/prepared_xacts STATEMENT: lock table pxtest3 in access share mode nowait; 2025-11-30 18:45:12.355 UTC client backend[45543] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-11-30 18:45:12.355 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('2024-12-31'::date, '2024-01-01'::date); 2025-11-30 18:45:12.355 UTC client backend[45540] pg_regress/arrays ERROR: number of array dimensions (7) exceeds the maximum allowed (6) 2025-11-30 18:45:12.355 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT ('{}'::int[])[1][2][3][4][5][6][7]; 2025-11-30 18:45:12.356 UTC client backend[45543] pg_regress/random ERROR: lower and upper bounds must be finite 2025-11-30 18:45:12.356 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('-infinity'::date, '2024-01-01'::date); 2025-11-30 18:45:12.359 UTC client backend[45543] pg_regress/random ERROR: lower and upper bounds must be finite 2025-11-30 18:45:12.359 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('2024-12-31'::date, 'infinity'::date); 2025-11-30 18:45:12.363 UTC client backend[45540] pg_regress/arrays ERROR: array subscript in assignment must not be null 2025-11-30 18:45:12.363 UTC client backend[45540] pg_regress/arrays STATEMENT: UPDATE arrtest SET c[NULL] = '{"can''t assign"}' WHERE array_dims(c) is not null; 2025-11-30 18:45:12.369 UTC client backend[45540] pg_regress/arrays ERROR: array subscript in assignment must not be null 2025-11-30 18:45:12.369 UTC client backend[45540] pg_regress/arrays STATEMENT: UPDATE arrtest SET c[NULL:1] = '{"can''t assign"}' WHERE array_dims(c) is not null; 2025-11-30 18:45:12.369 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.369 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.369 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.369 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.370 UTC unrecognized[45559] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.370 UTC client backend[45536] pg_regress/transactions ERROR: relation "trans_bar" does not exist at character 15 2025-11-30 18:45:12.370 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT * FROM trans_bar; 2025-11-30 18:45:12.371 UTC client backend[45559] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.371 UTC client backend[45559] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/prepared_xacts 2025-11-30 18:45:12.372 UTC client backend[45540] pg_regress/arrays ERROR: array subscript in assignment must not be null 2025-11-30 18:45:12.372 UTC client backend[45540] pg_regress/arrays STATEMENT: UPDATE arrtest SET c[1:NULL] = '{"can''t assign"}' WHERE array_dims(c) is not null; 2025-11-30 18:45:12.372 UTC client backend[45543] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-11-30 18:45:12.372 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('2024-12-31'::timestamp, '2024-01-01'::timestamp); 2025-11-30 18:45:12.372 UTC client backend[45559] pg_regress/prepared_xacts LOG: connection ready: setup total=23.148 ms, fork=10.523 ms, authentication=0.121 ms 2025-11-30 18:45:12.372 UTC client backend[45549] pg_regress/prepared_xacts LOG: disconnection: session time: 0:00:00.215 user=postgres database=regression host=[local] 2025-11-30 18:45:12.373 UTC client backend[45543] pg_regress/random ERROR: lower and upper bounds must be finite 2025-11-30 18:45:12.373 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('-infinity'::timestamp, '2024-01-01'::timestamp); 2025-11-30 18:45:12.375 UTC client backend[45543] pg_regress/random ERROR: lower and upper bounds must be finite 2025-11-30 18:45:12.375 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('2024-12-31'::timestamp, 'infinity'::timestamp); 2025-11-30 18:45:12.377 UTC client backend[45540] pg_regress/arrays ERROR: cannot subscript type timestamp with time zone because it does not support subscripting at character 9 2025-11-30 18:45:12.377 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT (now())[1]; 2025-11-30 18:45:12.381 UTC client backend[45536] pg_regress/transactions ERROR: relation "trans_bar" does not exist at character 13 2025-11-30 18:45:12.381 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT into trans_bar VALUES (1); 2025-11-30 18:45:12.386 UTC client backend[45543] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-11-30 18:45:12.386 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('2024-01-01 +06'::timestamptz, '2024-01-01 +07'::timestamptz); 2025-11-30 18:45:12.386 UTC client backend[45543] pg_regress/random ERROR: lower and upper bounds must be finite 2025-11-30 18:45:12.386 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('-infinity'::timestamptz, '2024-01-01 +07'::timestamptz); 2025-11-30 18:45:12.388 UTC client backend[45543] pg_regress/random ERROR: lower and upper bounds must be finite 2025-11-30 18:45:12.388 UTC client backend[45543] pg_regress/random STATEMENT: SELECT random('2024-01-01 +06'::timestamptz, 'infinity'::timestamptz); 2025-11-30 18:45:12.389 UTC client backend[45543] pg_regress/random LOG: disconnection: session time: 0:00:00.230 user=postgres database=regression host=[local] 2025-11-30 18:45:12.390 UTC client backend[45534] pg_regress/select_into ERROR: too many column names were specified 2025-11-30 18:45:12.390 UTC client backend[45534] pg_regress/select_into STATEMENT: CREATE TABLE ctas_nodata (ii, jj, kk) AS SELECT i, j FROM ctas_base; 2025-11-30 18:45:12.392 UTC client backend[45534] pg_regress/select_into ERROR: too many column names were specified 2025-11-30 18:45:12.392 UTC client backend[45534] pg_regress/select_into STATEMENT: CREATE TABLE ctas_nodata (ii, jj, kk) AS SELECT i, j FROM ctas_base WITH NO DATA; 2025-11-30 18:45:12.392 UTC client backend[45559] pg_regress/prepared_xacts ERROR: could not obtain lock on relation "pxtest3" 2025-11-30 18:45:12.392 UTC client backend[45559] pg_regress/prepared_xacts STATEMENT: lock table pxtest3 in access share mode nowait; 2025-11-30 18:45:12.399 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.399 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on conflict out to pivot 13659, during read. 2025-11-30 18:45:12.399 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.399 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: select * from test_t where val2 = 1; 2025-11-30 18:45:12.401 UTC client backend[45541] pg_regress/portals ERROR: cursor can only scan forward 2025-11-30 18:45:12.401 UTC client backend[45541] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-11-30 18:45:12.401 UTC client backend[45541] pg_regress/portals STATEMENT: FETCH ABSOLUTE 4 FROM foo25ns; 2025-11-30 18:45:12.416 UTC client backend[45540] pg_regress/arrays ERROR: source array too small 2025-11-30 18:45:12.416 UTC client backend[45540] pg_regress/arrays STATEMENT: UPDATE arrtest_s SET a[:] = '{23, 24, 25}'; 2025-11-30 18:45:12.417 UTC client backend[45541] pg_regress/portals ERROR: cursor "foo26" does not exist 2025-11-30 18:45:12.417 UTC client backend[45541] pg_regress/portals STATEMENT: FETCH FROM foo26; 2025-11-30 18:45:12.419 UTC unrecognized[45564] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.422 UTC client backend[45564] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.422 UTC client backend[45564] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.422 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate functions are not allowed in WHERE at character 114 2025-11-30 18:45:12.422 UTC client backend[45539] 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-11-30 18:45:12.422 UTC client backend[45540] pg_regress/arrays ERROR: array slice subscript must provide both boundaries 2025-11-30 18:45:12.422 UTC client backend[45540] pg_regress/arrays DETAIL: When assigning to a slice of an empty array value, slice boundaries must be fully specified. 2025-11-30 18:45:12.422 UTC client backend[45540] pg_regress/arrays STATEMENT: UPDATE arrtest_s SET a[:] = '{11, 12, 13, 14, 15}'; 2025-11-30 18:45:12.423 UTC client backend[45564] ecpg/thread-thread_implicit LOG: connection ready: setup total=7.298 ms, fork=2.441 ms, authentication=0.121 ms 2025-11-30 18:45:12.427 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.427 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.427 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.427 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.428 UTC client backend[45559] pg_regress/prepared_xacts ERROR: relation "pxtest3" does not exist at character 15 2025-11-30 18:45:12.428 UTC client backend[45559] pg_regress/prepared_xacts STATEMENT: SELECT * FROM pxtest3; 2025-11-30 18:45:12.436 UTC client backend[45559] pg_regress/prepared_xacts ERROR: table "pxtest3" does not exist 2025-11-30 18:45:12.436 UTC client backend[45559] pg_regress/prepared_xacts STATEMENT: DROP TABLE pxtest3; 2025-11-30 18:45:12.437 UTC client backend[45534] pg_regress/select_into ERROR: SELECT ... INTO is not allowed here at character 38 2025-11-30 18:45:12.437 UTC client backend[45534] pg_regress/select_into STATEMENT: DECLARE foo CURSOR FOR SELECT 1 INTO int4_tbl; 2025-11-30 18:45:12.438 UTC client backend[45559] pg_regress/prepared_xacts LOG: disconnection: session time: 0:00:00.078 user=postgres database=regression host=[local] 2025-11-30 18:45:12.440 UTC client backend[45534] pg_regress/select_into ERROR: COPY (SELECT INTO) is not supported 2025-11-30 18:45:12.440 UTC client backend[45534] pg_regress/select_into STATEMENT: COPY (SELECT 1 INTO frak UNION SELECT 2) TO 'blob'; 2025-11-30 18:45:12.440 UTC client backend[45534] pg_regress/select_into ERROR: SELECT ... INTO is not allowed here at character 30 2025-11-30 18:45:12.440 UTC client backend[45534] pg_regress/select_into STATEMENT: SELECT * FROM (SELECT 1 INTO f) bar; 2025-11-30 18:45:12.441 UTC client backend[45534] pg_regress/select_into ERROR: views must not contain SELECT INTO 2025-11-30 18:45:12.441 UTC client backend[45534] pg_regress/select_into STATEMENT: CREATE VIEW foo AS SELECT 1 INTO int4_tbl; 2025-11-30 18:45:12.441 UTC client backend[45534] pg_regress/select_into ERROR: SELECT ... INTO is not allowed here at character 36 2025-11-30 18:45:12.441 UTC client backend[45534] pg_regress/select_into STATEMENT: INSERT INTO int4_tbl SELECT 1 INTO f; 2025-11-30 18:45:12.442 UTC client backend[45534] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-11-30 18:45:12.442 UTC client backend[45534] pg_regress/select_into STATEMENT: CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0; 2025-11-30 18:45:12.444 UTC client backend[45534] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-11-30 18:45:12.444 UTC client backend[45534] pg_regress/select_into STATEMENT: CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0 WITH NO DATA; 2025-11-30 18:45:12.444 UTC client backend[45536] pg_regress/transactions ERROR: column "trans_foo" does not exist at character 8 2025-11-30 18:45:12.444 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT trans_foo; 2025-11-30 18:45:12.447 UTC client backend[45546] pg_regress/update ERROR: new row for relation "part_c_100_200" violates partition constraint 2025-11-30 18:45:12.447 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (105, 85, null, b, 15). 2025-11-30 18:45:12.447 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE part_c_100_200 set c = c - 20, d = c WHERE c = 105; 2025-11-30 18:45:12.447 UTC client backend[45534] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-11-30 18:45:12.447 UTC client backend[45534] pg_regress/select_into STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF) CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0; 2025-11-30 18:45:12.447 UTC client backend[45540] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-11-30 18:45:12.447 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT f1[0:1] FROM POINT_TBL; 2025-11-30 18:45:12.448 UTC client backend[45546] pg_regress/update ERROR: new row for relation "part_b_10_b_20" violates partition constraint 2025-11-30 18:45:12.448 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (null, 96, a, 12, 1). 2025-11-30 18:45:12.448 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE part_b_10_b_20 set a = 'a'; 2025-11-30 18:45:12.448 UTC client backend[45540] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-11-30 18:45:12.448 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT f1[0:] FROM POINT_TBL; 2025-11-30 18:45:12.448 UTC client backend[45534] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-11-30 18:45:12.448 UTC client backend[45534] 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-11-30 18:45:12.450 UTC client backend[45540] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-11-30 18:45:12.450 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT f1[:1] FROM POINT_TBL; 2025-11-30 18:45:12.452 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.452 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.452 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.452 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.457 UTC client backend[45546] pg_regress/update ERROR: new row for relation "part_b_10_b_20" violates partition constraint 2025-11-30 18:45:12.457 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (2, 117, b, 7, 2). 2025-11-30 18:45:12.457 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE part_b_10_b_20 set b = b - 6 WHERE c > 116 returning *; 2025-11-30 18:45:12.467 UTC client backend[45540] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-11-30 18:45:12.467 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT f1[:] FROM POINT_TBL; 2025-11-30 18:45:12.468 UTC client backend[45534] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-11-30 18:45:12.468 UTC client backend[45534] pg_regress/select_into STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF) CREATE TABLE ctas_ine_tbl AS EXECUTE ctas_ine_query; 2025-11-30 18:45:12.470 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.470 UTC client backend[45534] pg_regress/select_into LOG: disconnection: session time: 0:00:00.325 user=postgres database=regression host=[local] 2025-11-30 18:45:12.472 UTC client backend[45540] pg_regress/arrays ERROR: array subscript out of range 2025-11-30 18:45:12.472 UTC client backend[45540] pg_regress/arrays STATEMENT: UPDATE point_tbl SET f1[3] = 10 WHERE f1::text = '(-10,-10)'::point::text RETURNING *; 2025-11-30 18:45:12.473 UTC client backend[45530] pg_regress/union ERROR: column "q2" does not exist at character 65 2025-11-30 18:45:12.473 UTC client backend[45530] pg_regress/union DETAIL: There is a column named "q2" in table "unnamed_subquery", but it cannot be referenced from this part of the query. 2025-11-30 18:45:12.473 UTC client backend[45530] pg_regress/union STATEMENT: SELECT q1 FROM int8_tbl EXCEPT SELECT q2 FROM int8_tbl ORDER BY q2 LIMIT 1; 2025-11-30 18:45:12.473 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.473 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.473 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.473 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.474 UTC client backend[45546] pg_regress/update ERROR: new row violates check option for view "upview" 2025-11-30 18:45:12.474 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (a, 4, 120, 1, 1). 2025-11-30 18:45:12.474 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE upview set c = 120 WHERE b = 4; 2025-11-30 18:45:12.474 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.476 UTC client backend[45546] pg_regress/update ERROR: new row violates check option for view "upview" 2025-11-30 18:45:12.476 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (b, 15, 120, 1, 1). 2025-11-30 18:45:12.476 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE upview set a = 'b', b = 15, c = 120 WHERE b = 4; 2025-11-30 18:45:12.477 UTC client backend[45564] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.058 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.479 UTC client backend[45536] pg_regress/transactions ERROR: column "trans_foo" does not exist at character 8 2025-11-30 18:45:12.479 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT trans_foo; 2025-11-30 18:45:12.492 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.492 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.492 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.492 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.494 UTC unrecognized[45566] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.498 UTC client backend[45536] pg_regress/transactions ERROR: SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:12.498 UTC client backend[45536] pg_regress/transactions STATEMENT: SAVEPOINT one; 2025-11-30 18:45:12.498 UTC client backend[45536] pg_regress/transactions ERROR: ROLLBACK TO SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:12.498 UTC client backend[45536] pg_regress/transactions STATEMENT: ROLLBACK TO SAVEPOINT one; 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions ERROR: RELEASE SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions STATEMENT: RELEASE SAVEPOINT one; 2025-11-30 18:45:12.499 UTC client backend[45541] pg_regress/portals ERROR: cursor can only scan forward 2025-11-30 18:45:12.499 UTC client backend[45541] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-11-30 18:45:12.499 UTC client backend[45541] pg_regress/portals STATEMENT: FETCH RELATIVE 0 FROM c1; 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions ERROR: division by zero 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT 0/0; 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions STATEMENT: SAVEPOINT two; 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:12.499 UTC client backend[45536] pg_regress/transactions STATEMENT: RELEASE SAVEPOINT one; 2025-11-30 18:45:12.503 UTC client backend[45566] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.503 UTC client backend[45566] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.504 UTC client backend[45566] ecpg/thread-thread_implicit LOG: connection ready: setup total=13.466 ms, fork=0.993 ms, authentication=0.121 ms 2025-11-30 18:45:12.504 UTC client backend[45536] pg_regress/transactions ERROR: division by zero 2025-11-30 18:45:12.504 UTC client backend[45536] pg_regress/transactions STATEMENT: FETCH 10 FROM c; 2025-11-30 18:45:12.504 UTC client backend[45536] pg_regress/transactions ERROR: portal "c" cannot be run 2025-11-30 18:45:12.504 UTC client backend[45536] pg_regress/transactions STATEMENT: FETCH 10 FROM c; 2025-11-30 18:45:12.505 UTC client backend[45536] pg_regress/transactions ERROR: portal "c" cannot be run 2025-11-30 18:45:12.505 UTC client backend[45536] pg_regress/transactions STATEMENT: FETCH 10 FROM c; 2025-11-30 18:45:12.508 UTC client backend[45533] pg_regress/select_distinct LOG: disconnection: session time: 0:00:00.366 user=postgres database=regression host=[local] 2025-11-30 18:45:12.511 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.511 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:12.511 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.511 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: update test_t set val2 = 2 where val2 = 1 and id = 10; 2025-11-30 18:45:12.513 UTC client backend[45530] pg_regress/union ERROR: invalid input syntax for type numeric: "foo" at character 36 2025-11-30 18:45:12.513 UTC client backend[45530] pg_regress/union STATEMENT: SELECT '3.4'::numeric UNION SELECT 'foo'; 2025-11-30 18:45:12.513 UTC unrecognized[45567] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.514 UTC client backend[45567] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.514 UTC client backend[45567] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.514 UTC client backend[45541] pg_regress/portals ERROR: cursor "c1" is not a simply updatable scan of table "uctest" 2025-11-30 18:45:12.514 UTC client backend[45541] pg_regress/portals STATEMENT: UPDATE uctest SET f1 = f1 + 10 WHERE CURRENT OF c1; 2025-11-30 18:45:12.515 UTC client backend[45567] ecpg/thread-thread_implicit LOG: connection ready: setup total=5.774 ms, fork=3.006 ms, authentication=0.113 ms 2025-11-30 18:45:12.524 UTC client backend[45541] pg_regress/portals ERROR: cursor "c1" has multiple FOR UPDATE/SHARE references to table "uctest" 2025-11-30 18:45:12.524 UTC client backend[45541] pg_regress/portals STATEMENT: UPDATE uctest SET f1 = f1 + 10 WHERE CURRENT OF c1; 2025-11-30 18:45:12.528 UTC unrecognized[45568] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.528 UTC client backend[45568] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.528 UTC client backend[45568] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.529 UTC client backend[45568] ecpg/thread-thread_implicit LOG: connection ready: setup total=3.289 ms, fork=1.278 ms, authentication=0.111 ms 2025-11-30 18:45:12.529 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.529 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on conflict out to pivot 13903, during read. 2025-11-30 18:45:12.529 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.529 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: select * from test_t where val2 = 1; 2025-11-30 18:45:12.530 UTC unrecognized[45569] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.530 UTC client backend[45569] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.530 UTC client backend[45569] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.531 UTC client backend[45569] ecpg/thread-thread_implicit LOG: connection ready: setup total=1.708 ms, fork=0.385 ms, authentication=0.100 ms 2025-11-30 18:45:12.534 UTC unrecognized[45570] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.535 UTC client backend[45570] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.535 UTC client backend[45570] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.536 UTC client backend[45570] ecpg/thread-thread_implicit LOG: connection ready: setup total=4.358 ms, fork=2.328 ms, authentication=0.111 ms 2025-11-30 18:45:12.537 UTC client backend[45536] pg_regress/transactions ERROR: duplicate key value violates unique constraint "koju_a_key" 2025-11-30 18:45:12.537 UTC client backend[45536] pg_regress/transactions DETAIL: Key (a)=(1) already exists. 2025-11-30 18:45:12.537 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO koju VALUES (1); 2025-11-30 18:45:12.537 UTC client backend[45541] pg_regress/portals ERROR: cursor "c1" does not exist 2025-11-30 18:45:12.537 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c1; 2025-11-30 18:45:12.540 UTC unrecognized[45571] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.540 UTC client backend[45571] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.540 UTC client backend[45571] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.541 UTC client backend[45571] ecpg/thread-thread_implicit LOG: connection ready: setup total=3.494 ms, fork=2.132 ms, authentication=0.108 ms 2025-11-30 18:45:12.542 UTC client backend[45541] pg_regress/portals ERROR: cursor "cx" is held from a previous transaction 2025-11-30 18:45:12.542 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF cx; 2025-11-30 18:45:12.545 UTC client backend[45541] pg_regress/portals ERROR: cursor "c" is not a simply updatable scan of table "uctest" 2025-11-30 18:45:12.545 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c; 2025-11-30 18:45:12.545 UTC unrecognized[45572] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.553 UTC client backend[45541] pg_regress/portals ERROR: cursor "c" does not have a FOR UPDATE/SHARE reference to table "uctest" 2025-11-30 18:45:12.553 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c; 2025-11-30 18:45:12.553 UTC client backend[45536] pg_regress/transactions ERROR: duplicate key value violates unique constraint "koju_a_key" 2025-11-30 18:45:12.553 UTC client backend[45536] pg_regress/transactions DETAIL: Key (a)=(1) already exists. 2025-11-30 18:45:12.553 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO koju VALUES (1); 2025-11-30 18:45:12.555 UTC client backend[45572] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.555 UTC client backend[45572] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.556 UTC client backend[45572] ecpg/thread-thread_implicit LOG: connection ready: setup total=14.777 ms, fork=3.255 ms, authentication=0.120 ms 2025-11-30 18:45:12.558 UTC client backend[45540] pg_regress/arrays ERROR: searching for elements in multidimensional arrays is not supported 2025-11-30 18:45:12.558 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT array_position(ARRAY[[1,2],[3,4]], 3); 2025-11-30 18:45:12.559 UTC client backend[45540] pg_regress/arrays ERROR: searching for elements in multidimensional arrays is not supported 2025-11-30 18:45:12.559 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT array_positions(ARRAY[[1,2],[3,4]], 4); 2025-11-30 18:45:12.559 UTC client backend[45541] pg_regress/portals ERROR: cursor "c" is not a simply updatable scan of table "tenk1" 2025-11-30 18:45:12.559 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM tenk1 WHERE CURRENT OF c; 2025-11-30 18:45:12.559 UTC client backend[45541] pg_regress/portals ERROR: cursor "c" is not a simply updatable scan of table "uctest" 2025-11-30 18:45:12.559 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c; 2025-11-30 18:45:12.560 UTC client backend[45541] pg_regress/portals ERROR: cursor "c1" is not positioned on a row 2025-11-30 18:45:12.560 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c1; 2025-11-30 18:45:12.560 UTC client backend[45541] pg_regress/portals ERROR: FOR UPDATE is not allowed with aggregate functions 2025-11-30 18:45:12.560 UTC client backend[45541] pg_regress/portals STATEMENT: DECLARE c1 CURSOR FOR SELECT MIN(f1) FROM uctest FOR UPDATE; 2025-11-30 18:45:12.566 UTC client backend[45541] pg_regress/portals ERROR: WHERE CURRENT OF on a view is not implemented 2025-11-30 18:45:12.566 UTC client backend[45541] pg_regress/portals STATEMENT: DELETE FROM ucview WHERE CURRENT OF c1; 2025-11-30 18:45:12.568 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.568 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.568 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.568 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.582 UTC unrecognized[45573] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.600 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 12 2025-11-30 18:45:12.600 UTC client backend[45539] pg_regress/aggregates STATEMENT: select max(min(unique1)) from tenk1; 2025-11-30 18:45:12.600 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 20 2025-11-30 18:45:12.600 UTC client backend[45539] pg_regress/aggregates STATEMENT: select (select max(min(unique1)) from int8_tbl) from tenk1; 2025-11-30 18:45:12.601 UTC client backend[45540] pg_regress/arrays ERROR: op ANY/ALL (array) requires operator to yield boolean at character 11 2025-11-30 18:45:12.601 UTC client backend[45540] pg_regress/arrays STATEMENT: select 33 * any ('{1,2,3}'); 2025-11-30 18:45:12.601 UTC client backend[45540] pg_regress/arrays ERROR: op ANY/ALL (array) requires array on right side at character 11 2025-11-30 18:45:12.601 UTC client backend[45540] pg_regress/arrays STATEMENT: select 33 * any (44); 2025-11-30 18:45:12.601 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 49 2025-11-30 18:45:12.601 UTC client backend[45539] 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-11-30 18:45:12.602 UTC client backend[45573] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.602 UTC client backend[45573] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.603 UTC client backend[45573] ecpg/thread-thread_implicit LOG: connection ready: setup total=24.081 ms, fork=1.111 ms, authentication=0.135 ms 2025-11-30 18:45:12.617 UTC unrecognized[45574] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.617 UTC client backend[45574] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.617 UTC client backend[45574] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.622 UTC client backend[45574] ecpg/thread-thread_implicit LOG: connection ready: setup total=18.838 ms, fork=13.077 ms, authentication=0.117 ms 2025-11-30 18:45:12.623 UTC client backend[45569] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.093 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.624 UTC client backend[45546] pg_regress/update ERROR: new row violates row-level security policy for table "range_parted" 2025-11-30 18:45:12.624 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 151 WHERE a = 'a' and c = 200; 2025-11-30 18:45:12.626 UTC client backend[45536] pg_regress/transactions ERROR: cursor "foo" does not exist 2025-11-30 18:45:12.626 UTC client backend[45536] pg_regress/transactions STATEMENT: fetch from foo; 2025-11-30 18:45:12.629 UTC unrecognized[45575] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.630 UTC client backend[45575] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.630 UTC client backend[45575] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.631 UTC client backend[45540] pg_regress/arrays ERROR: duplicate key value violates unique constraint "arr_tbl_f1_key" 2025-11-30 18:45:12.631 UTC client backend[45540] pg_regress/arrays DETAIL: Key (f1)=({1,2,3}) already exists. 2025-11-30 18:45:12.631 UTC client backend[45540] pg_regress/arrays STATEMENT: insert into arr_tbl values ('{1,2,3}'); 2025-11-30 18:45:12.631 UTC client backend[45575] ecpg/thread-thread_implicit LOG: connection ready: setup total=6.417 ms, fork=4.419 ms, authentication=0.110 ms 2025-11-30 18:45:12.635 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.635 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.635 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.635 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.640 UTC client backend[45541] pg_regress/portals LOG: disconnection: session time: 0:00:00.494 user=postgres database=regression host=[local] 2025-11-30 18:45:12.652 UTC client backend[45536] pg_regress/transactions ERROR: division by zero 2025-11-30 18:45:12.652 UTC client backend[45536] 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-11-30 18:45:12.652 UTC client backend[45536] pg_regress/transactions STATEMENT: FETCH ctt; 2025-11-30 18:45:12.652 UTC client backend[45536] pg_regress/transactions ERROR: portal "ctt" cannot be run 2025-11-30 18:45:12.652 UTC client backend[45536] pg_regress/transactions STATEMENT: FETCH ctt; 2025-11-30 18:45:12.654 UTC client backend[45536] pg_regress/transactions ERROR: invalid input syntax for type integer: "error" at character 31 2025-11-30 18:45:12.654 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES ('error'); 2025-11-30 18:45:12.654 UTC client backend[45536] pg_regress/transactions ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:12.654 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (3); 2025-11-30 18:45:12.661 UTC client backend[45536] pg_regress/transactions ERROR: invalid input syntax for type integer: "error" at character 31 2025-11-30 18:45:12.661 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES ('error'); 2025-11-30 18:45:12.663 UTC client backend[45536] pg_regress/transactions ERROR: invalid input syntax for type integer: "error" at character 31 2025-11-30 18:45:12.663 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES ('error'); 2025-11-30 18:45:12.663 UTC client backend[45536] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.663 UTC client backend[45536] pg_regress/transactions STATEMENT: COMMIT AND CHAIN; 2025-11-30 18:45:12.663 UTC client backend[45536] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.663 UTC client backend[45536] pg_regress/transactions STATEMENT: ROLLBACK AND CHAIN; 2025-11-30 18:45:12.675 UTC client backend[45536] pg_regress/transactions ERROR: division by zero 2025-11-30 18:45:12.675 UTC client backend[45536] pg_regress/transactions STATEMENT: insert into i_table values(2); select * from i_table; select 1/0; 2025-11-30 18:45:12.676 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.676 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.676 UTC client backend[45532] pg_regress/subselect ERROR: operator does not exist: bigint = text at character 33 2025-11-30 18:45:12.676 UTC client backend[45532] pg_regress/subselect DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:12.676 UTC client backend[45532] pg_regress/subselect HINT: You might need to add explicit type casts. 2025-11-30 18:45:12.676 UTC client backend[45532] pg_regress/subselect STATEMENT: select * from int8_tbl where q1 in (select c1 from inner_text); 2025-11-30 18:45:12.676 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions ERROR: division by zero 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions STATEMENT: insert into i_table values(7); commit; insert into i_table values(8); select 1/0; 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.677 UTC client backend[45540] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-11-30 18:45:12.677 UTC client backend[45540] pg_regress/arrays STATEMENT: update arr_pk_tbl set f1[2147483647] = 42 where pk = 10; 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions ERROR: VACUUM cannot run inside a transaction block 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT 1; VACUUM; 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions ERROR: VACUUM cannot run inside a transaction block 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT 1; COMMIT; VACUUM; 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions ERROR: SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT 1; SAVEPOINT sp; 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions ERROR: SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:12.677 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT 1; COMMIT; SAVEPOINT sp; 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions ERROR: ROLLBACK TO SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions STATEMENT: ROLLBACK TO SAVEPOINT sp; SELECT 2; 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions ERROR: RELEASE SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions STATEMENT: SELECT 2; RELEASE SAVEPOINT sp; SELECT 3; 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions STATEMENT: SET TRANSACTION READ ONLY; COMMIT AND CHAIN; 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.678 UTC client backend[45536] pg_regress/transactions STATEMENT: SET TRANSACTION READ ONLY; ROLLBACK AND CHAIN; 2025-11-30 18:45:12.678 UTC client backend[45540] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-11-30 18:45:12.678 UTC client backend[45540] pg_regress/arrays STATEMENT: update arr_pk_tbl set f1[2147483646:2147483647] = array[4,2] where pk = 10; 2025-11-30 18:45:12.678 UTC client backend[45540] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-11-30 18:45:12.678 UTC client backend[45540] pg_regress/arrays STATEMENT: insert into arr_pk_tbl(pk, f1[0:2147483647]) values (2, '{}'); 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (7); COMMIT; INSERT INTO trans_abc VALUES (8); COMMIT AND CHAIN; 2025-11-30 18:45:12.679 UTC client backend[45540] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-11-30 18:45:12.679 UTC client backend[45540] pg_regress/arrays STATEMENT: insert into arr_pk_tbl(pk, f1[-2147483648:2147483647]) values (2, '{}'); 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions WARNING: there is no transaction in progress 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (9); ROLLBACK; INSERT INTO trans_abc VALUES (10); ROLLBACK AND CHAIN; 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (11); COMMIT AND CHAIN; INSERT INTO trans_abc VALUES (12); COMMIT; 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.679 UTC client backend[45536] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (13); ROLLBACK AND CHAIN; INSERT INTO trans_abc VALUES (14); ROLLBACK; 2025-11-30 18:45:12.679 UTC client backend[45540] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-11-30 18:45:12.679 UTC client backend[45540] pg_regress/arrays CONTEXT: PL/pgSQL function inline_code_block line 4 at assignment 2025-11-30 18:45:12.679 UTC client backend[45540] pg_regress/arrays STATEMENT: do $$ declare a int[]; begin a := '[-2147483648:-2147483647]={1,2}'::int[]; a[2147483647] := 42; end $$; 2025-11-30 18:45:12.681 UTC client backend[45536] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.681 UTC client backend[45536] 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-11-30 18:45:12.681 UTC client backend[45536] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-11-30 18:45:12.681 UTC client backend[45536] 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-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions ERROR: invalid snapshot identifier: "Incorrect Identifier" 2025-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions STATEMENT: SET TRANSACTION SNAPSHOT 'Incorrect Identifier'; 2025-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions ERROR: snapshot "FFF-FFF-F" does not exist 2025-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions STATEMENT: SET TRANSACTION SNAPSHOT 'FFF-FFF-F'; 2025-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions ERROR: division by zero 2025-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions STATEMENT: select 1/0; 2025-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions ERROR: savepoint "x" does not exist 2025-11-30 18:45:12.683 UTC client backend[45536] pg_regress/transactions STATEMENT: rollback to X; 2025-11-30 18:45:12.683 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{1,{2}},{2,3}}" at character 8 2025-11-30 18:45:12.683 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.683 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{1,{2}},{2,3}}'::text[]; 2025-11-30 18:45:12.684 UTC client backend[45536] pg_regress/transactions LOG: disconnection: session time: 0:00:00.540 user=postgres database=regression host=[local] 2025-11-30 18:45:12.684 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{1,2},\{2,3}}" at character 8 2025-11-30 18:45:12.684 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.684 UTC client backend[45540] pg_regress/arrays STATEMENT: select E'{{1,2},\\{2,3}}'::text[]; 2025-11-30 18:45:12.687 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{"a"b}" at character 8 2025-11-30 18:45:12.687 UTC client backend[45540] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-11-30 18:45:12.687 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{"a"b}'::text[]; 2025-11-30 18:45:12.688 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{a"b"}" at character 8 2025-11-30 18:45:12.688 UTC client backend[45540] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-11-30 18:45:12.688 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{a"b"}'::text[]; 2025-11-30 18:45:12.691 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{"a""b"}" at character 8 2025-11-30 18:45:12.691 UTC client backend[45540] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-11-30 18:45:12.691 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{"a""b"}'::text[]; 2025-11-30 18:45:12.696 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{"1 2" x},{3}}" at character 8 2025-11-30 18:45:12.696 UTC client backend[45540] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-11-30 18:45:12.696 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{"1 2" x},{3}}'::text[]; 2025-11-30 18:45:12.698 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{"1 2"} x,{3}}" at character 8 2025-11-30 18:45:12.698 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected array element. 2025-11-30 18:45:12.698 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{"1 2"} x,{3}}'::text[]; 2025-11-30 18:45:12.699 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{}}" at character 8 2025-11-30 18:45:12.699 UTC client backend[45540] pg_regress/arrays DETAIL: Junk after closing right brace. 2025-11-30 18:45:12.699 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{}}'::text[]; 2025-11-30 18:45:12.700 UTC client backend[45546] pg_regress/update ERROR: new row violates row-level security policy for table "range_parted" 2025-11-30 18:45:12.700 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 150 WHERE a = 'a' and c = 200; 2025-11-30 18:45:12.701 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{ }}" at character 8 2025-11-30 18:45:12.701 UTC client backend[45540] pg_regress/arrays DETAIL: Junk after closing right brace. 2025-11-30 18:45:12.701 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{ }}'::text[]; 2025-11-30 18:45:12.701 UTC client backend[45570] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.167 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.702 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "}{" at character 8 2025-11-30 18:45:12.702 UTC client backend[45540] pg_regress/arrays DETAIL: Array value must start with "{" or dimension information. 2025-11-30 18:45:12.702 UTC client backend[45540] pg_regress/arrays STATEMENT: select '}{'::text[]; 2025-11-30 18:45:12.702 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{foo{}}" at character 8 2025-11-30 18:45:12.702 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected "{" character. 2025-11-30 18:45:12.702 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{foo{}}'::text[]; 2025-11-30 18:45:12.702 UTC client backend[45567] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.190 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.703 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.703 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.703 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.703 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.703 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{"foo"{}}" at character 8 2025-11-30 18:45:12.703 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected "{" character. 2025-11-30 18:45:12.703 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{"foo"{}}'::text[]; 2025-11-30 18:45:12.704 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{foo,,bar}" at character 8 2025-11-30 18:45:12.704 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected "," character. 2025-11-30 18:45:12.704 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{foo,,bar}'::text[]; 2025-11-30 18:45:12.707 UTC client backend[45539] pg_regress/aggregates ERROR: column "t1.c" must appear in the GROUP BY clause or be used in an aggregate function at character 40 2025-11-30 18:45:12.707 UTC client backend[45539] pg_regress/aggregates STATEMENT: EXPLAIN (COSTS OFF) SELECT a, SUM(b) + c FROM t1 GROUP BY ALL; 2025-11-30 18:45:12.707 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{1},{{2}}}" at character 8 2025-11-30 18:45:12.707 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.707 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{1},{{2}}}'::text[]; 2025-11-30 18:45:12.708 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{{1}},{2}}" at character 8 2025-11-30 18:45:12.708 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.708 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{{1}},{2}}'::text[]; 2025-11-30 18:45:12.708 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{},{{}}}" at character 8 2025-11-30 18:45:12.708 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.708 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{},{{}}}'::text[]; 2025-11-30 18:45:12.708 UTC client backend[45571] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.168 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{{}},{}}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{{}},{}}'::text[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{1},{}}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{1},{}}'::text[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{},{1}}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{},{1}}'::text[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: upper bound cannot be less than lower bound at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[1:0]={}'::int[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: array upper bound is too large: 2147483647 at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[2147483646:2147483647]={1,2}'::int[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: upper bound cannot be less than lower bound at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[1:-1]={}'::int[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "[2]={1}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Specified array dimensions do not match array contents. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[2]={1}'::int[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "[1:]={1}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Missing array dimension value. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[1:]={1}'::int[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "[:1]={1}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: "[" must introduce explicitly-specified array dimensions. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[:1]={1}'::int[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: cannot determine type of empty array at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays HINT: Explicitly cast to the desired type, for example ARRAY[]::integer[]. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select array[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{1,},{1},}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{1,},{1},}'::text[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{1,},{1}}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{1,},{1}}'::text[]; 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{{1,}}" at character 8 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-11-30 18:45:12.709 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{{1,}}'::text[]; 2025-11-30 18:45:12.710 UTC client backend[45540] pg_regress/arrays ERROR: malformed array literal: "{1,}" at character 8 2025-11-30 18:45:12.710 UTC client backend[45540] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-11-30 18:45:12.710 UTC client backend[45540] pg_regress/arrays STATEMENT: select '{1,}'::text[]; 2025-11-30 18:45:12.710 UTC client backend[45540] pg_regress/arrays ERROR: array bound is out of integer range at character 8 2025-11-30 18:45:12.710 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[21474836488:21474836489]={1,2}'::int[]; 2025-11-30 18:45:12.710 UTC client backend[45540] pg_regress/arrays ERROR: array bound is out of integer range at character 8 2025-11-30 18:45:12.710 UTC client backend[45540] pg_regress/arrays STATEMENT: select '[-2147483649:-2147483648]={1,2}'::int[]; 2025-11-30 18:45:12.719 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:12.722 UTC client backend[45568] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.195 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.728 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.728 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.728 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.728 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays ERROR: dimension array or low bound array cannot be null 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_fill(1, null, array[2,2]); 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays ERROR: dimension array or low bound array cannot be null 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_fill(1, array[2,2], null); 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays ERROR: wrong number of array subscripts 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays DETAIL: Low bound array has different size than dimensions array. 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_fill(1, array[2,2], '{}'); 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays ERROR: wrong number of array subscripts 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays DETAIL: Low bound array has different size than dimensions array. 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_fill(1, array[3,3], array[1,1,1]); 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays ERROR: dimension values cannot be null 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_fill(1, array[1,2,null]); 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays ERROR: wrong number of array subscripts 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays DETAIL: Dimension array must be one dimensional. 2025-11-30 18:45:12.734 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_fill(1, array[[1,2],[3,4]]); 2025-11-30 18:45:12.737 UTC client backend[45539] 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-11-30 18:45:12.737 UTC client backend[45539] pg_regress/aggregates STATEMENT: select t1.f1 from t1 left join t2 using (f1) group by f1; 2025-11-30 18:45:12.744 UTC client backend[45546] pg_regress/update ERROR: new row violates row-level security policy "policy_range_parted_subplan" for table "range_parted" 2025-11-30 18:45:12.744 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 122 WHERE a = 'a' and c = 200; 2025-11-30 18:45:12.745 UTC client backend[45540] pg_regress/arrays ERROR: cannot accumulate empty arrays 2025-11-30 18:45:12.745 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_agg('{}'::int[]) from generate_series(1,2); 2025-11-30 18:45:12.745 UTC client backend[45540] pg_regress/arrays ERROR: cannot accumulate null arrays 2025-11-30 18:45:12.745 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_agg(null::int[]) from generate_series(1,2); 2025-11-30 18:45:12.745 UTC client backend[45540] pg_regress/arrays ERROR: cannot accumulate arrays of different dimensionality 2025-11-30 18:45:12.745 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_agg(ar) from (values ('{1,2}'::int[]), ('{3}'::int[])) v(ar); 2025-11-30 18:45:12.747 UTC client backend[45540] pg_regress/arrays ERROR: removing elements from multidimensional arrays is not supported 2025-11-30 18:45:12.747 UTC client backend[45540] pg_regress/arrays STATEMENT: select array_remove('{{1,2,2},{1,4,3}}', 2); 2025-11-30 18:45:12.750 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.750 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:12.750 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.750 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: update test_t set val2 = 2 where val2 = 1 and id = 10; 2025-11-30 18:45:12.751 UTC client backend[45566] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.259 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.766 UTC checkpointer[43405] LOG: checkpoint complete: wrote 11041 buffers (67.4%), wrote 6 SLRU buffers; 0 WAL file(s) added, 0 removed, 19 recycled; write=0.040 s, sync=0.002 s, total=0.048 s; sync files=0, longest=0.000 s, average=0.000 s; distance=315168 kB, estimate=315168 kB; lsn=0/2BDD96B0, redo lsn=0/2BC6F6F0 2025-11-30 18:45:12.776 UTC client backend[45573] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.196 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.781 UTC client backend[45530] pg_regress/union LOG: disconnection: session time: 0:00:00.636 user=postgres database=regression host=[local] 2025-11-30 18:45:12.791 UTC client backend[45554] isolation/partial-index/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.791 UTC client backend[45554] isolation/partial-index/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.791 UTC client backend[45554] isolation/partial-index/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.791 UTC client backend[45554] isolation/partial-index/s2 STATEMENT: COMMIT; 2025-11-30 18:45:12.797 UTC client backend[45539] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 39 2025-11-30 18:45:12.797 UTC client backend[45539] 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-11-30 18:45:12.798 UTC client backend[45539] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 41 2025-11-30 18:45:12.798 UTC client backend[45539] 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-11-30 18:45:12.798 UTC client backend[45539] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 43 2025-11-30 18:45:12.798 UTC client backend[45539] 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-11-30 18:45:12.798 UTC client backend[45539] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 41 2025-11-30 18:45:12.798 UTC client backend[45539] 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-11-30 18:45:12.799 UTC client backend[45539] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 51 2025-11-30 18:45:12.799 UTC client backend[45539] pg_regress/aggregates STATEMENT: select string_agg(distinct f1::text, ',' order by f1) from varchar_tbl; 2025-11-30 18:45:12.799 UTC client backend[45539] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 45 2025-11-30 18:45:12.799 UTC client backend[45539] pg_regress/aggregates STATEMENT: select string_agg(distinct f1, ',' order by f1::text) from varchar_tbl; 2025-11-30 18:45:12.811 UTC client backend[45575] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.181 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.811 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.811 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:12.811 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.811 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: COMMIT; 2025-11-30 18:45:12.813 UTC client backend[45574] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.196 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.814 UTC client backend[45572] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.269 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.817 UTC unrecognized[45576] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.817 UTC client backend[45576] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.817 UTC client backend[45576] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-thread_implicit 2025-11-30 18:45:12.818 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:12.818 UTC client backend[45576] ecpg/thread-thread_implicit LOG: connection ready: setup total=2.746 ms, fork=1.253 ms, authentication=0.111 ms 2025-11-30 18:45:12.819 UTC checkpointer[43405] LOG: checkpoint complete: wrote 304 buffers (1.9%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 1 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=4045 kB, estimate=284056 kB; lsn=0/2C082530, redo lsn=0/2C062DE8 2025-11-30 18:45:12.820 UTC client backend[45576] ecpg/thread-thread_implicit LOG: disconnection: session time: 0:00:00.003 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays ERROR: function width_bucket(text, integer[]) does not exist at character 8 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays HINT: You might need to add explicit type casts. 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT width_bucket('5'::text, ARRAY[3, 4]::integer[]); 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays ERROR: thresholds array must not contain NULLs 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT width_bucket(5, ARRAY[3, 4, NULL]); 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays ERROR: thresholds must be one-dimensional array 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT width_bucket(5, ARRAY[ARRAY[1, 2], ARRAY[3, 4]]); 2025-11-30 18:45:12.827 UTC client backend[45546] pg_regress/update ERROR: new row violates row-level security policy "policy_range_parted_wholerow" for table "range_parted" 2025-11-30 18:45:12.827 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 116 WHERE a = 'a' and c = 200; 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays ERROR: number of elements to trim must be between 0 and 3 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT trim_array(ARRAY[1, 2, 3], -1); 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays ERROR: number of elements to trim must be between 0 and 3 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT trim_array(ARRAY[1, 2, 3], 10); 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays ERROR: number of elements to trim must be between 0 and 0 2025-11-30 18:45:12.827 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT trim_array(ARRAY[]::int[], 1); 2025-11-30 18:45:12.828 UTC client backend[45540] pg_regress/arrays ERROR: sample size must be between 0 and 6 2025-11-30 18:45:12.828 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT array_sample('{1,2,3,4,5,6}'::int[], -1); 2025-11-30 18:45:12.828 UTC client backend[45540] pg_regress/arrays ERROR: sample size must be between 0 and 6 2025-11-30 18:45:12.828 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT array_sample('{1,2,3,4,5,6}'::int[], 7); 2025-11-30 18:45:12.832 UTC client backend[45540] pg_regress/arrays ERROR: could not identify a comparison function for type xid 2025-11-30 18:45:12.832 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT array_sort('{1,2,3}'::xid[]); 2025-11-30 18:45:12.833 UTC client backend[45540] pg_regress/arrays ERROR: could not identify a comparison function for type xid 2025-11-30 18:45:12.833 UTC client backend[45540] pg_regress/arrays STATEMENT: SELECT array_sort('{{1,2,3},{2,3,4}}'::xid[]); 2025-11-30 18:45:12.838 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:12.839 UTC checkpointer[43405] LOG: checkpoint complete: wrote 229 buffers (1.4%), 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=1865 kB, estimate=255837 kB; lsn=0/2C24F3A0, redo lsn=0/2C235320 2025-11-30 18:45:12.844 UTC client backend[45540] pg_regress/arrays LOG: disconnection: session time: 0:00:00.700 user=postgres database=regression host=[local] 2025-11-30 18:45:12.852 UTC client backend[45544] pg_regress/hash_index ERROR: value 9 out of bounds for option "fillfactor" 2025-11-30 18:45:12.852 UTC client backend[45544] pg_regress/hash_index DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:12.852 UTC client backend[45544] pg_regress/hash_index STATEMENT: CREATE INDEX hash_f8_index2 ON hash_f8_heap USING hash (random float8_ops) WITH (fillfactor=9); 2025-11-30 18:45:12.852 UTC client backend[45544] pg_regress/hash_index ERROR: value 101 out of bounds for option "fillfactor" 2025-11-30 18:45:12.852 UTC client backend[45544] pg_regress/hash_index DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:12.852 UTC client backend[45544] pg_regress/hash_index STATEMENT: CREATE INDEX hash_f8_index2 ON hash_f8_heap USING hash (random float8_ops) WITH (fillfactor=101); 2025-11-30 18:45:12.852 UTC client backend[45544] pg_regress/hash_index LOG: disconnection: session time: 0:00:00.693 user=postgres database=regression host=[local] 2025-11-30 18:45:12.857 UTC client backend[45553] isolation/partial-index/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:12.857 UTC client backend[45553] isolation/partial-index/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:12.857 UTC client backend[45553] isolation/partial-index/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:12.857 UTC client backend[45553] isolation/partial-index/s1 STATEMENT: update test_t set val2 = 2 where val2 = 1 and id = 10; 2025-11-30 18:45:12.872 UTC unrecognized[45584] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.873 UTC client backend[45584] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.873 UTC client backend[45584] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.874 UTC client backend[45584] ecpg/thread-prep LOG: connection ready: setup total=2.938 ms, fork=0.924 ms, authentication=0.114 ms 2025-11-30 18:45:12.876 UTC client backend[45584] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.004 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.878 UTC client backend[45553] isolation/partial-index/s1 LOG: disconnection: session time: 0:00:00.690 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:12.878 UTC client backend[45554] isolation/partial-index/s2 LOG: disconnection: session time: 0:00:00.683 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:12.881 UTC unrecognized[45589] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.882 UTC client backend[45589] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.882 UTC client backend[45589] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.882 UTC client backend[45589] ecpg/thread-prep LOG: connection ready: setup total=1.723 ms, fork=0.370 ms, authentication=0.102 ms 2025-11-30 18:45:12.884 UTC client backend[45538] pg_regress/join ERROR: column t1.x does not exist at character 8 2025-11-30 18:45:12.884 UTC client backend[45538] pg_regress/join HINT: Perhaps you meant to reference the column "t3.x". 2025-11-30 18:45:12.884 UTC client backend[45538] pg_regress/join STATEMENT: select t1.x from t1 join t3 on (t1.a = t3.x); 2025-11-30 18:45:12.884 UTC unrecognized[45591] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.886 UTC client backend[45591] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.886 UTC client backend[45591] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.887 UTC client backend[45591] ecpg/thread-prep LOG: connection ready: setup total=2.931 ms, fork=0.271 ms, authentication=0.104 ms 2025-11-30 18:45:12.889 UTC unrecognized[45592] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.890 UTC client backend[45538] pg_regress/join ERROR: FOR UPDATE cannot be applied to a join at character 101 2025-11-30 18:45:12.890 UTC client backend[45538] 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-11-30 18:45:12.890 UTC client backend[45592] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.890 UTC client backend[45592] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.890 UTC client backend[45538] pg_regress/join ERROR: relation "foo" in FOR UPDATE clause not found in FROM clause at character 110 2025-11-30 18:45:12.890 UTC client backend[45538] 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-11-30 18:45:12.890 UTC client backend[45538] pg_regress/join ERROR: FOR UPDATE cannot be applied to a join at character 110 2025-11-30 18:45:12.890 UTC client backend[45538] 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-11-30 18:45:12.891 UTC client backend[45592] ecpg/thread-prep LOG: connection ready: setup total=1.864 ms, fork=0.574 ms, authentication=0.098 ms 2025-11-30 18:45:12.900 UTC client backend[45552] isolation/partial-index/control connection LOG: disconnection: session time: 0:00:00.734 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:12.901 UTC unrecognized[45590] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.902 UTC client backend[45590] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.902 UTC client backend[45590] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/two-ids 2025-11-30 18:45:12.902 UTC client backend[45590] isolation/two-ids LOG: connection ready: setup total=19.773 ms, fork=2.079 ms, authentication=0.122 ms 2025-11-30 18:45:12.903 UTC unrecognized[45593] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.904 UTC client backend[45593] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.904 UTC client backend[45593] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.904 UTC unrecognized[45594] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.905 UTC client backend[45594] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.905 UTC client backend[45594] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/two-ids 2025-11-30 18:45:12.905 UTC client backend[45593] ecpg/thread-prep LOG: connection ready: setup total=13.963 ms, fork=11.807 ms, authentication=0.108 ms 2025-11-30 18:45:12.905 UTC client backend[45594] isolation/two-ids LOG: connection ready: setup total=1.763 ms, fork=0.428 ms, authentication=0.103 ms 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate functions are not allowed in FILTER at character 35 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates STATEMENT: select max(unique1) filter (where sum(ten) > 0) from tenk1; 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 43 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates STATEMENT: select (select max(unique1) filter (where sum(ten) > 0) from int8_tbl) from tenk1; 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate functions are not allowed in FILTER at character 35 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates STATEMENT: select max(unique1) filter (where bool_or(ten > 0)) from tenk1; 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 43 2025-11-30 18:45:12.906 UTC client backend[45539] pg_regress/aggregates STATEMENT: select (select max(unique1) filter (where bool_or(ten > 0)) from int8_tbl) from tenk1; 2025-11-30 18:45:12.907 UTC client backend[45539] pg_regress/aggregates ERROR: cannot use multiple ORDER BY clauses with WITHIN GROUP at character 41 2025-11-30 18:45:12.907 UTC client backend[45539] 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-11-30 18:45:12.907 UTC client backend[45539] pg_regress/aggregates ERROR: sum is not an ordered-set aggregate, so it cannot have WITHIN GROUP at character 11 2025-11-30 18:45:12.907 UTC client backend[45539] 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-11-30 18:45:12.907 UTC unrecognized[45595] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.907 UTC unrecognized[45596] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.908 UTC client backend[45595] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.908 UTC client backend[45595] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.908 UTC client backend[45596] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.908 UTC client backend[45596] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/two-ids 2025-11-30 18:45:12.909 UTC client backend[45595] ecpg/thread-prep LOG: connection ready: setup total=2.140 ms, fork=0.686 ms, authentication=0.118 ms 2025-11-30 18:45:12.909 UTC client backend[45539] pg_regress/aggregates ERROR: WITHIN GROUP is required for ordered-set aggregate percentile_cont at character 11 2025-11-30 18:45:12.909 UTC client backend[45539] 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-11-30 18:45:12.910 UTC client backend[45596] isolation/two-ids LOG: connection ready: setup total=2.964 ms, fork=0.641 ms, authentication=0.101 ms 2025-11-30 18:45:12.929 UTC client backend[45539] 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-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates DETAIL: Direct arguments of an ordered-set aggregate must use only grouped columns. 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates STATEMENT: select rank(x) within group (order by x) from generate_series(1,5) x; 2025-11-30 18:45:12.929 UTC client backend[45532] pg_regress/subselect LOG: disconnection: session time: 0:00:00.785 user=postgres database=regression host=[local] 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates ERROR: outer-level aggregate cannot contain a lower-level variable in its direct arguments at character 37 2025-11-30 18:45:12.929 UTC client backend[45539] 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-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 13 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates STATEMENT: select rank(sum(x)) within group (order by x) from generate_series(1,5) x; 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates ERROR: WITHIN GROUP types text and integer cannot be matched at character 13 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates STATEMENT: select rank(3) within group (order by x) from (values ('fred'),('jim')) v(x); 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates ERROR: function rank(integer, name, name) does not exist at character 8 2025-11-30 18:45:12.929 UTC client backend[45539] 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-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates STATEMENT: select rank(3) within group (order by stringu1,stringu2) from tenk1; 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates ERROR: invalid input syntax for type integer: "fred" at character 13 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates STATEMENT: select rank('fred') within group (order by x) from generate_series(1,5) x; 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates ERROR: collation mismatch between explicit collations "C" and "POSIX" at character 64 2025-11-30 18:45:12.929 UTC client backend[45539] pg_regress/aggregates STATEMENT: select rank('adam'::text collate "C") within group (order by x collate "POSIX") from (values ('fred'),('jim')) v(x); 2025-11-30 18:45:12.932 UTC unrecognized[45597] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.932 UTC client backend[45597] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.932 UTC client backend[45597] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.933 UTC client backend[45597] ecpg/thread-prep LOG: connection ready: setup total=24.225 ms, fork=22.646 ms, authentication=0.114 ms 2025-11-30 18:45:12.933 UTC unrecognized[45598] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.934 UTC client backend[45598] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.934 UTC client backend[45598] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/two-ids 2025-11-30 18:45:12.934 UTC unrecognized[45599] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.934 UTC client backend[45599] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.934 UTC client backend[45599] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.935 UTC client backend[45598] isolation/two-ids LOG: connection ready: setup total=24.035 ms, fork=20.951 ms, authentication=0.109 ms 2025-11-30 18:45:12.935 UTC client backend[45599] ecpg/thread-prep LOG: connection ready: setup total=1.940 ms, fork=0.611 ms, authentication=0.101 ms 2025-11-30 18:45:12.937 UTC unrecognized[45600] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.937 UTC client backend[45600] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.937 UTC client backend[45600] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.938 UTC client backend[45600] ecpg/thread-prep LOG: connection ready: setup total=1.720 ms, fork=0.394 ms, authentication=0.111 ms 2025-11-30 18:45:12.940 UTC client backend[45546] pg_regress/update ERROR: new row for relation "part_def" violates partition constraint 2025-11-30 18:45:12.940 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (a, 9, null, null, null). 2025-11-30 18:45:12.940 UTC client backend[45546] pg_regress/update STATEMENT: update part_def set a = 'a' where a = 'd'; 2025-11-30 18:45:12.942 UTC client backend[45546] pg_regress/update ERROR: new row for relation "part_a_10_a_20" violates partition constraint 2025-11-30 18:45:12.942 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (ad, 10, 200, 1, null). 2025-11-30 18:45:12.942 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE part_a_10_a_20 set a = 'ad' WHERE a = 'a'; 2025-11-30 18:45:12.946 UTC unrecognized[45601] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.946 UTC client backend[45601] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.946 UTC client backend[45601] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.947 UTC client backend[45601] ecpg/thread-prep LOG: connection ready: setup total=9.076 ms, fork=7.043 ms, authentication=0.116 ms 2025-11-30 18:45:12.957 UTC unrecognized[45602] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.958 UTC client backend[45602] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.958 UTC client backend[45602] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.958 UTC client backend[45602] ecpg/thread-prep LOG: connection ready: setup total=10.804 ms, fork=9.178 ms, authentication=0.109 ms 2025-11-30 18:45:12.967 UTC client backend[45486] postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.967 UTC client backend[45486] postgres_fdw DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-11-30 18:45:12.967 UTC client backend[45486] postgres_fdw STATEMENT: INSERT INTO "S 1"."T 1"("C 1", c2, c3, c4, c5, c6, c7, c8) VALUES ($1, $2, $3, $4, $5, $6, $7, $8) 2025-11-30 18:45:12.967 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.967 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-11-30 18:45:12.967 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: INSERT INTO "S 1"."T 1"("C 1", c2, c3, c4, c5, c6, c7, c8) VALUES ($1, $2, $3, $4, $5, $6, $7, $8) 2025-11-30 18:45:12.967 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(1111, -2); 2025-11-30 18:45:12.973 UTC unrecognized[45603] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.973 UTC client backend[45603] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.973 UTC client backend[45603] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.974 UTC client backend[45603] ecpg/thread-prep LOG: connection ready: setup total=1.849 ms, fork=0.423 ms, authentication=0.113 ms 2025-11-30 18:45:12.975 UTC unrecognized[45604] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.976 UTC client backend[45604] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.976 UTC client backend[45604] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.977 UTC client backend[45604] ecpg/thread-prep LOG: connection ready: setup total=2.152 ms, fork=0.358 ms, authentication=0.108 ms 2025-11-30 18:45:12.977 UTC client backend[45546] pg_regress/update ERROR: new row for relation "list_default" violates partition constraint 2025-11-30 18:45:12.977 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (a, 10). 2025-11-30 18:45:12.977 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE list_default set a = 'a' WHERE a = 'd'; 2025-11-30 18:45:12.978 UTC unrecognized[45605] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.978 UTC client backend[45605] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.978 UTC client backend[45605] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.979 UTC client backend[45605] ecpg/thread-prep LOG: connection ready: setup total=2.087 ms, fork=0.424 ms, authentication=0.107 ms 2025-11-30 18:45:12.982 UTC unrecognized[45606] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:12.987 UTC client backend[45606] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:12.987 UTC client backend[45606] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:12.988 UTC client backend[45606] ecpg/thread-prep LOG: connection ready: setup total=7.064 ms, fork=0.413 ms, authentication=0.124 ms 2025-11-30 18:45:12.993 UTC client backend[45589] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.111 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:12.998 UTC client backend[45486] postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.998 UTC client backend[45486] postgres_fdw DETAIL: Failing row contains (1, -1, 00001_trig_update, 1970-01-02 08:00:00+00, 1970-01-02 00:00:00, 1, 1 , foo). 2025-11-30 18:45:12.998 UTC client backend[45486] postgres_fdw STATEMENT: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-11-30 18:45:12.998 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-11-30 18:45:12.998 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (1, -1, 00001_trig_update, 1970-01-02 08:00:00+00, 1970-01-02 00:00:00, 1, 1 , foo). 2025-11-30 18:45:12.998 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-11-30 18:45:12.998 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: UPDATE ft1 SET c2 = -c2 WHERE c1 = 1; 2025-11-30 18:45:13.002 UTC client backend[45595] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.095 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.008 UTC unrecognized[45607] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.008 UTC client backend[45607] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.008 UTC client backend[45607] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:13.009 UTC client backend[45607] ecpg/thread-prep LOG: connection ready: setup total=5.172 ms, fork=2.625 ms, authentication=0.128 ms 2025-11-30 18:45:13.010 UTC unrecognized[45608] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.010 UTC client backend[45546] pg_regress/update ERROR: cannot retrieve a system column in this context 2025-11-30 18:45:13.010 UTC client backend[45546] pg_regress/update STATEMENT: insert into utrtest values (2, 'bar') returning *, tableoid::regclass, xmin = pg_current_xact_id()::xid as xmin_ok; 2025-11-30 18:45:13.011 UTC client backend[45608] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.011 UTC client backend[45608] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-prep 2025-11-30 18:45:13.012 UTC client backend[45608] ecpg/thread-prep LOG: connection ready: setup total=2.114 ms, fork=0.409 ms, authentication=0.116 ms 2025-11-30 18:45:13.012 UTC client backend[45592] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.122 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.014 UTC client backend[45599] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.079 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.014 UTC client backend[45600] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.076 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.015 UTC client backend[45593] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.112 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.016 UTC client backend[45591] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.131 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.017 UTC client backend[45603] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.044 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.019 UTC client backend[45546] pg_regress/update ERROR: cannot retrieve a system column in this context 2025-11-30 18:45:13.019 UTC client backend[45546] 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-11-30 18:45:13.023 UTC client backend[45607] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.016 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.029 UTC client backend[45608] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.019 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.036 UTC client backend[45604] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.061 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.041 UTC client backend[45606] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.059 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.041 UTC client backend[45601] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.095 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.044 UTC client backend[45605] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.066 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.055 UTC client backend[45597] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.123 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.063 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-11-30 18:45:13.063 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-11-30 18:45:13.063 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 5); 2025-11-30 18:45:13.065 UTC client backend[45546] pg_regress/update ERROR: new row for relation "sub_parted" violates partition constraint 2025-11-30 18:45:13.065 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (2, 2, 10). 2025-11-30 18:45:13.065 UTC client backend[45546] pg_regress/update STATEMENT: UPDATE sub_parted set a = 2 WHERE c = 10; 2025-11-30 18:45:13.070 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-11-30 18:45:13.070 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (20, 20). 2025-11-30 18:45:13.070 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: UPDATE rw_view SET b = b + 5; 2025-11-30 18:45:13.073 UTC client backend[45486] postgres_fdw LOG: disconnection: session time: 0:00:01.054 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.075 UTC unrecognized[45609] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.076 UTC client backend[45609] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.076 UTC client backend[45609] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.076 UTC client backend[45609] postgres_fdw LOG: connection ready: setup total=1.660 ms, fork=0.336 ms, authentication=0.112 ms 2025-11-30 18:45:13.078 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-11-30 18:45:13.078 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-11-30 18:45:13.078 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 15), (0, 5); 2025-11-30 18:45:13.080 UTC client backend[45602] ecpg/thread-prep LOG: disconnection: session time: 0:00:00.123 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.086 UTC client backend[45609] postgres_fdw LOG: disconnection: session time: 0:00:00.010 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.099 UTC client backend[45546] pg_regress/update ERROR: new row for relation "hpart1" violates partition constraint 2025-11-30 18:45:13.099 UTC client backend[45546] pg_regress/update DETAIL: Failing row contains (3, 4). 2025-11-30 18:45:13.099 UTC client backend[45546] pg_regress/update STATEMENT: update hpart1 set a = 3, b=4 where a = 1; 2025-11-30 18:45:13.104 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.104 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.104 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.104 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.114 UTC client backend[45546] pg_regress/update LOG: disconnection: session time: 0:00:00.955 user=postgres database=regression host=[local] 2025-11-30 18:45:13.118 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.118 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.118 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.118 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.123 UTC unrecognized[45623] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.123 UTC client backend[45623] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.123 UTC client backend[45623] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.124 UTC client backend[45623] ecpg/thread-alloc LOG: connection ready: setup total=2.503 ms, fork=0.586 ms, authentication=0.100 ms 2025-11-30 18:45:13.126 UTC unrecognized[45624] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.126 UTC client backend[45624] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.126 UTC client backend[45624] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.127 UTC client backend[45624] ecpg/thread-alloc LOG: connection ready: setup total=1.858 ms, fork=0.532 ms, authentication=0.109 ms 2025-11-30 18:45:13.145 UTC unrecognized[45625] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.145 UTC client backend[45625] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.145 UTC client backend[45625] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.146 UTC client backend[45625] ecpg/thread-alloc LOG: connection ready: setup total=17.919 ms, fork=16.597 ms, authentication=0.112 ms 2025-11-30 18:45:13.147 UTC unrecognized[45630] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.147 UTC client backend[45630] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.147 UTC client backend[45630] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.148 UTC client backend[45630] ecpg/thread-alloc LOG: connection ready: setup total=1.566 ms, fork=0.268 ms, authentication=0.097 ms 2025-11-30 18:45:13.149 UTC unrecognized[45631] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.149 UTC client backend[45631] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.149 UTC client backend[45631] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.150 UTC client backend[45631] ecpg/thread-alloc LOG: connection ready: setup total=1.538 ms, fork=0.270 ms, authentication=0.099 ms 2025-11-30 18:45:13.150 UTC unrecognized[45632] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.151 UTC client backend[45632] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.151 UTC client backend[45632] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.152 UTC client backend[45632] ecpg/thread-alloc LOG: connection ready: setup total=1.544 ms, fork=0.274 ms, authentication=0.099 ms 2025-11-30 18:45:13.152 UTC unrecognized[45633] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.153 UTC client backend[45633] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.153 UTC client backend[45633] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.154 UTC client backend[45633] ecpg/thread-alloc LOG: connection ready: setup total=1.784 ms, fork=0.450 ms, authentication=0.105 ms 2025-11-30 18:45:13.160 UTC unrecognized[45634] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.161 UTC client backend[45634] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.161 UTC client backend[45634] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.161 UTC client backend[45634] ecpg/thread-alloc LOG: connection ready: setup total=7.468 ms, fork=5.832 ms, authentication=0.114 ms 2025-11-30 18:45:13.162 UTC unrecognized[45635] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.163 UTC client backend[45635] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.163 UTC client backend[45635] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.163 UTC client backend[45635] ecpg/thread-alloc LOG: connection ready: setup total=1.686 ms, fork=0.340 ms, authentication=0.108 ms 2025-11-30 18:45:13.164 UTC client backend[45624] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.037 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.167 UTC unrecognized[45636] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.167 UTC client backend[45636] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.167 UTC client backend[45636] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.168 UTC client backend[45636] ecpg/thread-alloc LOG: connection ready: setup total=1.678 ms, fork=0.323 ms, authentication=0.113 ms 2025-11-30 18:45:13.170 UTC unrecognized[45638] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.171 UTC unrecognized[45637] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.172 UTC client backend[45637] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.172 UTC client backend[45637] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.172 UTC client backend[45637] ecpg/thread-alloc LOG: connection ready: setup total=4.116 ms, fork=2.103 ms, authentication=0.107 ms 2025-11-30 18:45:13.175 UTC unrecognized[45639] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.176 UTC client backend[45639] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.176 UTC client backend[45639] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.176 UTC client backend[45639] ecpg/thread-alloc LOG: connection ready: setup total=2.363 ms, fork=0.409 ms, authentication=0.105 ms 2025-11-30 18:45:13.177 UTC client backend[45638] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.177 UTC client backend[45638] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.178 UTC client backend[45638] postgres_fdw LOG: connection ready: setup total=8.378 ms, fork=0.334 ms, authentication=0.111 ms 2025-11-30 18:45:13.178 UTC unrecognized[45640] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.179 UTC client backend[45640] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.179 UTC client backend[45640] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.180 UTC client backend[45640] ecpg/thread-alloc LOG: connection ready: setup total=3.163 ms, fork=0.949 ms, authentication=0.103 ms 2025-11-30 18:45:13.192 UTC unrecognized[45641] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.192 UTC client backend[45641] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.192 UTC client backend[45641] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.193 UTC client backend[45641] ecpg/thread-alloc LOG: connection ready: setup total=12.787 ms, fork=10.958 ms, authentication=0.124 ms 2025-11-30 18:45:13.193 UTC client backend[45632] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.043 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.194 UTC client backend[45623] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.072 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.196 UTC unrecognized[45642] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.197 UTC client backend[45642] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.197 UTC client backend[45642] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.197 UTC client backend[45642] ecpg/thread-alloc LOG: connection ready: setup total=1.833 ms, fork=0.502 ms, authentication=0.102 ms 2025-11-30 18:45:13.198 UTC unrecognized[45643] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.199 UTC client backend[45643] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.199 UTC client backend[45643] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/thread-alloc 2025-11-30 18:45:13.200 UTC client backend[45643] ecpg/thread-alloc LOG: connection ready: setup total=1.918 ms, fork=0.423 ms, authentication=0.100 ms 2025-11-30 18:45:13.200 UTC client backend[45625] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.055 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.202 UTC client backend[45633] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.049 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.205 UTC client backend[45635] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.042 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.206 UTC client backend[45640] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.028 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.208 UTC client backend[45637] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.038 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.209 UTC client backend[45636] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.042 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.212 UTC client backend[45630] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.065 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.214 UTC client backend[45641] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.022 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.216 UTC client backend[45639] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.040 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.216 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-11-30 18:45:13.216 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-11-30 18:45:13.216 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 5); 2025-11-30 18:45:13.219 UTC client backend[45643] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.021 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.219 UTC client backend[45634] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.059 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.220 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.220 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.220 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.220 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.221 UTC client backend[45631] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.072 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.223 UTC client backend[45642] ecpg/thread-alloc LOG: disconnection: session time: 0:00:00.027 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.225 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-11-30 18:45:13.225 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (20, 20). 2025-11-30 18:45:13.225 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: UPDATE rw_view SET b = b + 5; 2025-11-30 18:45:13.228 UTC client backend[45638] postgres_fdw LOG: disconnection: session time: 0:00:00.058 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.252 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.252 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.252 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.252 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.262 UTC unrecognized[45648] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.262 UTC client backend[45648] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.262 UTC client backend[45648] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.263 UTC client backend[45648] postgres_fdw LOG: connection ready: setup total=3.158 ms, fork=1.838 ms, authentication=0.128 ms 2025-11-30 18:45:13.269 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-11-30 18:45:13.269 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-11-30 18:45:13.269 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 15), (0, 5); 2025-11-30 18:45:13.270 UTC client backend[45648] postgres_fdw LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.281 UTC unrecognized[45649] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.281 UTC client backend[45649] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.281 UTC client backend[45649] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.282 UTC client backend[45649] postgres_fdw LOG: connection ready: setup total=1.548 ms, fork=0.314 ms, authentication=0.111 ms 2025-11-30 18:45:13.319 UTC client backend[45649] postgres_fdw LOG: disconnection: session time: 0:00:00.038 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.322 UTC unrecognized[45652] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.322 UTC client backend[45652] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.322 UTC client backend[45652] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.323 UTC client backend[45652] postgres_fdw LOG: connection ready: setup total=2.073 ms, fork=0.773 ms, authentication=0.131 ms 2025-11-30 18:45:13.330 UTC unrecognized[45655] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.330 UTC client backend[45655] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.330 UTC client backend[45655] [unknown] LOG: connection authorized: user=postgres database=ecpg1_regression application_name=ecpg/sql-twophase 2025-11-30 18:45:13.331 UTC client backend[45655] ecpg/sql-twophase LOG: connection ready: setup total=1.864 ms, fork=0.413 ms, authentication=0.111 ms 2025-11-30 18:45:13.334 UTC client backend[45539] pg_regress/aggregates LOG: disconnection: session time: 0:00:01.190 user=postgres database=regression host=[local] 2025-11-30 18:45:13.337 UTC client backend[45655] ecpg/sql-twophase LOG: disconnection: session time: 0:00:00.007 user=postgres database=ecpg1_regression host=[local] 2025-11-30 18:45:13.355 UTC client backend[45652] postgres_fdw LOG: disconnection: session time: 0:00:00.032 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.358 UTC client backend[45538] pg_regress/join ERROR: column reference "f1" is ambiguous at character 78 2025-11-30 18:45:13.358 UTC client backend[45538] pg_regress/join STATEMENT: select * from int8_tbl x join (int4_tbl x cross join int4_tbl y) j on q1 = f1; 2025-11-30 18:45:13.358 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "y" at character 78 2025-11-30 18:45:13.358 UTC client backend[45538] pg_regress/join DETAIL: There is an entry for table "y", but it cannot be referenced from this part of the query. 2025-11-30 18:45:13.358 UTC client backend[45538] pg_regress/join STATEMENT: select * from int8_tbl x join (int4_tbl x cross join int4_tbl y) j on q1 = y.f1; 2025-11-30 18:45:13.360 UTC unrecognized[45659] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.360 UTC client backend[45659] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.360 UTC client backend[45659] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.361 UTC client backend[45659] postgres_fdw LOG: connection ready: setup total=1.624 ms, fork=0.331 ms, authentication=0.125 ms 2025-11-30 18:45:13.370 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.370 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.370 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.370 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.375 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.375 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.375 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.375 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.423 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.423 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.423 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.423 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.428 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.428 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.428 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.428 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.449 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.449 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.449 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.449 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.455 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.455 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.455 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.455 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join ERROR: column t1.uunique1 does not exist at character 8 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join HINT: Perhaps you meant to reference the column "t1.unique1". 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join STATEMENT: select t1.uunique1 from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join ERROR: column t2.uunique1 does not exist at character 8 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join HINT: Perhaps you meant to reference the column "t2.unique1". 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join STATEMENT: select t2.uunique1 from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join ERROR: column "uunique1" does not exist at character 8 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join HINT: Perhaps you meant to reference the column "t1.unique1" or the column "t2.unique1". 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join STATEMENT: select uunique1 from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join ERROR: column "ctid" does not exist at character 8 2025-11-30 18:45:13.457 UTC client backend[45538] 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-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join HINT: Try using a table-qualified name. 2025-11-30 18:45:13.457 UTC client backend[45538] pg_regress/join STATEMENT: select ctid from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-11-30 18:45:13.458 UTC client backend[45538] pg_regress/join ERROR: column atts.relid does not exist at character 8 2025-11-30 18:45:13.458 UTC client backend[45538] 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-11-30 18:45:13.485 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.485 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO parent_tbl VALUES ('AAA', 42); 2025-11-30 18:45:13.486 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.486 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: COPY parent_tbl, line 1: "AAA 42" 2025-11-30 18:45:13.486 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: COPY parent_tbl (a, b) FROM stdin; 2025-11-30 18:45:13.486 UTC client backend[45659] postgres_fdw LOG: disconnection: session time: 0:00:00.126 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.488 UTC unrecognized[45660] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.488 UTC client backend[45660] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.488 UTC client backend[45660] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.489 UTC client backend[45660] postgres_fdw LOG: connection ready: setup total=1.746 ms, fork=0.401 ms, authentication=0.120 ms 2025-11-30 18:45:13.489 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.489 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: INSERT INTO parent_tbl VALUES ('AAA', 42); 2025-11-30 18:45:13.490 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.490 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: COPY parent_tbl, line 1: "AAA 42" 2025-11-30 18:45:13.490 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: COPY parent_tbl (a, b) FROM stdin; 2025-11-30 18:45:13.490 UTC client backend[45660] postgres_fdw LOG: disconnection: session time: 0:00:00.002 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:13.493 UTC unrecognized[45661] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.493 UTC client backend[45661] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.493 UTC client backend[45661] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:13.494 UTC client backend[45661] postgres_fdw LOG: connection ready: setup total=1.484 ms, fork=0.287 ms, authentication=0.106 ms 2025-11-30 18:45:13.496 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.496 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: UPDATE parent_tbl SET b = b + 1; 2025-11-30 18:45:13.497 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.497 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: DELETE FROM parent_tbl; 2025-11-30 18:45:13.505 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.505 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: UPDATE parent_tbl SET b = b + 1; 2025-11-30 18:45:13.506 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot collect transition tuples from child foreign tables 2025-11-30 18:45:13.506 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: DELETE FROM parent_tbl; 2025-11-30 18:45:13.515 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.515 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.515 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.515 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.517 UTC client backend[45538] pg_regress/join ERROR: join expression "ss" has 3 columns available but 4 columns specified 2025-11-30 18:45:13.517 UTC client backend[45538] pg_regress/join STATEMENT: SELECT * FROM (int8_tbl i cross join int4_tbl j) ss(a,b,c,d); 2025-11-30 18:45:13.519 UTC client backend[45538] pg_regress/join ERROR: column "f1" does not exist at character 38 2025-11-30 18:45:13.519 UTC client backend[45538] 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-11-30 18:45:13.519 UTC client backend[45538] pg_regress/join HINT: To reference that column, you must mark this subquery with LATERAL. 2025-11-30 18:45:13.519 UTC client backend[45538] pg_regress/join STATEMENT: select f1,g from int4_tbl a, (select f1 as g) ss; 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 38 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join DETAIL: There is an entry for table "a", but it cannot be referenced from this part of the query. 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join HINT: To reference that table, you must mark this subquery with LATERAL. 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join STATEMENT: select f1,g from int4_tbl a, (select a.f1 as g) ss; 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join ERROR: column "f1" does not exist at character 48 2025-11-30 18:45:13.520 UTC client backend[45538] 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-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join HINT: To reference that column, you must mark this subquery with LATERAL. 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join STATEMENT: select f1,g from int4_tbl a cross join (select f1 as g) ss; 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 48 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join DETAIL: There is an entry for table "a", but it cannot be referenced from this part of the query. 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join HINT: To reference that table, you must mark this subquery with LATERAL. 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join STATEMENT: select f1,g from int4_tbl a cross join (select a.f1 as g) ss; 2025-11-30 18:45:13.520 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.520 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.520 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.520 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 67 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join DETAIL: The combining JOIN type must be INNER or LEFT for a LATERAL reference. 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join STATEMENT: select f1,g from int4_tbl a right join lateral generate_series(0, a.f1) g on true; 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 66 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join DETAIL: The combining JOIN type must be INNER or LEFT for a LATERAL reference. 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join STATEMENT: select f1,g from int4_tbl a full join lateral generate_series(0, a.f1) g on true; 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join ERROR: table reference "x" is ambiguous at character 78 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join STATEMENT: select * from int8_tbl x cross join (int4_tbl x cross join lateral (select x.f1) ss); 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 40 2025-11-30 18:45:13.520 UTC client backend[45538] pg_regress/join STATEMENT: select 1 from tenk1 a, lateral (select max(a.unique1) from int4_tbl b) ss; 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join ERROR: column "x1" does not exist at character 64 2025-11-30 18:45:13.521 UTC client backend[45538] 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-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join STATEMENT: update xx1 set x2 = f1 from (select * from int4_tbl where f1 = x1) ss; 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 64 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join DETAIL: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join STATEMENT: update xx1 set x2 = f1 from (select * from int4_tbl where f1 = xx1.x1) ss; 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 72 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join HINT: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join STATEMENT: update xx1 set x2 = f1 from lateral (select * from int4_tbl where f1 = x1) ss; 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join ERROR: table name "xx1" specified more than once 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join STATEMENT: update xx1 set x2 = f1 from xx1, lateral (select * from int4_tbl where f1 = x1) ss; 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join ERROR: column "x1" does not exist at character 58 2025-11-30 18:45:13.521 UTC client backend[45538] 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-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join STATEMENT: delete from xx1 using (select * from int4_tbl where f1 = x1) ss; 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 58 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join DETAIL: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join STATEMENT: delete from xx1 using (select * from int4_tbl where f1 = xx1.x1) ss; 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 66 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join HINT: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-11-30 18:45:13.521 UTC client backend[45538] pg_regress/join STATEMENT: delete from xx1 using lateral (select * from int4_tbl where f1 = x1) ss; 2025-11-30 18:45:13.593 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.593 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.593 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.593 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.596 UTC client backend[44596] pg_regress/postgres_fdw ERROR: WHERE CURRENT OF is not supported for this table type 2025-11-30 18:45:13.596 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update bar set f2 = null where current of c; 2025-11-30 18:45:13.599 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.599 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.599 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.599 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.641 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.641 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.641 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.641 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.646 UTC client backend[45596] isolation/two-ids/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:13.646 UTC client backend[45596] isolation/two-ids/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:13.646 UTC client backend[45596] isolation/two-ids/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:13.646 UTC client backend[45596] isolation/two-ids/s2 STATEMENT: COMMIT; 2025-11-30 18:45:13.655 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot execute MERGE on relation "remp1" 2025-11-30 18:45:13.655 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:13.655 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: merge into itrtest using (select 1, 'foo') as source on (true) when matched then do nothing; 2025-11-30 18:45:13.658 UTC client backend[44596] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:13.658 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: insert into itrtest values (1, 'bar') on conflict (a) do nothing; 2025-11-30 18:45:13.658 UTC client backend[44596] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:13.658 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: insert into itrtest values (1, 'bar') on conflict (a) do update set b = excluded.b; 2025-11-30 18:45:13.676 UTC client backend[45538] pg_regress/join LOG: disconnection: session time: 0:00:01.529 user=postgres database=regression host=[local] 2025-11-30 18:45:13.691 UTC client backend[45661] postgres_fdw ERROR: new row for relation "loct" violates check constraint "loct_a_check" 2025-11-30 18:45:13.691 UTC client backend[45661] postgres_fdw DETAIL: Failing row contains (2, foo). 2025-11-30 18:45:13.691 UTC client backend[45661] postgres_fdw STATEMENT: UPDATE public.loct SET a = 2 WHERE ((b = 'foo')) RETURNING a, b 2025-11-30 18:45:13.691 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "loct" violates check constraint "loct_a_check" 2025-11-30 18:45:13.691 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (2, foo). 2025-11-30 18:45:13.691 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE public.loct SET a = 2 WHERE ((b = 'foo')) RETURNING a, b 2025-11-30 18:45:13.691 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 2 where b = 'foo' returning *; 2025-11-30 18:45:13.692 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-11-30 18:45:13.692 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 where b = 'qux' returning *; 2025-11-30 18:45:13.692 UTC client backend[45542] pg_regress/btree_index ERROR: operator class int4_ops has no options 2025-11-30 18:45:13.692 UTC client backend[45542] pg_regress/btree_index STATEMENT: create index on btree_tall_tbl (id int4_ops(foo=1)); 2025-11-30 18:45:13.701 UTC client backend[45542] pg_regress/btree_index ERROR: ALTER action ALTER COLUMN ... SET cannot be performed on relation "btree_tall_idx2" 2025-11-30 18:45:13.701 UTC client backend[45542] pg_regress/btree_index DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:13.701 UTC client backend[45542] pg_regress/btree_index STATEMENT: ALTER INDEX btree_tall_idx2 ALTER COLUMN id SET (n_distinct=100); 2025-11-30 18:45:13.702 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-11-30 18:45:13.702 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 where a = 1 or a = 2 returning *; 2025-11-30 18:45:13.703 UTC client backend[45542] pg_regress/btree_index ERROR: ALTER action ALTER COLUMN ... SET cannot be performed on relation "btree_part_idx" 2025-11-30 18:45:13.703 UTC client backend[45542] pg_regress/btree_index DETAIL: This operation is not supported for partitioned indexes. 2025-11-30 18:45:13.703 UTC client backend[45542] pg_regress/btree_index STATEMENT: ALTER INDEX btree_part_idx ALTER COLUMN id SET (n_distinct=100); 2025-11-30 18:45:13.705 UTC client backend[45542] pg_regress/btree_index LOG: disconnection: session time: 0:00:01.559 user=postgres database=regression host=[local] 2025-11-30 18:45:13.712 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-11-30 18:45:13.712 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 returning *; 2025-11-30 18:45:13.718 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-11-30 18:45:13.718 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 from (values (1), (2)) s(x) where a = s.x returning *; 2025-11-30 18:45:13.728 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-11-30 18:45:13.728 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 3 returning *; 2025-11-30 18:45:13.740 UTC client backend[45596] isolation/two-ids/s2 LOG: disconnection: session time: 0:00:00.832 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:13.740 UTC client backend[45598] isolation/two-ids/s3 LOG: disconnection: session time: 0:00:00.808 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:13.747 UTC client backend[45594] isolation/two-ids/s1 LOG: disconnection: session time: 0:00:00.842 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:13.748 UTC unrecognized[45708] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.748 UTC client backend[45708] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.748 UTC client backend[45708] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/gin 2025-11-30 18:45:13.748 UTC unrecognized[45707] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.749 UTC unrecognized[45712] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.749 UTC client backend[45707] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.749 UTC client backend[45707] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/brin 2025-11-30 18:45:13.749 UTC client backend[45712] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.749 UTC client backend[45712] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/spgist 2025-11-30 18:45:13.749 UTC client backend[45708] pg_regress/gin LOG: connection ready: setup total=16.225 ms, fork=1.217 ms, authentication=0.133 ms 2025-11-30 18:45:13.750 UTC client backend[45707] pg_regress/brin LOG: connection ready: setup total=16.920 ms, fork=9.756 ms, authentication=0.113 ms 2025-11-30 18:45:13.750 UTC client backend[45712] pg_regress/spgist LOG: connection ready: setup total=12.635 ms, fork=11.196 ms, authentication=0.110 ms 2025-11-30 18:45:13.750 UTC unrecognized[45709] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.750 UTC unrecognized[45710] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.750 UTC client backend[45709] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.750 UTC client backend[45709] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:13.751 UTC client backend[45710] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.751 UTC client backend[45710] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rowsecurity 2025-11-30 18:45:13.751 UTC client backend[45709] pg_regress/privileges LOG: connection ready: setup total=17.868 ms, fork=16.502 ms, authentication=0.106 ms 2025-11-30 18:45:13.751 UTC client backend[45710] pg_regress/rowsecurity LOG: connection ready: setup total=14.987 ms, fork=11.975 ms, authentication=0.104 ms 2025-11-30 18:45:13.752 UTC unrecognized[45715] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.752 UTC unrecognized[45717] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.752 UTC client backend[45715] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.752 UTC client backend[45715] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/replica_identity 2025-11-30 18:45:13.752 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-11-30 18:45:13.752 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 3 from (values (2), (3)) s(x) where a = s.x returning *; 2025-11-30 18:45:13.752 UTC client backend[45717] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.752 UTC client backend[45717] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/lock 2025-11-30 18:45:13.752 UTC client backend[45590] isolation/two-ids/control connection LOG: disconnection: session time: 0:00:00.867 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:13.753 UTC client backend[45715] pg_regress/replica_identity LOG: connection ready: setup total=13.189 ms, fork=8.895 ms, authentication=0.097 ms 2025-11-30 18:45:13.753 UTC client backend[45717] pg_regress/lock LOG: connection ready: setup total=11.896 ms, fork=10.493 ms, authentication=0.119 ms 2025-11-30 18:45:13.753 UTC unrecognized[45718] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.754 UTC unrecognized[45719] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.754 UTC client backend[45718] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.754 UTC client backend[45718] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/generated_stored 2025-11-30 18:45:13.754 UTC client backend[45719] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.754 UTC client backend[45719] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/multiple-row-versions 2025-11-30 18:45:13.755 UTC client backend[45718] pg_regress/generated_stored LOG: connection ready: setup total=9.821 ms, fork=5.169 ms, authentication=0.108 ms 2025-11-30 18:45:13.755 UTC client backend[45719] isolation/multiple-row-versions LOG: connection ready: setup total=9.570 ms, fork=4.811 ms, authentication=0.101 ms 2025-11-30 18:45:13.755 UTC unrecognized[45720] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.755 UTC client backend[45720] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.755 UTC client backend[45720] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate 2025-11-30 18:45:13.755 UTC unrecognized[45723] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.756 UTC client backend[45723] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.756 UTC client backend[45723] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/matview 2025-11-30 18:45:13.756 UTC unrecognized[45724] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.756 UTC client backend[45720] pg_regress/collate LOG: connection ready: setup total=10.675 ms, fork=4.731 ms, authentication=0.120 ms 2025-11-30 18:45:13.756 UTC unrecognized[45722] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.756 UTC client backend[45724] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.756 UTC client backend[45724] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/identity 2025-11-30 18:45:13.757 UTC client backend[45723] pg_regress/matview LOG: connection ready: setup total=10.544 ms, fork=3.932 ms, authentication=0.102 ms 2025-11-30 18:45:13.757 UTC client backend[45722] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.757 UTC client backend[45722] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/object_address 2025-11-30 18:45:13.757 UTC client backend[45724] pg_regress/identity LOG: connection ready: setup total=10.870 ms, fork=5.039 ms, authentication=0.110 ms 2025-11-30 18:45:13.757 UTC unrecognized[45711] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.758 UTC unrecognized[45726] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.758 UTC client backend[45722] pg_regress/object_address LOG: connection ready: setup total=11.733 ms, fork=4.337 ms, authentication=0.125 ms 2025-11-30 18:45:13.758 UTC client backend[45711] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.758 UTC client backend[45711] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/init_privs 2025-11-30 18:45:13.758 UTC unrecognized[45714] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.758 UTC client backend[45726] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.758 UTC client backend[45726] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/groupingsets 2025-11-30 18:45:13.758 UTC client backend[45714] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.758 UTC client backend[45714] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/security_label 2025-11-30 18:45:13.759 UTC client backend[45711] pg_regress/init_privs LOG: connection ready: setup total=21.590 ms, fork=12.638 ms, authentication=0.111 ms 2025-11-30 18:45:13.759 UTC client backend[45726] pg_regress/groupingsets LOG: connection ready: setup total=10.867 ms, fork=3.642 ms, authentication=0.106 ms 2025-11-30 18:45:13.759 UTC unrecognized[45727] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.759 UTC client backend[45714] pg_regress/security_label LOG: connection ready: setup total=19.689 ms, fork=10.888 ms, authentication=0.117 ms 2025-11-30 18:45:13.759 UTC client backend[45727] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.759 UTC client backend[45727] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/password 2025-11-30 18:45:13.760 UTC unrecognized[45729] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.760 UTC unrecognized[45721] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.760 UTC client backend[45727] pg_regress/password LOG: connection ready: setup total=12.064 ms, fork=3.480 ms, authentication=0.107 ms 2025-11-30 18:45:13.761 UTC client backend[45729] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.761 UTC client backend[45729] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/drop_operator 2025-11-30 18:45:13.761 UTC client backend[45721] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.761 UTC client backend[45721] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/join_hash 2025-11-30 18:45:13.761 UTC client backend[45729] pg_regress/drop_operator LOG: connection ready: setup total=8.364 ms, fork=6.287 ms, authentication=0.109 ms 2025-11-30 18:45:13.761 UTC client backend[45721] pg_regress/join_hash LOG: connection ready: setup total=15.760 ms, fork=8.693 ms, authentication=0.107 ms 2025-11-30 18:45:13.762 UTC unrecognized[45725] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.762 UTC client backend[45725] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.762 UTC client backend[45725] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/gist 2025-11-30 18:45:13.763 UTC client backend[45725] pg_regress/gist LOG: connection ready: setup total=15.253 ms, fork=6.867 ms, authentication=0.103 ms 2025-11-30 18:45:13.768 UTC unrecognized[45728] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.769 UTC client backend[45728] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.769 UTC client backend[45728] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tablesample 2025-11-30 18:45:13.769 UTC client backend[45728] pg_regress/tablesample LOG: connection ready: setup total=19.750 ms, fork=6.072 ms, authentication=0.118 ms 2025-11-30 18:45:13.773 UTC client backend[45727] pg_regress/password ERROR: invalid value for parameter "password_encryption": "novalue" 2025-11-30 18:45:13.773 UTC client backend[45727] pg_regress/password HINT: Available values: md5, scram-sha-256. 2025-11-30 18:45:13.773 UTC client backend[45727] pg_regress/password STATEMENT: SET password_encryption = 'novalue'; 2025-11-30 18:45:13.774 UTC client backend[45727] pg_regress/password ERROR: invalid value for parameter "password_encryption": "true" 2025-11-30 18:45:13.774 UTC client backend[45727] pg_regress/password HINT: Available values: md5, scram-sha-256. 2025-11-30 18:45:13.774 UTC client backend[45727] pg_regress/password STATEMENT: SET password_encryption = true; 2025-11-30 18:45:13.777 UTC client backend[45727] pg_regress/password WARNING: setting an MD5-encrypted password 2025-11-30 18:45:13.777 UTC client backend[45727] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-11-30 18:45:13.777 UTC client backend[45727] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-11-30 18:45:13.784 UTC unrecognized[45730] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.785 UTC client backend[45730] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.785 UTC client backend[45730] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/multiple-row-versions 2025-11-30 18:45:13.789 UTC client backend[45730] isolation/multiple-row-versions LOG: connection ready: setup total=22.719 ms, fork=6.415 ms, authentication=0.116 ms 2025-11-30 18:45:13.792 UTC client backend[45711] pg_regress/init_privs LOG: disconnection: session time: 0:00:00.042 user=postgres database=regression host=[local] 2025-11-30 18:45:13.817 UTC unrecognized[45731] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.818 UTC client backend[45731] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.818 UTC client backend[45731] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/multiple-row-versions 2025-11-30 18:45:13.819 UTC client backend[45731] isolation/multiple-row-versions LOG: connection ready: setup total=13.254 ms, fork=4.023 ms, authentication=0.122 ms 2025-11-30 18:45:13.837 UTC unrecognized[45733] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.837 UTC client backend[45729] pg_regress/drop_operator LOG: disconnection: session time: 0:00:00.077 user=postgres database=regression host=[local] 2025-11-30 18:45:13.837 UTC client backend[45733] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.837 UTC client backend[45733] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/multiple-row-versions 2025-11-30 18:45:13.838 UTC client backend[45733] isolation/multiple-row-versions LOG: connection ready: setup total=15.414 ms, fork=10.828 ms, authentication=0.116 ms 2025-11-30 18:45:13.841 UTC client backend[45723] pg_regress/matview ERROR: materialized view "mvtest_tm" has not been populated 2025-11-30 18:45:13.841 UTC client backend[45723] pg_regress/matview HINT: Use the REFRESH MATERIALIZED VIEW command. 2025-11-30 18:45:13.841 UTC client backend[45723] pg_regress/matview STATEMENT: SELECT * FROM mvtest_tm ORDER BY type; 2025-11-30 18:45:13.843 UTC client backend[45724] pg_regress/identity ERROR: column "a" of relation "itest3" is already an identity column 2025-11-30 18:45:13.843 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest3 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:13.844 UTC client backend[45727] pg_regress/password WARNING: setting an MD5-encrypted password 2025-11-30 18:45:13.844 UTC client backend[45727] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-11-30 18:45:13.844 UTC client backend[45727] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-11-30 18:45:13.847 UTC unrecognized[45734] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:13.848 UTC client backend[45734] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:13.848 UTC client backend[45734] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/multiple-row-versions 2025-11-30 18:45:13.848 UTC client backend[45734] isolation/multiple-row-versions LOG: connection ready: setup total=6.251 ms, fork=3.337 ms, authentication=0.110 ms 2025-11-30 18:45:13.855 UTC client backend[45720] pg_regress/collate ERROR: collations are not supported by type integer at character 44 2025-11-30 18:45:13.855 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE TABLE collate_test_fail ( a int COLLATE "C", b text ); 2025-11-30 18:45:13.860 UTC client backend[45714] pg_regress/security_label ERROR: no security label providers have been loaded 2025-11-30 18:45:13.860 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL ON TABLE seclabel_tbl1 IS 'classified'; 2025-11-30 18:45:13.868 UTC client backend[45714] pg_regress/security_label ERROR: security label provider "dummy" is not loaded 2025-11-30 18:45:13.868 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL FOR 'dummy' ON TABLE seclabel_tbl1 IS 'classified'; 2025-11-30 18:45:13.891 UTC client backend[45725] pg_regress/gist ERROR: invalid value for enum option "buffering": invalid_value 2025-11-30 18:45:13.891 UTC client backend[45725] pg_regress/gist DETAIL: Valid values are "on", "off", and "auto". 2025-11-30 18:45:13.891 UTC client backend[45725] pg_regress/gist STATEMENT: create index gist_pointidx5 on gist_point_tbl using gist(p) with (buffering = invalid_value); 2025-11-30 18:45:13.893 UTC client backend[45725] pg_regress/gist ERROR: value 9 out of bounds for option "fillfactor" 2025-11-30 18:45:13.893 UTC client backend[45725] pg_regress/gist DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:13.893 UTC client backend[45725] pg_regress/gist STATEMENT: create index gist_pointidx5 on gist_point_tbl using gist(p) with (fillfactor=9); 2025-11-30 18:45:13.893 UTC client backend[45725] pg_regress/gist ERROR: value 101 out of bounds for option "fillfactor" 2025-11-30 18:45:13.893 UTC client backend[45725] pg_regress/gist DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:13.893 UTC client backend[45725] pg_regress/gist STATEMENT: create index gist_pointidx5 on gist_point_tbl using gist(p) with (fillfactor=101); 2025-11-30 18:45:13.896 UTC client backend[45727] pg_regress/password WARNING: setting an MD5-encrypted password 2025-11-30 18:45:13.896 UTC client backend[45727] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-11-30 18:45:13.896 UTC client backend[45727] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-11-30 18:45:13.907 UTC client backend[45727] pg_regress/password WARNING: setting an MD5-encrypted password 2025-11-30 18:45:13.907 UTC client backend[45727] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-11-30 18:45:13.907 UTC client backend[45727] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-11-30 18:45:13.909 UTC client backend[45714] pg_regress/security_label ERROR: no security label providers have been loaded 2025-11-30 18:45:13.909 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL ON TABLE seclabel_tbl1 IS '...invalid label...'; 2025-11-30 18:45:13.935 UTC client backend[45718] pg_regress/generated_stored ERROR: multiple generation clauses specified for column "b" of table "gtest_err_1" at character 87 2025-11-30 18:45:13.935 UTC client backend[45718] 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-11-30 18:45:13.940 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column "b" in column generation expression at character 74 2025-11-30 18:45:13.940 UTC client backend[45718] pg_regress/generated_stored DETAIL: A generated column cannot reference another generated column. 2025-11-30 18:45:13.940 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_2a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (b * 2) STORED); 2025-11-30 18:45:13.952 UTC client backend[45714] pg_regress/security_label ERROR: no security label providers have been loaded 2025-11-30 18:45:13.952 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL ON TABLE seclabel_tbl3 IS 'unclassified'; 2025-11-30 18:45:13.953 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column "b" in column generation expression at character 116 2025-11-30 18:45:13.953 UTC client backend[45718] pg_regress/generated_stored DETAIL: A generated column cannot reference another generated column. 2025-11-30 18:45:13.953 UTC client backend[45718] 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-11-30 18:45:13.958 UTC client backend[45727] pg_regress/password WARNING: setting an MD5-encrypted password 2025-11-30 18:45:13.958 UTC client backend[45727] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-11-30 18:45:13.958 UTC client backend[45727] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-11-30 18:45:13.960 UTC client backend[45714] pg_regress/security_label ERROR: no security label providers have been loaded 2025-11-30 18:45:13.960 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL ON ROLE regress_seclabel_user1 IS 'classified'; 2025-11-30 18:45:13.966 UTC client backend[45715] pg_regress/replica_identity ERROR: cannot use non-unique index "test_replica_identity_keyab" as replica identity 2025-11-30 18:45:13.966 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_keyab; 2025-11-30 18:45:13.966 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use whole-row variable in column generation expression at character 88 2025-11-30 18:45:13.966 UTC client backend[45718] pg_regress/generated_stored DETAIL: This would cause the generated column to depend on its own value. 2025-11-30 18:45:13.966 UTC client backend[45718] 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-11-30 18:45:13.967 UTC client backend[45715] pg_regress/replica_identity ERROR: index "test_replica_identity_nonkey" cannot be used as replica identity because column "nonkey" is nullable 2025-11-30 18:45:13.967 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_nonkey; 2025-11-30 18:45:13.968 UTC client backend[45718] pg_regress/generated_stored ERROR: column "c" does not exist at character 73 2025-11-30 18:45:13.968 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_3 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (c * 2) STORED); 2025-11-30 18:45:13.968 UTC client backend[45715] pg_regress/replica_identity ERROR: cannot use non-unique index "test_replica_identity_hash" as replica identity 2025-11-30 18:45:13.968 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_hash; 2025-11-30 18:45:13.969 UTC client backend[45718] pg_regress/generated_stored ERROR: generation expression is not immutable 2025-11-30 18:45:13.969 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_4 (a int PRIMARY KEY, b double precision GENERATED ALWAYS AS (random()) STORED); 2025-11-30 18:45:13.969 UTC client backend[45715] pg_regress/replica_identity ERROR: cannot use expression index "test_replica_identity_expr" as replica identity 2025-11-30 18:45:13.969 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_expr; 2025-11-30 18:45:13.970 UTC client backend[45715] pg_regress/replica_identity ERROR: cannot use partial index "test_replica_identity_partial" as replica identity 2025-11-30 18:45:13.970 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_partial; 2025-11-30 18:45:13.970 UTC client backend[45714] pg_regress/security_label ERROR: security label provider "dummy" is not loaded 2025-11-30 18:45:13.970 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL FOR 'dummy' ON ROLE regress_seclabel_user1 IS 'classified'; 2025-11-30 18:45:13.971 UTC client backend[45714] pg_regress/security_label ERROR: no security label providers have been loaded 2025-11-30 18:45:13.971 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL ON ROLE regress_seclabel_user1 IS '...invalid label...'; 2025-11-30 18:45:13.974 UTC client backend[45720] pg_regress/collate ERROR: collation mismatch between explicit collations "C" and "POSIX" at character 58 2025-11-30 18:45:13.974 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT * FROM collate_test1 WHERE b COLLATE "C" >= 'bbc' COLLATE "POSIX"; 2025-11-30 18:45:13.976 UTC client backend[45720] pg_regress/collate ERROR: collations are not supported by type integer at character 31 2025-11-30 18:45:13.976 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE DOMAIN testdomain_i AS int COLLATE "POSIX"; 2025-11-30 18:45:13.977 UTC client backend[45715] pg_regress/replica_identity ERROR: "test_replica_identity_othertable_pkey" is not an index for table "test_replica_identity" 2025-11-30 18:45:13.977 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_othertable_pkey; 2025-11-30 18:45:13.981 UTC client backend[45714] pg_regress/security_label ERROR: no security label providers have been loaded 2025-11-30 18:45:13.981 UTC client backend[45714] pg_regress/security_label STATEMENT: SECURITY LABEL ON ROLE regress_seclabel_user3 IS 'unclassified'; 2025-11-30 18:45:13.982 UTC client backend[45715] pg_regress/replica_identity ERROR: cannot use non-immediate index "test_replica_identity_unique_defer" as replica identity 2025-11-30 18:45:13.982 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_unique_defer; 2025-11-30 18:45:13.982 UTC client backend[45715] pg_regress/replica_identity ERROR: cannot use non-immediate index "pk" as replica identity 2025-11-30 18:45:13.982 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity_t3 REPLICA IDENTITY USING INDEX pk; 2025-11-30 18:45:14.003 UTC client backend[45724] pg_regress/identity ERROR: column "a" of relation "itest4" must be declared NOT NULL before identity can be added 2025-11-30 18:45:14.003 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:14.007 UTC client backend[45726] pg_regress/groupingsets ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 69 2025-11-30 18:45:14.007 UTC client backend[45726] 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-11-30 18:45:14.008 UTC client backend[45718] pg_regress/generated_stored ERROR: both default and generation expression specified for column "b" of table "gtest_err_5a" at character 63 2025-11-30 18:45:14.008 UTC client backend[45718] 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-11-30 18:45:14.008 UTC client backend[45718] pg_regress/generated_stored ERROR: both identity and generation expression specified for column "b" of table "gtest_err_5b" at character 82 2025-11-30 18:45:14.008 UTC client backend[45718] 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-11-30 18:45:14.014 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use system column "xmin" in column generation expression at character 75 2025-11-30 18:45:14.014 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_6a (a int PRIMARY KEY, b bool GENERATED ALWAYS AS (xmin <> 37) STORED); 2025-11-30 18:45:14.027 UTC client backend[45718] pg_regress/generated_stored ERROR: aggregate functions are not allowed in column generation expressions at character 74 2025-11-30 18:45:14.027 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_7a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (avg(a)) STORED); 2025-11-30 18:45:14.058 UTC client backend[45724] pg_regress/identity ERROR: column "c" of relation "itest4" does not exist 2025-11-30 18:45:14.058 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN c ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:14.061 UTC client backend[45718] pg_regress/generated_stored ERROR: window functions are not allowed in column generation expressions at character 74 2025-11-30 18:45:14.061 UTC client backend[45718] 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-11-30 18:45:14.068 UTC client backend[45724] pg_regress/identity ERROR: column "a" of relation "itest4" is an identity column 2025-11-30 18:45:14.068 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a DROP NOT NULL; 2025-11-30 18:45:14.070 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use subquery in column generation expression at character 74 2025-11-30 18:45:14.070 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_7c (a int PRIMARY KEY, b int GENERATED ALWAYS AS ((SELECT a)) STORED); 2025-11-30 18:45:14.070 UTC client backend[45709] pg_regress/privileges ERROR: role "regress_priv_user5" already exists 2025-11-30 18:45:14.070 UTC client backend[45709] pg_regress/privileges STATEMENT: CREATE USER regress_priv_user5; 2025-11-30 18:45:14.071 UTC client backend[45718] pg_regress/generated_stored ERROR: set-returning functions are not allowed in column generation expressions at character 74 2025-11-30 18:45:14.071 UTC client backend[45718] 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-11-30 18:45:14.071 UTC client backend[45718] pg_regress/generated_stored ERROR: for a generated column, GENERATED ALWAYS must be specified at character 62 2025-11-30 18:45:14.071 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_8 (a int PRIMARY KEY, b int GENERATED BY DEFAULT AS (a * 2) STORED); 2025-11-30 18:45:14.073 UTC client backend[45724] pg_regress/identity ERROR: column "a" of relation "itest4" is already an identity column 2025-11-30 18:45:14.073 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:14.080 UTC client backend[45724] pg_regress/identity ERROR: identity column type must be smallint, integer, or bigint 2025-11-30 18:45:14.080 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN b ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:14.091 UTC client backend[45728] pg_regress/tablesample ERROR: tablesample method foobar does not exist at character 45 2025-11-30 18:45:14.091 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE FOOBAR (1); 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity ERROR: identity column type must be smallint, integer, or bigint 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity STATEMENT: CREATE TABLE itest_err_1 (a text generated by default as identity); 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity ERROR: multiple identity specifications for column "a" of table "itest_err_2" at character 62 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity STATEMENT: CREATE TABLE itest_err_2 (a int generated always as identity generated by default as identity); 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity ERROR: both default and identity specified for column "a" of table "itest_err_3" at character 43 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity STATEMENT: CREATE TABLE itest_err_3 (a int default 5 generated by default as identity); 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity ERROR: both default and identity specified for column "a" of table "itest_err_4" 2025-11-30 18:45:14.091 UTC client backend[45724] pg_regress/identity STATEMENT: CREATE TABLE itest_err_4 (a serial generated by default as identity); 2025-11-30 18:45:14.091 UTC client backend[45728] pg_regress/tablesample ERROR: TABLESAMPLE parameter cannot be null 2025-11-30 18:45:14.091 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (NULL); 2025-11-30 18:45:14.093 UTC client backend[45728] pg_regress/tablesample ERROR: TABLESAMPLE REPEATABLE parameter cannot be null 2025-11-30 18:45:14.093 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (50) REPEATABLE (NULL); 2025-11-30 18:45:14.094 UTC client backend[45726] pg_regress/groupingsets ERROR: arguments to GROUPING must be grouping expressions of the associated query level at character 25 2025-11-30 18:45:14.094 UTC client backend[45726] pg_regress/groupingsets STATEMENT: select (select grouping(a,b) from gstest2) from gstest2 group by a,b; 2025-11-30 18:45:14.094 UTC client backend[45728] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-11-30 18:45:14.094 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE BERNOULLI (-1); 2025-11-30 18:45:14.096 UTC client backend[45728] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-11-30 18:45:14.096 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE BERNOULLI (200); 2025-11-30 18:45:14.100 UTC client backend[45728] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-11-30 18:45:14.100 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (-1); 2025-11-30 18:45:14.101 UTC client backend[45717] pg_regress/lock ERROR: permission denied for table lock_tbl2 2025-11-30 18:45:14.101 UTC client backend[45717] pg_regress/lock STATEMENT: LOCK TABLE lock_tbl2; 2025-11-30 18:45:14.101 UTC client backend[45728] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-11-30 18:45:14.101 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (200); 2025-11-30 18:45:14.101 UTC client backend[45717] pg_regress/lock ERROR: permission denied for view lock_view1 2025-11-30 18:45:14.101 UTC client backend[45717] pg_regress/lock STATEMENT: LOCK TABLE lock_view1; 2025-11-30 18:45:14.105 UTC client backend[45728] pg_regress/tablesample ERROR: TABLESAMPLE clause can only be applied to tables and materialized views at character 16 2025-11-30 18:45:14.105 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample_v1 TABLESAMPLE BERNOULLI (1); 2025-11-30 18:45:14.105 UTC client backend[45724] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-11-30 18:45:14.105 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:14.105 UTC client backend[45724] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-11-30 18:45:14.105 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (1, 'a'); 2025-11-30 18:45:14.106 UTC client backend[45728] pg_regress/tablesample ERROR: cannot insert into view "test_tablesample_v1" 2025-11-30 18:45:14.106 UTC client backend[45728] pg_regress/tablesample DETAIL: Views containing TABLESAMPLE are not automatically updatable. 2025-11-30 18:45:14.106 UTC client backend[45728] 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-11-30 18:45:14.106 UTC client backend[45728] pg_regress/tablesample STATEMENT: INSERT INTO test_tablesample_v1 VALUES(1); 2025-11-30 18:45:14.107 UTC client backend[45724] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-11-30 18:45:14.107 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:14.107 UTC client backend[45724] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-11-30 18:45:14.107 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (2, 'b'), (3, 'c'); 2025-11-30 18:45:14.107 UTC client backend[45728] pg_regress/tablesample ERROR: TABLESAMPLE clause can only be applied to tables and materialized views at character 69 2025-11-30 18:45:14.107 UTC client backend[45728] pg_regress/tablesample STATEMENT: WITH query_select AS (SELECT * FROM test_tablesample) SELECT * FROM query_select TABLESAMPLE BERNOULLI (5.5) REPEATABLE (1); 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (DEFAULT, 'b'), (3, 'c'); 2025-11-30 18:45:14.108 UTC client backend[45728] pg_regress/tablesample ERROR: syntax error at or near "TABLESAMPLE" at character 55 2025-11-30 18:45:14.108 UTC client backend[45728] pg_regress/tablesample STATEMENT: SELECT q.* FROM (SELECT * FROM test_tablesample) as q TABLESAMPLE BERNOULLI (5); 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-11-30 18:45:14.108 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (2, 'b'), (DEFAULT, 'c'); 2025-11-30 18:45:14.116 UTC client backend[45720] pg_regress/collate ERROR: collation mismatch between explicit collations "C" and "POSIX" at character 36 2025-11-30 18:45:14.116 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT string_agg(x COLLATE "C", y COLLATE "POSIX") FROM collate_test10; 2025-11-30 18:45:14.116 UTC client backend[45720] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 32 2025-11-30 18:45:14.116 UTC client backend[45720] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:14.116 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT array_agg(a ORDER BY x||y) FROM collate_test10; 2025-11-30 18:45:14.118 UTC client backend[45720] pg_regress/collate ERROR: could not determine which collation to use for string comparison 2025-11-30 18:45:14.118 UTC client backend[45720] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:14.118 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test2 ORDER BY 2; 2025-11-30 18:45:14.119 UTC client backend[45728] pg_regress/tablesample LOG: disconnection: session time: 0:00:00.363 user=postgres database=regression host=[local] 2025-11-30 18:45:14.119 UTC client backend[45720] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 48 2025-11-30 18:45:14.119 UTC client backend[45720] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:14.119 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 UNION SELECT a, b FROM collate_test2 ORDER BY 2; 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 52 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 INTERSECT SELECT a, b FROM collate_test2 ORDER BY 2; 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 49 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 EXCEPT SELECT a, b FROM collate_test2 ORDER BY 2; 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate ERROR: no collation was derived for column "b" with collatable type text 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE TABLE test_u AS SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test2; 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate ERROR: could not determine which collation to use for string comparison 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:14.120 UTC client backend[45720] pg_regress/collate STATEMENT: select x < y from collate_test10; 2025-11-30 18:45:14.123 UTC client backend[45720] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 47 2025-11-30 18:45:14.123 UTC client backend[45720] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:14.123 UTC client backend[45720] pg_regress/collate STATEMENT: select x, y from collate_test10 order by x || y; 2025-11-30 18:45:14.123 UTC client backend[45720] pg_regress/collate ERROR: recursive query "foo" column 1 has collation "C" in non-recursive term but collation "POSIX" overall at character 37 2025-11-30 18:45:14.123 UTC client backend[45720] pg_regress/collate HINT: Use the COLLATE clause to set the collation of the non-recursive term. 2025-11-30 18:45:14.123 UTC client backend[45720] 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-11-30 18:45:14.124 UTC client backend[45720] pg_regress/collate ERROR: could not determine which collation to use for string hashing 2025-11-30 18:45:14.124 UTC client backend[45720] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:14.124 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT * FROM collate_test10 WHERE (x, y) NOT IN (SELECT y, x FROM collate_test10); 2025-11-30 18:45:14.124 UTC client backend[45720] pg_regress/collate ERROR: syntax error at or near "COLLATE" at character 26 2025-11-30 18:45:14.124 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT CAST('42' AS text COLLATE "C"); 2025-11-30 18:45:14.128 UTC client backend[45727] pg_regress/password ERROR: encrypted password is too long 2025-11-30 18:45:14.128 UTC client backend[45727] pg_regress/password DETAIL: Encrypted passwords must be no longer than 512 bytes. 2025-11-30 18:45:14.128 UTC client backend[45727] pg_regress/password STATEMENT: CREATE ROLE regress_passwd10 PASSWORD 'SCRAM-SHA-256$000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004096:wNFxNSk1hAXBkgub8py3bg==$65zC6E+R0U7tiYTC9+Wtq4Thw6gUDj3eDCINij8TflU=:rC1I7tcVugrHEY2DT0iPjGyjM4aJxkMM9n8WBxtUtHU='; 2025-11-30 18:45:14.134 UTC client backend[45714] pg_regress/security_label LOG: disconnection: session time: 0:00:00.383 user=postgres database=regression host=[local] 2025-11-30 18:45:14.135 UTC client backend[45727] pg_regress/password ERROR: encrypted password is too long 2025-11-30 18:45:14.135 UTC client backend[45727] pg_regress/password DETAIL: Encrypted passwords must be no longer than 512 bytes. 2025-11-30 18:45:14.135 UTC client backend[45727] pg_regress/password STATEMENT: ALTER ROLE regress_passwd9 PASSWORD 'SCRAM-SHA-256$000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004096:wNFxNSk1hAXBkgub8py3bg==$65zC6E+R0U7tiYTC9+Wtq4Thw6gUDj3eDCINij8TflU=:rC1I7tcVugrHEY2DT0iPjGyjM4aJxkMM9n8WBxtUtHU='; 2025-11-30 18:45:14.135 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.135 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.135 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, 33); 2025-11-30 18:45:14.136 UTC client backend[45720] pg_regress/collate ERROR: collations are not supported by type integer 2025-11-30 18:45:14.136 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE INDEX collate_test1_idx5 ON collate_test1 (a COLLATE "POSIX"); 2025-11-30 18:45:14.136 UTC client backend[45720] pg_regress/collate ERROR: collations are not supported by type integer at character 54 2025-11-30 18:45:14.136 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE INDEX collate_test1_idx6 ON collate_test1 ((a COLLATE "POSIX")); 2025-11-30 18:45:14.137 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.137 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.137 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, 44); 2025-11-30 18:45:14.140 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.140 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.140 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, DEFAULT), (4, 44); 2025-11-30 18:45:14.140 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.140 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.140 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, DEFAULT); 2025-11-30 18:45:14.141 UTC client backend[45726] pg_regress/groupingsets ERROR: could not implement GROUP BY 2025-11-30 18:45:14.141 UTC client backend[45726] pg_regress/groupingsets DETAIL: Some of the datatypes only support hashing, while others only support sorting. 2025-11-30 18:45:14.141 UTC client backend[45726] pg_regress/groupingsets STATEMENT: select count(*) from gstest4 group by rollup(unhashable_col,unsortable_col); 2025-11-30 18:45:14.144 UTC client backend[45726] pg_regress/groupingsets ERROR: could not implement GROUP BY 2025-11-30 18:45:14.144 UTC client backend[45726] pg_regress/groupingsets DETAIL: Some of the datatypes only support hashing, while others only support sorting. 2025-11-30 18:45:14.144 UTC client backend[45726] pg_regress/groupingsets STATEMENT: select array_agg(v order by v) from gstest4 group by grouping sets ((id,unsortable_col),(id)); 2025-11-30 18:45:14.145 UTC client backend[45709] pg_regress/privileges ERROR: ADMIN option cannot be granted back to your own grantor 2025-11-30 18:45:14.145 UTC client backend[45709] pg_regress/privileges STATEMENT: GRANT regress_priv_user1 TO regress_priv_user2 WITH ADMIN OPTION GRANTED BY regress_priv_user3; 2025-11-30 18:45:14.147 UTC client backend[45709] pg_regress/privileges ERROR: dependent privileges exist 2025-11-30 18:45:14.147 UTC client backend[45709] pg_regress/privileges HINT: Use CASCADE to revoke them too. 2025-11-30 18:45:14.147 UTC client backend[45709] pg_regress/privileges STATEMENT: REVOKE ADMIN OPTION FOR regress_priv_user1 FROM regress_priv_user2; 2025-11-30 18:45:14.149 UTC client backend[45709] pg_regress/privileges ERROR: dependent privileges exist 2025-11-30 18:45:14.149 UTC client backend[45709] pg_regress/privileges HINT: Use CASCADE to revoke them too. 2025-11-30 18:45:14.149 UTC client backend[45709] pg_regress/privileges STATEMENT: REVOKE regress_priv_user1 FROM regress_priv_user2; 2025-11-30 18:45:14.150 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" can only be updated to DEFAULT 2025-11-30 18:45:14.150 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.150 UTC client backend[45718] pg_regress/generated_stored STATEMENT: UPDATE gtest1 SET b = 11 WHERE a = 1; 2025-11-30 18:45:14.151 UTC client backend[45717] pg_regress/lock ERROR: permission denied for view lock_view8 2025-11-30 18:45:14.151 UTC client backend[45717] pg_regress/lock STATEMENT: LOCK TABLE lock_view8; 2025-11-30 18:45:14.161 UTC client backend[45718] pg_regress/generated_stored ERROR: integer out of range 2025-11-30 18:45:14.161 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (2000000000); 2025-11-30 18:45:14.167 UTC client backend[45727] pg_regress/password LOG: disconnection: session time: 0:00:00.415 user=postgres database=regression host=[local] 2025-11-30 18:45:14.172 UTC client backend[45726] pg_regress/groupingsets ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 69 2025-11-30 18:45:14.172 UTC client backend[45726] 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-11-30 18:45:14.172 UTC client backend[45726] pg_regress/groupingsets ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 95 2025-11-30 18:45:14.172 UTC client backend[45726] 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-11-30 18:45:14.198 UTC client backend[45717] pg_regress/lock ERROR: permission denied for table lock_tbl1 2025-11-30 18:45:14.198 UTC client backend[45717] pg_regress/lock STATEMENT: LOCK TABLE lock_view8; 2025-11-30 18:45:14.253 UTC client backend[45722] pg_regress/object_address WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:14.253 UTC client backend[45722] pg_regress/object_address HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:14.253 UTC client backend[45722] pg_regress/object_address WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:14.253 UTC client backend[45722] pg_regress/object_address HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:14.255 UTC client backend[45722] pg_regress/object_address WARNING: subscription was created, but is not connected 2025-11-30 18:45:14.255 UTC client backend[45722] pg_regress/object_address HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:14.256 UTC client backend[45722] pg_regress/object_address ERROR: unrecognized object type "stone" 2025-11-30 18:45:14.256 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('stone', '{}', '{}'); 2025-11-30 18:45:14.256 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be at least 1 2025-11-30 18:45:14.256 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('table', '{}', '{}'); 2025-11-30 18:45:14.256 UTC client backend[45722] pg_regress/object_address ERROR: name or argument lists may not contain nulls 2025-11-30 18:45:14.256 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('table', '{NULL}', '{}'); 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address WARNING: error for toast table: unsupported object type "toast table" 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address WARNING: error for index column: unsupported object type "index column" 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address WARNING: error for sequence column: unsupported object type "sequence column" 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address WARNING: error for toast table column: unsupported object type "toast table column" 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address WARNING: error for view column: unsupported object type "view column" 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address WARNING: error for materialized view column: unsupported object type "materialized view column" 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address ERROR: operator 1 (int4, bool) of operator family integer_ops for access method btree does not exist 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address STATEMENT: select * from pg_get_object_address('operator of access method', '{btree,integer_ops,1}', '{int4,bool}'); 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address ERROR: operator 99 (int4, int4) of operator family integer_ops for access method btree does not exist 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address STATEMENT: select * from pg_get_object_address('operator of access method', '{btree,integer_ops,99}', '{int4,int4}'); 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address ERROR: function 1 (int4, bool) of operator family integer_ops for access method btree does not exist 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address STATEMENT: select * from pg_get_object_address('function of access method', '{btree,integer_ops,1}', '{int4,bool}'); 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address ERROR: function 99 (int4, int4) of operator family integer_ops for access method btree does not exist 2025-11-30 18:45:14.257 UTC client backend[45722] pg_regress/object_address STATEMENT: select * from pg_get_object_address('function of access method', '{btree,integer_ops,99}', '{int4,int4}'); 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for table,{eins},{}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for table,{eins},{integer}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for table,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for table,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for table,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for table,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for index,{eins},{}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for index,{eins},{integer}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for index,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for index,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for index,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for index,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for sequence,{eins},{}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for sequence,{eins},{integer}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for sequence,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for sequence,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for sequence,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for sequence,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for view,{eins},{}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for view,{eins},{integer}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for view,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for view,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for view,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for view,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for materialized view,{eins},{}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for materialized view,{eins},{integer}: relation "eins" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for materialized view,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for materialized view,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address WARNING: error for materialized view,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.258 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for materialized view,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table,{eins},{}: relation "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table,{eins},{integer}: relation "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for table column,{eins},{}: column name must be qualified 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for table column,{eins},{integer}: column name must be qualified 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for table column,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for table column,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for table column,{eins,zwei,drei},{}: schema "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for table column,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table column,{eins},{}: column name must be qualified 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table column,{eins},{integer}: column name must be qualified 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table column,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table column,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table column,{eins,zwei,drei},{}: schema "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for foreign table column,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for aggregate,{eins},{}: aggregate eins(*) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for aggregate,{eins},{integer}: aggregate eins(integer) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for aggregate,{addr_nsp,zwei},{}: aggregate addr_nsp.zwei(*) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for aggregate,{addr_nsp,zwei},{integer}: aggregate addr_nsp.zwei(integer) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for aggregate,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for aggregate,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for function,{eins},{}: function eins() does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for function,{eins},{integer}: function eins(integer) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for function,{addr_nsp,zwei},{}: function addr_nsp.zwei() does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for function,{addr_nsp,zwei},{integer}: function addr_nsp.zwei(integer) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for function,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for function,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for procedure,{eins},{}: procedure eins() does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for procedure,{eins},{integer}: procedure eins(integer) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for procedure,{addr_nsp,zwei},{}: procedure addr_nsp.zwei() does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for procedure,{addr_nsp,zwei},{integer}: procedure addr_nsp.zwei(integer) does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for procedure,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for procedure,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for type,{eins},{}: type "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for type,{eins},{integer}: type "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for type,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for type,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for type,{eins,zwei,drei},{}: name list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for type,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for cast,{eins},{}: argument list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for cast,{eins},{integer}: type "eins" does not exist 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for cast,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for cast,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address WARNING: error for cast,{eins,zwei,drei},{}: name list length must be exactly 1 2025-11-30 18:45:14.259 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for cast,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for table constraint,{eins},{}: must specify relation and object name 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for table constraint,{eins},{integer}: must specify relation and object name 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for table constraint,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for table constraint,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for table constraint,{eins,zwei,drei},{}: schema "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for table constraint,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for domain constraint,{eins},{}: argument list length must be exactly 1 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for domain constraint,{eins},{integer}: type "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for domain constraint,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for domain constraint,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for domain constraint,{eins,zwei,drei},{}: name list length must be exactly 1 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for domain constraint,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for conversion,{eins},{}: conversion "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for conversion,{eins},{integer}: conversion "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for conversion,{addr_nsp,zwei},{}: conversion "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for conversion,{addr_nsp,zwei},{integer}: conversion "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for conversion,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for conversion,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for default value,{eins},{}: column name must be qualified 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for default value,{eins},{integer}: column name must be qualified 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for default value,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for default value,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for default value,{eins,zwei,drei},{}: schema "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for default value,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator,{eins},{}: argument list length must be exactly 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator,{eins},{integer}: argument list length must be exactly 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator,{addr_nsp,zwei},{}: argument list length must be exactly 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator,{addr_nsp,zwei},{integer}: argument list length must be exactly 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator,{eins,zwei,drei},{}: argument list length must be exactly 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator,{eins,zwei,drei},{integer}: argument list length must be exactly 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator class,{eins},{}: name list length must be at least 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator class,{eins},{integer}: name list length must be at least 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator class,{addr_nsp,zwei},{}: access method "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator class,{addr_nsp,zwei},{integer}: access method "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator class,{eins,zwei,drei},{}: access method "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator class,{eins,zwei,drei},{integer}: access method "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator family,{eins},{}: name list length must be at least 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator family,{eins},{integer}: name list length must be at least 2 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator family,{addr_nsp,zwei},{}: access method "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator family,{addr_nsp,zwei},{integer}: access method "addr_nsp" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator family,{eins,zwei,drei},{}: access method "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for operator family,{eins,zwei,drei},{integer}: access method "eins" does not exist 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for rule,{eins},{}: must specify relation and object name 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address WARNING: error for rule,{eins},{integer}: must specify relation and object name 2025-11-30 18:45:14.260 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for rule,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for rule,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for rule,{eins,zwei,drei},{}: schema "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for rule,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for trigger,{eins},{}: must specify relation and object name 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for trigger,{eins},{integer}: must specify relation and object name 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for trigger,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for trigger,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for trigger,{eins,zwei,drei},{}: schema "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for trigger,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search parser,{eins},{}: text search parser "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search parser,{eins},{integer}: text search parser "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search parser,{addr_nsp,zwei},{}: text search parser "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search parser,{addr_nsp,zwei},{integer}: text search parser "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search parser,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search parser,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search dictionary,{eins},{}: text search dictionary "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search dictionary,{eins},{integer}: text search dictionary "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search dictionary,{addr_nsp,zwei},{}: text search dictionary "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search dictionary,{addr_nsp,zwei},{integer}: text search dictionary "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search dictionary,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search dictionary,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search template,{eins},{}: text search template "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search template,{eins},{integer}: text search template "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search template,{addr_nsp,zwei},{}: text search template "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search template,{addr_nsp,zwei},{integer}: text search template "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search template,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search template,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search configuration,{eins},{}: text search configuration "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search configuration,{eins},{integer}: text search configuration "eins" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search configuration,{addr_nsp,zwei},{}: text search configuration "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search configuration,{addr_nsp,zwei},{integer}: text search configuration "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search configuration,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for text search configuration,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for policy,{eins},{}: must specify relation and object name 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address WARNING: error for policy,{eins},{integer}: must specify relation and object name 2025-11-30 18:45:14.261 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for policy,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for policy,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for policy,{eins,zwei,drei},{}: schema "eins" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for policy,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for user mapping,{eins},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for user mapping,{eins},{integer}: user mapping for user "eins" on server "integer" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for user mapping,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for user mapping,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for user mapping,{eins,zwei,drei},{}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for user mapping,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for default acl,{eins},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for default acl,{eins},{integer}: unrecognized default ACL object type "i" 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for default acl,{addr_nsp,zwei},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for default acl,{addr_nsp,zwei},{integer}: unrecognized default ACL object type "i" 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for default acl,{eins,zwei,drei},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for default acl,{eins,zwei,drei},{integer}: unrecognized default ACL object type "i" 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for transform,{eins},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for transform,{eins},{integer}: type "eins" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for transform,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for transform,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for transform,{eins,zwei,drei},{}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for transform,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for operator of access method,{eins},{}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for operator of access method,{eins},{integer}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for operator of access method,{addr_nsp,zwei},{}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for operator of access method,{addr_nsp,zwei},{integer}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for operator of access method,{eins,zwei,drei},{}: argument list length must be exactly 2 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for operator of access method,{eins,zwei,drei},{integer}: argument list length must be exactly 2 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for function of access method,{eins},{}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for function of access method,{eins},{integer}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for function of access method,{addr_nsp,zwei},{}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for function of access method,{addr_nsp,zwei},{integer}: name list length must be at least 3 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for function of access method,{eins,zwei,drei},{}: argument list length must be exactly 2 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for function of access method,{eins,zwei,drei},{integer}: argument list length must be exactly 2 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication namespace,{eins},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication namespace,{eins},{integer}: schema "eins" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication namespace,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication namespace,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication namespace,{eins,zwei,drei},{}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication namespace,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication relation,{eins},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication relation,{eins},{integer}: relation "eins" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication relation,{addr_nsp,zwei},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication relation,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication relation,{eins,zwei,drei},{}: argument list length must be exactly 1 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address WARNING: error for publication relation,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-11-30 18:45:14.262 UTC client backend[45722] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: language "one" does not exist 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('language', '{one}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('language', '{one,two}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: large object 123 does not exist 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('large object', '{123}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('large object', '{123,456}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: invalid input syntax for type oid: "blargh" 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('large object', '{blargh}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: schema "one" does not exist 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('schema', '{one}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('schema', '{one,two}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: role "one" does not exist 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('role', '{one}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('role', '{one,two}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: database "one" does not exist 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('database', '{one}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('database', '{one,two}', '{}'); 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address ERROR: tablespace "one" does not exist 2025-11-30 18:45:14.266 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('tablespace', '{one}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('tablespace', '{one,two}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: foreign-data wrapper "one" does not exist 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('foreign-data wrapper', '{one}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('foreign-data wrapper', '{one,two}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: server "one" does not exist 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('server', '{one}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('server', '{one,two}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: extension "one" does not exist 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('extension', '{one}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('extension', '{one,two}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: event trigger "one" does not exist 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('event trigger', '{one}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('event trigger', '{one,two}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: access method "one" does not exist 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('access method', '{one}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('access method', '{one,two}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: publication "one" does not exist 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('publication', '{one}', '{}'); 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.267 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('publication', '{one,two}', '{}'); 2025-11-30 18:45:14.268 UTC client backend[45722] pg_regress/object_address ERROR: subscription "one" does not exist 2025-11-30 18:45:14.268 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('subscription', '{one}', '{}'); 2025-11-30 18:45:14.268 UTC client backend[45722] pg_regress/object_address ERROR: name list length must be exactly 1 2025-11-30 18:45:14.268 UTC client backend[45722] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('subscription', '{one,two}', '{}'); 2025-11-30 18:45:14.280 UTC client backend[45709] pg_regress/privileges ERROR: role "regress_priv_user2" cannot be dropped because some objects depend on it 2025-11-30 18:45:14.280 UTC client backend[45709] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user3 in role regress_priv_user1 2025-11-30 18:45:14.280 UTC client backend[45709] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user2; 2025-11-30 18:45:14.281 UTC client backend[45720] pg_regress/collate ERROR: insert or update on table "collate_test21" violates foreign key constraint "collate_test21_f2_fkey" 2025-11-30 18:45:14.281 UTC client backend[45720] pg_regress/collate DETAIL: Key (f2)=(baz) is not present in table "collate_test20". 2025-11-30 18:45:14.281 UTC client backend[45720] pg_regress/collate STATEMENT: INSERT INTO collate_test21 VALUES ('baz'); 2025-11-30 18:45:14.282 UTC client backend[45709] pg_regress/privileges ERROR: role "regress_priv_user2" cannot be dropped because some objects depend on it 2025-11-30 18:45:14.282 UTC client backend[45709] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user3 in role regress_priv_user1 2025-11-30 18:45:14.282 UTC client backend[45709] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user2; 2025-11-30 18:45:14.290 UTC client backend[45720] pg_regress/collate ERROR: insert or update on table "collate_test22" violates foreign key constraint "collate_test22_f2_fkey" 2025-11-30 18:45:14.290 UTC client backend[45720] pg_regress/collate DETAIL: Key (f2)=(baz) is not present in table "collate_test20". 2025-11-30 18:45:14.290 UTC client backend[45720] pg_regress/collate STATEMENT: ALTER TABLE collate_test22 ADD FOREIGN KEY (f2) REFERENCES collate_test20; 2025-11-30 18:45:14.292 UTC client backend[45709] pg_regress/privileges ERROR: role "regress_priv_user3" cannot be dropped because some objects depend on it 2025-11-30 18:45:14.292 UTC client backend[45709] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user4 in role regress_priv_user1 2025-11-30 18:45:14.292 UTC client backend[45709] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user3; 2025-11-30 18:45:14.297 UTC client backend[45709] pg_regress/privileges ERROR: role "regress_priv_user5" cannot be dropped because some objects depend on it 2025-11-30 18:45:14.297 UTC client backend[45709] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user6 in role regress_priv_user1 2025-11-30 18:45:14.297 UTC client backend[45709] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user5; 2025-11-30 18:45:14.298 UTC client backend[45717] pg_regress/lock LOG: disconnection: session time: 0:00:00.546 user=postgres database=regression host=[local] 2025-11-30 18:45:14.301 UTC client backend[45720] pg_regress/collate ERROR: parameter "locale" must be specified 2025-11-30 18:45:14.301 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION builtin2 ( PROVIDER = builtin ); 2025-11-30 18:45:14.301 UTC client backend[45720] pg_regress/collate ERROR: invalid locale name "en_US" for builtin provider 2025-11-30 18:45:14.301 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION builtin2 ( PROVIDER = builtin, LOCALE = "en_US" ); 2025-11-30 18:45:14.302 UTC client backend[45720] pg_regress/collate ERROR: parameter "locale" must be specified 2025-11-30 18:45:14.302 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION builtin2 ( PROVIDER = builtin, LC_CTYPE = "C", LC_COLLATE = "C" ); 2025-11-30 18:45:14.303 UTC client backend[45720] pg_regress/collate ERROR: collation "default" cannot be copied 2025-11-30 18:45:14.303 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION mycoll3 FROM "default"; 2025-11-30 18:45:14.305 UTC client backend[45724] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-11-30 18:45:14.305 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:14.305 UTC client backend[45724] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-11-30 18:45:14.305 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT INTO itest2 VALUES (10, 'xyz'); 2025-11-30 18:45:14.306 UTC client backend[45720] pg_regress/collate ERROR: cannot drop collation mycoll2 because other objects depend on it 2025-11-30 18:45:14.306 UTC client backend[45720] pg_regress/collate DETAIL: column f1 of table collate_test23 depends on collation mycoll2 2025-11-30 18:45:14.306 UTC client backend[45720] pg_regress/collate HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:14.306 UTC client backend[45720] pg_regress/collate STATEMENT: DROP COLLATION mycoll2; 2025-11-30 18:45:14.306 UTC client backend[45720] pg_regress/collate ERROR: collation attribute "Lc_Collate" not recognized at character 29 2025-11-30 18:45:14.306 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION case_coll ("Lc_Collate" = "POSIX", "Lc_Ctype" = "POSIX"); 2025-11-30 18:45:14.309 UTC client backend[45720] pg_regress/collate ERROR: collations are not supported by type integer 2025-11-30 18:45:14.309 UTC client backend[45720] pg_regress/collate STATEMENT: SELECT collation for ((SELECT a FROM collate_test1 LIMIT 1)); 2025-11-30 18:45:14.309 UTC client backend[45709] pg_regress/privileges ERROR: permission denied to set role "pg_read_all_settings" 2025-11-30 18:45:14.309 UTC client backend[45709] pg_regress/privileges STATEMENT: SET ROLE pg_read_all_settings; 2025-11-30 18:45:14.310 UTC client backend[45709] pg_regress/privileges ERROR: permission denied to set role "pg_read_all_stats" 2025-11-30 18:45:14.310 UTC client backend[45709] pg_regress/privileges STATEMENT: SET ROLE pg_read_all_stats; 2025-11-30 18:45:14.318 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.318 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.318 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (4, 8); 2025-11-30 18:45:14.320 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.320 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.320 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, 77); 2025-11-30 18:45:14.320 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.320 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.320 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (6, DEFAULT), (7, 77); 2025-11-30 18:45:14.322 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.322 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.322 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, DEFAULT); 2025-11-30 18:45:14.331 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.331 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.331 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT); 2025-11-30 18:45:14.333 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:14.333 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.333 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT), (9, DEFAULT); 2025-11-30 18:45:14.337 UTC client backend[45722] pg_regress/object_address LOG: disconnection: session time: 0:00:00.586 user=postgres database=regression host=[local] 2025-11-30 18:45:14.337 UTC client backend[45724] pg_regress/identity ERROR: column "a" can only be updated to DEFAULT 2025-11-30 18:45:14.337 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:14.337 UTC client backend[45724] pg_regress/identity STATEMENT: UPDATE itest2 SET a = 101 WHERE a = 1; 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options at character 54 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LC_COLLATE = "NONSENSE", LC_CTYPE = "POSIX"); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options at character 52 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_CTYPE = "POSIX", LC_CTYPE = "NONSENSE", LC_COLLATE = "POSIX"); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options at character 48 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (PROVIDER = icu, PROVIDER = NONSENSE, LC_COLLATE = "POSIX", LC_CTYPE = "POSIX"); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options at character 47 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION case_sensitive (LOCALE = '', LOCALE = "NONSENSE"); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options at character 54 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (DETERMINISTIC = TRUE, DETERMINISTIC = NONSENSE, LOCALE = ''); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options at character 47 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (VERSION = '1', VERSION = "NONSENSE", LOCALE = ''); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate DETAIL: LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE. 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LC_CTYPE = "POSIX", LOCALE = ''); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate DETAIL: LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE. 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LOCALE = ''); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate DETAIL: LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE. 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_CTYPE = "POSIX", LOCALE = ''); 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate ERROR: conflicting or redundant options 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate DETAIL: FROM cannot be specified together with any other options. 2025-11-30 18:45:14.345 UTC client backend[45720] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (FROM = "C", VERSION = "1"); 2025-11-30 18:45:14.397 UTC client backend[45720] pg_regress/collate LOG: disconnection: session time: 0:00:00.646 user=postgres database=regression host=[local] 2025-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges ERROR: permission denied to alter role 2025-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may add or drop members. 2025-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges STATEMENT: ALTER GROUP regress_priv_group2 ADD USER regress_priv_user2; 2025-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges ERROR: permission denied to alter role 2025-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may add or drop members. 2025-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges STATEMENT: ALTER GROUP regress_priv_group2 DROP USER regress_priv_user2; 2025-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges ERROR: permission denied to alter role 2025-11-30 18:45:14.425 UTC client backend[45709] 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-11-30 18:45:14.425 UTC client backend[45709] pg_regress/privileges STATEMENT: ALTER USER regress_priv_user2 PASSWORD 'verysecret'; 2025-11-30 18:45:14.427 UTC client backend[45724] pg_regress/identity ERROR: column "a" of relation "itest4" is not an identity column 2025-11-30 18:45:14.427 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a DROP IDENTITY; 2025-11-30 18:45:14.427 UTC client backend[45724] pg_regress/identity ERROR: null value in column "a" of relation "itest4" violates not-null constraint 2025-11-30 18:45:14.427 UTC client backend[45724] pg_regress/identity DETAIL: Failing row contains (null, ). 2025-11-30 18:45:14.427 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT INTO itest4 DEFAULT VALUES; 2025-11-30 18:45:14.428 UTC client backend[45709] pg_regress/privileges ERROR: permission denied to grant privileges as role "regress_priv_role" 2025-11-30 18:45:14.428 UTC client backend[45709] pg_regress/privileges DETAIL: The grantor must have the ADMIN option on role "regress_priv_role". 2025-11-30 18:45:14.428 UTC client backend[45709] pg_regress/privileges STATEMENT: GRANT regress_priv_role TO regress_priv_user1 WITH ADMIN OPTION GRANTED BY regress_priv_role; 2025-11-30 18:45:14.431 UTC client backend[45709] pg_regress/privileges ERROR: role "foo" does not exist 2025-11-30 18:45:14.431 UTC client backend[45709] pg_regress/privileges STATEMENT: REVOKE ADMIN OPTION FOR regress_priv_role FROM regress_priv_user1 GRANTED BY foo; 2025-11-30 18:45:14.431 UTC client backend[45709] pg_regress/privileges WARNING: role "regress_priv_user1" has not been granted membership in role "regress_priv_role" by role "regress_priv_user2" 2025-11-30 18:45:14.435 UTC client backend[45715] pg_regress/replica_identity ERROR: column "id" is in index used as replica identity 2025-11-30 18:45:14.435 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity3 ALTER COLUMN id DROP NOT NULL; 2025-11-30 18:45:14.449 UTC client backend[45712] pg_regress/spgist ERROR: value 9 out of bounds for option "fillfactor" 2025-11-30 18:45:14.449 UTC client backend[45712] pg_regress/spgist DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:14.449 UTC client backend[45712] pg_regress/spgist STATEMENT: create index spgist_point_idx2 on spgist_point_tbl using spgist(p) with (fillfactor = 9); 2025-11-30 18:45:14.449 UTC client backend[45712] pg_regress/spgist ERROR: value 101 out of bounds for option "fillfactor" 2025-11-30 18:45:14.449 UTC client backend[45712] pg_regress/spgist DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:14.449 UTC client backend[45712] pg_regress/spgist STATEMENT: create index spgist_point_idx2 on spgist_point_tbl using spgist(p) with (fillfactor = 101); 2025-11-30 18:45:14.452 UTC client backend[45724] pg_regress/identity ERROR: relation "itest4_a_seq" does not exist at character 27 2025-11-30 18:45:14.452 UTC client backend[45724] pg_regress/identity STATEMENT: SELECT sequence_name FROM itest4_a_seq; 2025-11-30 18:45:14.453 UTC client backend[45718] pg_regress/generated_stored ERROR: child column "b" specifies generation expression 2025-11-30 18:45:14.453 UTC client backend[45718] pg_regress/generated_stored HINT: A child table column cannot be generated unless its parent column is. 2025-11-30 18:45:14.453 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_normal_child (a int, b int GENERATED ALWAYS AS (a * 2) STORED) INHERITS (gtest_normal); 2025-11-30 18:45:14.476 UTC client backend[45726] pg_regress/groupingsets LOG: disconnection: session time: 0:00:00.724 user=postgres database=regression host=[local] 2025-11-30 18:45:14.493 UTC client backend[45724] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-11-30 18:45:14.493 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:14.493 UTC client backend[45724] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-11-30 18:45:14.493 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT INTO itestv11 VALUES (10, 'xyz'); 2025-11-30 18:45:14.496 UTC client backend[45709] pg_regress/privileges ERROR: grantor must be current user 2025-11-30 18:45:14.496 UTC client backend[45709] pg_regress/privileges STATEMENT: GRANT TRUNCATE ON atest2 TO regress_priv_user4 GRANTED BY regress_priv_user5; 2025-11-30 18:45:14.497 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.497 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest2 VALUES ('foo', true); 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE atest2 SET col2 = NOT col2; 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest2 FOR UPDATE; 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges STATEMENT: DELETE FROM atest2; 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges STATEMENT: TRUNCATE atest2; 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.498 UTC client backend[45709] pg_regress/privileges STATEMENT: LOCK atest2 IN ACCESS EXCLUSIVE MODE; 2025-11-30 18:45:14.507 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" in child table must not be a generated column 2025-11-30 18:45:14.507 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_normal_child INHERIT gtest_normal; 2025-11-30 18:45:14.524 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.524 UTC client backend[45709] pg_regress/privileges STATEMENT: COPY atest2 FROM stdin; 2025-11-30 18:45:14.524 UTC client backend[45709] pg_regress/privileges WARNING: no privileges were granted for "atest1" 2025-11-30 18:45:14.549 UTC client backend[45710] pg_regress/rowsecurity ERROR: unrecognized row security option "ugly" at character 33 2025-11-30 18:45:14.549 UTC client backend[45710] pg_regress/rowsecurity HINT: Only PERMISSIVE or RESTRICTIVE policies are supported currently. 2025-11-30 18:45:14.549 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: CREATE POLICY p1 ON document AS UGLY USING (dlevel <= (SELECT seclv FROM uaccount WHERE pguser = current_user)); 2025-11-30 18:45:14.560 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" inherits from generated column but specifies default 2025-11-30 18:45:14.560 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtestx (x int, b int DEFAULT 10) INHERITS (gtest1); 2025-11-30 18:45:14.562 UTC client backend[45724] pg_regress/identity ERROR: column "a" of relation "itest1" is an identity column 2025-11-30 18:45:14.562 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest1 ALTER COLUMN a SET DEFAULT 1; 2025-11-30 18:45:14.570 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.570 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest2 VALUES ('foo', true); 2025-11-30 18:45:14.571 UTC client backend[45724] pg_regress/identity ERROR: column "a" of relation "itest5" already has a default value 2025-11-30 18:45:14.571 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest5 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:14.571 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest1 2025-11-30 18:45:14.571 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest1; 2025-11-30 18:45:14.571 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.571 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest2; 2025-11-30 18:45:14.578 UTC client backend[45707] pg_regress/brin ERROR: "brintest" is not an index 2025-11-30 18:45:14.578 UTC client backend[45707] pg_regress/brin STATEMENT: SELECT brin_summarize_new_values('brintest'); 2025-11-30 18:45:14.592 UTC client backend[45715] pg_regress/replica_identity ERROR: constraint "test_replica_identity5_pkey" of relation "test_replica_identity5" does not exist 2025-11-30 18:45:14.592 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity5 DROP CONSTRAINT test_replica_identity5_pkey; 2025-11-30 18:45:14.593 UTC client backend[45715] pg_regress/replica_identity ERROR: column "b" is in index used as replica identity 2025-11-30 18:45:14.593 UTC client backend[45715] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity5 ALTER b DROP NOT NULL; 2025-11-30 18:45:14.609 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table pg_class 2025-11-30 18:45:14.609 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE pg_catalog.pg_class SET relname = '123'; 2025-11-30 18:45:14.610 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" inherits from generated column but specifies identity 2025-11-30 18:45:14.610 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS IDENTITY) INHERITS (gtest1); 2025-11-30 18:45:14.612 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" inherits from generated column of different kind 2025-11-30 18:45:14.612 UTC client backend[45718] pg_regress/generated_stored DETAIL: Parent column is STORED, child column is VIRTUAL. 2025-11-30 18:45:14.612 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS (a * 22) VIRTUAL) INHERITS (gtest1); 2025-11-30 18:45:14.614 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table pg_class 2025-11-30 18:45:14.614 UTC client backend[45709] pg_regress/privileges STATEMENT: DELETE FROM pg_catalog.pg_class; 2025-11-30 18:45:14.615 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table pg_toast_1213 2025-11-30 18:45:14.615 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE pg_toast.pg_toast_1213 SET chunk_id = 1; 2025-11-30 18:45:14.623 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.623 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest2; 2025-11-30 18:45:14.624 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest1 2025-11-30 18:45:14.624 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest1 VALUES (2, 'two'); 2025-11-30 18:45:14.625 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.625 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest2 VALUES ('foo', true); 2025-11-30 18:45:14.632 UTC client backend[45707] pg_regress/brin ERROR: "tenk1_unique1" is not a BRIN index 2025-11-30 18:45:14.632 UTC client backend[45707] pg_regress/brin STATEMENT: SELECT brin_summarize_new_values('tenk1_unique1'); 2025-11-30 18:45:14.641 UTC client backend[45715] pg_regress/replica_identity LOG: disconnection: session time: 0:00:00.892 user=postgres database=regression host=[local] 2025-11-30 18:45:14.648 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" in child table must be a generated column 2025-11-30 18:45:14.648 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtestxx_1 INHERIT gtest1; 2025-11-30 18:45:14.649 UTC client backend[45724] pg_regress/identity ERROR: identity column type must be smallint, integer, or bigint 2025-11-30 18:45:14.649 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest3 ALTER COLUMN a TYPE text; 2025-11-30 18:45:14.649 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest1 2025-11-30 18:45:14.649 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest1 SELECT 1, b FROM atest1; 2025-11-30 18:45:14.651 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest1 2025-11-30 18:45:14.651 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE atest1 SET a = 1 WHERE a = 2; 2025-11-30 18:45:14.652 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.652 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE atest2 SET col2 = NOT col2; 2025-11-30 18:45:14.652 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest1 2025-11-30 18:45:14.652 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest1 FOR UPDATE; 2025-11-30 18:45:14.652 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.652 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest2 FOR UPDATE; 2025-11-30 18:45:14.653 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.653 UTC client backend[45709] pg_regress/privileges STATEMENT: DELETE FROM atest2; 2025-11-30 18:45:14.653 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.653 UTC client backend[45709] pg_regress/privileges STATEMENT: TRUNCATE atest2; 2025-11-30 18:45:14.657 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.657 UTC client backend[45709] pg_regress/privileges STATEMENT: COPY atest2 FROM stdin; 2025-11-30 18:45:14.657 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.657 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest1 WHERE ( b IN ( SELECT col1 FROM atest2 ) ); 2025-11-30 18:45:14.657 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.657 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest2 WHERE ( col1 IN ( SELECT b FROM atest1 ) ); 2025-11-30 18:45:14.658 UTC client backend[45707] pg_regress/brin ERROR: block number out of range: -1 2025-11-30 18:45:14.658 UTC client backend[45707] pg_regress/brin STATEMENT: SELECT brin_desummarize_range('brinidx', -1); 2025-11-30 18:45:14.670 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p1r" for table "document" 2025-11-30 18:45:14.670 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (100, 44, 1, 'regress_rls_dave', 'testing sorting of policies'); 2025-11-30 18:45:14.671 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p2r" for table "document" 2025-11-30 18:45:14.671 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (100, 55, 1, 'regress_rls_dave', 'testing sorting of policies'); 2025-11-30 18:45:14.671 UTC client backend[45710] pg_regress/rowsecurity ERROR: must be owner of table document 2025-11-30 18:45:14.671 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: ALTER POLICY p1 ON document USING (true); 2025-11-30 18:45:14.671 UTC client backend[45710] pg_regress/rowsecurity ERROR: must be owner of relation document 2025-11-30 18:45:14.671 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP POLICY p1 ON document; 2025-11-30 18:45:14.679 UTC client backend[45718] pg_regress/generated_stored ERROR: inherited column "b" has a generation conflict 2025-11-30 18:45:14.679 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest0, gtesty); 2025-11-30 18:45:14.699 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest12 2025-11-30 18:45:14.699 UTC client backend[45709] pg_regress/privileges STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM atest12 WHERE a >>> 0; 2025-11-30 18:45:14.699 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for view atest12v 2025-11-30 18:45:14.699 UTC client backend[45709] pg_regress/privileges STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM atest12v WHERE a >>> 0; 2025-11-30 18:45:14.699 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for view atest12sbv 2025-11-30 18:45:14.699 UTC client backend[45709] pg_regress/privileges STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM atest12sbv WHERE a >>> 0; 2025-11-30 18:45:14.711 UTC client backend[45718] pg_regress/generated_stored ERROR: inherited column "b" has a generation conflict 2025-11-30 18:45:14.711 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-11-30 18:45:14.718 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" inherits conflicting generation expressions 2025-11-30 18:45:14.718 UTC client backend[45718] pg_regress/generated_stored HINT: To resolve the conflict, specify a generation expression explicitly. 2025-11-30 18:45:14.718 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-11-30 18:45:14.719 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest3 2025-11-30 18:45:14.719 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest3; 2025-11-30 18:45:14.732 UTC client backend[45661] postgres_fdw LOG: disconnection: session time: 0:00:01.239 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:14.734 UTC client backend[45707] pg_regress/brin ERROR: block number out of range: -1 2025-11-30 18:45:14.734 UTC client backend[45707] pg_regress/brin STATEMENT: SELECT brin_summarize_range('brin_summarize_idx', -1); 2025-11-30 18:45:14.734 UTC client backend[45707] pg_regress/brin ERROR: block number out of range: 4294967296 2025-11-30 18:45:14.734 UTC client backend[45707] pg_regress/brin STATEMENT: SELECT brin_summarize_range('brin_summarize_idx', 4294967296); 2025-11-30 18:45:14.748 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest3 2025-11-30 18:45:14.748 UTC client backend[45709] pg_regress/privileges STATEMENT: DELETE FROM atest3; 2025-11-30 18:45:14.748 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest3 2025-11-30 18:45:14.748 UTC client backend[45709] pg_regress/privileges STATEMENT: DELETE FROM atest3; 2025-11-30 18:45:14.762 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.762 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atestv2; 2025-11-30 18:45:14.772 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for view atestv2 2025-11-30 18:45:14.772 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atestv2; 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored STATEMENT: COPY gtest1 (a, b) TO stdout; 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored STATEMENT: COPY gtest1 (a, b) FROM stdin; 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored ERROR: generated columns are not supported in COPY FROM WHERE conditions 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored STATEMENT: COPY gtest1 FROM stdin WHERE b <> 10; 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored ERROR: generated columns are not supported in COPY FROM WHERE conditions 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:14.776 UTC client backend[45718] pg_regress/generated_stored STATEMENT: COPY gtest1 FROM stdin WHERE gtest1 IS NULL; 2025-11-30 18:45:14.776 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for view atestv0 2025-11-30 18:45:14.776 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atestv0; 2025-11-30 18:45:14.778 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table int8_tbl 2025-11-30 18:45:14.778 UTC client backend[45709] 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-11-30 18:45:14.779 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-11-30 18:45:14.779 UTC client backend[45718] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:14.779 UTC client backend[45718] pg_regress/generated_stored STATEMENT: COPY gtest3 (a, b) TO stdout; 2025-11-30 18:45:14.779 UTC client backend[45718] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-11-30 18:45:14.779 UTC client backend[45718] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:14.779 UTC client backend[45718] pg_regress/generated_stored STATEMENT: COPY gtest3 (a, b) FROM stdin; 2025-11-30 18:45:14.781 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table int8_tbl 2025-11-30 18:45:14.781 UTC client backend[45709] 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-11-30 18:45:14.785 UTC client backend[45710] pg_regress/rowsecurity ERROR: update or delete on table "category" violates foreign key constraint "document_cid_fkey" on table "document" 2025-11-30 18:45:14.785 UTC client backend[45710] pg_regress/rowsecurity DETAIL: Key is still referenced from table "document". 2025-11-30 18:45:14.785 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DELETE FROM category WHERE cid = 33; 2025-11-30 18:45:14.786 UTC client backend[45725] pg_regress/gist ERROR: lossy distance functions are not supported in index-only scans 2025-11-30 18:45:14.786 UTC client backend[45725] pg_regress/gist STATEMENT: select p from gist_tbl order by circle(p,1) <-> point(0,0) limit 1; 2025-11-30 18:45:14.791 UTC client backend[45712] pg_regress/spgist LOG: disconnection: session time: 0:00:01.042 user=postgres database=regression host=[local] 2025-11-30 18:45:14.794 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for view atestv3 2025-11-30 18:45:14.794 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atestv3; 2025-11-30 18:45:14.798 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:14.798 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atestv2; 2025-11-30 18:45:14.804 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.804 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest5; 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT two FROM atest5; 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges STATEMENT: COPY atest5 (two) TO stdout; 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT atest5 FROM atest5; 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.805 UTC client backend[45709] pg_regress/privileges STATEMENT: COPY atest5 (one,two) TO stdout; 2025-11-30 18:45:14.808 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.808 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT 1 FROM atest5 a JOIN atest5 b USING (two); 2025-11-30 18:45:14.808 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.808 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT 1 FROM atest5 a NATURAL JOIN atest5 b; 2025-11-30 18:45:14.809 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.809 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM (atest5 a JOIN atest5 b USING (one)) j; 2025-11-30 18:45:14.809 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.809 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT j.* FROM (atest5 a JOIN atest5 b USING (one)) j; 2025-11-30 18:45:14.809 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.809 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT (j.*) IS NULL FROM (atest5 a JOIN atest5 b USING (one)) j; 2025-11-30 18:45:14.811 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.811 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-11-30 18:45:14.811 UTC client backend[45710] pg_regress/rowsecurity ERROR: duplicate key value violates unique constraint "document_pkey" 2025-11-30 18:45:14.811 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (8, 44, 1, 'regress_rls_bob', 'my third manga'); 2025-11-30 18:45:14.811 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.811 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT j.two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-11-30 18:45:14.811 UTC unrecognized[45760] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:14.812 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.812 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-11-30 18:45:14.812 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.812 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT j.y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-11-30 18:45:14.812 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.812 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM (atest5 a JOIN atest5 b USING (one)); 2025-11-30 18:45:14.813 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.813 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT a.* FROM (atest5 a JOIN atest5 b USING (one)); 2025-11-30 18:45:14.813 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.813 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT (a.*) IS NULL FROM (atest5 a JOIN atest5 b USING (one)); 2025-11-30 18:45:14.815 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.815 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.815 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.815 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT a.two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.816 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.816 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.816 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.816 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT b.y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.816 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.816 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a LEFT JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.817 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.817 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT b.y FROM (atest5 a LEFT JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.817 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.817 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a FULL JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.818 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.818 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT b.y FROM (atest5 a FULL JOIN atest5 b(one,x,y,z) USING (one)); 2025-11-30 18:45:14.818 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.818 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT 1 FROM atest5 WHERE two = 2; 2025-11-30 18:45:14.818 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.818 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest1, atest5; 2025-11-30 18:45:14.821 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.821 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT atest1.*,atest5.one FROM atest1 JOIN atest5 ON (atest1.a = atest5.two); 2025-11-30 18:45:14.822 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.822 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT one, two FROM atest5; 2025-11-30 18:45:14.823 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.823 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT one, two FROM atest5 NATURAL JOIN atest6; 2025-11-30 18:45:14.826 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.826 UTC client backend[45709] pg_regress/privileges STATEMENT: COPY atest5 FROM stdin; 2025-11-30 18:45:14.826 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.826 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5 (three) VALUES (4); 2025-11-30 18:45:14.826 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.826 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5 VALUES (5,5,5); 2025-11-30 18:45:14.827 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.827 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE atest5 SET one = 8; 2025-11-30 18:45:14.827 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.827 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE atest5 SET three = 5, one = 2; 2025-11-30 18:45:14.828 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.828 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set three = 10 RETURNING atest5.three; 2025-11-30 18:45:14.828 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.828 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set three = EXCLUDED.three; 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set one = 8; 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5(three) VALUES (4) ON CONFLICT (two) DO UPDATE set three = 10; 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5(four) VALUES (4); 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.829 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5(four) VALUES (4) ON CONFLICT (four) DO UPDATE set three = 3; 2025-11-30 18:45:14.830 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.830 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO atest5(four) VALUES (4) ON CONFLICT ON CONSTRAINT atest5_four_key DO UPDATE set three = 3; 2025-11-30 18:45:14.830 UTC client backend[45760] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:14.830 UTC client backend[45760] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:14.830 UTC client backend[45724] pg_regress/identity ERROR: column "b" of relation "itest6" is not an identity column 2025-11-30 18:45:14.830 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest6 ALTER COLUMN b SET INCREMENT BY 2; 2025-11-30 18:45:14.831 UTC client backend[45760] postgres_fdw LOG: connection ready: setup total=20.258 ms, fork=0.808 ms, authentication=0.122 ms 2025-11-30 18:45:14.831 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:14.831 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (8, 44, 1, 'regress_rls_carol', 'my third manga'); 2025-11-30 18:45:14.832 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.832 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT one FROM atest5; 2025-11-30 18:45:14.832 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:14.832 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE atest5 SET one = 1; 2025-11-30 18:45:14.833 UTC client backend[45724] pg_regress/identity ERROR: cannot change ownership of identity sequence 2025-11-30 18:45:14.833 UTC client backend[45724] pg_regress/identity DETAIL: Sequence "itest6_a_seq" is linked to table "itest6". 2025-11-30 18:45:14.833 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER SEQUENCE itest6_a_seq OWNED BY NONE; 2025-11-30 18:45:14.834 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:14.834 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: UPDATE document SET did = 8, dauthor = 'regress_rls_carol' WHERE did = 5; 2025-11-30 18:45:14.848 UTC client backend[45708] pg_regress/gin LOG: disconnection: session time: 0:00:01.113 user=postgres database=regression host=[local] 2025-11-30 18:45:14.856 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot drop column b of table gtest10 because other objects depend on it 2025-11-30 18:45:14.856 UTC client backend[45718] pg_regress/generated_stored DETAIL: column c of table gtest10 depends on column b of table gtest10 2025-11-30 18:45:14.856 UTC client backend[45718] pg_regress/generated_stored HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:14.856 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest10 DROP COLUMN b; 2025-11-30 18:45:14.871 UTC client backend[45760] postgres_fdw LOG: disconnection: session time: 0:00:00.059 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:14.892 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table msource 2025-11-30 18:45:14.892 UTC client backend[45709] 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-11-30 18:45:14.892 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table msource 2025-11-30 18:45:14.892 UTC client backend[45709] 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-11-30 18:45:14.894 UTC client backend[45723] pg_regress/matview ERROR: cannot refresh materialized view "public.mvtest_tvmm" concurrently 2025-11-30 18:45:14.894 UTC client backend[45723] pg_regress/matview HINT: Create a unique index with no WHERE clause on one or more columns of the materialized view. 2025-11-30 18:45:14.894 UTC client backend[45723] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_tvmm; 2025-11-30 18:45:14.901 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table msource 2025-11-30 18:45:14.901 UTC client backend[45709] 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-11-30 18:45:14.904 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table mtarget 2025-11-30 18:45:14.904 UTC client backend[45709] 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-11-30 18:45:14.905 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table mtarget 2025-11-30 18:45:14.905 UTC client backend[45709] 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-11-30 18:45:14.905 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table mtarget 2025-11-30 18:45:14.905 UTC client backend[45709] 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-11-30 18:45:14.906 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table mtarget 2025-11-30 18:45:14.906 UTC client backend[45709] 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-11-30 18:45:14.915 UTC client backend[45723] pg_regress/matview ERROR: CONCURRENTLY and WITH NO DATA options cannot be used together 2025-11-30 18:45:14.915 UTC client backend[45723] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_tvmm WITH NO DATA; 2025-11-30 18:45:14.916 UTC client backend[45723] pg_regress/matview ERROR: cannot lock rows in materialized view "mvtest_tvvm" 2025-11-30 18:45:14.916 UTC client backend[45723] pg_regress/matview STATEMENT: SELECT * FROM mvtest_tvvm FOR SHARE; 2025-11-30 18:45:14.918 UTC client backend[45723] pg_regress/matview ERROR: materialized views must not use temporary objects 2025-11-30 18:45:14.918 UTC client backend[45723] pg_regress/matview DETAIL: This view depends on temporary table mvtest_temp_t. 2025-11-30 18:45:14.918 UTC client backend[45723] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW mvtest_temp_tm AS SELECT * FROM mvtest_temp_t; 2025-11-30 18:45:14.921 UTC client backend[45724] pg_regress/identity ERROR: cannot recursively add identity column to table that has child tables 2025-11-30 18:45:14.921 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest7d ADD COLUMN b int GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:14.922 UTC client backend[45723] pg_regress/matview ERROR: cannot drop table mvtest_t because other objects depend on it 2025-11-30 18:45:14.922 UTC client backend[45723] 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-11-30 18:45:14.922 UTC client backend[45723] pg_regress/matview HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:14.922 UTC client backend[45723] pg_regress/matview STATEMENT: DROP TABLE mvtest_t; 2025-11-30 18:45:14.934 UTC client backend[45709] pg_regress/privileges ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-11-30 18:45:14.934 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO t1 (c1, c2) VALUES (1, 1); 2025-11-30 18:45:14.935 UTC client backend[45709] pg_regress/privileges ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-11-30 18:45:14.935 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE t1 SET c2 = 1; 2025-11-30 18:45:14.936 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "c1" of relation "t1" violates not-null constraint 2025-11-30 18:45:14.936 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (c1, c2) = (null, null). 2025-11-30 18:45:14.936 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO t1 (c1, c2) VALUES (null, null); 2025-11-30 18:45:14.936 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "c1" of relation "t1" violates not-null constraint 2025-11-30 18:45:14.936 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (c1, c3) = (null, null). 2025-11-30 18:45:14.936 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO t1 (c3) VALUES (null); 2025-11-30 18:45:14.937 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "c2" of relation "t1" violates not-null constraint 2025-11-30 18:45:14.937 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (c1) = (5). 2025-11-30 18:45:14.937 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO t1 (c1) VALUES (5); 2025-11-30 18:45:14.937 UTC client backend[45709] pg_regress/privileges ERROR: new row for relation "t1" violates check constraint "t1_c3_check" 2025-11-30 18:45:14.937 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (c1, c3) = (1, 10). 2025-11-30 18:45:14.937 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE t1 SET c3 = 10; 2025-11-30 18:45:14.960 UTC client backend[45718] pg_regress/generated_stored ERROR: permission denied for table gtest11 2025-11-30 18:45:14.960 UTC client backend[45718] pg_regress/generated_stored STATEMENT: SELECT a, b FROM gtest11; 2025-11-30 18:45:14.962 UTC client backend[45718] pg_regress/generated_stored ERROR: permission denied for function gf1 2025-11-30 18:45:14.962 UTC client backend[45718] pg_regress/generated_stored STATEMENT: SELECT gf1(10); 2025-11-30 18:45:14.963 UTC client backend[45718] pg_regress/generated_stored ERROR: permission denied for function gf1 2025-11-30 18:45:14.963 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest12 VALUES (3, 30), (4, 40); 2025-11-30 18:45:14.963 UTC client backend[45725] pg_regress/gist LOG: disconnection: session time: 0:00:01.208 user=postgres database=regression host=[local] 2025-11-30 18:45:14.965 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot drop function gf1(integer) because other objects depend on it 2025-11-30 18:45:14.965 UTC client backend[45718] pg_regress/generated_stored DETAIL: column c of table gtest12 depends on function gf1(integer) 2025-11-30 18:45:14.965 UTC client backend[45718] pg_regress/generated_stored HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:14.965 UTC client backend[45718] pg_regress/generated_stored STATEMENT: DROP FUNCTION gf1(int); 2025-11-30 18:45:14.972 UTC unrecognized[45772] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:14.972 UTC client backend[45772] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:14.972 UTC client backend[45772] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:14.973 UTC client backend[45772] postgres_fdw LOG: connection ready: setup total=1.691 ms, fork=0.284 ms, authentication=0.122 ms 2025-11-30 18:45:14.976 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_1" violates not-null constraint 2025-11-30 18:45:14.976 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaa, null, null). 2025-11-30 18:45:14.976 UTC client backend[45709] pg_regress/privileges STATEMENT: INSERT INTO errtst (a, b) VALUES ('aaa', NULL); 2025-11-30 18:45:14.977 UTC client backend[45718] pg_regress/generated_stored ERROR: new row for relation "gtest20" violates check constraint "gtest20_b_check" 2025-11-30 18:45:14.977 UTC client backend[45718] pg_regress/generated_stored DETAIL: Failing row contains (30, 60). 2025-11-30 18:45:14.977 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest20 (a) VALUES (30); 2025-11-30 18:45:14.980 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_1" violates not-null constraint 2025-11-30 18:45:14.980 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaa, null, ccc). 2025-11-30 18:45:14.980 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE errtst SET b = NULL; 2025-11-30 18:45:14.981 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_1" violates not-null constraint 2025-11-30 18:45:14.981 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaa, null, ccc). 2025-11-30 18:45:14.981 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE errtst SET a = 'aaa', b = NULL; 2025-11-30 18:45:14.982 UTC client backend[45718] pg_regress/generated_stored ERROR: check constraint "gtest20_b_check" of relation "gtest20" is violated by some row 2025-11-30 18:45:14.982 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20 ALTER COLUMN b SET EXPRESSION AS (a * 100); 2025-11-30 18:45:14.982 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_2" violates not-null constraint 2025-11-30 18:45:14.982 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaaa, null, ccc). 2025-11-30 18:45:14.982 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE errtst SET a = 'aaaa', b = NULL; 2025-11-30 18:45:14.987 UTC client backend[45709] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_2" violates not-null constraint 2025-11-30 18:45:14.987 UTC client backend[45709] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaaa, null, ccc). 2025-11-30 18:45:14.987 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE errtst SET a = 'aaaa', b = NULL WHERE a = 'aaa'; 2025-11-30 18:45:14.994 UTC client backend[45718] pg_regress/generated_stored ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-11-30 18:45:14.994 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20a ADD CHECK (b < 50); 2025-11-30 18:45:14.997 UTC client backend[45718] pg_regress/generated_stored ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-11-30 18:45:14.997 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20a ADD COLUMN c float8 DEFAULT random() CHECK (b < 50); 2025-11-30 18:45:15.003 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest6 2025-11-30 18:45:15.003 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT atest6 FROM atest6; 2025-11-30 18:45:15.004 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:15.004 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT one FROM atest5 NATURAL JOIN atest6; 2025-11-30 18:45:15.006 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest6 2025-11-30 18:45:15.006 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT * FROM atest6; 2025-11-30 18:45:15.006 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest6 2025-11-30 18:45:15.006 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT 1 FROM atest6; 2025-11-30 18:45:15.006 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atest5 2025-11-30 18:45:15.006 UTC client backend[45709] pg_regress/privileges STATEMENT: DELETE FROM atest5 WHERE one = 1; 2025-11-30 18:45:15.011 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atestc 2025-11-30 18:45:15.011 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT fy FROM atestc; 2025-11-30 18:45:15.015 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atestc 2025-11-30 18:45:15.015 UTC client backend[45709] pg_regress/privileges STATEMENT: SELECT f2 FROM atestc; 2025-11-30 18:45:15.016 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atestc 2025-11-30 18:45:15.016 UTC client backend[45709] pg_regress/privileges STATEMENT: DELETE FROM atestc; 2025-11-30 18:45:15.017 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atestc 2025-11-30 18:45:15.017 UTC client backend[45709] pg_regress/privileges STATEMENT: UPDATE atestc SET f1 = 1; 2025-11-30 18:45:15.017 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atestc 2025-11-30 18:45:15.017 UTC client backend[45709] pg_regress/privileges STATEMENT: TRUNCATE atestc; 2025-11-30 18:45:15.017 UTC client backend[45709] pg_regress/privileges ERROR: permission denied for table atestc 2025-11-30 18:45:15.017 UTC client backend[45709] pg_regress/privileges STATEMENT: LOCK atestc; 2025-11-30 18:45:15.021 UTC client backend[45772] postgres_fdw ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-11-30 18:45:15.021 UTC client backend[45772] postgres_fdw DETAIL: Failing row contains (-1, xyzzy). 2025-11-30 18:45:15.021 UTC client backend[45772] postgres_fdw STATEMENT: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) 2025-11-30 18:45:15.022 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-11-30 18:45:15.022 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (-1, xyzzy). 2025-11-30 18:45:15.022 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) COPY rem2, line 1: "-1 xyzzy" 2025-11-30 18:45:15.022 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: copy rem2 from stdin; 2025-11-30 18:45:15.034 UTC client backend[45718] pg_regress/generated_stored ERROR: check constraint "chk" of relation "gtest20b" is violated by some row 2025-11-30 18:45:15.034 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20b VALIDATE CONSTRAINT chk; 2025-11-30 18:45:15.037 UTC unrecognized[45775] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.037 UTC client backend[45775] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.037 UTC client backend[45775] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.038 UTC client backend[45775] pg_regress/privileges LOG: connection ready: setup total=11.781 ms, fork=10.335 ms, authentication=0.128 ms 2025-11-30 18:45:15.039 UTC client backend[45775] pg_regress/privileges ERROR: language "c" is not trusted 2025-11-30 18:45:15.039 UTC client backend[45775] pg_regress/privileges DETAIL: GRANT and REVOKE are not allowed on untrusted languages, because only superusers can use untrusted languages. 2025-11-30 18:45:15.039 UTC client backend[45775] pg_regress/privileges STATEMENT: GRANT USAGE ON LANGUAGE c TO PUBLIC; 2025-11-30 18:45:15.039 UTC client backend[45775] pg_regress/privileges WARNING: no privileges were granted for "sql" 2025-11-30 18:45:15.042 UTC client backend[45724] pg_regress/identity ERROR: column "f22" of relation "itest8" contains null values 2025-11-30 18:45:15.042 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE itest8 ADD COLUMN f22 int NOT NULL, ALTER COLUMN f22 ADD GENERATED ALWAYS AS IDENTITY; 2025-11-30 18:45:15.044 UTC client backend[45775] pg_regress/privileges ERROR: priv_testproc1(integer) is not a function 2025-11-30 18:45:15.044 UTC client backend[45775] pg_regress/privileges STATEMENT: REVOKE ALL ON FUNCTION priv_testproc1(int) FROM PUBLIC; 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges ERROR: invalid privilege type USAGE for function 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges STATEMENT: GRANT USAGE ON FUNCTION priv_testfunc1(int) TO regress_priv_user3; 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges ERROR: invalid privilege type USAGE for function 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges STATEMENT: GRANT USAGE ON FUNCTION priv_testagg1(int) TO regress_priv_user3; 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges ERROR: invalid privilege type USAGE for procedure 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges STATEMENT: GRANT USAGE ON PROCEDURE priv_testproc1(int) TO regress_priv_user3; 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges ERROR: function priv_testfunc_nosuch(integer) does not exist 2025-11-30 18:45:15.045 UTC client backend[45775] pg_regress/privileges STATEMENT: GRANT ALL PRIVILEGES ON FUNCTION priv_testfunc_nosuch(int) TO regress_priv_user4; 2025-11-30 18:45:15.047 UTC client backend[45775] pg_regress/privileges ERROR: permission denied for language sql 2025-11-30 18:45:15.047 UTC client backend[45775] pg_regress/privileges STATEMENT: CREATE FUNCTION priv_testfunc3(int) RETURNS int AS 'select 2 * $1;' LANGUAGE sql; 2025-11-30 18:45:15.047 UTC client backend[45775] pg_regress/privileges ERROR: permission denied for function priv_testfunc1 2025-11-30 18:45:15.047 UTC client backend[45775] pg_regress/privileges STATEMENT: SELECT priv_testfunc1(5); 2025-11-30 18:45:15.048 UTC client backend[45775] pg_regress/privileges ERROR: permission denied for aggregate priv_testagg1 2025-11-30 18:45:15.048 UTC client backend[45775] pg_regress/privileges STATEMENT: SELECT priv_testagg1(x) FROM (VALUES (1), (2), (3)) _(x); 2025-11-30 18:45:15.048 UTC client backend[45775] pg_regress/privileges ERROR: permission denied for procedure priv_testproc1 2025-11-30 18:45:15.048 UTC client backend[45775] pg_regress/privileges STATEMENT: CALL priv_testproc1(6); 2025-11-30 18:45:15.048 UTC client backend[45775] pg_regress/privileges ERROR: permission denied for table atest2 2025-11-30 18:45:15.048 UTC client backend[45775] pg_regress/privileges STATEMENT: SELECT col1 FROM atest2 WHERE col2 = true; 2025-11-30 18:45:15.049 UTC client backend[45775] pg_regress/privileges ERROR: must be owner of function priv_testfunc1 2025-11-30 18:45:15.049 UTC client backend[45775] pg_regress/privileges STATEMENT: DROP FUNCTION priv_testfunc1(int); 2025-11-30 18:45:15.049 UTC client backend[45775] pg_regress/privileges ERROR: must be owner of aggregate priv_testagg1 2025-11-30 18:45:15.049 UTC client backend[45775] pg_regress/privileges STATEMENT: DROP AGGREGATE priv_testagg1(int); 2025-11-30 18:45:15.049 UTC client backend[45775] pg_regress/privileges ERROR: must be owner of procedure priv_testproc1 2025-11-30 18:45:15.049 UTC client backend[45775] pg_regress/privileges STATEMENT: DROP PROCEDURE priv_testproc1(int); 2025-11-30 18:45:15.049 UTC client backend[45718] pg_regress/generated_stored ERROR: new row for relation "gtest20c" violates check constraint "whole_row_check" 2025-11-30 18:45:15.049 UTC client backend[45718] pg_regress/generated_stored DETAIL: Failing row contains (null, null). 2025-11-30 18:45:15.049 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest20c VALUES (NULL); 2025-11-30 18:45:15.051 UTC client backend[45709] pg_regress/privileges LOG: disconnection: session time: 0:00:01.301 user=postgres database=regression host=[local] 2025-11-30 18:45:15.051 UTC client backend[45723] pg_regress/matview ERROR: could not create unique index "mvtest_mv_a_idx" 2025-11-30 18:45:15.051 UTC client backend[45723] pg_regress/matview DETAIL: Key (a)=(1) is duplicated. 2025-11-30 18:45:15.051 UTC client backend[45723] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW mvtest_mv; 2025-11-30 18:45:15.052 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "part_document" 2025-11-30 18:45:15.052 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 11, 5, 'regress_rls_dave', 'testing pp1'); 2025-11-30 18:45:15.055 UTC unrecognized[45778] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.055 UTC client backend[45723] pg_regress/matview ERROR: new data for materialized view "mvtest_mv" contains duplicate rows without any null columns 2025-11-30 18:45:15.055 UTC client backend[45723] pg_regress/matview DETAIL: Row: (1,10) 2025-11-30 18:45:15.055 UTC client backend[45723] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_mv; 2025-11-30 18:45:15.055 UTC client backend[45778] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.055 UTC client backend[45778] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.056 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy "pp1r" for table "part_document" 2025-11-30 18:45:15.056 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 99, 1, 'regress_rls_dave', 'testing pp1r'); 2025-11-30 18:45:15.056 UTC client backend[45778] pg_regress/privileges LOG: connection ready: setup total=2.956 ms, fork=1.464 ms, authentication=0.116 ms 2025-11-30 18:45:15.057 UTC client backend[45775] pg_regress/privileges LOG: disconnection: session time: 0:00:00.019 user=postgres database=regression host=[local] 2025-11-30 18:45:15.059 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy "pp1r" for table "part_document" 2025-11-30 18:45:15.059 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 55, 1, 'regress_rls_dave', 'testing RLS with partitions'); 2025-11-30 18:45:15.059 UTC client backend[45718] pg_regress/generated_stored ERROR: null value in column "b" of relation "gtest21a" violates not-null constraint 2025-11-30 18:45:15.059 UTC client backend[45718] pg_regress/generated_stored DETAIL: Failing row contains (0, null). 2025-11-30 18:45:15.059 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest21a (a) VALUES (0); 2025-11-30 18:45:15.061 UTC client backend[45778] pg_regress/privileges ERROR: permission denied for function int8 2025-11-30 18:45:15.061 UTC client backend[45778] pg_regress/privileges STATEMENT: SELECT '{1}'::int4[]::int8[]; 2025-11-30 18:45:15.062 UTC unrecognized[45780] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.063 UTC client backend[45780] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.063 UTC client backend[45780] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.063 UTC client backend[45780] pg_regress/privileges LOG: connection ready: setup total=1.934 ms, fork=0.561 ms, authentication=0.114 ms 2025-11-30 18:45:15.066 UTC client backend[45778] pg_regress/privileges LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression host=[local] 2025-11-30 18:45:15.066 UTC client backend[45780] pg_regress/privileges ERROR: cannot set privileges of array types 2025-11-30 18:45:15.066 UTC client backend[45780] pg_regress/privileges HINT: Set the privileges of the element type instead. 2025-11-30 18:45:15.066 UTC client backend[45780] pg_regress/privileges STATEMENT: GRANT USAGE ON TYPE _priv_testtype1 TO regress_priv_user2; 2025-11-30 18:45:15.066 UTC client backend[45780] pg_regress/privileges ERROR: "priv_testtype1" is not a domain 2025-11-30 18:45:15.066 UTC client backend[45780] pg_regress/privileges STATEMENT: GRANT USAGE ON DOMAIN priv_testtype1 TO regress_priv_user2; 2025-11-30 18:45:15.071 UTC client backend[45724] pg_regress/identity ERROR: identity columns are not supported on typed tables 2025-11-30 18:45:15.071 UTC client backend[45724] pg_regress/identity STATEMENT: CREATE TABLE itest12 OF itest_type (f1 WITH OPTIONS GENERATED ALWAYS AS IDENTITY); 2025-11-30 18:45:15.071 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.071 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE AGGREGATE priv_testagg1a(priv_testdomain1) (sfunc = int4_sum, stype = bigint); 2025-11-30 18:45:15.072 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.072 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE DOMAIN priv_testdomain2a AS priv_testdomain1; 2025-11-30 18:45:15.075 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.075 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE CAST (priv_testdomain1 AS priv_testdomain3a) WITH FUNCTION castfunc(int); 2025-11-30 18:45:15.081 UTC client backend[45724] pg_regress/identity ERROR: column "f3" in child table "pitest1_p2" must be marked NOT NULL 2025-11-30 18:45:15.081 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ATTACH PARTITION pitest1_p2 FOR VALUES FROM ('2016-08-01') TO ('2016-09-01'); 2025-11-30 18:45:15.086 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.086 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE FUNCTION priv_testfunc5a(a priv_testdomain1) RETURNS int LANGUAGE SQL AS $$ SELECT $1 $$; 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE FUNCTION priv_testfunc6a(b int) RETURNS priv_testdomain1 LANGUAGE SQL AS $$ SELECT $1::priv_testdomain1 $$; 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE OPERATOR !+! (PROCEDURE = int4pl, LEFTARG = priv_testdomain1, RIGHTARG = priv_testdomain1); 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE TABLE test5a (a int, b priv_testdomain1); 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testtype1 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE TABLE test6a OF priv_testtype1; 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testtype1 2025-11-30 18:45:15.087 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE TABLE test10a (a int[], b priv_testtype1[]); 2025-11-30 18:45:15.087 UTC client backend[45718] pg_regress/generated_stored ERROR: null value in column "b" of relation "gtest21b" violates not-null constraint 2025-11-30 18:45:15.087 UTC client backend[45718] pg_regress/generated_stored DETAIL: Failing row contains (0, null). 2025-11-30 18:45:15.087 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest21b (a) VALUES (0); 2025-11-30 18:45:15.088 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.088 UTC client backend[45780] pg_regress/privileges STATEMENT: ALTER TABLE test9a ADD COLUMN c priv_testdomain1; 2025-11-30 18:45:15.088 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.088 UTC client backend[45780] pg_regress/privileges STATEMENT: ALTER TABLE test9a ALTER COLUMN b TYPE priv_testdomain1; 2025-11-30 18:45:15.088 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.088 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE TYPE test7a AS (a int, b priv_testdomain1); 2025-11-30 18:45:15.091 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.091 UTC client backend[45780] pg_regress/privileges STATEMENT: ALTER TYPE test8a ADD ATTRIBUTE c priv_testdomain1; 2025-11-30 18:45:15.092 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.092 UTC client backend[45780] pg_regress/privileges STATEMENT: ALTER TYPE test8a ALTER ATTRIBUTE b TYPE priv_testdomain1; 2025-11-30 18:45:15.092 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-11-30 18:45:15.092 UTC client backend[45780] pg_regress/privileges STATEMENT: CREATE TABLE test11a AS (SELECT 1::priv_testdomain1 AS a); 2025-11-30 18:45:15.092 UTC client backend[45780] pg_regress/privileges ERROR: permission denied for type priv_testtype1 2025-11-30 18:45:15.092 UTC client backend[45780] pg_regress/privileges STATEMENT: REVOKE ALL ON TYPE priv_testtype1 FROM PUBLIC; 2025-11-30 18:45:15.094 UTC client backend[45780] pg_regress/privileges WARNING: cast will be ignored because the source data type is a domain 2025-11-30 18:45:15.096 UTC client backend[45718] pg_regress/generated_stored ERROR: duplicate key value violates unique constraint "gtest22a_b_key" 2025-11-30 18:45:15.096 UTC client backend[45718] pg_regress/generated_stored DETAIL: Key (b)=(1) already exists. 2025-11-30 18:45:15.096 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest22a VALUES (3); 2025-11-30 18:45:15.097 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "part_document_satire" 2025-11-30 18:45:15.097 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document_satire VALUES (101, 55, 1, 'regress_rls_dave', 'testing RLS with partitions'); 2025-11-30 18:45:15.106 UTC client backend[45710] pg_regress/rowsecurity ERROR: must be owner of table part_document 2025-11-30 18:45:15.106 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: ALTER POLICY pp1 ON part_document USING (true); 2025-11-30 18:45:15.107 UTC client backend[45710] pg_regress/rowsecurity ERROR: must be owner of relation part_document 2025-11-30 18:45:15.107 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP POLICY pp1 ON part_document; 2025-11-30 18:45:15.109 UTC client backend[45718] pg_regress/generated_stored ERROR: duplicate key value violates unique constraint "gtest22b_pkey" 2025-11-30 18:45:15.109 UTC client backend[45718] pg_regress/generated_stored DETAIL: Key (a, b)=(2, 1) already exists. 2025-11-30 18:45:15.109 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest22b VALUES (2); 2025-11-30 18:45:15.126 UTC client backend[45723] pg_regress/matview ERROR: too many column names were specified 2025-11-30 18:45:15.126 UTC client backend[45723] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW mvtest_mv_v (ii, jj, kk) AS SELECT i, j FROM mvtest_v; 2025-11-30 18:45:15.135 UTC client backend[45723] pg_regress/matview ERROR: too many column names were specified 2025-11-30 18:45:15.135 UTC client backend[45723] 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-11-30 18:45:15.142 UTC client backend[45724] pg_regress/identity ERROR: cannot change identity column of a partition 2025-11-30 18:45:15.142 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest2_p1 ALTER COLUMN f3 SET GENERATED BY DEFAULT; 2025-11-30 18:45:15.144 UTC client backend[45724] pg_regress/identity ERROR: cannot change identity column of a partition 2025-11-30 18:45:15.144 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest2_p1 ALTER COLUMN f3 SET INCREMENT BY 2; 2025-11-30 18:45:15.145 UTC client backend[45780] pg_regress/privileges WARNING: no privileges could be revoked for "priv_testtype1" 2025-11-30 18:45:15.146 UTC client backend[45724] pg_regress/identity ERROR: cannot change identity column of only the partitioned table 2025-11-30 18:45:15.146 UTC client backend[45724] pg_regress/identity HINT: Do not specify the ONLY keyword. 2025-11-30 18:45:15.146 UTC client backend[45724] 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-11-30 18:45:15.147 UTC unrecognized[45788] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.147 UTC client backend[45788] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.147 UTC client backend[45788] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.148 UTC client backend[45788] pg_regress/privileges LOG: connection ready: setup total=2.158 ms, fork=0.750 ms, authentication=0.116 ms 2025-11-30 18:45:15.149 UTC client backend[45780] pg_regress/privileges LOG: disconnection: session time: 0:00:00.086 user=postgres database=regression host=[local] 2025-11-30 18:45:15.149 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "part_document" 2025-11-30 18:45:15.149 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM part_document ORDER by did; 2025-11-30 18:45:15.149 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "part_document_satire" 2025-11-30 18:45:15.149 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM part_document_satire ORDER by did; 2025-11-30 18:45:15.151 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy "pp3" for table "part_document" 2025-11-30 18:45:15.151 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 11, 5, 'regress_rls_carol', 'testing pp3'); 2025-11-30 18:45:15.154 UTC client backend[45710] pg_regress/rowsecurity ERROR: cannot drop table dependee because other objects depend on it 2025-11-30 18:45:15.154 UTC client backend[45710] pg_regress/rowsecurity DETAIL: policy d1 on table dependent depends on table dependee 2025-11-30 18:45:15.154 UTC client backend[45710] pg_regress/rowsecurity HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:15.154 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP TABLE dependee; 2025-11-30 18:45:15.161 UTC client backend[45710] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-11-30 18:45:15.161 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-11-30 18:45:15.173 UTC client backend[45710] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-11-30 18:45:15.173 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-11-30 18:45:15.174 UTC client backend[45724] pg_regress/identity ERROR: null value in column "f3" of relation "pitest2_p1" violates not-null constraint 2025-11-30 18:45:15.174 UTC client backend[45724] pg_regress/identity DETAIL: Failing row contains (07-07-2016, from pitest2_p1, null). 2025-11-30 18:45:15.174 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT into pitest2_p1 (f1, f2) VALUES ('2016-07-7', 'from pitest2_p1'); 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges ERROR: permission denied for table atest3 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges STATEMENT: TRUNCATE atest3; 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges ERROR: relation "pg_shad" does not exist 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges STATEMENT: select has_table_privilege('pg_shad','select'); 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges ERROR: role "nosuchuser" does not exist 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges STATEMENT: select has_table_privilege('nosuchuser','pg_authid','select'); 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges ERROR: unrecognized privilege type: "sel" 2025-11-30 18:45:15.179 UTC client backend[45788] pg_regress/privileges STATEMENT: select has_table_privilege('pg_authid','sel'); 2025-11-30 18:45:15.180 UTC unrecognized[45791] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.181 UTC client backend[45791] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.181 UTC client backend[45791] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.186 UTC client backend[45791] pg_regress/privileges LOG: connection ready: setup total=6.068 ms, fork=0.498 ms, authentication=0.118 ms 2025-11-30 18:45:15.188 UTC client backend[45788] pg_regress/privileges LOG: disconnection: session time: 0:00:00.041 user=postgres database=regression host=[local] 2025-11-30 18:45:15.192 UTC client backend[45724] pg_regress/identity ERROR: cannot add identity to a column of a partition 2025-11-30 18:45:15.192 UTC client backend[45724] 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-11-30 18:45:15.193 UTC client backend[45710] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-11-30 18:45:15.193 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-11-30 18:45:15.194 UTC client backend[45772] postgres_fdw LOG: disconnection: session time: 0:00:00.222 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.195 UTC client backend[45724] pg_regress/identity ERROR: cannot add identity to a column of only the partitioned table 2025-11-30 18:45:15.195 UTC client backend[45724] pg_regress/identity HINT: Do not specify the ONLY keyword. 2025-11-30 18:45:15.195 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE ONLY pitest3 ALTER COLUMN f3 ADD GENERATED ALWAYS AS IDENTITY (START WITH 3); 2025-11-30 18:45:15.197 UTC unrecognized[45792] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.198 UTC client backend[45792] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.198 UTC client backend[45792] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.198 UTC client backend[45792] postgres_fdw LOG: connection ready: setup total=3.148 ms, fork=1.282 ms, authentication=0.117 ms 2025-11-30 18:45:15.199 UTC client backend[45724] pg_regress/identity ERROR: cannot drop identity from a column of a partition 2025-11-30 18:45:15.199 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest3_p1 ALTER COLUMN f3 DROP IDENTITY; 2025-11-30 18:45:15.200 UTC client backend[45724] pg_regress/identity ERROR: cannot drop identity from a column of only the partitioned table 2025-11-30 18:45:15.200 UTC client backend[45724] pg_regress/identity HINT: Do not specify the ONLY keyword. 2025-11-30 18:45:15.200 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE ONLY pitest3 ALTER COLUMN f3 DROP IDENTITY; 2025-11-30 18:45:15.201 UTC client backend[45718] pg_regress/generated_stored ERROR: invalid ON UPDATE action for foreign key constraint containing generated column 2025-11-30 18:45:15.201 UTC client backend[45718] 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-11-30 18:45:15.201 UTC client backend[45724] pg_regress/identity ERROR: null value in column "f3" of relation "pitest3_p1" violates not-null constraint 2025-11-30 18:45:15.201 UTC client backend[45724] pg_regress/identity DETAIL: Failing row contains (07-04-2016, from pitest3, null). 2025-11-30 18:45:15.201 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT into pitest3(f1, f2) VALUES ('2016-07-4', 'from pitest3'); 2025-11-30 18:45:15.201 UTC client backend[45724] pg_regress/identity ERROR: null value in column "f3" of relation "pitest3_p1" violates not-null constraint 2025-11-30 18:45:15.201 UTC client backend[45724] pg_regress/identity DETAIL: Failing row contains (07-05-2016, from pitest3_p1, null). 2025-11-30 18:45:15.201 UTC client backend[45724] pg_regress/identity STATEMENT: INSERT into pitest3_p1 (f1, f2) VALUES ('2016-07-5', 'from pitest3_p1'); 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity ERROR: column "f3" of relation "pitest1_p1" is an identity column 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1_p1 ALTER COLUMN f3 DROP NOT NULL; 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity ERROR: column "f3" of relation "pitest1" is an identity column 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ALTER COLUMN f3 DROP NOT NULL; 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity ERROR: column "f3" of relation "pitest1_p2" is an identity column 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1_p2 ALTER COLUMN f3 SET DEFAULT 10000; 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity ERROR: column "f3" of relation "pitest1" is an identity column 2025-11-30 18:45:15.203 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ALTER COLUMN f3 SET DEFAULT 10000; 2025-11-30 18:45:15.204 UTC client backend[45724] pg_regress/identity ERROR: cannot add identity to a column of a partition 2025-11-30 18:45:15.204 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1_p2 ALTER COLUMN f3 ADD GENERATED BY DEFAULT AS IDENTITY; 2025-11-30 18:45:15.204 UTC client backend[45718] pg_regress/generated_stored ERROR: invalid ON DELETE action for foreign key constraint containing generated column 2025-11-30 18:45:15.204 UTC client backend[45718] 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-11-30 18:45:15.205 UTC client backend[45724] pg_regress/identity ERROR: column "f3" of relation "pitest1" is already an identity column 2025-11-30 18:45:15.205 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ALTER COLUMN f3 ADD GENERATED BY DEFAULT AS IDENTITY; 2025-11-30 18:45:15.205 UTC client backend[45724] pg_regress/identity ERROR: identity columns are not supported on partitions 2025-11-30 18:45:15.205 UTC client backend[45724] 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-11-30 18:45:15.205 UTC client backend[45724] pg_regress/identity ERROR: identity columns are not supported on partitions 2025-11-30 18:45:15.205 UTC client backend[45724] 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-11-30 18:45:15.211 UTC client backend[45724] pg_regress/identity ERROR: table "pitest1_pfail" being attached contains an identity column "f3" 2025-11-30 18:45:15.211 UTC client backend[45724] pg_regress/identity DETAIL: The new partition may not contain an identity column. 2025-11-30 18:45:15.211 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ATTACH PARTITION pitest1_pfail FOR VALUES FROM ('2016-11-01') TO ('2016-12-01'); 2025-11-30 18:45:15.211 UTC client backend[45791] pg_regress/privileges ERROR: column "nosuchcol" of relation "pg_authid" does not exist 2025-11-30 18:45:15.211 UTC client backend[45791] pg_regress/privileges STATEMENT: select has_column_privilege('pg_authid','nosuchcol','select'); 2025-11-30 18:45:15.211 UTC client backend[45724] pg_regress/identity ERROR: table "pitest1_pfail" being attached contains an identity column "f3" 2025-11-30 18:45:15.211 UTC client backend[45724] pg_regress/identity DETAIL: The new partition may not contain an identity column. 2025-11-30 18:45:15.211 UTC client backend[45724] pg_regress/identity STATEMENT: ALTER TABLE pitest3 ATTACH PARTITION pitest1_pfail FOR VALUES FROM ('2016-11-01') TO ('2016-12-01'); 2025-11-30 18:45:15.212 UTC client backend[45710] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-11-30 18:45:15.212 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-11-30 18:45:15.220 UTC client backend[45710] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "s1" 2025-11-30 18:45:15.220 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM s1 WHERE f_leak(b); 2025-11-30 18:45:15.220 UTC client backend[45710] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "s1" 2025-11-30 18:45:15.220 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO s1 VALUES (1, 'foo'); 2025-11-30 18:45:15.222 UTC client backend[45791] pg_regress/privileges ERROR: column "f2" of relation "mytable" does not exist 2025-11-30 18:45:15.222 UTC client backend[45791] pg_regress/privileges STATEMENT: select has_column_privilege('mytable','f2','select'); 2025-11-30 18:45:15.222 UTC client backend[45723] pg_regress/matview ERROR: division by zero 2025-11-30 18:45:15.222 UTC client backend[45723] pg_regress/matview STATEMENT: create materialized view mvtest_error as select 1/0 as x; 2025-11-30 18:45:15.222 UTC client backend[45724] pg_regress/identity ERROR: conflicting NULL/NOT NULL declarations for column "id" of table "itest15" at character 63 2025-11-30 18:45:15.222 UTC client backend[45724] pg_regress/identity STATEMENT: CREATE TABLE itest15 (id integer GENERATED ALWAYS AS IDENTITY NULL); 2025-11-30 18:45:15.222 UTC client backend[45724] pg_regress/identity ERROR: conflicting NULL/NOT NULL declarations for column "id" of table "itest15" at character 39 2025-11-30 18:45:15.222 UTC client backend[45724] pg_regress/identity STATEMENT: CREATE TABLE itest15 (id integer NULL GENERATED ALWAYS AS IDENTITY); 2025-11-30 18:45:15.228 UTC client backend[45723] pg_regress/matview ERROR: division by zero 2025-11-30 18:45:15.228 UTC client backend[45723] pg_regress/matview STATEMENT: refresh materialized view mvtest_error; 2025-11-30 18:45:15.229 UTC client backend[45710] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "s1" 2025-11-30 18:45:15.229 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM s1 WHERE f_leak(b); 2025-11-30 18:45:15.242 UTC client backend[45791] pg_regress/privileges WARNING: no privileges were granted for "atest4" 2025-11-30 18:45:15.242 UTC client backend[45791] pg_regress/privileges ERROR: dependent privileges exist 2025-11-30 18:45:15.242 UTC client backend[45791] pg_regress/privileges HINT: Use CASCADE to revoke them too. 2025-11-30 18:45:15.242 UTC client backend[45791] pg_regress/privileges STATEMENT: REVOKE SELECT ON atest4 FROM regress_priv_user2; 2025-11-30 18:45:15.243 UTC client backend[45718] pg_regress/generated_stored ERROR: insert or update on table "gtest23b" violates foreign key constraint "gtest23b_b_fkey" 2025-11-30 18:45:15.243 UTC client backend[45718] pg_regress/generated_stored DETAIL: Key (b)=(10) is not present in table "gtest23a". 2025-11-30 18:45:15.243 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest23b VALUES (5); 2025-11-30 18:45:15.245 UTC client backend[45724] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-11-30 18:45:15.245 UTC client backend[45724] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-11-30 18:45:15.245 UTC client backend[45724] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-11-30 18:45:15.245 UTC client backend[45724] 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-11-30 18:45:15.250 UTC client backend[45718] pg_regress/generated_stored ERROR: insert or update on table "gtest23b" violates foreign key constraint "gtest23b_b_fkey" 2025-11-30 18:45:15.250 UTC client backend[45718] pg_regress/generated_stored DETAIL: Key (b)=(5) is not present in table "gtest23a". 2025-11-30 18:45:15.250 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest23b ALTER COLUMN b SET EXPRESSION AS (a * 5); 2025-11-30 18:45:15.255 UTC unrecognized[45796] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.256 UTC client backend[45796] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.256 UTC client backend[45796] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.257 UTC client backend[45796] pg_regress/privileges LOG: connection ready: setup total=2.157 ms, fork=0.487 ms, authentication=0.124 ms 2025-11-30 18:45:15.257 UTC client backend[45791] pg_regress/privileges LOG: disconnection: session time: 0:00:00.077 user=postgres database=regression host=[local] 2025-11-30 18:45:15.266 UTC client backend[45724] pg_regress/identity LOG: disconnection: session time: 0:00:01.514 user=postgres database=regression host=[local] 2025-11-30 18:45:15.270 UTC client backend[45723] pg_regress/matview ERROR: relation "mvtest_mv_foo" already exists 2025-11-30 18:45:15.270 UTC client backend[45723] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW mvtest_mv_foo AS SELECT * FROM mvtest_foo_data; 2025-11-30 18:45:15.274 UTC client backend[45718] pg_regress/generated_stored ERROR: insert or update on table "gtest23q" violates foreign key constraint "gtest23q_b_fkey" 2025-11-30 18:45:15.274 UTC client backend[45718] pg_regress/generated_stored DETAIL: Key (b)=(5) is not present in table "gtest23p". 2025-11-30 18:45:15.274 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest23q VALUES (2, 5); 2025-11-30 18:45:15.278 UTC client backend[45718] pg_regress/generated_stored ERROR: value for domain gtestdomain1 violates check constraint "gtestdomain1_check" 2025-11-30 18:45:15.278 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest24 (a) VALUES (6); 2025-11-30 18:45:15.289 UTC client backend[45792] postgres_fdw ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-11-30 18:45:15.289 UTC client backend[45792] postgres_fdw DETAIL: Failing row contains (-1, xyzzy). 2025-11-30 18:45:15.289 UTC client backend[45792] postgres_fdw STATEMENT: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) 2025-11-30 18:45:15.289 UTC client backend[44596] pg_regress/postgres_fdw ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-11-30 18:45:15.289 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Failing row contains (-1, xyzzy). 2025-11-30 18:45:15.289 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) COPY rem2 2025-11-30 18:45:15.289 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: copy rem2 from stdin; 2025-11-30 18:45:15.289 UTC client backend[45718] pg_regress/generated_stored ERROR: value for domain gtestdomain1 violates check constraint "gtestdomain1_check" 2025-11-30 18:45:15.289 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest24r (a) VALUES (6); 2025-11-30 18:45:15.297 UTC client backend[45718] pg_regress/generated_stored ERROR: value for domain gtestdomainnn violates check constraint "gtestdomainnn_check" 2025-11-30 18:45:15.297 UTC client backend[45718] pg_regress/generated_stored STATEMENT: INSERT INTO gtest24nn (a) VALUES (NULL); 2025-11-30 18:45:15.303 UTC client backend[45723] pg_regress/matview ERROR: could not find suitable unique index on materialized view "drop_idx_matview" 2025-11-30 18:45:15.303 UTC client backend[45723] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY drop_idx_matview; 2025-11-30 18:45:15.303 UTC client backend[45718] pg_regress/generated_stored ERROR: generated columns are not supported on typed tables 2025-11-30 18:45:15.303 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest28 OF gtest_type (f1 WITH OPTIONS GENERATED ALWAYS AS (f2 *2) STORED); 2025-11-30 18:45:15.307 UTC client backend[45792] postgres_fdw LOG: disconnection: session time: 0:00:00.110 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.307 UTC client backend[45718] pg_regress/generated_stored ERROR: child column "f3" specifies generation expression 2025-11-30 18:45:15.307 UTC client backend[45718] pg_regress/generated_stored HINT: A child table column cannot be generated unless its parent column is. 2025-11-30 18:45:15.307 UTC client backend[45718] 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-11-30 18:45:15.313 UTC client backend[45718] pg_regress/generated_stored ERROR: column "f3" in child table must not be a generated column 2025-11-30 18:45:15.313 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-11-30 18:45:15.313 UTC client backend[45723] pg_regress/matview ERROR: materialized view "mvtest2" has not been populated 2025-11-30 18:45:15.313 UTC client backend[45723] pg_regress/matview HINT: Use the REFRESH MATERIALIZED VIEW command. 2025-11-30 18:45:15.313 UTC client backend[45723] pg_regress/matview STATEMENT: SELECT * FROM mvtest2; 2025-11-30 18:45:15.319 UTC unrecognized[45799] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.320 UTC client backend[45799] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.320 UTC client backend[45799] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.322 UTC client backend[45799] postgres_fdw LOG: connection ready: setup total=4.109 ms, fork=1.188 ms, authentication=0.128 ms 2025-11-30 18:45:15.323 UTC client backend[45718] pg_regress/generated_stored ERROR: column "f3" inherits from generated column but specifies default 2025-11-30 18:45:15.323 UTC client backend[45718] 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-11-30 18:45:15.323 UTC client backend[45718] pg_regress/generated_stored ERROR: identity columns are not supported on partitions 2025-11-30 18:45:15.323 UTC client backend[45718] 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-11-30 18:45:15.323 UTC client backend[45718] pg_regress/generated_stored ERROR: column "f3" inherits from generated column of different kind 2025-11-30 18:45:15.323 UTC client backend[45718] pg_regress/generated_stored DETAIL: Parent column is STORED, child column is VIRTUAL. 2025-11-30 18:45:15.323 UTC client backend[45718] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 GENERATED ALWAYS AS (f2 * 2) VIRTUAL -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:15.324 UTC client backend[45718] pg_regress/generated_stored ERROR: column "f3" in child table must be a generated column 2025-11-30 18:45:15.324 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:15.327 UTC client backend[45718] pg_regress/generated_stored ERROR: column "f3" in child table must be a generated column 2025-11-30 18:45:15.327 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:15.330 UTC client backend[45718] pg_regress/generated_stored ERROR: table "gtest_child3" being attached contains an identity column "f3" 2025-11-30 18:45:15.330 UTC client backend[45718] pg_regress/generated_stored DETAIL: The new partition may not contain an identity column. 2025-11-30 18:45:15.330 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:15.334 UTC client backend[45718] pg_regress/generated_stored ERROR: column "f3" inherits from generated column of different kind 2025-11-30 18:45:15.334 UTC client backend[45718] pg_regress/generated_stored DETAIL: Parent column is STORED, child column is VIRTUAL. 2025-11-30 18:45:15.334 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:15.342 UTC client backend[45723] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-11-30 18:45:15.342 UTC client backend[45723] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW matview_ine_tab AS SELECT 1 / 0; 2025-11-30 18:45:15.343 UTC client backend[45723] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-11-30 18:45:15.343 UTC client backend[45723] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW matview_ine_tab AS SELECT 1 / 0 WITH NO DATA; 2025-11-30 18:45:15.343 UTC client backend[45723] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-11-30 18:45:15.343 UTC client backend[45723] 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-11-30 18:45:15.343 UTC client backend[45723] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-11-30 18:45:15.343 UTC client backend[45723] 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-11-30 18:45:15.346 UTC client backend[45723] pg_regress/matview LOG: disconnection: session time: 0:00:01.595 user=postgres database=regression host=[local] 2025-11-30 18:45:15.361 UTC client backend[45799] postgres_fdw LOG: disconnection: session time: 0:00:00.041 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.362 UTC client backend[44596] pg_regress/postgres_fdw ERROR: foreign table "tru_ftable" does not allow truncates 2025-11-30 18:45:15.362 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_ftable; 2025-11-30 18:45:15.363 UTC unrecognized[45802] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.364 UTC client backend[45802] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.364 UTC client backend[45802] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.364 UTC client backend[45802] postgres_fdw LOG: connection ready: setup total=1.593 ms, fork=0.324 ms, authentication=0.110 ms 2025-11-30 18:45:15.367 UTC client backend[44596] pg_regress/postgres_fdw ERROR: foreign table "tru_ftable" does not allow truncates 2025-11-30 18:45:15.367 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_ftable; 2025-11-30 18:45:15.367 UTC client backend[45802] postgres_fdw LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.370 UTC client backend[44596] pg_regress/postgres_fdw ERROR: foreign table "tru_ftable" does not allow truncates 2025-11-30 18:45:15.370 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_ftable; 2025-11-30 18:45:15.377 UTC unrecognized[45803] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.378 UTC client backend[45803] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.378 UTC client backend[45803] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.379 UTC client backend[45803] postgres_fdw LOG: connection ready: setup total=8.754 ms, fork=6.729 ms, authentication=0.113 ms 2025-11-30 18:45:15.393 UTC client backend[45803] postgres_fdw ERROR: cannot truncate a table referenced in a foreign key constraint 2025-11-30 18:45:15.393 UTC client backend[45803] postgres_fdw DETAIL: Table "tru_fk_table" references "tru_pk_table". 2025-11-30 18:45:15.393 UTC client backend[45803] postgres_fdw HINT: Truncate table "tru_fk_table" at the same time, or use TRUNCATE ... CASCADE. 2025-11-30 18:45:15.393 UTC client backend[45803] postgres_fdw STATEMENT: TRUNCATE public.tru_pk_table CONTINUE IDENTITY RESTRICT 2025-11-30 18:45:15.393 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot truncate a table referenced in a foreign key constraint 2025-11-30 18:45:15.393 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Table "tru_fk_table" references "tru_pk_table". 2025-11-30 18:45:15.393 UTC client backend[44596] pg_regress/postgres_fdw HINT: Truncate table "tru_fk_table" at the same time, or use TRUNCATE ... CASCADE. 2025-11-30 18:45:15.393 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: TRUNCATE public.tru_pk_table CONTINUE IDENTITY RESTRICT 2025-11-30 18:45:15.393 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_pk_ftable; 2025-11-30 18:45:15.394 UTC client backend[44596] pg_regress/postgres_fdw LOG: received message via remote connection: NOTICE: truncate cascades to table "tru_fk_table" 2025-11-30 18:45:15.394 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_pk_ftable CASCADE; 2025-11-30 18:45:15.405 UTC client backend[44596] pg_regress/postgres_fdw LOG: received message via remote connection: NOTICE: truncate cascades to table "tru_fk_table" 2025-11-30 18:45:15.405 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_ftable, tru_pk_ftable CASCADE; 2025-11-30 18:45:15.443 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "b1" 2025-11-30 18:45:15.443 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO bv1 VALUES (-1, 'xxx'); 2025-11-30 18:45:15.443 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "b1" 2025-11-30 18:45:15.443 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO bv1 VALUES (11, 'xxx'); 2025-11-30 18:45:15.463 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.463 UTC client backend[45710] 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-11-30 18:45:15.466 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.466 UTC client backend[45710] 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-11-30 18:45:15.477 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.477 UTC client backend[45710] 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-11-30 18:45:15.483 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.483 UTC client backend[45710] 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-11-30 18:45:15.498 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.498 UTC client backend[45710] 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-11-30 18:45:15.501 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.501 UTC client backend[45710] 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-11-30 18:45:15.501 UTC client backend[45730] isolation/multiple-row-versions/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.501 UTC client backend[45730] isolation/multiple-row-versions/s1 DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-11-30 18:45:15.501 UTC client backend[45730] isolation/multiple-row-versions/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.501 UTC client backend[45730] isolation/multiple-row-versions/s1 STATEMENT: UPDATE t SET txt = 'a' WHERE id = 1; 2025-11-30 18:45:15.505 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.505 UTC client backend[45710] 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-11-30 18:45:15.510 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.510 UTC client backend[45710] 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-11-30 18:45:15.511 UTC client backend[45730] isolation/multiple-row-versions/s1 LOG: disconnection: session time: 0:00:01.738 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.511 UTC client backend[45733] isolation/multiple-row-versions/s3 LOG: disconnection: session time: 0:00:01.677 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.511 UTC client backend[45731] isolation/multiple-row-versions/s2 LOG: disconnection: session time: 0:00:01.701 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.511 UTC client backend[45734] isolation/multiple-row-versions/s4 LOG: disconnection: session time: 0:00:01.665 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.513 UTC client backend[45719] isolation/multiple-row-versions/control connection LOG: disconnection: session time: 0:00:01.763 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.517 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.517 UTC client backend[45710] 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-11-30 18:45:15.517 UTC unrecognized[45826] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.518 UTC client backend[45826] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.518 UTC client backend[45826] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/index-only-scan 2025-11-30 18:45:15.519 UTC client backend[45826] isolation/index-only-scan LOG: connection ready: setup total=2.152 ms, fork=0.645 ms, authentication=0.117 ms 2025-11-30 18:45:15.522 UTC unrecognized[45829] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.522 UTC client backend[45829] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.522 UTC client backend[45829] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/index-only-scan 2025-11-30 18:45:15.523 UTC client backend[45829] isolation/index-only-scan LOG: connection ready: setup total=2.510 ms, fork=1.150 ms, authentication=0.104 ms 2025-11-30 18:45:15.525 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column in partition key at character 126 2025-11-30 18:45:15.525 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:15.525 UTC client backend[45718] 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-11-30 18:45:15.525 UTC unrecognized[45830] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.526 UTC client backend[45830] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.526 UTC client backend[45830] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/index-only-scan 2025-11-30 18:45:15.527 UTC client backend[45830] isolation/index-only-scan LOG: connection ready: setup total=1.748 ms, fork=0.410 ms, authentication=0.107 ms 2025-11-30 18:45:15.528 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column in partition key at character 126 2025-11-30 18:45:15.528 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:15.528 UTC client backend[45718] 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-11-30 18:45:15.529 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.529 UTC client backend[45710] 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-11-30 18:45:15.529 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column in partition key at character 126 2025-11-30 18:45:15.529 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:15.529 UTC client backend[45718] 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-11-30 18:45:15.530 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column in partition key at character 126 2025-11-30 18:45:15.530 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:15.530 UTC client backend[45718] 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 ((gtest_part_key)); 2025-11-30 18:45:15.537 UTC client backend[45710] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.537 UTC client backend[45710] 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-11-30 18:45:15.538 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column in partition key at character 126 2025-11-30 18:45:15.538 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:15.538 UTC client backend[45718] 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 ((gtest_part_key is not null)); 2025-11-30 18:45:15.548 UTC client backend[45710] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.548 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 3 as sdid) s ON did = s.sdid WHEN MATCHED THEN DELETE; 2025-11-30 18:45:15.554 UTC client backend[45710] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.554 UTC client backend[45710] 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-11-30 18:45:15.556 UTC client backend[45710] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-11-30 18:45:15.556 UTC client backend[45710] 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-11-30 18:45:15.560 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot use generated column "b" in column generation expression 2025-11-30 18:45:15.560 UTC client backend[45718] pg_regress/generated_stored DETAIL: A generated column cannot reference another generated column. 2025-11-30 18:45:15.560 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (b * 4) STORED; 2025-11-30 18:45:15.561 UTC client backend[45718] pg_regress/generated_stored ERROR: column "z" does not exist 2025-11-30 18:45:15.561 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (z * 4) STORED; 2025-11-30 18:45:15.571 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.571 UTC client backend[45710] 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-11-30 18:45:15.583 UTC client backend[45710] pg_regress/rowsecurity ERROR: duplicate key value violates unique constraint "document_pkey" 2025-11-30 18:45:15.583 UTC client backend[45710] 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-11-30 18:45:15.583 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot alter type of a column used by a generated column 2025-11-30 18:45:15.583 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "a" is used by generated column "x". 2025-11-30 18:45:15.583 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE text; 2025-11-30 18:45:15.587 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.587 UTC client backend[45710] 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-11-30 18:45:15.599 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot specify USING when altering type of generated column at character 34 2025-11-30 18:45:15.599 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "x" is a generated column. 2025-11-30 18:45:15.599 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x TYPE boolean USING x <> 0; 2025-11-30 18:45:15.599 UTC client backend[45718] pg_regress/generated_stored ERROR: column "x" of relation "gtest27" is a generated column 2025-11-30 18:45:15.599 UTC client backend[45718] pg_regress/generated_stored HINT: Use ALTER TABLE ... ALTER COLUMN ... DROP EXPRESSION instead. 2025-11-30 18:45:15.599 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x DROP DEFAULT; 2025-11-30 18:45:15.604 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-11-30 18:45:15.604 UTC client backend[45710] 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-11-30 18:45:15.612 UTC client backend[45830] isolation/index-only-scan/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.612 UTC client backend[45830] isolation/index-only-scan/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:15.612 UTC client backend[45830] isolation/index-only-scan/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.612 UTC client backend[45830] isolation/index-only-scan/s2 STATEMENT: COMMIT; 2025-11-30 18:45:15.612 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot alter type of a column used by a generated column 2025-11-30 18:45:15.612 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "a" is used by generated column "x". 2025-11-30 18:45:15.612 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE float8, ALTER COLUMN b TYPE float8; 2025-11-30 18:45:15.629 UTC client backend[45718] pg_regress/generated_stored ERROR: column "a" of relation "gtest29" is not a generated column 2025-11-30 18:45:15.629 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a SET EXPRESSION AS (a * 3); 2025-11-30 18:45:15.629 UTC client backend[45718] pg_regress/generated_stored ERROR: column "a" of relation "gtest29" is not a generated column 2025-11-30 18:45:15.629 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a DROP EXPRESSION; 2025-11-30 18:45:15.635 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for view rls_view 2025-11-30 18:45:15.635 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-11-30 18:45:15.636 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for view rls_view 2025-11-30 18:45:15.636 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-11-30 18:45:15.639 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.639 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-11-30 18:45:15.640 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.640 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-11-30 18:45:15.641 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.641 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-11-30 18:45:15.644 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.644 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-11-30 18:45:15.648 UTC client backend[45829] isolation/index-only-scan/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.648 UTC client backend[45829] isolation/index-only-scan/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:15.648 UTC client backend[45829] isolation/index-only-scan/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.648 UTC client backend[45829] isolation/index-only-scan/s1 STATEMENT: COMMIT; 2025-11-30 18:45:15.677 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.677 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-11-30 18:45:15.677 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.677 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-11-30 18:45:15.678 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.678 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-11-30 18:45:15.678 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.678 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-11-30 18:45:15.681 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.681 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-11-30 18:45:15.682 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-11-30 18:45:15.682 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-11-30 18:45:15.685 UTC client backend[45830] isolation/index-only-scan/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.685 UTC client backend[45830] isolation/index-only-scan/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:15.685 UTC client backend[45830] isolation/index-only-scan/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.685 UTC client backend[45830] isolation/index-only-scan/s2 STATEMENT: COMMIT; 2025-11-30 18:45:15.686 UTC client backend[45718] pg_regress/generated_stored ERROR: ALTER TABLE / DROP EXPRESSION must be applied to child tables too 2025-11-30 18:45:15.686 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE ONLY gtest30 ALTER COLUMN b DROP EXPRESSION; 2025-11-30 18:45:15.715 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot drop generation expression from inherited column 2025-11-30 18:45:15.715 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest30_1 ALTER COLUMN b DROP EXPRESSION; 2025-11-30 18:45:15.720 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-11-30 18:45:15.720 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-11-30 18:45:15.720 UTC client backend[45710] pg_regress/rowsecurity ERROR: policy "p1" for table "y1" already exists 2025-11-30 18:45:15.720 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: CREATE POLICY p1 ON y1 FOR SELECT USING (a % 2 = 1); 2025-11-30 18:45:15.723 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-11-30 18:45:15.723 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b SET EXPRESSION AS ('hello1'); 2025-11-30 18:45:15.723 UTC client backend[45829] isolation/index-only-scan/s1 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.723 UTC client backend[45829] isolation/index-only-scan/s1 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:15.723 UTC client backend[45829] isolation/index-only-scan/s1 HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.723 UTC client backend[45829] isolation/index-only-scan/s1 STATEMENT: COMMIT; 2025-11-30 18:45:15.728 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-11-30 18:45:15.728 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b SET EXPRESSION AS ('hello2'); 2025-11-30 18:45:15.733 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-11-30 18:45:15.733 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b SET EXPRESSION AS ('hello3'); 2025-11-30 18:45:15.739 UTC client backend[45707] pg_regress/brin LOG: disconnection: session time: 0:00:01.996 user=postgres database=regression host=[local] 2025-11-30 18:45:15.744 UTC client backend[45718] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-11-30 18:45:15.744 UTC client backend[45718] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-11-30 18:45:15.750 UTC client backend[45718] pg_regress/generated_stored ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-11-30 18:45:15.750 UTC client backend[45718] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-11-30 18:45:15.750 UTC client backend[45718] 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-11-30 18:45:15.750 UTC client backend[45718] pg_regress/generated_stored ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-11-30 18:45:15.750 UTC client backend[45718] pg_regress/generated_stored DETAIL: A whole-row reference is used and the table contains generated columns. 2025-11-30 18:45:15.750 UTC client backend[45718] 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-11-30 18:45:15.762 UTC client backend[45826] isolation/index-only-scan/control connection LOG: disconnection: session time: 0:00:00.244 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.762 UTC client backend[45829] isolation/index-only-scan/s1 LOG: disconnection: session time: 0:00:00.240 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.764 UTC client backend[45830] isolation/index-only-scan/s2 LOG: disconnection: session time: 0:00:00.238 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.770 UTC unrecognized[45855] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.771 UTC client backend[45855] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.771 UTC client backend[45855] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/index-only-bitmapscan 2025-11-30 18:45:15.772 UTC client backend[45855] isolation/index-only-bitmapscan LOG: connection ready: setup total=4.609 ms, fork=3.078 ms, authentication=0.134 ms 2025-11-30 18:45:15.776 UTC client backend[45796] pg_regress/privileges ERROR: cannot create a cursor WITH HOLD within security-restricted operation 2025-11-30 18:45:15.776 UTC client backend[45796] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-11-30 18:45:15.776 UTC client backend[45796] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-11-30 18:45:15.776 UTC client backend[45721] pg_regress/join_hash LOG: disconnection: session time: 0:00:02.021 user=postgres database=regression host=[local] 2025-11-30 18:45:15.778 UTC unrecognized[45857] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.778 UTC unrecognized[45856] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.778 UTC client backend[45857] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.778 UTC client backend[45857] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.779 UTC client backend[45857] pg_regress/privileges LOG: connection ready: setup total=2.402 ms, fork=0.893 ms, authentication=0.133 ms 2025-11-30 18:45:15.779 UTC client backend[45856] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.779 UTC client backend[45856] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/index-only-bitmapscan 2025-11-30 18:45:15.779 UTC client backend[45796] pg_regress/privileges LOG: disconnection: session time: 0:00:00.523 user=postgres database=regression host=[local] 2025-11-30 18:45:15.780 UTC client backend[45856] isolation/index-only-bitmapscan LOG: connection ready: setup total=3.739 ms, fork=1.288 ms, authentication=1.222 ms 2025-11-30 18:45:15.782 UTC client backend[45857] pg_regress/privileges ERROR: cannot create a cursor WITH HOLD within security-restricted operation 2025-11-30 18:45:15.782 UTC client backend[45857] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-11-30 18:45:15.782 UTC client backend[45857] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-11-30 18:45:15.784 UTC unrecognized[45858] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.784 UTC client backend[45858] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.784 UTC client backend[45858] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/index-only-bitmapscan 2025-11-30 18:45:15.785 UTC client backend[45858] isolation/index-only-bitmapscan LOG: connection ready: setup total=1.943 ms, fork=0.566 ms, authentication=0.108 ms 2025-11-30 18:45:15.787 UTC client backend[45857] pg_regress/privileges ERROR: cannot fire deferred trigger within security-restricted operation 2025-11-30 18:45:15.787 UTC client backend[45857] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-11-30 18:45:15.787 UTC client backend[45857] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-11-30 18:45:15.789 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "t1" 2025-11-30 18:45:15.789 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: WITH cte1 AS (UPDATE t1 SET a = a + 1 RETURNING *) SELECT * FROM cte1; 2025-11-30 18:45:15.789 UTC client backend[45718] pg_regress/generated_stored LOG: disconnection: session time: 0:00:02.038 user=postgres database=regression host=[local] 2025-11-30 18:45:15.790 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "t1" 2025-11-30 18:45:15.790 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: WITH cte1 AS (INSERT INTO t1 VALUES (21, 'Fail') RETURNING *) SELECT * FROM cte1; 2025-11-30 18:45:15.790 UTC client backend[45710] pg_regress/rowsecurity ERROR: policy "p1" for table "t1" already exists 2025-11-30 18:45:15.790 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: ALTER POLICY p1 ON t1 RENAME TO p1; 2025-11-30 18:45:15.791 UTC unrecognized[45859] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.791 UTC client backend[44596] pg_regress/postgres_fdw ERROR: relation "t1" already exists 2025-11-30 18:45:15.791 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: importing foreign table "t1" 2025-11-30 18:45:15.791 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA import_source FROM SERVER loopback INTO import_dest4; 2025-11-30 18:45:15.791 UTC client backend[45859] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.791 UTC client backend[45859] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.792 UTC client backend[44596] pg_regress/postgres_fdw ERROR: schema "nonesuch" is not present on foreign server "loopback" 2025-11-30 18:45:15.792 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA nonesuch FROM SERVER loopback INTO import_dest4; 2025-11-30 18:45:15.792 UTC client backend[44596] pg_regress/postgres_fdw ERROR: schema "notthere" does not exist 2025-11-30 18:45:15.792 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA nonesuch FROM SERVER loopback INTO notthere; 2025-11-30 18:45:15.792 UTC client backend[44596] pg_regress/postgres_fdw ERROR: server "nowhere" does not exist 2025-11-30 18:45:15.792 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA nonesuch FROM SERVER nowhere INTO notthere; 2025-11-30 18:45:15.792 UTC client backend[45859] pg_regress/privileges LOG: connection ready: setup total=1.784 ms, fork=0.290 ms, authentication=0.140 ms 2025-11-30 18:45:15.793 UTC client backend[45857] pg_regress/privileges LOG: disconnection: session time: 0:00:00.015 user=postgres database=regression host=[local] 2025-11-30 18:45:15.794 UTC client backend[45859] pg_regress/privileges ERROR: cannot fire deferred trigger within security-restricted operation 2025-11-30 18:45:15.794 UTC client backend[45859] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-11-30 18:45:15.794 UTC client backend[45859] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-11-30 18:45:15.796 UTC client backend[45859] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-11-30 18:45:15.796 UTC client backend[45859] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-11-30 18:45:15.796 UTC client backend[45859] pg_regress/privileges CONTEXT: SQL function "unwanted_grant" statement 1 SQL statement "SELECT public.unwanted_grant()" PL/pgSQL function public.sro_trojan() line 1 at PERFORM SQL function "mv_action" statement 1 2025-11-30 18:45:15.796 UTC client backend[45859] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-11-30 18:45:15.799 UTC client backend[44596] pg_regress/postgres_fdw ERROR: type "public.Colors" does not exist at character 137 2025-11-30 18:45:15.799 UTC client backend[44596] pg_regress/postgres_fdw QUERY: CREATE FOREIGN TABLE t5 ( c1 integer OPTIONS (column_name 'c1'), c2 text OPTIONS (column_name 'c2') COLLATE pg_catalog."C", "Col" public."Colors" OPTIONS (column_name 'Col') ) SERVER loopback OPTIONS (schema_name 'import_source', table_name 't5'); 2025-11-30 18:45:15.799 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: importing foreign table "t5" 2025-11-30 18:45:15.799 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA import_source LIMIT TO (t5) FROM SERVER loopback INTO import_dest5; 2025-11-30 18:45:15.802 UTC client backend[45856] isolation/index-only-bitmapscan/s1 LOG: disconnection: session time: 0:00:00.024 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.802 UTC unrecognized[45861] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.803 UTC client backend[45858] isolation/index-only-bitmapscan/s2 LOG: disconnection: session time: 0:00:00.018 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.803 UTC client backend[45861] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.803 UTC client backend[45861] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.803 UTC client backend[45855] isolation/index-only-bitmapscan/control connection LOG: disconnection: session time: 0:00:00.032 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.804 UTC client backend[45861] pg_regress/privileges LOG: connection ready: setup total=1.874 ms, fork=0.420 ms, authentication=0.112 ms 2025-11-30 18:45:15.804 UTC client backend[45859] pg_regress/privileges LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression host=[local] 2025-11-30 18:45:15.807 UTC unrecognized[45863] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.807 UTC client backend[45863] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.807 UTC client backend[45863] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/predicate-lock-hot-tuple 2025-11-30 18:45:15.808 UTC client backend[45863] isolation/predicate-lock-hot-tuple LOG: connection ready: setup total=1.700 ms, fork=0.304 ms, authentication=0.107 ms 2025-11-30 18:45:15.809 UTC unrecognized[45864] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.810 UTC client backend[45864] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.810 UTC client backend[45864] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/predicate-lock-hot-tuple 2025-11-30 18:45:15.810 UTC client backend[45864] isolation/predicate-lock-hot-tuple LOG: connection ready: setup total=1.589 ms, fork=0.298 ms, authentication=0.101 ms 2025-11-30 18:45:15.812 UTC unrecognized[45865] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.812 UTC client backend[45865] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.812 UTC client backend[45865] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/predicate-lock-hot-tuple 2025-11-30 18:45:15.813 UTC client backend[45865] isolation/predicate-lock-hot-tuple LOG: connection ready: setup total=1.576 ms, fork=0.315 ms, authentication=0.099 ms 2025-11-30 18:45:15.817 UTC client backend[45710] pg_regress/rowsecurity ERROR: table "copy_t" does not exist 2025-11-30 18:45:15.817 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP TABLE copy_t CASCADE; 2025-11-30 18:45:15.821 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_t" 2025-11-30 18:45:15.821 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.822 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_t" 2025-11-30 18:45:15.822 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.823 UTC client backend[45865] isolation/predicate-lock-hot-tuple/s2 ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.823 UTC client backend[45865] isolation/predicate-lock-hot-tuple/s2 DETAIL: Reason code: Canceled on identification as a pivot, during commit attempt. 2025-11-30 18:45:15.823 UTC client backend[45865] isolation/predicate-lock-hot-tuple/s2 HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.823 UTC client backend[45865] isolation/predicate-lock-hot-tuple/s2 STATEMENT: COMMIT; 2025-11-30 18:45:15.823 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table copy_t 2025-11-30 18:45:15.823 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.825 UTC client backend[45865] isolation/predicate-lock-hot-tuple/s2 LOG: disconnection: session time: 0:00:00.013 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.826 UTC client backend[45864] isolation/predicate-lock-hot-tuple/s1 LOG: disconnection: session time: 0:00:00.016 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.826 UTC client backend[45861] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-11-30 18:45:15.826 UTC client backend[45861] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-11-30 18:45:15.826 UTC client backend[45861] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-11-30 18:45:15.826 UTC client backend[45861] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-11-30 18:45:15.826 UTC client backend[45861] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-11-30 18:45:15.826 UTC client backend[45861] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-11-30 18:45:15.826 UTC client backend[45863] isolation/predicate-lock-hot-tuple/control connection LOG: disconnection: session time: 0:00:00.019 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.827 UTC client backend[45861] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-11-30 18:45:15.827 UTC client backend[45861] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-11-30 18:45:15.827 UTC client backend[45861] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-11-30 18:45:15.827 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_rel_to" 2025-11-30 18:45:15.827 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.827 UTC client backend[45861] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-11-30 18:45:15.827 UTC client backend[45861] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-11-30 18:45:15.827 UTC client backend[45861] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-11-30 18:45:15.828 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-11-30 18:45:15.828 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.828 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-11-30 18:45:15.828 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.828 UTC unrecognized[45868] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.829 UTC client backend[45868] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.829 UTC client backend[45868] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.830 UTC client backend[45868] pg_regress/privileges LOG: connection ready: setup total=1.790 ms, fork=0.305 ms, authentication=0.110 ms 2025-11-30 18:45:15.830 UTC unrecognized[45869] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.830 UTC client backend[45869] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.830 UTC client backend[45869] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/update-conflict-out 2025-11-30 18:45:15.830 UTC client backend[45861] pg_regress/privileges LOG: disconnection: session time: 0:00:00.027 user=postgres database=regression host=[local] 2025-11-30 18:45:15.831 UTC client backend[45869] isolation/update-conflict-out LOG: connection ready: setup total=1.669 ms, fork=0.308 ms, authentication=0.101 ms 2025-11-30 18:45:15.831 UTC client backend[45868] pg_regress/privileges ERROR: "atest1" is not a sequence 2025-11-30 18:45:15.831 UTC client backend[45868] pg_regress/privileges STATEMENT: SELECT has_sequence_privilege('regress_priv_user1', 'atest1', 'SELECT'); 2025-11-30 18:45:15.832 UTC client backend[45868] pg_regress/privileges ERROR: unrecognized privilege type: "INSERT" 2025-11-30 18:45:15.832 UTC client backend[45868] pg_regress/privileges STATEMENT: SELECT has_sequence_privilege('regress_priv_user1', 'x_seq', 'INSERT'); 2025-11-30 18:45:15.832 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_rel_to" 2025-11-30 18:45:15.832 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.832 UTC unrecognized[45870] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.832 UTC unrecognized[45871] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.833 UTC client backend[45870] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.833 UTC client backend[45870] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/update-conflict-out 2025-11-30 18:45:15.833 UTC client backend[45871] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.833 UTC client backend[45871] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.833 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-11-30 18:45:15.833 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.833 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-11-30 18:45:15.833 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-11-30 18:45:15.834 UTC client backend[45870] isolation/update-conflict-out LOG: connection ready: setup total=1.779 ms, fork=0.292 ms, authentication=0.107 ms 2025-11-30 18:45:15.834 UTC client backend[45871] pg_regress/privileges LOG: connection ready: setup total=1.624 ms, fork=0.296 ms, authentication=0.108 ms 2025-11-30 18:45:15.834 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_t" 2025-11-30 18:45:15.834 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-11-30 18:45:15.834 UTC client backend[45710] pg_regress/rowsecurity ERROR: COPY FROM not supported with row-level security 2025-11-30 18:45:15.834 UTC client backend[45710] pg_regress/rowsecurity HINT: Use INSERT statements instead. 2025-11-30 18:45:15.834 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-11-30 18:45:15.834 UTC client backend[45868] pg_regress/privileges LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression host=[local] 2025-11-30 18:45:15.835 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table copy_t 2025-11-30 18:45:15.835 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-11-30 18:45:15.835 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table copy_t 2025-11-30 18:45:15.835 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-11-30 18:45:15.835 UTC unrecognized[45872] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.836 UTC client backend[45872] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.836 UTC client backend[45872] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/update-conflict-out 2025-11-30 18:45:15.837 UTC client backend[45872] isolation/update-conflict-out LOG: connection ready: setup total=1.819 ms, fork=0.453 ms, authentication=0.096 ms 2025-11-30 18:45:15.837 UTC client backend[45871] pg_regress/privileges ERROR: invalid privilege type INSERT for large object 2025-11-30 18:45:15.837 UTC client backend[45871] pg_regress/privileges STATEMENT: GRANT SELECT, INSERT ON LARGE OBJECT 1001 TO PUBLIC; 2025-11-30 18:45:15.837 UTC client backend[45871] pg_regress/privileges ERROR: role "nosuchuser" does not exist 2025-11-30 18:45:15.837 UTC client backend[45871] pg_regress/privileges STATEMENT: GRANT SELECT, UPDATE ON LARGE OBJECT 1001 TO nosuchuser; 2025-11-30 18:45:15.837 UTC client backend[45871] pg_regress/privileges ERROR: large object 999 does not exist 2025-11-30 18:45:15.837 UTC client backend[45871] pg_regress/privileges STATEMENT: GRANT SELECT, UPDATE ON LARGE OBJECT 999 TO PUBLIC; 2025-11-30 18:45:15.838 UTC unrecognized[45873] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.838 UTC unrecognized[45874] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.838 UTC client backend[45873] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.838 UTC client backend[45873] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.838 UTC client backend[45874] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.838 UTC client backend[45874] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/update-conflict-out 2025-11-30 18:45:15.839 UTC client backend[45873] pg_regress/privileges LOG: connection ready: setup total=1.794 ms, fork=0.299 ms, authentication=0.105 ms 2025-11-30 18:45:15.839 UTC client backend[45874] isolation/update-conflict-out LOG: connection ready: setup total=1.589 ms, fork=0.287 ms, authentication=0.115 ms 2025-11-30 18:45:15.839 UTC client backend[45871] pg_regress/privileges LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression host=[local] 2025-11-30 18:45:15.841 UTC client backend[45873] pg_regress/privileges ERROR: large object descriptor 0 was not opened for writing 2025-11-30 18:45:15.841 UTC client backend[45873] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1001, x'40000'::int), 'abcd'); 2025-11-30 18:45:15.841 UTC client backend[45873] pg_regress/privileges ERROR: permission denied for large object 1002 2025-11-30 18:45:15.841 UTC client backend[45873] pg_regress/privileges STATEMENT: SELECT loread(lo_open(1002, x'40000'::int), 32); 2025-11-30 18:45:15.842 UTC client backend[45873] pg_regress/privileges ERROR: permission denied for large object 1002 2025-11-30 18:45:15.842 UTC client backend[45873] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1002, x'20000'::int), 'abcd'); 2025-11-30 18:45:15.842 UTC client backend[45873] pg_regress/privileges ERROR: permission denied for large object 1003 2025-11-30 18:45:15.842 UTC client backend[45873] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1003, x'20000'::int), 'abcd'); 2025-11-30 18:45:15.842 UTC client backend[45873] pg_regress/privileges ERROR: large object 1006 does not exist 2025-11-30 18:45:15.842 UTC client backend[45873] pg_regress/privileges STATEMENT: GRANT UPDATE ON LARGE OBJECT 1006 TO regress_priv_user3; 2025-11-30 18:45:15.843 UTC client backend[45873] pg_regress/privileges ERROR: must be owner of large object 1001 2025-11-30 18:45:15.843 UTC client backend[45873] pg_regress/privileges STATEMENT: SELECT lo_unlink(1001); 2025-11-30 18:45:15.844 UTC unrecognized[45875] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.844 UTC client backend[45875] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.844 UTC client backend[45875] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.845 UTC client backend[45875] pg_regress/privileges LOG: connection ready: setup total=1.682 ms, fork=0.311 ms, authentication=0.106 ms 2025-11-30 18:45:15.847 UTC client backend[45873] pg_regress/privileges LOG: disconnection: session time: 0:00:00.009 user=postgres database=regression host=[local] 2025-11-30 18:45:15.849 UTC client backend[45875] pg_regress/privileges ERROR: permission denied for large object 1003 2025-11-30 18:45:15.849 UTC client backend[45875] pg_regress/privileges STATEMENT: SELECT loread(lo_open(1003, x'40000'::int), 32); 2025-11-30 18:45:15.850 UTC client backend[45875] pg_regress/privileges ERROR: permission denied for large object 1005 2025-11-30 18:45:15.850 UTC client backend[45875] pg_regress/privileges STATEMENT: SELECT lo_truncate(lo_open(1005, x'20000'::int), 10); 2025-11-30 18:45:15.850 UTC unrecognized[45876] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.851 UTC client backend[45876] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.851 UTC client backend[45876] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.852 UTC client backend[45876] pg_regress/privileges LOG: connection ready: setup total=1.661 ms, fork=0.318 ms, authentication=0.102 ms 2025-11-30 18:45:15.852 UTC client backend[45875] pg_regress/privileges LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression host=[local] 2025-11-30 18:45:15.853 UTC client backend[45872] isolation/update-conflict-out/bar ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.853 UTC client backend[45872] isolation/update-conflict-out/bar DETAIL: Reason code: Canceled on conflict out to pivot 18219, during read. 2025-11-30 18:45:15.853 UTC client backend[45872] isolation/update-conflict-out/bar HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.853 UTC client backend[45872] isolation/update-conflict-out/bar STATEMENT: SELECT * FROM txn1 WHERE id = 7; 2025-11-30 18:45:15.855 UTC unrecognized[45877] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.855 UTC client backend[45877] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.855 UTC client backend[45877] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.856 UTC client backend[45877] pg_regress/privileges LOG: connection ready: setup total=1.640 ms, fork=0.302 ms, authentication=0.105 ms 2025-11-30 18:45:15.857 UTC client backend[45876] pg_regress/privileges LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression host=[local] 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges ERROR: permission denied for large object 1002 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT loread(lo_open(1002, x'40000'::int), 32); 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges ERROR: permission denied for large object 1002 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1002, x'20000'::int), 'abcd'); 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges ERROR: permission denied for large object 1002 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT lo_truncate(lo_open(1002, x'20000'::int), 10); 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges ERROR: permission denied for large object 1002 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT lo_put(1002, 1, 'abcd'); 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges ERROR: must be owner of large object 1002 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT lo_unlink(1002); 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges ERROR: permission denied for function lo_export 2025-11-30 18:45:15.858 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT lo_export(1001, '/dev/null'); 2025-11-30 18:45:15.859 UTC client backend[45877] pg_regress/privileges ERROR: permission denied for function lo_import 2025-11-30 18:45:15.859 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT lo_import('/dev/null'); 2025-11-30 18:45:15.859 UTC client backend[45877] pg_regress/privileges ERROR: permission denied for function lo_import 2025-11-30 18:45:15.859 UTC client backend[45877] pg_regress/privileges STATEMENT: SELECT lo_import('/dev/null', 2003); 2025-11-30 18:45:15.859 UTC unrecognized[45878] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.860 UTC client backend[45878] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.860 UTC client backend[45878] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.860 UTC client backend[45878] pg_regress/privileges LOG: connection ready: setup total=1.632 ms, fork=0.311 ms, authentication=0.099 ms 2025-11-30 18:45:15.861 UTC client backend[45877] pg_regress/privileges LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression host=[local] 2025-11-30 18:45:15.862 UTC client backend[45710] pg_regress/rowsecurity ERROR: role "regress_rls_eve" cannot be dropped because some objects depend on it 2025-11-30 18:45:15.862 UTC client backend[45710] pg_regress/rowsecurity DETAIL: privileges for table tbl1 target of policy p on table tbl1 2025-11-30 18:45:15.862 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP ROLE regress_rls_eve; 2025-11-30 18:45:15.863 UTC client backend[45710] pg_regress/rowsecurity ERROR: role "regress_rls_eve" cannot be dropped because some objects depend on it 2025-11-30 18:45:15.863 UTC client backend[45710] pg_regress/rowsecurity DETAIL: privileges for table tbl1 2025-11-30 18:45:15.863 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP ROLE regress_rls_eve; 2025-11-30 18:45:15.863 UTC client backend[45878] pg_regress/privileges ERROR: permission denied for function lo_export 2025-11-30 18:45:15.863 UTC client backend[45878] pg_regress/privileges STATEMENT: SELECT lo_export(1001, '/dev/null'); 2025-11-30 18:45:15.864 UTC unrecognized[45879] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.864 UTC client backend[45710] pg_regress/rowsecurity ERROR: role "regress_rls_frank" cannot be dropped because some objects depend on it 2025-11-30 18:45:15.864 UTC client backend[45710] pg_regress/rowsecurity DETAIL: target of policy p on table tbl1 2025-11-30 18:45:15.864 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP ROLE regress_rls_frank; 2025-11-30 18:45:15.864 UTC client backend[45879] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.864 UTC client backend[45879] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.865 UTC client backend[45879] pg_regress/privileges LOG: connection ready: setup total=1.608 ms, fork=0.307 ms, authentication=0.103 ms 2025-11-30 18:45:15.866 UTC client backend[45878] pg_regress/privileges LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression host=[local] 2025-11-30 18:45:15.866 UTC client backend[45879] pg_regress/privileges ERROR: permission denied for table pg_largeobject 2025-11-30 18:45:15.866 UTC client backend[45879] pg_regress/privileges STATEMENT: SELECT * FROM pg_largeobject LIMIT 0; 2025-11-30 18:45:15.866 UTC client backend[45710] pg_regress/rowsecurity ERROR: aggregate functions are not allowed in policy expressions 2025-11-30 18:45:15.866 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: CREATE POLICY p ON t USING (max(c)); 2025-11-30 18:45:15.867 UTC client backend[45872] isolation/update-conflict-out/bar ERROR: could not serialize access due to read/write dependencies among transactions 2025-11-30 18:45:15.867 UTC client backend[45872] isolation/update-conflict-out/bar DETAIL: Reason code: Canceled on conflict out to pivot 18235, during read. 2025-11-30 18:45:15.867 UTC client backend[45872] isolation/update-conflict-out/bar HINT: The transaction might succeed if retried. 2025-11-30 18:45:15.867 UTC client backend[45872] isolation/update-conflict-out/bar STATEMENT: SELECT * FROM txn1 WHERE id = 7; 2025-11-30 18:45:15.871 UTC client backend[45870] isolation/update-conflict-out/foo LOG: disconnection: session time: 0:00:00.038 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.871 UTC client backend[45869] isolation/update-conflict-out/control connection LOG: disconnection: session time: 0:00:00.040 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.871 UTC client backend[45874] isolation/update-conflict-out/trouble LOG: disconnection: session time: 0:00:00.032 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges WARNING: PID 43402 is not a PostgreSQL backend process 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges WARNING: PID 43403 is not a PostgreSQL backend process 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges WARNING: PID 43405 is not a PostgreSQL backend process 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges WARNING: PID 43404 is not a PostgreSQL backend process 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges WARNING: PID 43406 is not a PostgreSQL backend process 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges WARNING: PID 43408 is not a PostgreSQL backend process 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-11-30 18:45:15.872 UTC client backend[45872] isolation/update-conflict-out/bar LOG: disconnection: session time: 0:00:00.036 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges ERROR: role "pg_database_owner" cannot have explicit members 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges STATEMENT: GRANT pg_database_owner TO regress_priv_user1; 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges ERROR: role "pg_database_owner" cannot be a member of any role 2025-11-30 18:45:15.872 UTC client backend[45879] pg_regress/privileges STATEMENT: GRANT regress_priv_user1 TO pg_database_owner; 2025-11-30 18:45:15.873 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r2" 2025-11-30 18:45:15.873 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r2 VALUES (2); 2025-11-30 18:45:15.877 UTC unrecognized[45882] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.878 UTC client backend[45882] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.878 UTC client backend[45882] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-simple 2025-11-30 18:45:15.878 UTC client backend[45879] pg_regress/privileges ERROR: permission denied for table datdba_only 2025-11-30 18:45:15.878 UTC client backend[45879] pg_regress/privileges STATEMENT: DELETE FROM datdba_only; 2025-11-30 18:45:15.878 UTC client backend[45879] pg_regress/privileges ERROR: permission denied for table datdba_only 2025-11-30 18:45:15.878 UTC client backend[45879] pg_regress/privileges STATEMENT: INSERT INTO datdba_only DEFAULT VALUES; 2025-11-30 18:45:15.879 UTC client backend[45882] isolation/deadlock-simple LOG: connection ready: setup total=1.895 ms, fork=0.370 ms, authentication=0.122 ms 2025-11-30 18:45:15.879 UTC unrecognized[45883] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.879 UTC client backend[45883] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.879 UTC client backend[45883] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.880 UTC unrecognized[45884] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.880 UTC client backend[45883] pg_regress/privileges LOG: connection ready: setup total=1.709 ms, fork=0.301 ms, authentication=0.108 ms 2025-11-30 18:45:15.880 UTC client backend[45884] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.880 UTC client backend[45884] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-simple 2025-11-30 18:45:15.880 UTC client backend[45879] pg_regress/privileges LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression host=[local] 2025-11-30 18:45:15.881 UTC client backend[45884] isolation/deadlock-simple LOG: connection ready: setup total=1.698 ms, fork=0.315 ms, authentication=0.112 ms 2025-11-30 18:45:15.882 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-11-30 18:45:15.882 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (1); 2025-11-30 18:45:15.882 UTC unrecognized[45885] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.883 UTC client backend[45885] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.883 UTC client backend[45885] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-simple 2025-11-30 18:45:15.884 UTC client backend[45885] isolation/deadlock-simple LOG: connection ready: setup total=1.682 ms, fork=0.340 ms, authentication=0.103 ms 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: TABLE r1; 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: UPDATE r1 SET a = 1; 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-11-30 18:45:15.884 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DELETE FROM r1; 2025-11-30 18:45:15.889 UTC client backend[45883] pg_regress/privileges ERROR: cannot use IN SCHEMA clause when using GRANT/REVOKE ON SCHEMAS 2025-11-30 18:45:15.889 UTC client backend[45883] pg_regress/privileges STATEMENT: ALTER DEFAULT PRIVILEGES IN SCHEMA testns GRANT USAGE ON SCHEMAS TO regress_priv_user2; 2025-11-30 18:45:15.889 UTC client backend[45883] pg_regress/privileges ERROR: unrecognized privilege type: "fake_privilege" 2025-11-30 18:45:15.889 UTC client backend[45883] pg_regress/privileges STATEMENT: SELECT makeaclitem('regress_priv_user1'::regrole, 'regress_priv_user2'::regrole, 'SELECT, fake_privilege', FALSE); 2025-11-30 18:45:15.890 UTC client backend[45883] pg_regress/privileges ERROR: a name must follow the "/" sign at character 8 2025-11-30 18:45:15.890 UTC client backend[45883] pg_regress/privileges STATEMENT: SELECT '""=r*/""'::aclitem; 2025-11-30 18:45:15.892 UTC client backend[45710] pg_regress/rowsecurity ERROR: update or delete on table "r1" violates foreign key constraint "r2_a_fkey" on table "r2" 2025-11-30 18:45:15.892 UTC client backend[45710] pg_regress/rowsecurity DETAIL: Key (a)=(10) is still referenced from table "r2". 2025-11-30 18:45:15.892 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DELETE FROM r1; 2025-11-30 18:45:15.896 UTC client backend[45883] pg_regress/privileges ERROR: cannot use IN SCHEMA clause when using GRANT/REVOKE ON LARGE OBJECTS 2025-11-30 18:45:15.896 UTC client backend[45883] pg_regress/privileges STATEMENT: ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL ON LARGE OBJECTS TO public; 2025-11-30 18:45:15.897 UTC unrecognized[45886] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.897 UTC client backend[45885] isolation/deadlock-simple/s2 ERROR: deadlock detected 2025-11-30 18:45:15.897 UTC client backend[45885] isolation/deadlock-simple/s2 DETAIL: Process 45885 waits for AccessExclusiveLock on relation 47577 of database 16387; blocked by process 45884. Process 45884 waits for AccessExclusiveLock on relation 47577 of database 16387; blocked by process 45885. Process 45885: LOCK TABLE a1 IN ACCESS EXCLUSIVE MODE; Process 45884: LOCK TABLE a1 IN ACCESS EXCLUSIVE MODE; 2025-11-30 18:45:15.897 UTC client backend[45885] isolation/deadlock-simple/s2 HINT: See server log for query details. 2025-11-30 18:45:15.897 UTC client backend[45885] isolation/deadlock-simple/s2 STATEMENT: LOCK TABLE a1 IN ACCESS EXCLUSIVE MODE; 2025-11-30 18:45:15.897 UTC client backend[45886] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.897 UTC client backend[45886] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.898 UTC client backend[45886] pg_regress/privileges LOG: connection ready: setup total=1.856 ms, fork=0.392 ms, authentication=0.133 ms 2025-11-30 18:45:15.898 UTC client backend[45882] isolation/deadlock-simple/control connection LOG: disconnection: session time: 0:00:00.020 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.899 UTC client backend[45884] isolation/deadlock-simple/s1 LOG: disconnection: session time: 0:00:00.019 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.900 UTC client backend[45883] pg_regress/privileges LOG: disconnection: session time: 0:00:00.020 user=postgres database=regression host=[local] 2025-11-30 18:45:15.900 UTC client backend[45885] isolation/deadlock-simple/s2 LOG: disconnection: session time: 0:00:00.017 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:15.906 UTC unrecognized[45889] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.906 UTC client backend[45889] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.906 UTC client backend[45889] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.907 UTC client backend[45889] isolation/deadlock-hard LOG: connection ready: setup total=1.771 ms, fork=0.333 ms, authentication=0.113 ms 2025-11-30 18:45:15.908 UTC unrecognized[45890] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.908 UTC client backend[45890] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.908 UTC client backend[45890] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.909 UTC client backend[45890] isolation/deadlock-hard LOG: connection ready: setup total=1.595 ms, fork=0.296 ms, authentication=0.101 ms 2025-11-30 18:45:15.910 UTC unrecognized[45891] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.911 UTC client backend[45891] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.911 UTC client backend[45891] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.912 UTC client backend[45891] isolation/deadlock-hard LOG: connection ready: setup total=1.590 ms, fork=0.316 ms, authentication=0.097 ms 2025-11-30 18:45:15.913 UTC unrecognized[45892] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.913 UTC client backend[45892] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.913 UTC client backend[45892] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.914 UTC client backend[45892] isolation/deadlock-hard LOG: connection ready: setup total=1.577 ms, fork=0.308 ms, authentication=0.099 ms 2025-11-30 18:45:15.915 UTC unrecognized[45893] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.915 UTC client backend[45893] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.915 UTC client backend[45893] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.916 UTC client backend[45893] isolation/deadlock-hard LOG: connection ready: setup total=1.595 ms, fork=0.314 ms, authentication=0.100 ms 2025-11-30 18:45:15.917 UTC unrecognized[45894] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.918 UTC client backend[45894] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.918 UTC client backend[45894] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.918 UTC client backend[45894] isolation/deadlock-hard LOG: connection ready: setup total=1.584 ms, fork=0.315 ms, authentication=0.099 ms 2025-11-30 18:45:15.919 UTC unrecognized[45895] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.919 UTC client backend[45895] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.919 UTC client backend[45895] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.920 UTC unrecognized[45896] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.920 UTC client backend[45896] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.920 UTC client backend[45896] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.920 UTC client backend[45895] pg_regress/privileges LOG: connection ready: setup total=1.633 ms, fork=0.303 ms, authentication=0.112 ms 2025-11-30 18:45:15.921 UTC client backend[45896] isolation/deadlock-hard LOG: connection ready: setup total=1.579 ms, fork=0.330 ms, authentication=0.098 ms 2025-11-30 18:45:15.921 UTC client backend[45886] pg_regress/privileges LOG: disconnection: session time: 0:00:00.024 user=postgres database=regression host=[local] 2025-11-30 18:45:15.923 UTC unrecognized[45897] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.924 UTC client backend[45897] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.924 UTC client backend[45897] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.924 UTC client backend[45897] isolation/deadlock-hard LOG: connection ready: setup total=1.601 ms, fork=0.280 ms, authentication=0.099 ms 2025-11-30 18:45:15.925 UTC unrecognized[45898] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.926 UTC client backend[45898] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.926 UTC client backend[45898] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-hard 2025-11-30 18:45:15.926 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-11-30 18:45:15.926 UTC client backend[45710] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-11-30 18:45:15.926 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: TABLE r1; 2025-11-30 18:45:15.927 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-11-30 18:45:15.927 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10), (20) RETURNING *; 2025-11-30 18:45:15.927 UTC client backend[45898] isolation/deadlock-hard LOG: connection ready: setup total=1.585 ms, fork=0.323 ms, authentication=0.096 ms 2025-11-30 18:45:15.931 UTC unrecognized[45899] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.931 UTC client backend[45899] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.931 UTC client backend[45899] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.932 UTC client backend[45899] pg_regress/privileges LOG: connection ready: setup total=1.701 ms, fork=0.327 ms, authentication=0.110 ms 2025-11-30 18:45:15.933 UTC client backend[45895] pg_regress/privileges LOG: disconnection: session time: 0:00:00.013 user=postgres database=regression host=[local] 2025-11-30 18:45:15.936 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-11-30 18:45:15.936 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: UPDATE r1 SET a = 30 RETURNING *; 2025-11-30 18:45:15.937 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-11-30 18:45:15.937 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10) ON CONFLICT (a) DO UPDATE SET a = 30 RETURNING *; 2025-11-30 18:45:15.937 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-11-30 18:45:15.937 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10) ON CONFLICT (a) DO UPDATE SET a = 30; 2025-11-30 18:45:15.938 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-11-30 18:45:15.938 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10) ON CONFLICT ON CONSTRAINT r1_pkey DO UPDATE SET a = 30; 2025-11-30 18:45:15.939 UTC unrecognized[45900] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.939 UTC client backend[45900] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.939 UTC client backend[45900] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.940 UTC client backend[45900] pg_regress/privileges LOG: connection ready: setup total=1.683 ms, fork=0.325 ms, authentication=0.105 ms 2025-11-30 18:45:15.940 UTC client backend[45899] pg_regress/privileges LOG: disconnection: session time: 0:00:00.009 user=postgres database=regression host=[local] 2025-11-30 18:45:15.941 UTC unrecognized[45901] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.941 UTC client backend[45901] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.941 UTC client backend[45901] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.942 UTC client backend[45901] pg_regress/privileges LOG: connection ready: setup total=1.641 ms, fork=0.324 ms, authentication=0.104 ms 2025-11-30 18:45:15.942 UTC client backend[45900] pg_regress/privileges LOG: disconnection: session time: 0:00:00.003 user=postgres database=regression host=[local] 2025-11-30 18:45:15.945 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p1" for table "r1" 2025-11-30 18:45:15.945 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (0); 2025-11-30 18:45:15.946 UTC client backend[45710] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p2" for table "r1" 2025-11-30 18:45:15.946 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (4); 2025-11-30 18:45:15.957 UTC client backend[45710] pg_regress/rowsecurity ERROR: policy "p1" for table "dob_t1" does not exist 2025-11-30 18:45:15.957 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP POLICY p1 ON dob_t1; 2025-11-30 18:45:15.959 UTC client backend[45710] pg_regress/rowsecurity ERROR: policy "p1" for table "dob_t1" does not exist 2025-11-30 18:45:15.959 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: DROP POLICY p1 ON dob_t1; 2025-11-30 18:45:15.962 UTC unrecognized[45902] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.963 UTC client backend[45902] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.963 UTC client backend[45902] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.963 UTC client backend[45902] pg_regress/privileges LOG: connection ready: setup total=1.746 ms, fork=0.320 ms, authentication=0.114 ms 2025-11-30 18:45:15.964 UTC client backend[45901] pg_regress/privileges LOG: disconnection: session time: 0:00:00.022 user=postgres database=regression host=[local] 2025-11-30 18:45:15.966 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table ref_tbl 2025-11-30 18:45:15.966 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM ref_tbl; 2025-11-30 18:45:15.967 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table rls_tbl 2025-11-30 18:45:15.967 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_tbl; 2025-11-30 18:45:15.970 UTC client backend[45902] pg_regress/privileges ERROR: view "atestv4" does not exist 2025-11-30 18:45:15.970 UTC client backend[45902] pg_regress/privileges STATEMENT: DROP VIEW atestv4; 2025-11-30 18:45:15.981 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table rls_child_tbl 2025-11-30 18:45:15.981 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_child_tbl WHERE a <<< 1000; 2025-11-30 18:45:15.983 UTC client backend[44596] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-11-30 18:45:15.983 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Non-superusers must delegate GSSAPI credentials, provide a password, or enable SCRAM pass-through in user mapping. 2025-11-30 18:45:15.983 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-11-30 18:45:15.983 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid option "password" 2025-11-30 18:45:15.983 UTC client backend[44596] pg_regress/postgres_fdw HINT: Perhaps you meant the option "passfile". 2025-11-30 18:45:15.983 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ALTER SERVER loopback_nopw OPTIONS (ADD password 'dummypw'); 2025-11-30 18:45:15.983 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table rls_child_tbl 2025-11-30 18:45:15.983 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM (SELECT * FROM rls_child_tbl UNION ALL SELECT * FROM rls_child_tbl) t WHERE a <<< 1000; 2025-11-30 18:45:15.984 UTC unrecognized[45903] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.984 UTC client backend[45903] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.984 UTC client backend[45903] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.985 UTC client backend[45903] postgres_fdw LOG: connection ready: setup total=1.675 ms, fork=0.357 ms, authentication=0.116 ms 2025-11-30 18:45:15.985 UTC client backend[44596] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-11-30 18:45:15.985 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Non-superuser cannot connect if the server does not request a password or use GSSAPI with delegated credentials. 2025-11-30 18:45:15.985 UTC client backend[44596] pg_regress/postgres_fdw HINT: Target server's authentication method must be changed or password_required=false set in the user mapping attributes. 2025-11-30 18:45:15.985 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-11-30 18:45:15.985 UTC client backend[45903] postgres_fdw LOG: disconnection: session time: 0:00:00.001 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.985 UTC client backend[44596] pg_regress/postgres_fdw ERROR: password_required=false is superuser-only 2025-11-30 18:45:15.985 UTC client backend[44596] pg_regress/postgres_fdw HINT: User mappings with the password_required option set to false may only be created or modified by the superuser. 2025-11-30 18:45:15.985 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD password_required 'false'); 2025-11-30 18:45:15.986 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table rls_tbl 2025-11-30 18:45:15.986 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_tbl WHERE a <<< 1000; 2025-11-30 18:45:15.986 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for view rls_tbl_view 2025-11-30 18:45:15.986 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_tbl_view WHERE a <<< 1000; 2025-11-30 18:45:15.986 UTC unrecognized[45904] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.987 UTC client backend[45904] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.987 UTC client backend[45904] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.988 UTC client backend[45904] postgres_fdw LOG: connection ready: setup total=1.486 ms, fork=0.313 ms, authentication=0.102 ms 2025-11-30 18:45:15.988 UTC client backend[44596] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-11-30 18:45:15.988 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Non-superuser cannot connect if the server does not request a password or use GSSAPI with delegated credentials. 2025-11-30 18:45:15.988 UTC client backend[44596] pg_regress/postgres_fdw HINT: Target server's authentication method must be changed or password_required=false set in the user mapping attributes. 2025-11-30 18:45:15.988 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-11-30 18:45:15.988 UTC client backend[45904] postgres_fdw LOG: disconnection: session time: 0:00:00.001 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.988 UTC client backend[45710] pg_regress/rowsecurity ERROR: permission denied for table rls_tbl 2025-11-30 18:45:15.988 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: SELECT * FROM (SELECT * FROM rls_tbl UNION ALL SELECT * FROM rls_tbl) t WHERE a <<< 1000; 2025-11-30 18:45:15.990 UTC unrecognized[45905] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.990 UTC client backend[45905] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.990 UTC client backend[45905] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.991 UTC client backend[45905] postgres_fdw LOG: connection ready: setup total=1.461 ms, fork=0.274 ms, authentication=0.104 ms 2025-11-30 18:45:15.991 UTC client backend[45902] pg_regress/privileges ERROR: role "regress_priv_user8" does not exist 2025-11-30 18:45:15.991 UTC client backend[45902] pg_regress/privileges STATEMENT: DROP USER regress_priv_user8; 2025-11-30 18:45:15.993 UTC client backend[45902] pg_regress/privileges ERROR: permission denied for table lock_table 2025-11-30 18:45:15.993 UTC client backend[45902] pg_regress/privileges STATEMENT: LOCK TABLE lock_table IN ROW EXCLUSIVE MODE; 2025-11-30 18:45:15.993 UTC client backend[45902] pg_regress/privileges ERROR: permission denied for table lock_table 2025-11-30 18:45:15.993 UTC client backend[45902] pg_regress/privileges STATEMENT: LOCK TABLE lock_table IN ACCESS EXCLUSIVE MODE; 2025-11-30 18:45:15.993 UTC unrecognized[45906] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.994 UTC client backend[45906] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.994 UTC client backend[45906] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.994 UTC unrecognized[45907] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.994 UTC client backend[45907] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.994 UTC client backend[45907] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:15.995 UTC client backend[45906] pg_regress/privileges LOG: connection ready: setup total=1.679 ms, fork=0.294 ms, authentication=0.107 ms 2025-11-30 18:45:15.995 UTC client backend[45902] pg_regress/privileges LOG: disconnection: session time: 0:00:00.032 user=postgres database=regression host=[local] 2025-11-30 18:45:15.995 UTC client backend[45907] postgres_fdw LOG: connection ready: setup total=1.470 ms, fork=0.295 ms, authentication=0.102 ms 2025-11-30 18:45:15.996 UTC client backend[45906] pg_regress/privileges ERROR: permission denied for table lock_table 2025-11-30 18:45:15.996 UTC client backend[45906] pg_regress/privileges STATEMENT: LOCK TABLE lock_table IN ACCESS EXCLUSIVE MODE; 2025-11-30 18:45:15.996 UTC unrecognized[45908] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:15.997 UTC client backend[45908] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:15.997 UTC client backend[45908] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:15.998 UTC client backend[45908] pg_regress/privileges LOG: connection ready: setup total=1.584 ms, fork=0.290 ms, authentication=0.110 ms 2025-11-30 18:45:15.998 UTC client backend[45906] pg_regress/privileges LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression host=[local] 2025-11-30 18:45:15.998 UTC client backend[45905] postgres_fdw LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.999 UTC client backend[45907] postgres_fdw LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:15.999 UTC client backend[44596] pg_regress/postgres_fdw ERROR: sslcert and sslkey are superuser-only 2025-11-30 18:45:15.999 UTC client backend[44596] pg_regress/postgres_fdw HINT: User mappings with the sslcert or sslkey options set may only be created or modified by the superuser. 2025-11-30 18:45:15.999 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD sslcert 'foo.crt'); 2025-11-30 18:45:15.999 UTC client backend[44596] pg_regress/postgres_fdw ERROR: sslcert and sslkey are superuser-only 2025-11-30 18:45:15.999 UTC client backend[44596] pg_regress/postgres_fdw HINT: User mappings with the sslcert or sslkey options set may only be created or modified by the superuser. 2025-11-30 18:45:15.999 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD sslkey 'foo.key'); 2025-11-30 18:45:16.000 UTC unrecognized[45909] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.000 UTC client backend[44596] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-11-30 18:45:16.000 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Non-superusers must delegate GSSAPI credentials, provide a password, or enable SCRAM pass-through in user mapping. 2025-11-30 18:45:16.000 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-11-30 18:45:16.000 UTC client backend[45909] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.000 UTC client backend[45909] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:16.001 UTC client backend[45909] pg_regress/privileges LOG: connection ready: setup total=1.689 ms, fork=0.359 ms, authentication=0.102 ms 2025-11-30 18:45:16.001 UTC client backend[45908] pg_regress/privileges LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression host=[local] 2025-11-30 18:45:16.001 UTC unrecognized[45910] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.001 UTC client backend[45910] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.001 UTC client backend[45910] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.002 UTC client backend[45910] postgres_fdw LOG: connection ready: setup total=1.475 ms, fork=0.251 ms, authentication=0.101 ms 2025-11-30 18:45:16.003 UTC unrecognized[45911] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.003 UTC client backend[45911] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.003 UTC client backend[45911] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:16.004 UTC client backend[45911] pg_regress/privileges LOG: connection ready: setup total=1.593 ms, fork=0.297 ms, authentication=0.100 ms 2025-11-30 18:45:16.004 UTC client backend[45909] pg_regress/privileges LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression host=[local] 2025-11-30 18:45:16.005 UTC unrecognized[45912] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.006 UTC client backend[45912] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.006 UTC client backend[45912] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.006 UTC unrecognized[45913] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.006 UTC client backend[45913] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.006 UTC client backend[45913] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:16.006 UTC client backend[45912] postgres_fdw LOG: connection ready: setup total=1.429 ms, fork=0.257 ms, authentication=0.101 ms 2025-11-30 18:45:16.007 UTC client backend[45913] pg_regress/privileges LOG: connection ready: setup total=1.587 ms, fork=0.272 ms, authentication=0.100 ms 2025-11-30 18:45:16.007 UTC client backend[45911] pg_regress/privileges LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression host=[local] 2025-11-30 18:45:16.009 UTC unrecognized[45914] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.009 UTC client backend[45914] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.009 UTC client backend[45914] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:16.009 UTC client backend[45910] postgres_fdw LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.010 UTC client backend[45912] postgres_fdw LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.010 UTC client backend[45914] pg_regress/privileges LOG: connection ready: setup total=1.782 ms, fork=0.255 ms, authentication=0.111 ms 2025-11-30 18:45:16.011 UTC client backend[45913] pg_regress/privileges LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression host=[local] 2025-11-30 18:45:16.013 UTC unrecognized[45915] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.013 UTC client backend[45915] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.013 UTC client backend[45915] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-11-30 18:45:16.014 UTC client backend[45915] pg_regress/privileges LOG: connection ready: setup total=1.606 ms, fork=0.287 ms, authentication=0.101 ms 2025-11-30 18:45:16.014 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot PREPARE a transaction that has operated on postgres_fdw foreign tables 2025-11-30 18:45:16.014 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: PREPARE TRANSACTION 'fdw_tpc'; 2025-11-30 18:45:16.014 UTC client backend[45914] pg_regress/privileges LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression host=[local] 2025-11-30 18:45:16.014 UTC client backend[44596] pg_regress/postgres_fdw WARNING: there is no transaction in progress 2025-11-30 18:45:16.015 UTC client backend[45803] postgres_fdw LOG: disconnection: session time: 0:00:00.637 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.016 UTC unrecognized[45916] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.016 UTC client backend[45916] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.016 UTC client backend[45916] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.017 UTC client backend[45916] fdw_retry_check LOG: connection ready: setup total=1.470 ms, fork=0.249 ms, authentication=0.104 ms 2025-11-30 18:45:16.021 UTC client backend[45916] fdw_retry_check FATAL: terminating connection due to administrator command 2025-11-30 18:45:16.021 UTC client backend[45916] fdw_retry_check LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.025 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "rls_t" 2025-11-30 18:45:16.025 UTC client backend[45710] pg_regress/rowsecurity CONTEXT: SQL function "rls_f" statement 1 2025-11-30 18:45:16.025 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: select rls_f(c) from test_t order by rls_f; 2025-11-30 18:45:16.027 UTC client backend[45710] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "rls_t" 2025-11-30 18:45:16.027 UTC client backend[45710] pg_regress/rowsecurity CONTEXT: SQL function "rls_f" statement 1 2025-11-30 18:45:16.027 UTC client backend[45710] pg_regress/rowsecurity STATEMENT: select rls_f(c) from test_t order by rls_f; 2025-11-30 18:45:16.028 UTC client backend[45915] pg_regress/privileges ERROR: must be able to SET ROLE "regress_roleoption_donor" 2025-11-30 18:45:16.028 UTC client backend[45915] pg_regress/privileges STATEMENT: ALTER TABLE regress_roleoption.t1 OWNER TO regress_roleoption_donor; 2025-11-30 18:45:16.029 UTC client backend[45915] pg_regress/privileges ERROR: must be owner of table t4 2025-11-30 18:45:16.029 UTC client backend[45915] pg_regress/privileges STATEMENT: ALTER TABLE regress_roleoption.t4 OWNER TO regress_roleoption_protagonist; 2025-11-30 18:45:16.037 UTC client backend[45915] pg_regress/privileges WARNING: permission denied to vacuum "maintain_test", skipping it 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges WARNING: permission denied to analyze "maintain_test", skipping it 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges WARNING: permission denied to vacuum "maintain_test", skipping it 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges ERROR: permission denied for table maintain_test 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges STATEMENT: CLUSTER maintain_test USING maintain_test_a_idx; 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges ERROR: permission denied for materialized view refresh_test 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW refresh_test; 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges ERROR: permission denied for table maintain_test 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges STATEMENT: REINDEX TABLE maintain_test; 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges ERROR: permission denied for index maintain_test_a_idx 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges STATEMENT: REINDEX INDEX maintain_test_a_idx; 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges ERROR: must be owner of schema reindex_test 2025-11-30 18:45:16.038 UTC client backend[45915] pg_regress/privileges STATEMENT: REINDEX SCHEMA reindex_test; 2025-11-30 18:45:16.044 UTC client backend[45915] pg_regress/privileges ERROR: must be owner of schema reindex_test 2025-11-30 18:45:16.044 UTC client backend[45915] pg_regress/privileges STATEMENT: REINDEX SCHEMA reindex_test; 2025-11-30 18:45:16.054 UTC client backend[45915] pg_regress/privileges ERROR: permission denied for table grantor_test1 2025-11-30 18:45:16.054 UTC client backend[45915] pg_regress/privileges STATEMENT: GRANT SELECT, UPDATE ON grantor_test1 TO regress_grantor3; 2025-11-30 18:45:16.054 UTC client backend[45915] pg_regress/privileges WARNING: not all privileges were granted for "grantor_test2" 2025-11-30 18:45:16.068 UTC unrecognized[45917] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.069 UTC client backend[45917] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.069 UTC client backend[45917] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.070 UTC client backend[45917] fdw_retry_check LOG: connection ready: setup total=1.899 ms, fork=0.481 ms, authentication=0.124 ms 2025-11-30 18:45:16.073 UTC client backend[45917] fdw_retry_check FATAL: terminating connection due to administrator command 2025-11-30 18:45:16.073 UTC client backend[45917] fdw_retry_check LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.074 UTC client backend[45915] pg_regress/privileges LOG: disconnection: session time: 0:00:00.060 user=postgres database=regression host=[local] 2025-11-30 18:45:16.075 UTC client backend[45710] pg_regress/rowsecurity LOG: disconnection: session time: 0:00:02.326 user=postgres database=regression host=[local] 2025-11-30 18:45:16.099 UTC unrecognized[45940] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.099 UTC unrecognized[45941] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.099 UTC client backend[45940] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.099 UTC client backend[45940] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/brin_multi 2025-11-30 18:45:16.099 UTC client backend[45941] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.100 UTC client backend[45941] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/brin_bloom 2025-11-30 18:45:16.100 UTC client backend[45940] pg_regress/brin_multi LOG: connection ready: setup total=2.234 ms, fork=0.449 ms, authentication=0.140 ms 2025-11-30 18:45:16.100 UTC client backend[45941] pg_regress/brin_bloom LOG: connection ready: setup total=1.814 ms, fork=0.332 ms, authentication=0.108 ms 2025-11-30 18:45:16.112 UTC client backend[45941] pg_regress/brin_bloom ERROR: value -1.1 out of bounds for option "n_distinct_per_range" 2025-11-30 18:45:16.112 UTC client backend[45941] pg_regress/brin_bloom DETAIL: Valid values are between "-1.000000" and "2147483647.000000". 2025-11-30 18:45:16.112 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: CREATE INDEX brinidx_bloom ON brintest_bloom USING brin ( byteacol bytea_bloom_ops(n_distinct_per_range = -1.1) ); 2025-11-30 18:45:16.113 UTC client backend[45940] pg_regress/brin_multi ERROR: value 7 out of bounds for option "values_per_range" 2025-11-30 18:45:16.113 UTC client backend[45940] pg_regress/brin_multi DETAIL: Valid values are between "8" and "256". 2025-11-30 18:45:16.113 UTC client backend[45940] pg_regress/brin_multi STATEMENT: CREATE INDEX brinidx_multi ON brintest_multi USING brin ( int8col int8_minmax_multi_ops(values_per_range = 7) ); 2025-11-30 18:45:16.113 UTC client backend[45941] pg_regress/brin_bloom ERROR: value 0.00009 out of bounds for option "false_positive_rate" 2025-11-30 18:45:16.113 UTC client backend[45941] pg_regress/brin_bloom DETAIL: Valid values are between "0.000100" and "0.250000". 2025-11-30 18:45:16.113 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: CREATE INDEX brinidx_bloom ON brintest_bloom USING brin ( byteacol bytea_bloom_ops(false_positive_rate = 0.00009) ); 2025-11-30 18:45:16.113 UTC client backend[45940] pg_regress/brin_multi ERROR: value 257 out of bounds for option "values_per_range" 2025-11-30 18:45:16.113 UTC client backend[45940] pg_regress/brin_multi DETAIL: Valid values are between "8" and "256". 2025-11-30 18:45:16.113 UTC client backend[45940] pg_regress/brin_multi STATEMENT: CREATE INDEX brinidx_multi ON brintest_multi USING brin ( int8col int8_minmax_multi_ops(values_per_range = 257) ); 2025-11-30 18:45:16.113 UTC client backend[45941] pg_regress/brin_bloom ERROR: value 0.26 out of bounds for option "false_positive_rate" 2025-11-30 18:45:16.113 UTC client backend[45941] pg_regress/brin_bloom DETAIL: Valid values are between "0.000100" and "0.250000". 2025-11-30 18:45:16.113 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: CREATE INDEX brinidx_bloom ON brintest_bloom USING brin ( byteacol bytea_bloom_ops(false_positive_rate = 0.26) ); 2025-11-30 18:45:16.175 UTC client backend[45941] pg_regress/brin_bloom ERROR: "brintest_bloom" is not an index 2025-11-30 18:45:16.175 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_new_values('brintest_bloom'); 2025-11-30 18:45:16.176 UTC client backend[45941] pg_regress/brin_bloom ERROR: "tenk1_unique1" is not a BRIN index 2025-11-30 18:45:16.176 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_new_values('tenk1_unique1'); 2025-11-30 18:45:16.176 UTC client backend[45941] pg_regress/brin_bloom ERROR: block number out of range: -1 2025-11-30 18:45:16.176 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: SELECT brin_desummarize_range('brinidx_bloom', -1); 2025-11-30 18:45:16.181 UTC client backend[44596] pg_regress/postgres_fdw ERROR: FATAL: terminating connection due to administrator command server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. invalid socket 2025-11-30 18:45:16.181 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: SAVEPOINT s2 2025-11-30 18:45:16.181 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1 LIMIT 1; 2025-11-30 18:45:16.182 UTC client backend[45941] pg_regress/brin_bloom ERROR: block number out of range: -1 2025-11-30 18:45:16.182 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_range('brin_summarize_bloom_idx', -1); 2025-11-30 18:45:16.182 UTC client backend[45941] pg_regress/brin_bloom ERROR: block number out of range: 4294967296 2025-11-30 18:45:16.182 UTC client backend[45941] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_range('brin_summarize_bloom_idx', 4294967296); 2025-11-30 18:45:16.184 UTC unrecognized[45942] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.184 UTC client backend[45942] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.184 UTC client backend[45942] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.185 UTC client backend[45942] fdw_retry_check LOG: connection ready: setup total=1.923 ms, fork=0.518 ms, authentication=0.129 ms 2025-11-30 18:45:16.188 UTC unrecognized[45943] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.188 UTC client backend[45943] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.189 UTC client backend[45943] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.189 UTC client backend[45943] postgres_fdw LOG: connection ready: setup total=1.599 ms, fork=0.372 ms, authentication=0.115 ms 2025-11-30 18:45:16.196 UTC client backend[45942] fdw_retry_check LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.196 UTC client backend[45943] postgres_fdw LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.198 UTC unrecognized[45944] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.198 UTC client backend[45944] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.198 UTC client backend[45944] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.199 UTC client backend[45944] fdw_retry_check LOG: connection ready: setup total=1.632 ms, fork=0.370 ms, authentication=0.111 ms 2025-11-30 18:45:16.201 UTC client backend[45941] pg_regress/brin_bloom LOG: disconnection: session time: 0:00:00.101 user=postgres database=regression host=[local] 2025-11-30 18:45:16.202 UTC unrecognized[45945] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.202 UTC client backend[45945] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.202 UTC client backend[45945] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.203 UTC client backend[45945] postgres_fdw LOG: connection ready: setup total=1.549 ms, fork=0.311 ms, authentication=0.118 ms 2025-11-30 18:45:16.206 UTC client backend[44596] pg_regress/postgres_fdw WARNING: cannot close connection for server "loopback" because it is still in use 2025-11-30 18:45:16.206 UTC client backend[44596] pg_regress/postgres_fdw WARNING: cannot close connection for server "loopback" because it is still in use 2025-11-30 18:45:16.206 UTC client backend[44596] pg_regress/postgres_fdw WARNING: cannot close connection for server "loopback2" because it is still in use 2025-11-30 18:45:16.207 UTC client backend[45945] postgres_fdw LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.208 UTC client backend[44596] pg_regress/postgres_fdw ERROR: server "unknownserver" does not exist 2025-11-30 18:45:16.208 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT postgres_fdw_disconnect('unknownserver'); 2025-11-30 18:45:16.208 UTC client backend[45944] fdw_retry_check LOG: disconnection: session time: 0:00:00.011 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.212 UTC unrecognized[45946] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.212 UTC client backend[45946] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.212 UTC client backend[45946] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.213 UTC client backend[45946] fdw_retry_check LOG: connection ready: setup total=1.550 ms, fork=0.319 ms, authentication=0.108 ms 2025-11-30 18:45:16.217 UTC unrecognized[45947] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.217 UTC client backend[45947] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.217 UTC client backend[45947] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.218 UTC client backend[45947] fdw_retry_check LOG: connection ready: setup total=1.507 ms, fork=0.306 ms, authentication=0.105 ms 2025-11-30 18:45:16.221 UTC client backend[45946] fdw_retry_check LOG: disconnection: session time: 0:00:00.009 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.221 UTC client backend[45947] fdw_retry_check LOG: disconnection: session time: 0:00:00.004 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.225 UTC unrecognized[45948] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.225 UTC client backend[45948] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.225 UTC client backend[45948] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.226 UTC client backend[45948] fdw_retry_check LOG: connection ready: setup total=1.451 ms, fork=0.276 ms, authentication=0.102 ms 2025-11-30 18:45:16.227 UTC client backend[45948] fdw_retry_check LOG: disconnection: session time: 0:00:00.003 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.237 UTC unrecognized[45949] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.237 UTC client backend[45949] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.237 UTC client backend[45949] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.238 UTC client backend[45949] fdw_retry_check LOG: connection ready: setup total=1.555 ms, fork=0.329 ms, authentication=0.107 ms 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 LOG: process 45898 detected deadlock while waiting for AccessExclusiveLock on relation 47693 of database 16387 after 10.553 ms 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 DETAIL: Process holding the lock: 45890. Wait queue: . 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 CONTEXT: waiting for AccessExclusiveLock on relation 47693 of database 16387 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 STATEMENT: LOCK TABLE a1; 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 ERROR: deadlock detected 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 DETAIL: Process 45898 waits for AccessExclusiveLock on relation 47693 of database 16387; blocked by process 45890. Process 45890 waits for AccessExclusiveLock on relation 47700 of database 16387; blocked by process 45891. Process 45891 waits for AccessExclusiveLock on relation 47705 of database 16387; blocked by process 45892. Process 45892 waits for AccessExclusiveLock on relation 47709 of database 16387; blocked by process 45893. Process 45893 waits for AccessExclusiveLock on relation 47713 of database 16387; blocked by process 45894. Process 45894 waits for AccessExclusiveLock on relation 47717 of database 16387; blocked by process 45896. Process 45896 waits for AccessExclusiveLock on relation 47720 of database 16387; blocked by process 45897. Process 45897 waits for AccessExclusiveLock on relation 47723 of database 16387; blocked by process 45898. Process 45898: LOCK TABLE a1; Process 45890: LOCK TABLE a2; Process 45891: LOCK TABLE a3; Process 45892: LOCK TABLE a4; Process 45893: LOCK TABLE a5; Process 45894: LOCK TABLE a6; Process 45896: LOCK TABLE a7; Process 45897: LOCK TABLE a8; 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 HINT: See server log for query details. 2025-11-30 18:45:16.245 UTC client backend[45898] isolation/deadlock-hard/s8 STATEMENT: LOCK TABLE a1; 2025-11-30 18:45:16.292 UTC client backend[45949] fdw_retry_check LOG: disconnection: session time: 0:00:00.055 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.304 UTC unrecognized[45950] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.304 UTC client backend[45950] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.304 UTC client backend[45950] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.305 UTC client backend[45950] fdw_retry_check LOG: connection ready: setup total=1.926 ms, fork=0.457 ms, authentication=0.142 ms 2025-11-30 18:45:16.320 UTC client backend[45950] fdw_retry_check LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.327 UTC unrecognized[45951] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.327 UTC client backend[45951] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.327 UTC client backend[45951] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.328 UTC client backend[45951] fdw_retry_check LOG: connection ready: setup total=1.794 ms, fork=0.433 ms, authentication=0.127 ms 2025-11-30 18:45:16.355 UTC client backend[45940] pg_regress/brin_multi ERROR: "brintest_multi" is not an index 2025-11-30 18:45:16.355 UTC client backend[45940] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_new_values('brintest_multi'); 2025-11-30 18:45:16.355 UTC client backend[45940] pg_regress/brin_multi ERROR: "tenk1_unique1" is not a BRIN index 2025-11-30 18:45:16.355 UTC client backend[45940] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_new_values('tenk1_unique1'); 2025-11-30 18:45:16.355 UTC client backend[45940] pg_regress/brin_multi ERROR: block number out of range: -1 2025-11-30 18:45:16.355 UTC client backend[45940] pg_regress/brin_multi STATEMENT: SELECT brin_desummarize_range('brinidx_multi', -1); 2025-11-30 18:45:16.361 UTC client backend[45951] fdw_retry_check LOG: disconnection: session time: 0:00:00.034 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.370 UTC unrecognized[45952] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.370 UTC client backend[45952] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.371 UTC client backend[45952] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.371 UTC client backend[45952] fdw_retry_check LOG: connection ready: setup total=1.950 ms, fork=0.491 ms, authentication=0.132 ms 2025-11-30 18:45:16.384 UTC unrecognized[45953] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.384 UTC client backend[45953] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.384 UTC client backend[45953] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.385 UTC client backend[45953] postgres_fdw LOG: connection ready: setup total=1.861 ms, fork=0.483 ms, authentication=0.125 ms 2025-11-30 18:45:16.421 UTC client backend[45952] fdw_retry_check ERROR: relation "public.non_existent_table" does not exist at character 43 2025-11-30 18:45:16.421 UTC client backend[45952] fdw_retry_check STATEMENT: DECLARE c3 CURSOR FOR SELECT a, b, c FROM public.non_existent_table 2025-11-30 18:45:16.421 UTC client backend[44596] pg_regress/postgres_fdw ERROR: relation "public.non_existent_table" does not exist 2025-11-30 18:45:16.421 UTC client backend[44596] pg_regress/postgres_fdw CONTEXT: remote SQL command: SELECT a, b, c FROM public.non_existent_table 2025-11-30 18:45:16.421 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: SELECT * FROM async_pt; 2025-11-30 18:45:16.421 UTC unrecognized[45954] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.449 UTC client backend[44596] pg_regress/postgres_fdw ERROR: cannot copy from foreign table "async_p1" 2025-11-30 18:45:16.449 UTC client backend[44596] pg_regress/postgres_fdw DETAIL: Partition "async_p1" is a foreign table in partitioned table "async_pt" 2025-11-30 18:45:16.449 UTC client backend[44596] pg_regress/postgres_fdw HINT: Try the COPY (SELECT ...) TO variant. 2025-11-30 18:45:16.449 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: COPY async_pt TO stdout; 2025-11-30 18:45:16.521 UTC client backend[45953] postgres_fdw LOG: disconnection: session time: 0:00:00.136 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.523 UTC unrecognized[45955] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.523 UTC client backend[45955] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.523 UTC client backend[45955] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.524 UTC client backend[45955] postgres_fdw LOG: connection ready: setup total=1.918 ms, fork=0.369 ms, authentication=0.144 ms 2025-11-30 18:45:16.531 UTC client backend[45955] postgres_fdw LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.537 UTC unrecognized[45956] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.537 UTC client backend[45956] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.537 UTC client backend[45956] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.538 UTC client backend[45956] postgres_fdw LOG: connection ready: setup total=1.818 ms, fork=0.463 ms, authentication=0.121 ms 2025-11-30 18:45:16.556 UTC client backend[45940] pg_regress/brin_multi ERROR: block number out of range: -1 2025-11-30 18:45:16.556 UTC client backend[45940] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_range('brin_summarize_multi_idx', -1); 2025-11-30 18:45:16.556 UTC client backend[45940] pg_regress/brin_multi ERROR: block number out of range: 4294967296 2025-11-30 18:45:16.556 UTC client backend[45940] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_range('brin_summarize_multi_idx', 4294967296); 2025-11-30 18:45:16.590 UTC client backend[45889] isolation/deadlock-hard/control connection LOG: disconnection: session time: 0:00:00.684 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.591 UTC client backend[45890] isolation/deadlock-hard/s1 LOG: disconnection: session time: 0:00:00.682 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.591 UTC client backend[45893] isolation/deadlock-hard/s4 LOG: disconnection: session time: 0:00:00.675 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.592 UTC client backend[45896] isolation/deadlock-hard/s6 LOG: disconnection: session time: 0:00:00.672 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.592 UTC client backend[45892] isolation/deadlock-hard/s3 LOG: disconnection: session time: 0:00:00.679 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.592 UTC client backend[45891] isolation/deadlock-hard/s2 LOG: disconnection: session time: 0:00:00.681 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.592 UTC client backend[45894] isolation/deadlock-hard/s5 LOG: disconnection: session time: 0:00:00.674 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.593 UTC client backend[45898] isolation/deadlock-hard/s8 LOG: disconnection: session time: 0:00:00.667 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.593 UTC client backend[45897] isolation/deadlock-hard/s7 LOG: disconnection: session time: 0:00:00.669 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.599 UTC unrecognized[45959] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.599 UTC client backend[45959] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.599 UTC client backend[45959] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft 2025-11-30 18:45:16.600 UTC client backend[45959] isolation/deadlock-soft LOG: connection ready: setup total=1.943 ms, fork=0.437 ms, authentication=0.121 ms 2025-11-30 18:45:16.601 UTC unrecognized[45960] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.602 UTC client backend[45960] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.602 UTC client backend[45960] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft 2025-11-30 18:45:16.602 UTC client backend[45960] isolation/deadlock-soft LOG: connection ready: setup total=1.639 ms, fork=0.298 ms, authentication=0.105 ms 2025-11-30 18:45:16.604 UTC unrecognized[45961] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.604 UTC client backend[45961] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.604 UTC client backend[45961] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft 2025-11-30 18:45:16.605 UTC client backend[45961] isolation/deadlock-soft LOG: connection ready: setup total=1.598 ms, fork=0.292 ms, authentication=0.102 ms 2025-11-30 18:45:16.606 UTC unrecognized[45962] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.607 UTC client backend[45962] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.607 UTC client backend[45962] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft 2025-11-30 18:45:16.607 UTC client backend[45962] isolation/deadlock-soft LOG: connection ready: setup total=1.933 ms, fork=0.488 ms, authentication=0.117 ms 2025-11-30 18:45:16.609 UTC unrecognized[45963] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.609 UTC client backend[45963] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.609 UTC client backend[45963] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft 2025-11-30 18:45:16.610 UTC client backend[45952] fdw_retry_check LOG: disconnection: session time: 0:00:00.239 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.610 UTC client backend[45956] postgres_fdw LOG: disconnection: session time: 0:00:00.073 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.611 UTC client backend[45963] isolation/deadlock-soft LOG: connection ready: setup total=2.199 ms, fork=0.478 ms, authentication=0.142 ms 2025-11-30 18:45:16.611 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid value for floating point option "fdw_startup_cost": 100$%$#$# 2025-11-30 18:45:16.611 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: CREATE SERVER inv_scst FOREIGN DATA WRAPPER postgres_fdw OPTIONS(fdw_startup_cost '100$%$#$#'); 2025-11-30 18:45:16.611 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid value for floating point option "fdw_tuple_cost": 100$%$#$# 2025-11-30 18:45:16.611 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: CREATE SERVER inv_scst FOREIGN DATA WRAPPER postgres_fdw OPTIONS(fdw_tuple_cost '100$%$#$#'); 2025-11-30 18:45:16.612 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid value for integer option "fetch_size": 100$%$#$# 2025-11-30 18:45:16.612 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: CREATE FOREIGN TABLE inv_fsz (c1 int ) SERVER loopback OPTIONS (fetch_size '100$%$#$#'); 2025-11-30 18:45:16.612 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid value for integer option "batch_size": 100$%$#$# 2025-11-30 18:45:16.612 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: CREATE FOREIGN TABLE inv_bsz (c1 int ) SERVER loopback OPTIONS (batch_size '100$%$#$#'); 2025-11-30 18:45:16.613 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid option "nonexistent" 2025-11-30 18:45:16.613 UTC client backend[44596] pg_regress/postgres_fdw HINT: There are no valid options in this context. 2025-11-30 18:45:16.613 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ALTER FOREIGN DATA WRAPPER postgres_fdw OPTIONS (nonexistent 'fdw'); 2025-11-30 18:45:16.616 UTC unrecognized[45964] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.616 UTC client backend[45964] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.616 UTC client backend[45964] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=postgres_fdw 2025-11-30 18:45:16.617 UTC client backend[45964] postgres_fdw LOG: connection ready: setup total=1.574 ms, fork=0.287 ms, authentication=0.110 ms 2025-11-30 18:45:16.622 UTC client backend[45964] postgres_fdw LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.623 UTC unrecognized[45965] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.623 UTC client backend[45965] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.623 UTC client backend[45965] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_regression_postgres_fdw44596 2025-11-30 18:45:16.624 UTC client backend[45965] fdw_regression_postgres_fdw44596 LOG: connection ready: setup total=1.507 ms, fork=0.297 ms, authentication=0.116 ms 2025-11-30 18:45:16.629 UTC client backend[45965] fdw_regression_postgres_fdw44596 LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.630 UTC unrecognized[45966] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.631 UTC client backend[45966] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.631 UTC client backend[45966] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_pg_regress/postgres_fdwpostgres% 2025-11-30 18:45:16.631 UTC client backend[45966] fdw_pg_regress/postgres_fdwpostgres% LOG: connection ready: setup total=1.880 ms, fork=0.522 ms, authentication=0.115 ms 2025-11-30 18:45:16.636 UTC client backend[45966] fdw_pg_regress/postgres_fdwpostgres% LOG: disconnection: session time: 0:00:00.005 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.637 UTC unrecognized[45967] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.638 UTC client backend[45967] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.638 UTC client backend[45967] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_692c90b2.ae34 2025-11-30 18:45:16.639 UTC client backend[45967] fdw_692c90b2.ae34 LOG: connection ready: setup total=1.818 ms, fork=0.521 ms, authentication=0.116 ms 2025-11-30 18:45:16.646 UTC client backend[45967] fdw_692c90b2.ae34 LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:16.649 UTC client backend[45940] pg_regress/brin_multi LOG: disconnection: session time: 0:00:00.549 user=postgres database=regression host=[local] 2025-11-30 18:45:16.664 UTC unrecognized[45989] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.664 UTC client backend[45989] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.664 UTC client backend[45989] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/alter_generic 2025-11-30 18:45:16.665 UTC client backend[45989] pg_regress/alter_generic LOG: connection ready: setup total=10.659 ms, fork=0.885 ms, authentication=0.164 ms 2025-11-30 18:45:16.668 UTC unrecognized[45990] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.669 UTC client backend[45990] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.669 UTC client backend[45990] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tidrangescan 2025-11-30 18:45:16.670 UTC client backend[45990] pg_regress/tidrangescan LOG: connection ready: setup total=12.757 ms, fork=6.395 ms, authentication=0.153 ms 2025-11-30 18:45:16.670 UTC unrecognized[45997] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.671 UTC unrecognized[45992] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.671 UTC client backend[45997] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.671 UTC client backend[45997] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sysviews 2025-11-30 18:45:16.671 UTC unrecognized[45991] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.671 UTC client backend[45992] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.671 UTC client backend[45992] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/alter_operator 2025-11-30 18:45:16.671 UTC unrecognized[45993] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.671 UTC client backend[45991] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.671 UTC client backend[45991] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_table_like 2025-11-30 18:45:16.672 UTC client backend[45993] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.672 UTC client backend[45993] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tidscan 2025-11-30 18:45:16.672 UTC client backend[45997] pg_regress/sysviews LOG: connection ready: setup total=10.471 ms, fork=1.831 ms, authentication=0.112 ms 2025-11-30 18:45:16.672 UTC client backend[45991] pg_regress/create_table_like LOG: connection ready: setup total=14.870 ms, fork=8.188 ms, authentication=0.140 ms 2025-11-30 18:45:16.672 UTC client backend[45992] pg_regress/alter_operator LOG: connection ready: setup total=11.837 ms, fork=3.133 ms, authentication=0.157 ms 2025-11-30 18:45:16.672 UTC unrecognized[45994] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.673 UTC unrecognized[45999] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.673 UTC unrecognized[45996] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.673 UTC client backend[45993] pg_regress/tidscan LOG: connection ready: setup total=11.984 ms, fork=7.593 ms, authentication=0.112 ms 2025-11-30 18:45:16.673 UTC client backend[45994] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.673 UTC client backend[45994] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tsrf 2025-11-30 18:45:16.673 UTC client backend[45999] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.673 UTC client backend[45999] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.icu.utf8 2025-11-30 18:45:16.673 UTC client backend[45996] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.673 UTC client backend[45996] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/misc 2025-11-30 18:45:16.674 UTC client backend[45994] pg_regress/tsrf LOG: connection ready: setup total=12.757 ms, fork=4.714 ms, authentication=0.117 ms 2025-11-30 18:45:16.674 UTC client backend[45999] pg_regress/collate.icu.utf8 LOG: connection ready: setup total=7.280 ms, fork=4.901 ms, authentication=0.116 ms 2025-11-30 18:45:16.674 UTC unrecognized[46003] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.674 UTC client backend[45996] pg_regress/misc LOG: connection ready: setup total=12.712 ms, fork=5.433 ms, authentication=0.137 ms 2025-11-30 18:45:16.676 UTC unrecognized[46000] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.676 UTC unrecognized[45995] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.676 UTC unrecognized[46002] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.676 UTC unrecognized[45998] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.676 UTC client backend[45995] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.676 UTC client backend[45995] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/async 2025-11-30 18:45:16.677 UTC client backend[46002] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.677 UTC client backend[46002] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.utf8 2025-11-30 18:45:16.677 UTC client backend[45998] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.677 UTC client backend[45998] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tid 2025-11-30 18:45:16.677 UTC unrecognized[46005] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.677 UTC client backend[46005] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.677 UTC client backend[46005] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/without_overlaps 2025-11-30 18:45:16.677 UTC client backend[45995] pg_regress/async LOG: connection ready: setup total=16.102 ms, fork=7.154 ms, authentication=0.137 ms 2025-11-30 18:45:16.678 UTC client backend[45998] pg_regress/tid LOG: connection ready: setup total=11.432 ms, fork=7.719 ms, authentication=0.142 ms 2025-11-30 18:45:16.678 UTC client backend[46002] pg_regress/collate.utf8 LOG: connection ready: setup total=9.861 ms, fork=6.529 ms, authentication=0.169 ms 2025-11-30 18:45:16.678 UTC unrecognized[46001] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.678 UTC client backend[46003] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.678 UTC client backend[46003] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/merge 2025-11-30 18:45:16.678 UTC client backend[46001] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.678 UTC client backend[46001] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_role 2025-11-30 18:45:16.678 UTC client backend[46005] pg_regress/without_overlaps LOG: connection ready: setup total=8.308 ms, fork=1.756 ms, authentication=0.122 ms 2025-11-30 18:45:16.679 UTC client backend[46003] pg_regress/merge LOG: connection ready: setup total=10.064 ms, fork=2.845 ms, authentication=0.105 ms 2025-11-30 18:45:16.679 UTC client backend[46001] pg_regress/create_role LOG: connection ready: setup total=12.058 ms, fork=6.947 ms, authentication=0.135 ms 2025-11-30 18:45:16.679 UTC client backend[46000] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.679 UTC client backend[46000] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/misc_functions 2025-11-30 18:45:16.680 UTC client backend[46000] pg_regress/misc_functions LOG: connection ready: setup total=13.422 ms, fork=7.569 ms, authentication=0.145 ms 2025-11-30 18:45:16.683 UTC unrecognized[46004] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.683 UTC client backend[46004] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.683 UTC client backend[46004] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/dbsize 2025-11-30 18:45:16.684 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions must appear at top level of FROM at character 34 2025-11-30 18:45:16.684 UTC client backend[45994] pg_regress/tsrf STATEMENT: SELECT * FROM generate_series(1, generate_series(1, 3)); 2025-11-30 18:45:16.684 UTC client backend[46004] pg_regress/dbsize LOG: connection ready: setup total=14.863 ms, fork=9.752 ms, authentication=0.115 ms 2025-11-30 18:45:16.686 UTC unrecognized[46006] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.687 UTC client backend[46006] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.687 UTC client backend[46006] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/generated_virtual 2025-11-30 18:45:16.687 UTC client backend[45991] pg_regress/create_table_like ERROR: relation "nonexistent" does not exist at character 24 2025-11-30 18:45:16.687 UTC client backend[45991] pg_regress/create_table_like STATEMENT: CREATE TABLE foo (LIKE nonexistent); 2025-11-30 18:45:16.688 UTC client backend[46006] pg_regress/generated_virtual LOG: connection ready: setup total=12.869 ms, fork=5.331 ms, authentication=0.118 ms 2025-11-30 18:45:16.688 UTC client backend[45998] pg_regress/tid ERROR: invalid input syntax for type tid: "(4294967296,1)" at character 8 2025-11-30 18:45:16.688 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT '(4294967296,1)'::tid; 2025-11-30 18:45:16.688 UTC client backend[45998] pg_regress/tid ERROR: invalid input syntax for type tid: "(1,65536)" at character 8 2025-11-30 18:45:16.688 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT '(1,65536)'::tid; 2025-11-30 18:45:16.690 UTC unrecognized[46007] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.690 UTC client backend[46007] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.690 UTC client backend[46007] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/incremental_sort 2025-11-30 18:45:16.691 UTC client backend[46007] pg_regress/incremental_sort LOG: connection ready: setup total=15.581 ms, fork=6.416 ms, authentication=0.108 ms 2025-11-30 18:45:16.691 UTC client backend[45995] pg_regress/async ERROR: channel name cannot be empty 2025-11-30 18:45:16.691 UTC client backend[45995] pg_regress/async STATEMENT: SELECT pg_notify('','sample message1'); 2025-11-30 18:45:16.691 UTC client backend[46005] pg_regress/without_overlaps ERROR: constraint using WITHOUT OVERLAPS needs at least two columns 2025-11-30 18:45:16.691 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng ( valid_at daterange, CONSTRAINT temporal_rng_pk PRIMARY KEY (valid_at WITHOUT OVERLAPS) ); 2025-11-30 18:45:16.693 UTC client backend[45995] pg_regress/async ERROR: channel name cannot be empty 2025-11-30 18:45:16.693 UTC client backend[45995] pg_regress/async STATEMENT: SELECT pg_notify(NULL,'sample message1'); 2025-11-30 18:45:16.697 UTC client backend[45995] pg_regress/async ERROR: channel name too long 2025-11-30 18:45:16.697 UTC client backend[45995] pg_regress/async STATEMENT: SELECT pg_notify('notify_async_channel_name_too_long______________________________','sample_message1'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "1 AB" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize DETAIL: Invalid size unit: "AB". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 AB'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "1 AB A" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize DETAIL: Invalid size unit: "AB A". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 AB A'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "1 AB A " 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize DETAIL: Invalid size unit: "AB A". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 AB A '); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: bigint out of range 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('9223372036854775807.9'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: bigint out of range 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1e100'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: value overflows numeric format 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1e1000000000000000000'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "1 byte" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize DETAIL: Invalid size unit: "byte". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 byte'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes(''); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "kb" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('kb'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: ".." 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('..'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "-." 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('-.'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "-.kb" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('-.kb'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "-. kb" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('-. kb'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: ".+912" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('.+912'); 2025-11-30 18:45:16.698 UTC client backend[46000] pg_regress/misc_functions ERROR: function num_nonnulls() does not exist at character 8 2025-11-30 18:45:16.698 UTC client backend[46000] pg_regress/misc_functions DETAIL: No function of that name accepts the given number of arguments. 2025-11-30 18:45:16.698 UTC client backend[46000] pg_regress/misc_functions STATEMENT: SELECT num_nonnulls(); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "+912+ kB" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize DETAIL: Invalid size unit: "+ kB". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('+912+ kB'); 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize ERROR: invalid size: "++123 kB" 2025-11-30 18:45:16.698 UTC client backend[46004] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('++123 kB'); 2025-11-30 18:45:16.698 UTC client backend[46000] pg_regress/misc_functions ERROR: function num_nulls() does not exist at character 8 2025-11-30 18:45:16.698 UTC client backend[46000] pg_regress/misc_functions DETAIL: No function of that name accepts the given number of arguments. 2025-11-30 18:45:16.698 UTC client backend[46000] pg_regress/misc_functions STATEMENT: SELECT num_nulls(); 2025-11-30 18:45:16.699 UTC client backend[46000] pg_regress/misc_functions ERROR: null value not allowed 2025-11-30 18:45:16.699 UTC client backend[46000] pg_regress/misc_functions STATEMENT: SELECT error_on_null(NULL::int); 2025-11-30 18:45:16.699 UTC client backend[46000] pg_regress/misc_functions ERROR: null value not allowed 2025-11-30 18:45:16.699 UTC client backend[46000] pg_regress/misc_functions STATEMENT: SELECT error_on_null(NULL::int[]); 2025-11-30 18:45:16.699 UTC client backend[46005] pg_regress/without_overlaps ERROR: column "valid_at" named in key does not exist at character 45 2025-11-30 18:45:16.699 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng ( id INTEGER, CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS) ); 2025-11-30 18:45:16.699 UTC client backend[46005] pg_regress/without_overlaps ERROR: column "valid_at" in WITHOUT OVERLAPS is not a range or multirange type at character 64 2025-11-30 18:45:16.699 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng ( id int4range, valid_at TEXT, CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS) ); 2025-11-30 18:45:16.700 UTC client backend[45991] pg_regress/create_table_like ERROR: column "xx" specified more than once 2025-11-30 18:45:16.700 UTC client backend[45991] pg_regress/create_table_like STATEMENT: /* Has ee entry */ CREATE TABLE inhf (LIKE inhx, LIKE inhx); 2025-11-30 18:45:16.700 UTC client backend[46004] pg_regress/dbsize LOG: disconnection: session time: 0:00:00.021 user=postgres database=regression host=[local] 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 LOG: process 45961 avoided deadlock for AccessShareLock on relation 48217 of database 16387 by rearranging queue order after 16.828 ms 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 DETAIL: Process holding the lock: 45960. Wait queue: 45962, 45961. 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 CONTEXT: waiting for AccessShareLock on relation 48217 of database 16387 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 STATEMENT: LOCK TABLE a1 IN ACCESS SHARE MODE; 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 LOG: process 45961 still waiting for AccessShareLock on relation 48217 of database 16387 after 16.828 ms 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 DETAIL: Process holding the lock: 45960. Wait queue: 45962, 45961. 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 CONTEXT: waiting for AccessShareLock on relation 48217 of database 16387 2025-11-30 18:45:16.701 UTC client backend[45961] isolation/deadlock-soft/d2 STATEMENT: LOCK TABLE a1 IN ACCESS SHARE MODE; 2025-11-30 18:45:16.719 UTC client backend[46002] pg_regress/collate.utf8 ERROR: invalid locale name "C_UTF8" for builtin provider 2025-11-30 18:45:16.719 UTC client backend[46002] pg_regress/collate.utf8 STATEMENT: CREATE COLLATION regress_pg_c_utf8 ( provider = builtin, locale = 'C_UTF8'); 2025-11-30 18:45:16.722 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to create role 2025-11-30 18:45:16.722 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may create roles with the SUPERUSER attribute. 2025-11-30 18:45:16.722 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_superuser SUPERUSER; 2025-11-30 18:45:16.723 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to create role 2025-11-30 18:45:16.723 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the REPLICATION attribute may create roles with the REPLICATION attribute. 2025-11-30 18:45:16.723 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_replication_bypassrls REPLICATION BYPASSRLS; 2025-11-30 18:45:16.727 UTC client backend[45995] pg_regress/async LOG: disconnection: session time: 0:00:00.058 user=postgres database=regression host=[local] 2025-11-30 18:45:16.728 UTC client backend[45998] pg_regress/tid ERROR: tid (0, 1) is not valid for relation "tid_matview" 2025-11-30 18:45:16.728 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT currtid2('tid_matview'::text, '(0,1)'::tid); 2025-11-30 18:45:16.731 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to create role 2025-11-30 18:45:16.731 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the REPLICATION attribute may create roles with the REPLICATION attribute. 2025-11-30 18:45:16.731 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_replication REPLICATION; 2025-11-30 18:45:16.733 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions are not allowed in CASE at character 34 2025-11-30 18:45:16.733 UTC client backend[45994] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-11-30 18:45:16.733 UTC client backend[45994] pg_regress/tsrf STATEMENT: SELECT q1, case when q1 > 0 then generate_series(1,3) else 0 end FROM int8_tbl; 2025-11-30 18:45:16.735 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to create role 2025-11-30 18:45:16.735 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the BYPASSRLS attribute may create roles with the BYPASSRLS attribute. 2025-11-30 18:45:16.735 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_bypassrls BYPASSRLS; 2025-11-30 18:45:16.735 UTC client backend[45989] pg_regress/alter_generic ERROR: function alt_func1(integer) is not an aggregate 2025-11-30 18:45:16.735 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_func1(int) RENAME TO alt_func3; 2025-11-30 18:45:16.736 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions are not allowed in COALESCE at character 21 2025-11-30 18:45:16.736 UTC client backend[45994] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-11-30 18:45:16.736 UTC client backend[45994] pg_regress/tsrf STATEMENT: SELECT q1, coalesce(generate_series(1,3), 0) FROM int8_tbl; 2025-11-30 18:45:16.736 UTC unrecognized[46008] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.737 UTC client backend[46008] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.737 UTC client backend[46008] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:16.738 UTC client backend[46008] fdw_retry_check LOG: connection ready: setup total=8.486 ms, fork=3.371 ms, authentication=0.142 ms 2025-11-30 18:45:16.740 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to create role 2025-11-30 18:45:16.740 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the CREATEDB attribute may create roles with the CREATEDB attribute. 2025-11-30 18:45:16.740 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_createdb CREATEDB; 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: logging memory contexts of PID 46000 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 1; TopMemoryContext: 99488 total in 5 blocks; 1648 free (11 chunks); 97840 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Record information cache: 8192 total in 1 blocks; 1600 free (0 chunks); 6592 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Operator lookup cache: 24576 total in 2 blocks; 10776 free (3 chunks); 13800 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; CFuncHash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Rendezvous variable hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; search_path processing cache: 8192 total in 1 blocks; 5616 free (2 chunks); 2576 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; RowDescriptionContext: 8192 total in 1 blocks; 6912 free (0 chunks); 1280 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; MessageContext: 16384 total in 2 blocks; 5120 free (2 chunks); 11264 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Operator class cache: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; smgr relation table: 32768 total in 3 blocks; 16848 free (8 chunks); 15920 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref Hash: 9280 total in 2 blocks; 704 free (0 chunks); 8576 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref: 4096 total in 3 blocks; 336 free (3 chunks); 3760 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PgStat Pending: 16384 total in 5 blocks; 7552 free (8 chunks); 8832 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; TopTransactionContext: 8192 total in 1 blocks; 7760 free (1 chunks); 432 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; TransactionAbortContext: 32768 total in 1 blocks; 32528 free (0 chunks); 240 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Portal hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; TopPortalContext: 8192 total in 1 blocks; 7680 free (0 chunks); 512 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; PortalContext: 1024 total in 1 blocks; 616 free (0 chunks); 408 used: 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 4; ExecutorState: 8192 total in 1 blocks; 3560 free (0 chunks); 4632 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 5; printtup: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 5; ExprContext: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Relcache by OID: 16384 total in 2 blocks; 7688 free (2 chunks); 8696 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; CacheMemoryContext: 524288 total in 7 blocks; 235672 free (16 chunks); 288616 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; Cached function hash: 8192 total in 1 blocks; 1600 free (0 chunks); 6592 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; Cached function hash: 24496 total in 2 blocks; 2640 free (0 chunks); 21856 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; EventTriggerCache: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 4; EventTriggerCacheHash: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_index_indexrelid_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_opclass_oid_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_trigger_tgrelid_tgname_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_rewrite_rel_rulename_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_class_oid_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_attribute_relid_attnum_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 816 free (2 chunks); 2448 used: pg_amproc_fam_proc_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_oid_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1088 free (2 chunks); 1984 used: pg_auth_members_member_role_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_shseclabel_object_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_datname_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_oid_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_rolname_index 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; LOCALLOCK hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; WAL record construction: 50216 total in 2 blocks; 6384 free (0 chunks); 43832 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PrivateRefCount: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; MdSmgr: 8192 total in 1 blocks; 7904 free (2 chunks); 288 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; GUCMemoryContext: 40960 total in 3 blocks; 25496 free (13 chunks); 15464 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; GUC hash table: 32768 total in 3 blocks; 7424 free (6 chunks); 25344 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Timezones: 104128 total in 2 blocks; 2640 free (0 chunks); 101488 used 2025-11-30 18:45:16.741 UTC client backend[45994] pg_regress/tsrf ERROR: aggregate function calls cannot contain set-returning function calls at character 12 2025-11-30 18:45:16.741 UTC client backend[45994] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-11-30 18:45:16.741 UTC client backend[45994] pg_regress/tsrf STATEMENT: SELECT min(generate_series(1, 3)) FROM few; 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.741 UTC client backend[46000] pg_regress/misc_functions LOG: Grand total: 1218616 bytes in 91 blocks; 457272 free (104 chunks); 761344 used 2025-11-30 18:45:16.742 UTC client backend[45991] pg_regress/create_table_like ERROR: new row for relation "inhg" violates check constraint "foo" 2025-11-30 18:45:16.742 UTC client backend[45991] pg_regress/create_table_like DETAIL: Failing row contains (x, foo, y). 2025-11-30 18:45:16.742 UTC client backend[45991] pg_regress/create_table_like STATEMENT: /* Succeeds -- Unique constraints not copied */ INSERT INTO inhg VALUES ('x', 'foo', 'y'); 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: logging memory contexts of PID 43405 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 1; TopMemoryContext: 61608 total in 3 blocks; 5072 free (0 chunks); 56536 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; smgr relation table: 524288 total in 7 blocks; 199744 free (24 chunks); 324544 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; Checkpointer: 32768 total in 3 blocks; 32448 free (21 chunks); 320 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; LOCALLOCK hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; WAL record construction: 50216 total in 2 blocks; 6384 free (0 chunks); 43832 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; PrivateRefCount: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; MdSmgr: 131072 total in 5 blocks; 130672 free (3350 chunks); 400 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; Pending ops context: 278592 total in 7 blocks; 195336 free (2224 chunks); 83256 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 3; Pending Ops Table: 2097152 total in 9 blocks; 1032448 free (34 chunks); 1064704 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; GUCMemoryContext: 24576 total in 2 blocks; 11464 free (12 chunks); 13112 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 3; GUC hash table: 32768 total in 3 blocks; 7424 free (6 chunks); 25344 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; Timezones: 104128 total in 2 blocks; 2640 free (0 chunks); 101488 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.746 UTC checkpointer[43405] LOG: Grand total: 3361744 bytes in 46 blocks; 1634800 free (5671 chunks); 1726944 used 2025-11-30 18:45:16.747 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to alter role 2025-11-30 18:45:16.747 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may change the SUPERUSER attribute. 2025-11-30 18:45:16.747 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited SUPERUSER; 2025-11-30 18:45:16.748 UTC client backend[45989] pg_regress/alter_generic ERROR: function alt_func1(integer) is not an aggregate 2025-11-30 18:45:16.748 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_func1(int) OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.748 UTC client backend[45992] pg_regress/alter_operator ERROR: function non_existent_func(internal, oid, internal, integer) does not exist 2025-11-30 18:45:16.748 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, boolean) SET (RESTRICT = non_existent_func); 2025-11-30 18:45:16.752 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "RANDOMWORD" at character 21 2025-11-30 18:45:16.752 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t RANDOMWORD USING source AS s ON t.tid = s.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-11-30 18:45:16.752 UTC client backend[45989] pg_regress/alter_generic ERROR: function alt_func1(integer) is not an aggregate 2025-11-30 18:45:16.752 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_func1(int) SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.753 UTC client backend[45994] pg_regress/tsrf ERROR: window function calls cannot contain set-returning function calls at character 12 2025-11-30 18:45:16.753 UTC client backend[45994] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-11-30 18:45:16.753 UTC client backend[45994] pg_regress/tsrf STATEMENT: SELECT min(generate_series(1, 3)) OVER() FROM few; 2025-11-30 18:45:16.753 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to alter role 2025-11-30 18:45:16.753 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the REPLICATION attribute may change the REPLICATION attribute. 2025-11-30 18:45:16.753 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited REPLICATION; 2025-11-30 18:45:16.755 UTC client backend[45992] pg_regress/alter_operator ERROR: function non_existent_func(internal, oid, internal, smallint, internal) does not exist 2025-11-30 18:45:16.755 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, boolean) SET (JOIN = non_existent_func); 2025-11-30 18:45:16.755 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "INSERT" at character 75 2025-11-30 18:45:16.755 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN INSERT DEFAULT VALUES; 2025-11-30 18:45:16.756 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "INSERT" at character 89 2025-11-30 18:45:16.756 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED BY SOURCE THEN INSERT DEFAULT VALUES; 2025-11-30 18:45:16.758 UTC client backend[45992] pg_regress/alter_operator ERROR: operator attribute "Restrict" not recognized 2025-11-30 18:45:16.758 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR & (bit, bit) SET ("Restrict" = _int_contsel, "Join" = _int_contjoinsel); 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: logging memory contexts of PID 46000 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 1; TopMemoryContext: 132256 total in 6 blocks; 34296 free (17 chunks); 97960 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Map from relid to OID of cached composite type: 8192 total in 1 blocks; 2512 free (0 chunks); 5680 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Type information cache: 24640 total in 2 blocks; 2640 free (0 chunks); 22000 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Record information cache: 8192 total in 1 blocks; 1600 free (0 chunks); 6592 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Operator lookup cache: 24576 total in 2 blocks; 10776 free (3 chunks); 13800 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; CFuncHash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Rendezvous variable hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; search_path processing cache: 8192 total in 1 blocks; 5424 free (13 chunks); 2768 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; RowDescriptionContext: 8192 total in 1 blocks; 6912 free (0 chunks); 1280 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; MessageContext: 16384 total in 2 blocks; 5200 free (2 chunks); 11184 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Operator class cache: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; smgr relation table: 32768 total in 3 blocks; 16848 free (8 chunks); 15920 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref Hash: 9280 total in 2 blocks; 704 free (0 chunks); 8576 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref: 8192 total in 4 blocks; 2952 free (2 chunks); 5240 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PgStat Pending: 24576 total in 6 blocks; 9448 free (11 chunks); 15128 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; TopTransactionContext: 8192 total in 1 blocks; 7760 free (1 chunks); 432 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; TransactionAbortContext: 32768 total in 1 blocks; 32528 free (0 chunks); 240 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Portal hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; TopPortalContext: 8192 total in 1 blocks; 7680 free (0 chunks); 512 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; PortalContext: 1024 total in 1 blocks; 616 free (0 chunks); 408 used: 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 4; ExecutorState: 8192 total in 1 blocks; 3560 free (0 chunks); 4632 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 5; printtup: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 5; ExprContext: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Relcache by OID: 16384 total in 2 blocks; 7688 free (2 chunks); 8696 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; CacheMemoryContext: 524288 total in 7 blocks; 167904 free (19 chunks); 356384 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; Cached function hash: 8192 total in 1 blocks; 1600 free (0 chunks); 6592 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; Cached function hash: 24496 total in 2 blocks; 2640 free (0 chunks); 21856 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; EventTriggerCache: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 4; EventTriggerCacheHash: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_index_indexrelid_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_opclass_oid_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_trigger_tgrelid_tgname_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1064 free (2 chunks); 2008 used: pg_rewrite_rel_rulename_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_class_oid_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_attribute_relid_attnum_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 736 free (2 chunks); 2528 used: pg_amproc_fam_proc_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_oid_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 928 free (1 chunks); 2144 used: pg_auth_members_member_role_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_shseclabel_object_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_datname_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_oid_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_rolname_index 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; LOCALLOCK hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; WAL record construction: 50216 total in 2 blocks; 6384 free (0 chunks); 43832 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; PrivateRefCount: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; MdSmgr: 8192 total in 1 blocks; 7736 free (2 chunks); 456 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; GUCMemoryContext: 40960 total in 3 blocks; 25424 free (13 chunks); 15536 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 3; GUC hash table: 32768 total in 3 blocks; 7424 free (6 chunks); 25344 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; Timezones: 104128 total in 2 blocks; 2640 free (0 chunks); 101488 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-11-30 18:45:16.759 UTC client backend[46000] pg_regress/misc_functions LOG: Grand total: 1296504 bytes in 97 blocks; 431064 free (124 chunks); 865440 used 2025-11-30 18:45:16.759 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "INTO" at character 86 2025-11-30 18:45:16.759 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT INTO target DEFAULT VALUES; 2025-11-30 18:45:16.759 UTC client backend[45998] pg_regress/tid ERROR: cannot open relation "tid_ind" 2025-11-30 18:45:16.759 UTC client backend[45998] pg_regress/tid DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:16.759 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT currtid2('tid_ind'::text, '(0,1)'::tid); 2025-11-30 18:45:16.759 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "," at character 98 2025-11-30 18:45:16.759 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT VALUES (1,1), (2,2); 2025-11-30 18:45:16.760 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "SELECT" at character 86 2025-11-30 18:45:16.760 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT SELECT (1, 1); 2025-11-30 18:45:16.761 UTC client backend[45989] pg_regress/alter_generic ERROR: function alt_func2(integer) already exists in schema "alt_nsp1" 2025-11-30 18:45:16.761 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func1(int) RENAME TO alt_func2; 2025-11-30 18:45:16.762 UTC client backend[45961] isolation/deadlock-soft/d2 LOG: process 45961 acquired AccessShareLock on relation 48217 of database 16387 after 77.470 ms 2025-11-30 18:45:16.762 UTC client backend[45961] isolation/deadlock-soft/d2 CONTEXT: waiting for AccessShareLock on relation 48217 of database 16387 2025-11-30 18:45:16.762 UTC client backend[45961] isolation/deadlock-soft/d2 STATEMENT: LOCK TABLE a1 IN ACCESS SHARE MODE; 2025-11-30 18:45:16.762 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "UPDATE" at character 79 2025-11-30 18:45:16.762 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN UPDATE SET balance = 0; 2025-11-30 18:45:16.765 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:16.765 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func2(int) OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.766 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation "ja_JP.eucjp-x-icu" for encoding "UTF8" does not exist at character 56 2025-11-30 18:45:16.766 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int, b text COLLATE "ja_JP.eucjp-x-icu" ); 2025-11-30 18:45:16.766 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "UPDATE" at character 89 2025-11-30 18:45:16.766 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED BY TARGET THEN UPDATE SET balance = 0; 2025-11-30 18:45:16.768 UTC client backend[45998] pg_regress/tid ERROR: cannot look at latest visible tid for relation "public.tid_part" 2025-11-30 18:45:16.768 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT currtid2('tid_part'::text, '(0,1)'::tid); 2025-11-30 18:45:16.768 UTC client backend[46003] pg_regress/merge ERROR: syntax error at or near "target" at character 82 2025-11-30 18:45:16.768 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN UPDATE target SET balance = 0; 2025-11-30 18:45:16.768 UTC client backend[46003] pg_regress/merge ERROR: name "target" specified more than once 2025-11-30 18:45:16.768 UTC client backend[46003] pg_regress/merge DETAIL: The name is used both as MERGE target table and data source. 2025-11-30 18:45:16.768 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target USING target ON tid = tid WHEN MATCHED THEN DO NOTHING; 2025-11-30 18:45:16.769 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to alter role 2025-11-30 18:45:16.769 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the CREATEDB attribute may change the CREATEDB attribute. 2025-11-30 18:45:16.769 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited CREATEDB; 2025-11-30 18:45:16.770 UTC client backend[46003] pg_regress/merge ERROR: WITH query "foo" does not have a RETURNING clause at character 101 2025-11-30 18:45:16.770 UTC client backend[46003] pg_regress/merge STATEMENT: WITH foo AS ( MERGE INTO target USING source ON (true) WHEN MATCHED THEN DELETE ) SELECT * FROM foo; 2025-11-30 18:45:16.770 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation "foo-x-icu" for encoding "UTF8" does not exist at character 56 2025-11-30 18:45:16.770 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int, b text COLLATE "foo-x-icu" ); 2025-11-30 18:45:16.770 UTC client backend[45992] pg_regress/alter_operator ERROR: must be owner of operator === 2025-11-30 18:45:16.770 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, boolean) SET (RESTRICT = NONE); 2025-11-30 18:45:16.771 UTC client backend[46003] pg_regress/merge ERROR: COPY query must have a RETURNING clause 2025-11-30 18:45:16.771 UTC client backend[46003] pg_regress/merge STATEMENT: COPY ( MERGE INTO target USING source ON (true) WHEN MATCHED THEN DELETE ) TO stdout; 2025-11-30 18:45:16.772 UTC client backend[45998] pg_regress/tid ERROR: currtid cannot handle views with no CTID 2025-11-30 18:45:16.772 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT currtid2('tid_view_no_ctid'::text, '(0,1)'::tid); 2025-11-30 18:45:16.772 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to alter role 2025-11-30 18:45:16.772 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the BYPASSRLS attribute may change the BYPASSRLS attribute. 2025-11-30 18:45:16.772 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited BYPASSRLS; 2025-11-30 18:45:16.773 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer at character 44 2025-11-30 18:45:16.773 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int COLLATE "en-x-icu", b text ); 2025-11-30 18:45:16.776 UTC client backend[46003] pg_regress/merge ERROR: cannot execute MERGE on relation "mv" 2025-11-30 18:45:16.776 UTC client backend[46003] pg_regress/merge DETAIL: This operation is not supported for materialized views. 2025-11-30 18:45:16.776 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO mv t USING source s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT DEFAULT VALUES; 2025-11-30 18:45:16.776 UTC client backend[45989] pg_regress/alter_generic ERROR: function alt_agg2(integer) already exists in schema "alt_nsp1" 2025-11-30 18:45:16.776 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg1(int) RENAME TO alt_agg2; 2025-11-30 18:45:16.779 UTC client backend[45997] pg_regress/sysviews LOG: disconnection: session time: 0:00:00.115 user=postgres database=regression host=[local] 2025-11-30 18:45:16.780 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:16.780 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg2(int) OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.781 UTC client backend[45993] pg_regress/tidscan ERROR: cursor "c" is not positioned on a row 2025-11-30 18:45:16.781 UTC client backend[45993] pg_regress/tidscan STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF, BUFFERS OFF) UPDATE tidscan SET id = -id WHERE CURRENT OF c RETURNING *; 2025-11-30 18:45:16.784 UTC client backend[45998] pg_regress/tid ERROR: tid (0, 1) is not valid for relation "tid_tab" 2025-11-30 18:45:16.784 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT currtid2('tid_view_with_ctid'::text, '(0,1)'::tid); 2025-11-30 18:45:16.785 UTC client backend[46003] pg_regress/merge ERROR: permission denied for table target 2025-11-30 18:45:16.785 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target USING (SELECT 1) ON true WHEN MATCHED THEN DO NOTHING; 2025-11-30 18:45:16.786 UTC client backend[45959] isolation/deadlock-soft/control connection LOG: disconnection: session time: 0:00:00.187 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.786 UTC client backend[46000] pg_regress/misc_functions ERROR: could not open file "does not exist" for reading: No such file or directory 2025-11-30 18:45:16.786 UTC client backend[46000] pg_regress/misc_functions STATEMENT: select pg_read_file('does not exist'); 2025-11-30 18:45:16.789 UTC client backend[45960] isolation/deadlock-soft/d1 LOG: disconnection: session time: 0:00:00.187 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.792 UTC client backend[45961] isolation/deadlock-soft/d2 LOG: disconnection: session time: 0:00:00.188 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.792 UTC client backend[46003] pg_regress/merge ERROR: permission denied for table source2 2025-11-30 18:45:16.792 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target USING source2 ON target.tid = source2.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-11-30 18:45:16.792 UTC client backend[46000] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-11-30 18:45:16.792 UTC client backend[46000] pg_regress/misc_functions STATEMENT: select pg_read_file('does not exist', 0, -1); 2025-11-30 18:45:16.795 UTC client backend[45962] isolation/deadlock-soft/e1 LOG: disconnection: session time: 0:00:00.188 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.795 UTC client backend[46000] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-11-30 18:45:16.795 UTC client backend[46000] pg_regress/misc_functions STATEMENT: select pg_read_file('does not exist', 0, -1, true); 2025-11-30 18:45:16.797 UTC client backend[45963] isolation/deadlock-soft/e2 LOG: disconnection: session time: 0:00:00.188 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:16.798 UTC unrecognized[46009] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.800 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of function alt_func3 2025-11-30 18:45:16.800 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func3(int) RENAME TO alt_func4; 2025-11-30 18:45:16.800 UTC client backend[45998] pg_regress/tid ERROR: ctid isn't of type TID 2025-11-30 18:45:16.800 UTC client backend[45998] pg_regress/tid STATEMENT: SELECT currtid2('tid_view_fake_ctid'::text, '(0,1)'::tid); 2025-11-30 18:45:16.803 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of function alt_func3 2025-11-30 18:45:16.803 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func3(int) OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.804 UTC client backend[46003] pg_regress/merge ERROR: permission denied for table target 2025-11-30 18:45:16.804 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target USING source2 ON target.tid = source2.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-11-30 18:45:16.804 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:16.804 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func2(int) OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.804 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to alter role 2025-11-30 18:45:16.804 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may change the SUPERUSER attribute. 2025-11-30 18:45:16.804 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_createdb SUPERUSER; 2025-11-30 18:45:16.805 UTC client backend[45998] pg_regress/tid LOG: disconnection: session time: 0:00:00.131 user=postgres database=regression host=[local] 2025-11-30 18:45:16.806 UTC client backend[46000] pg_regress/misc_functions ERROR: could not open file "does not exist" for reading: No such file or directory 2025-11-30 18:45:16.806 UTC client backend[46000] pg_regress/misc_functions STATEMENT: select pg_read_binary_file('does not exist'); 2025-11-30 18:45:16.806 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions are not allowed in UPDATE at character 27 2025-11-30 18:45:16.806 UTC client backend[45994] pg_regress/tsrf STATEMENT: UPDATE fewmore SET data = generate_series(4,9); 2025-11-30 18:45:16.807 UTC client backend[46006] pg_regress/generated_virtual ERROR: multiple generation clauses specified for column "b" of table "gtest_err_1" at character 88 2025-11-30 18:45:16.807 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_1 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL GENERATED ALWAYS AS (a * 3) VIRTUAL); 2025-11-30 18:45:16.807 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to alter role 2025-11-30 18:45:16.807 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may change the SUPERUSER attribute. 2025-11-30 18:45:16.807 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_createdb NOSUPERUSER; 2025-11-30 18:45:16.808 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column "b" in column generation expression at character 74 2025-11-30 18:45:16.808 UTC client backend[46006] pg_regress/generated_virtual DETAIL: A generated column cannot reference another generated column. 2025-11-30 18:45:16.808 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_2a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (b * 2) VIRTUAL); 2025-11-30 18:45:16.808 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions are not allowed in RETURNING at character 41 2025-11-30 18:45:16.808 UTC client backend[45994] pg_regress/tsrf STATEMENT: INSERT INTO fewmore VALUES(1) RETURNING generate_series(1,3); 2025-11-30 18:45:16.808 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of function alt_func3 2025-11-30 18:45:16.808 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func3(int) SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.809 UTC client backend[46003] pg_regress/merge ERROR: permission denied for table target2 2025-11-30 18:45:16.809 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target2 USING source ON target2.tid = source.sid WHEN MATCHED THEN DELETE; 2025-11-30 18:45:16.809 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column "b" in column generation expression at character 117 2025-11-30 18:45:16.809 UTC client backend[46006] pg_regress/generated_virtual DETAIL: A generated column cannot reference another generated column. 2025-11-30 18:45:16.809 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_2b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL, c int GENERATED ALWAYS AS (b * 3) VIRTUAL); 2025-11-30 18:45:16.810 UTC client backend[46000] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-11-30 18:45:16.810 UTC client backend[46000] pg_regress/misc_functions STATEMENT: select pg_read_binary_file('does not exist', 0, -1); 2025-11-30 18:45:16.811 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use whole-row variable in column generation expression at character 88 2025-11-30 18:45:16.811 UTC client backend[46006] pg_regress/generated_virtual DETAIL: This would cause the generated column to depend on its own value. 2025-11-30 18:45:16.811 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_2c (a int PRIMARY KEY, b int GENERATED ALWAYS AS (num_nulls(gtest_err_2c)) VIRTUAL); 2025-11-30 18:45:16.811 UTC client backend[46003] pg_regress/merge ERROR: permission denied for table target2 2025-11-30 18:45:16.811 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target2 USING source ON target2.tid = source.sid WHEN NOT MATCHED THEN INSERT DEFAULT VALUES; 2025-11-30 18:45:16.811 UTC client backend[45992] pg_regress/alter_operator ERROR: operator cannot be its own negator 2025-11-30 18:45:16.811 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (NEGATOR = ===); 2025-11-30 18:45:16.811 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions are not allowed in VALUES at character 11 2025-11-30 18:45:16.811 UTC client backend[45994] pg_regress/tsrf STATEMENT: VALUES(1, generate_series(1,2)); 2025-11-30 18:45:16.812 UTC client backend[46000] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-11-30 18:45:16.812 UTC client backend[46000] pg_regress/misc_functions STATEMENT: select pg_read_binary_file('does not exist', 0, -1, true); 2025-11-30 18:45:16.812 UTC client backend[46003] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 55 2025-11-30 18:45:16.812 UTC client backend[46003] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-11-30 18:45:16.812 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING (SELECT * FROM source WHERE t.tid > sid) s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT DEFAULT VALUES; 2025-11-30 18:45:16.812 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions must appear at top level of FROM at character 23 2025-11-30 18:45:16.812 UTC client backend[45994] pg_regress/tsrf STATEMENT: SELECT * FROM int4mul(generate_series(1,2), 10); 2025-11-30 18:45:16.814 UTC client backend[45989] pg_regress/alter_generic ERROR: function alt_func2(integer) already exists in schema "alt_nsp2" 2025-11-30 18:45:16.814 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func2(int) SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.816 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of function alt_agg3 2025-11-30 18:45:16.816 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg3(int) RENAME TO alt_agg4; 2025-11-30 18:45:16.816 UTC client backend[46000] pg_regress/misc_functions ERROR: could not open directory "does not exist": No such file or directory 2025-11-30 18:45:16.816 UTC client backend[46000] pg_regress/misc_functions STATEMENT: select pg_ls_dir('does not exist', false, false); 2025-11-30 18:45:16.816 UTC unrecognized[46012] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.816 UTC client backend[45991] pg_regress/create_table_like ERROR: null value in column "a" of relation "test_like_id_2" violates not-null constraint 2025-11-30 18:45:16.816 UTC client backend[45991] pg_regress/create_table_like DETAIL: Failing row contains (null, b2). 2025-11-30 18:45:16.816 UTC client backend[45991] pg_regress/create_table_like STATEMENT: INSERT INTO test_like_id_2 (b) VALUES ('b2'); 2025-11-30 18:45:16.816 UTC client backend[46009] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.816 UTC client backend[46009] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_692c90b2.ae34 2025-11-30 18:45:16.816 UTC client backend[46012] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.816 UTC client backend[46012] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft-2 2025-11-30 18:45:16.817 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "c" does not exist at character 73 2025-11-30 18:45:16.817 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_3 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (c * 2) VIRTUAL); 2025-11-30 18:45:16.817 UTC client backend[46009] fdw_692c90b2.ae34 LOG: connection ready: setup total=24.139 ms, fork=3.795 ms, authentication=0.671 ms 2025-11-30 18:45:16.817 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of function alt_agg3 2025-11-30 18:45:16.817 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg3(int) OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.817 UTC client backend[46012] isolation/deadlock-soft-2 LOG: connection ready: setup total=2.781 ms, fork=0.654 ms, authentication=0.110 ms 2025-11-30 18:45:16.817 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:16.817 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg2(int) OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.819 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of function alt_agg3 2025-11-30 18:45:16.819 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg3(int) SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.820 UTC client backend[45993] pg_regress/tidscan LOG: disconnection: session time: 0:00:00.151 user=postgres database=regression host=[local] 2025-11-30 18:45:16.820 UTC client backend[45989] pg_regress/alter_generic ERROR: function alt_agg2(integer) already exists in schema "alt_nsp2" 2025-11-30 18:45:16.820 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg2(int) SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.821 UTC client backend[45994] pg_regress/tsrf ERROR: set-returning functions are not allowed in LIMIT at character 16 2025-11-30 18:45:16.821 UTC client backend[45994] pg_regress/tsrf STATEMENT: SELECT 1 LIMIT generate_series(1,3); 2025-11-30 18:45:16.823 UTC unrecognized[46013] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.824 UTC client backend[46013] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.824 UTC client backend[46013] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft-2 2025-11-30 18:45:16.825 UTC client backend[46013] isolation/deadlock-soft-2 LOG: connection ready: setup total=5.638 ms, fork=2.272 ms, authentication=1.124 ms 2025-11-30 18:45:16.830 UTC unrecognized[46014] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.830 UTC client backend[46014] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.830 UTC client backend[46014] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft-2 2025-11-30 18:45:16.831 UTC client backend[46014] isolation/deadlock-soft-2 LOG: connection ready: setup total=3.516 ms, fork=1.200 ms, authentication=0.108 ms 2025-11-30 18:45:16.832 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "regress_role_super" 2025-11-30 18:45:16.832 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may grant roles with the SUPERUSER attribute. 2025-11-30 18:45:16.832 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_super IN ROLE regress_role_super; 2025-11-30 18:45:16.834 UTC client backend[46006] pg_regress/generated_virtual ERROR: generation expression is not immutable 2025-11-30 18:45:16.834 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_4 (a int PRIMARY KEY, b double precision GENERATED ALWAYS AS (random()) VIRTUAL); 2025-11-30 18:45:16.836 UTC client backend[46001] pg_regress/create_role ERROR: role "pg_database_owner" cannot have explicit members 2025-11-30 18:45:16.836 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_dbowner IN ROLE pg_database_owner; 2025-11-30 18:45:16.836 UTC unrecognized[46016] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.837 UTC client backend[46016] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.837 UTC client backend[46016] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft-2 2025-11-30 18:45:16.838 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_recursive" is a member of role "regress_nosuch_recursive" 2025-11-30 18:45:16.838 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_recursive ROLE regress_nosuch_recursive; 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator ERROR: operator attribute "commutator" cannot be changed if it has already been set 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (COMMUTATOR = @=); 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator ERROR: operator attribute "negator" cannot be changed if it has already been set 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (NEGATOR = @!=); 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator ERROR: operator attribute "merges" cannot be changed if it has already been set 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (MERGES = false); 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator ERROR: operator attribute "hashes" cannot be changed if it has already been set 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (HASHES = false); 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator ERROR: commutator operator === is already the commutator of operator ==== 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR @=(real, boolean) SET (COMMUTATOR = ===); 2025-11-30 18:45:16.840 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_admin_recursive" is a member of role "regress_nosuch_admin_recursive" 2025-11-30 18:45:16.840 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_admin_recursive ADMIN regress_nosuch_admin_recursive; 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator ERROR: negator operator === is already the negator of operator !==== 2025-11-30 18:45:16.840 UTC client backend[45992] pg_regress/alter_operator STATEMENT: ALTER OPERATOR @!=(boolean, real) SET (NEGATOR = ===); 2025-11-30 18:45:16.841 UTC client backend[46016] isolation/deadlock-soft-2 LOG: connection ready: setup total=5.504 ms, fork=0.634 ms, authentication=0.122 ms 2025-11-30 18:45:16.843 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to create database 2025-11-30 18:45:16.843 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE DATABASE regress_nosuch_db; 2025-11-30 18:45:16.844 UTC unrecognized[46017] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:16.844 UTC client backend[46017] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:16.844 UTC client backend[46017] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-soft-2 2025-11-30 18:45:16.845 UTC client backend[45992] pg_regress/alter_operator LOG: disconnection: session time: 0:00:00.180 user=postgres database=regression host=[local] 2025-11-30 18:45:16.845 UTC client backend[46017] isolation/deadlock-soft-2 LOG: connection ready: setup total=2.969 ms, fork=1.098 ms, authentication=0.138 ms 2025-11-30 18:45:16.847 UTC client backend[45994] pg_regress/tsrf LOG: disconnection: session time: 0:00:00.181 user=postgres database=regression host=[local] 2025-11-30 18:45:16.848 UTC client backend[46002] pg_regress/collate.utf8 ERROR: invalid locale name "unicode" for builtin provider 2025-11-30 18:45:16.848 UTC client backend[46002] pg_regress/collate.utf8 STATEMENT: CREATE COLLATION regress_pg_unicode_fast ( provider = builtin, locale = 'unicode'); 2025-11-30 18:45:16.848 UTC client backend[45989] pg_regress/alter_generic ERROR: conversion "alt_conv2" already exists in schema "alt_nsp1" 2025-11-30 18:45:16.848 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv1 RENAME TO alt_conv2; 2025-11-30 18:45:16.851 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation mismatch between explicit collations "C" and "en-x-icu" at character 58 2025-11-30 18:45:16.851 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT * FROM collate_test1 WHERE b COLLATE "C" >= 'bbc' COLLATE "en-x-icu"; 2025-11-30 18:45:16.851 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:16.851 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv2 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role ERROR: permission denied 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role DETAIL: The current user must have the ADMIN option on role "regress_role_normal". 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role STATEMENT: COMMENT ON ROLE regress_role_normal IS 'some comment'; 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to rename role 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "regress_role_normal" may rename this role. 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_normal RENAME TO regress_role_abnormal; 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to alter role 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "regress_role_normal" may alter this role. 2025-11-30 18:45:16.851 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_normal NOINHERIT NOLOGIN CONNECTION LIMIT 7; 2025-11-30 18:45:16.853 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer at character 31 2025-11-30 18:45:16.853 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE DOMAIN testdomain_i AS int COLLATE "sv-x-icu"; 2025-11-30 18:45:16.853 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of conversion alt_conv3 2025-11-30 18:45:16.853 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv3 RENAME TO alt_conv4; 2025-11-30 18:45:16.854 UTC client backend[46006] pg_regress/generated_virtual ERROR: both default and generation expression specified for column "b" of table "gtest_err_5a" at character 63 2025-11-30 18:45:16.854 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_5a (a int PRIMARY KEY, b int DEFAULT 5 GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-11-30 18:45:16.855 UTC client backend[46006] pg_regress/generated_virtual ERROR: both identity and generation expression specified for column "b" of table "gtest_err_5b" at character 82 2025-11-30 18:45:16.855 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_5b (a int PRIMARY KEY, b int GENERATED ALWAYS AS identity GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-11-30 18:45:16.858 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use system column "xmin" in column generation expression at character 75 2025-11-30 18:45:16.858 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_6a (a int PRIMARY KEY, b bool GENERATED ALWAYS AS (xmin <> 37) VIRTUAL); 2025-11-30 18:45:16.859 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of conversion alt_conv3 2025-11-30 18:45:16.859 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv3 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.860 UTC client backend[46001] pg_regress/create_role ERROR: must be owner of index tenant_idx 2025-11-30 18:45:16.860 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP INDEX tenant_idx; 2025-11-30 18:45:16.863 UTC client backend[46001] pg_regress/create_role ERROR: must be owner of table tenant_table 2025-11-30 18:45:16.863 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER TABLE tenant_table ADD COLUMN t text; 2025-11-30 18:45:16.863 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:16.863 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv2 OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role ERROR: must be owner of table tenant_table 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP TABLE tenant_table; 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role ERROR: must be owner of view tenant_view 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER VIEW tenant_view OWNER TO regress_role_admin; 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role ERROR: must be owner of view tenant_view 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP VIEW tenant_view; 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role ERROR: must be able to SET ROLE "regress_tenant" 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE SCHEMA regress_tenant_schema AUTHORIZATION regress_tenant; 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to reassign objects 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with privileges of role "regress_tenant" may reassign objects owned by it. 2025-11-30 18:45:16.864 UTC client backend[46001] pg_regress/create_role STATEMENT: REASSIGN OWNED BY regress_tenant TO regress_createrole; 2025-11-30 18:45:16.866 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of conversion alt_conv3 2025-11-30 18:45:16.866 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv3 SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.867 UTC client backend[46001] pg_regress/create_role ERROR: must be owner of table tenant2_table 2025-11-30 18:45:16.867 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER TABLE tenant2_table OWNER TO regress_createrole; 2025-11-30 18:45:16.868 UTC client backend[46001] pg_regress/create_role ERROR: must be able to SET ROLE "regress_tenant2" 2025-11-30 18:45:16.868 UTC client backend[46001] pg_regress/create_role STATEMENT: ALTER TABLE tenant2_table OWNER TO regress_tenant2; 2025-11-30 18:45:16.868 UTC client backend[45989] pg_regress/alter_generic ERROR: conversion "alt_conv2" already exists in schema "alt_nsp2" 2025-11-30 18:45:16.868 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv2 SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.869 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_read_all_data" 2025-11-30 18:45:16.869 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_all_data" may grant this role. 2025-11-30 18:45:16.869 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_all_data IN ROLE pg_read_all_data; 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_write_all_data" 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_write_all_data" may grant this role. 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_write_all_data IN ROLE pg_write_all_data; 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_monitor" 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_monitor" may grant this role. 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_monitor IN ROLE pg_monitor; 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_read_all_settings" 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_all_settings" may grant this role. 2025-11-30 18:45:16.870 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_all_settings IN ROLE pg_read_all_settings; 2025-11-30 18:45:16.871 UTC client backend[46006] pg_regress/generated_virtual ERROR: aggregate functions are not allowed in column generation expressions at character 74 2025-11-30 18:45:16.871 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (avg(a)) VIRTUAL); 2025-11-30 18:45:16.871 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_read_all_stats" 2025-11-30 18:45:16.871 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_all_stats" may grant this role. 2025-11-30 18:45:16.871 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_all_stats IN ROLE pg_read_all_stats; 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_stat_scan_tables" 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_stat_scan_tables" may grant this role. 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_stat_scan_tables IN ROLE pg_stat_scan_tables; 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_read_server_files" 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_server_files" may grant this role. 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_server_files IN ROLE pg_read_server_files; 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_write_server_files" 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_write_server_files" may grant this role. 2025-11-30 18:45:16.872 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_write_server_files IN ROLE pg_write_server_files; 2025-11-30 18:45:16.872 UTC client backend[46006] pg_regress/generated_virtual ERROR: window functions are not allowed in column generation expressions at character 74 2025-11-30 18:45:16.872 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (row_number() OVER (ORDER BY a)) VIRTUAL); 2025-11-30 18:45:16.873 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_execute_server_program" 2025-11-30 18:45:16.873 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_execute_server_program" may grant this role. 2025-11-30 18:45:16.873 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_execute_server_program IN ROLE pg_execute_server_program; 2025-11-30 18:45:16.873 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use subquery in column generation expression at character 74 2025-11-30 18:45:16.873 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7c (a int PRIMARY KEY, b int GENERATED ALWAYS AS ((SELECT a)) VIRTUAL); 2025-11-30 18:45:16.873 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to grant role "pg_signal_backend" 2025-11-30 18:45:16.873 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_signal_backend" may grant this role. 2025-11-30 18:45:16.873 UTC client backend[46001] pg_regress/create_role STATEMENT: CREATE ROLE regress_signal_backend IN ROLE pg_signal_backend; 2025-11-30 18:45:16.874 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_tenant" cannot be dropped because some objects depend on it 2025-11-30 18:45:16.874 UTC client backend[46001] pg_regress/create_role DETAIL: owner of table tenant_table owner of view tenant_view 2025-11-30 18:45:16.874 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_tenant; 2025-11-30 18:45:16.874 UTC client backend[46006] pg_regress/generated_virtual ERROR: set-returning functions are not allowed in column generation expressions at character 74 2025-11-30 18:45:16.874 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7d (a int PRIMARY KEY, b int GENERATED ALWAYS AS (generate_series(1, a)) VIRTUAL); 2025-11-30 18:45:16.874 UTC client backend[46006] pg_regress/generated_virtual ERROR: for a generated column, GENERATED ALWAYS must be specified at character 62 2025-11-30 18:45:16.874 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_8 (a int PRIMARY KEY, b int GENERATED BY DEFAULT AS (a * 2) VIRTUAL); 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_superuser" does not exist 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_superuser; 2025-11-30 18:45:16.875 UTC client backend[45989] pg_regress/alter_generic ERROR: foreign-data wrapper "alt_fdw2" already exists 2025-11-30 18:45:16.875 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER FOREIGN DATA WRAPPER alt_fdw1 RENAME TO alt_fdw2; 2025-11-30 18:45:16.875 UTC client backend[46000] pg_regress/misc_functions ERROR: step size cannot equal zero 2025-11-30 18:45:16.875 UTC client backend[46000] pg_regress/misc_functions STATEMENT: SELECT * FROM generate_series(TIMESTAMPTZ '2024-02-01', TIMESTAMPTZ '2024-03-01', INTERVAL '0 day') g(s); 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_replication_bypassrls" does not exist 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_replication_bypassrls; 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_replication" does not exist 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_replication; 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_bypassrls" does not exist 2025-11-30 18:45:16.875 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_bypassrls; 2025-11-30 18:45:16.876 UTC client backend[45989] pg_regress/alter_generic ERROR: server "alt_fserv2" already exists 2025-11-30 18:45:16.876 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER SERVER alt_fserv1 RENAME TO alt_fserv2; 2025-11-30 18:45:16.876 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_super" does not exist 2025-11-30 18:45:16.876 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_super; 2025-11-30 18:45:16.877 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_dbowner" does not exist 2025-11-30 18:45:16.877 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_dbowner; 2025-11-30 18:45:16.878 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_recursive" does not exist 2025-11-30 18:45:16.878 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_recursive; 2025-11-30 18:45:16.878 UTC client backend[46001] pg_regress/create_role ERROR: role "regress_nosuch_admin_recursive" does not exist 2025-11-30 18:45:16.878 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_admin_recursive; 2025-11-30 18:45:16.883 UTC client backend[46003] pg_regress/merge ERROR: MERGE command cannot affect row a second time 2025-11-30 18:45:16.883 UTC client backend[46003] pg_regress/merge HINT: Ensure that not more than one source row matches any one target row. 2025-11-30 18:45:16.883 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-11-30 18:45:16.883 UTC client backend[45989] pg_regress/alter_generic ERROR: language "alt_lang2" already exists 2025-11-30 18:45:16.883 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang1 RENAME TO alt_lang2; 2025-11-30 18:45:16.884 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of language alt_lang2 2025-11-30 18:45:16.884 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang2 RENAME TO alt_lang3; 2025-11-30 18:45:16.886 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of language alt_lang2 2025-11-30 18:45:16.886 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang2 OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.888 UTC client backend[46003] pg_regress/merge ERROR: MERGE command cannot affect row a second time 2025-11-30 18:45:16.888 UTC client backend[46003] pg_regress/merge HINT: Ensure that not more than one source row matches any one target row. 2025-11-30 18:45:16.888 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN DELETE; 2025-11-30 18:45:16.888 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:16.888 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang3 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.893 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.893 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.893 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, 33); 2025-11-30 18:45:16.893 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:16.893 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @+@(int4, int4) OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.894 UTC client backend[46003] pg_regress/merge ERROR: duplicate key value violates unique constraint "target_pkey" 2025-11-30 18:45:16.894 UTC client backend[46003] pg_regress/merge DETAIL: Key (tid)=(4) already exists. 2025-11-30 18:45:16.894 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT VALUES (4, NULL); 2025-11-30 18:45:16.895 UTC client backend[46003] pg_regress/merge ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:16.895 UTC client backend[46003] pg_regress/merge STATEMENT: SELECT * FROM target ORDER BY tid; 2025-11-30 18:45:16.895 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.895 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.895 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, 44); 2025-11-30 18:45:16.895 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator @+@ 2025-11-30 18:45:16.895 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @+@(int4, int4) OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.895 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:16.895 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @-@(int4, int4) OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.896 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator @+@ 2025-11-30 18:45:16.896 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @+@(int4, int4) SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.898 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to drop role 2025-11-30 18:45:16.898 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may drop roles with the SUPERUSER attribute. 2025-11-30 18:45:16.898 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_role_super; 2025-11-30 18:45:16.899 UTC client backend[46001] pg_regress/create_role ERROR: current user cannot be dropped 2025-11-30 18:45:16.899 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_role_admin; 2025-11-30 18:45:16.901 UTC client backend[46001] pg_regress/create_role ERROR: permission denied to drop role 2025-11-30 18:45:16.901 UTC client backend[46001] pg_regress/create_role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "regress_rolecreator" may drop this role. 2025-11-30 18:45:16.901 UTC client backend[46001] pg_regress/create_role STATEMENT: DROP ROLE regress_rolecreator; 2025-11-30 18:45:16.905 UTC client backend[45989] pg_regress/alter_generic ERROR: operator family "alt_opf2" for access method "hash" already exists in schema "alt_nsp1" 2025-11-30 18:45:16.905 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf1 USING hash RENAME TO alt_opf2; 2025-11-30 18:45:16.905 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:16.905 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf2 USING hash OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.905 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.905 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.905 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, DEFAULT), (4, 44); 2025-11-30 18:45:16.907 UTC client backend[45989] pg_regress/alter_generic ERROR: operator class "alt_opc2" for access method "hash" already exists in schema "alt_nsp1" 2025-11-30 18:45:16.907 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc1 USING hash RENAME TO alt_opc2; 2025-11-30 18:45:16.907 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.907 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.907 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, DEFAULT); 2025-11-30 18:45:16.908 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:16.908 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc2 USING hash OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.908 UTC client backend[46000] pg_regress/misc_functions ERROR: invalid WAL file name "invalid" 2025-11-30 18:45:16.908 UTC client backend[46000] pg_regress/misc_functions STATEMENT: SELECT * FROM pg_split_walfile_name('invalid'); 2025-11-30 18:45:16.914 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator family alt_opf3 2025-11-30 18:45:16.914 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf3 USING hash RENAME TO alt_opf4; 2025-11-30 18:45:16.914 UTC client backend[46003] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 109 2025-11-30 18:45:16.914 UTC client backend[46003] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-11-30 18:45:16.914 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT (tid, balance) VALUES (t.tid, s.delta); 2025-11-30 18:45:16.914 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator family alt_opf3 2025-11-30 18:45:16.914 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf3 USING hash OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf2 USING hash OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.915 UTC client backend[46003] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 109 2025-11-30 18:45:16.915 UTC client backend[46003] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-11-30 18:45:16.915 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON (SELECT true) WHEN NOT MATCHED THEN INSERT (tid, balance) VALUES (t.tid, s.delta); 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator family alt_opf3 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf3 USING hash SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic ERROR: operator family "alt_opf2" for access method "hash" already exists in schema "alt_nsp2" 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf2 USING hash SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.915 UTC client backend[46003] pg_regress/merge ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:16.915 UTC client backend[46003] pg_regress/merge STATEMENT: SELECT * FROM target ORDER BY tid; 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator class alt_opc3 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc3 USING hash RENAME TO alt_opc4; 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator class alt_opc3 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc3 USING hash OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:16.915 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc2 USING hash OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:16.916 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of operator class alt_opc3 2025-11-30 18:45:16.916 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc3 USING hash SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.917 UTC client backend[45989] pg_regress/alter_generic ERROR: operator class "alt_opc2" for access method "hash" already exists in schema "alt_nsp2" 2025-11-30 18:45:16.917 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc2 USING hash SET SCHEMA alt_nsp2; 2025-11-30 18:45:16.919 UTC client backend[46003] pg_regress/merge ERROR: unreachable WHEN clause specified after unconditional WHEN clause 2025-11-30 18:45:16.919 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN /* Terminal WHEN clause for MATCHED */ DELETE WHEN MATCHED THEN UPDATE SET balance = t.balance - s.delta; 2025-11-30 18:45:16.921 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" can only be updated to DEFAULT 2025-11-30 18:45:16.921 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.921 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: UPDATE gtest1 SET b = 11 WHERE a = 1; 2025-11-30 18:45:16.922 UTC client backend[46001] pg_regress/create_role LOG: disconnection: session time: 0:00:00.248 user=postgres database=regression host=[local] 2025-11-30 18:45:16.929 UTC client backend[46006] pg_regress/generated_virtual ERROR: integer out of range 2025-11-30 18:45:16.929 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: SELECT * FROM gtest1; 2025-11-30 18:45:16.931 UTC client backend[46007] pg_regress/incremental_sort LOG: disconnection: session time: 0:00:00.249 user=postgres database=regression host=[local] 2025-11-30 18:45:16.936 UTC client backend[45996] pg_regress/misc LOG: disconnection: session time: 0:00:00.268 user=postgres database=regression host=[local] 2025-11-30 18:45:16.936 UTC client backend[46002] pg_regress/collate.utf8 LOG: disconnection: session time: 0:00:00.261 user=postgres database=regression host=[local] 2025-11-30 18:45:16.939 UTC client backend[46013] isolation/deadlock-soft-2/s1 LOG: process 46013 avoided deadlock for ShareUpdateExclusiveLock on relation 48658 of database 16387 by rearranging queue order after 10.678 ms 2025-11-30 18:45:16.939 UTC client backend[46013] isolation/deadlock-soft-2/s1 DETAIL: Processes holding the lock: 46014, 46013. Wait queue: 46016, 46017. 2025-11-30 18:45:16.939 UTC client backend[46013] isolation/deadlock-soft-2/s1 CONTEXT: waiting for ShareUpdateExclusiveLock on relation 48658 of database 16387 2025-11-30 18:45:16.939 UTC client backend[46013] isolation/deadlock-soft-2/s1 STATEMENT: LOCK TABLE a2 IN SHARE UPDATE EXCLUSIVE MODE; 2025-11-30 18:45:16.939 UTC client backend[46013] isolation/deadlock-soft-2/s1 LOG: process 46013 acquired ShareUpdateExclusiveLock on relation 48658 of database 16387 after 10.678 ms 2025-11-30 18:45:16.939 UTC client backend[46013] isolation/deadlock-soft-2/s1 CONTEXT: waiting for ShareUpdateExclusiveLock on relation 48658 of database 16387 2025-11-30 18:45:16.939 UTC client backend[46013] isolation/deadlock-soft-2/s1 STATEMENT: LOCK TABLE a2 IN SHARE UPDATE EXCLUSIVE MODE; 2025-11-30 18:45:16.940 UTC client backend[46003] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 80 2025-11-30 18:45:16.940 UTC client backend[46003] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-11-30 18:45:16.940 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO wq_target t USING wq_source s ON t.tid = s.sid WHEN NOT MATCHED AND t.balance = 100 THEN INSERT (tid) VALUES (s.sid); 2025-11-30 18:45:16.940 UTC client backend[46003] pg_regress/merge ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:16.940 UTC client backend[46003] pg_regress/merge STATEMENT: SELECT * FROM wq_target; 2025-11-30 18:45:16.941 UTC client backend[45989] pg_regress/alter_generic ERROR: access method "invalid_index_method" does not exist 2025-11-30 18:45:16.941 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING invalid_index_method ADD OPERATOR 1 < (int4, int2); 2025-11-30 18:45:16.941 UTC client backend[46003] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "s" at character 90 2025-11-30 18:45:16.941 UTC client backend[46003] pg_regress/merge DETAIL: There is an entry for table "s", but it cannot be referenced from this part of the query. 2025-11-30 18:45:16.941 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO wq_target t USING wq_source s ON t.tid = s.sid WHEN NOT MATCHED BY SOURCE AND s.balance = 100 THEN DELETE; 2025-11-30 18:45:16.943 UTC client backend[46000] pg_regress/misc_functions ERROR: replication origin name is too long 2025-11-30 18:45:16.943 UTC client backend[46000] pg_regress/misc_functions DETAIL: Replication origin names must be no longer than 512 bytes. 2025-11-30 18:45:16.943 UTC client backend[46000] pg_regress/misc_functions STATEMENT: SELECT pg_replication_origin_create('regress_' || repeat('a', 505)); 2025-11-30 18:45:16.943 UTC client backend[46000] pg_regress/misc_functions LOG: disconnection: session time: 0:00:00.268 user=postgres database=regression host=[local] 2025-11-30 18:45:16.956 UTC client backend[45989] pg_regress/alter_generic ERROR: invalid operator number 6, must be between 1 and 5 2025-11-30 18:45:16.956 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD OPERATOR 6 < (int4, int2); 2025-11-30 18:45:16.964 UTC client backend[46003] pg_regress/merge ERROR: cannot use system column "xmin" in MERGE WHEN condition at character 76 2025-11-30 18:45:16.964 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO wq_target t USING wq_source s ON t.tid = s.sid WHEN MATCHED AND t.xmin = t.xmax THEN UPDATE SET balance = t.balance + s.balance; 2025-11-30 18:45:16.969 UTC client backend[45990] pg_regress/tidrangescan LOG: disconnection: session time: 0:00:00.305 user=postgres database=regression host=[local] 2025-11-30 18:45:16.972 UTC client backend[45989] pg_regress/alter_generic ERROR: invalid operator number 0, must be between 1 and 5 2025-11-30 18:45:16.972 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD OPERATOR 0 < (int4, int2); 2025-11-30 18:45:16.974 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.974 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.974 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (4, 8); 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, 77); 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (6, DEFAULT), (7, 77); 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.975 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, DEFAULT); 2025-11-30 18:45:16.977 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.977 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.977 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT); 2025-11-30 18:45:16.977 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:16.977 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:16.977 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT), (9, DEFAULT); 2025-11-30 18:45:16.977 UTC client backend[45989] pg_regress/alter_generic ERROR: operator argument types must be specified in ALTER OPERATOR FAMILY 2025-11-30 18:45:16.977 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD OPERATOR 1 < ; 2025-11-30 18:45:16.979 UTC client backend[45989] pg_regress/alter_generic ERROR: invalid function number 0, must be between 1 and 6 2025-11-30 18:45:16.979 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD FUNCTION 0 btint42cmp(int4, int2); 2025-11-30 18:45:16.981 UTC client backend[45989] pg_regress/alter_generic ERROR: invalid function number 7, must be between 1 and 6 2025-11-30 18:45:16.981 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD FUNCTION 7 btint42cmp(int4, int2); 2025-11-30 18:45:16.981 UTC client backend[45989] pg_regress/alter_generic ERROR: STORAGE cannot be specified in ALTER OPERATOR FAMILY 2025-11-30 18:45:16.981 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD STORAGE invalid_storage; 2025-11-30 18:45:16.987 UTC client backend[46005] pg_regress/without_overlaps ERROR: constraint using WITHOUT OVERLAPS needs at least two columns 2025-11-30 18:45:16.987 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng3 ( valid_at daterange, CONSTRAINT temporal_rng3_uq UNIQUE (valid_at WITHOUT OVERLAPS) ); 2025-11-30 18:45:16.987 UTC client backend[46005] pg_regress/without_overlaps ERROR: column "valid_at" named in key does not exist at character 46 2025-11-30 18:45:16.987 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng3 ( id INTEGER, CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS) ); 2025-11-30 18:45:16.987 UTC client backend[46005] pg_regress/without_overlaps ERROR: column "valid_at" in WITHOUT OVERLAPS is not a range or multirange type at character 65 2025-11-30 18:45:16.987 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng3 ( id int4range, valid_at TEXT, CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS) ); 2025-11-30 18:45:16.988 UTC client backend[45989] pg_regress/alter_generic ERROR: must be superuser to alter an operator family 2025-11-30 18:45:16.988 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf5 USING btree ADD OPERATOR 1 < (int4, int2), FUNCTION 1 btint42cmp(int4, int2); 2025-11-30 18:45:16.990 UTC client backend[45989] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:16.990 UTC client backend[45989] pg_regress/alter_generic STATEMENT: RESET ROLE; 2025-11-30 18:45:16.991 UTC client backend[45989] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:16.991 UTC client backend[45989] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf5 USING btree; 2025-11-30 18:45:16.998 UTC client backend[45989] pg_regress/alter_generic ERROR: permission denied for schema alt_nsp6 2025-11-30 18:45:16.998 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_nsp6.alt_opf6 USING btree ADD OPERATOR 1 < (int4, int2); 2025-11-30 18:45:17.002 UTC client backend[45989] pg_regress/alter_generic ERROR: one or two argument types must be specified 2025-11-30 18:45:17.002 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf7 USING btree DROP OPERATOR 1 (int4, int2, int8); 2025-11-30 18:45:17.006 UTC client backend[46006] pg_regress/generated_virtual ERROR: child column "b" specifies generation expression 2025-11-30 18:45:17.006 UTC client backend[46006] pg_regress/generated_virtual HINT: A child table column cannot be generated unless its parent column is. 2025-11-30 18:45:17.006 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_normal_child (a int, b int GENERATED ALWAYS AS (a * 2) VIRTUAL) INHERITS (gtest_normal); 2025-11-30 18:45:17.008 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" in child table must not be a generated column 2025-11-30 18:45:17.008 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_normal_child INHERIT gtest_normal; 2025-11-30 18:45:17.009 UTC client backend[46003] pg_regress/merge ERROR: column reference "balance" is ambiguous at character 99 2025-11-30 18:45:17.009 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO sq_target USING v ON tid = sid WHEN MATCHED AND tid >= 2 THEN UPDATE SET balance = balance + delta WHEN NOT MATCHED THEN INSERT (balance, tid) VALUES (balance + delta, sid) WHEN MATCHED AND tid < 2 THEN DELETE; 2025-11-30 18:45:17.012 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" inherits from generated column but specifies default 2025-11-30 18:45:17.012 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtestx (x int, b int DEFAULT 10) INHERITS (gtest1); 2025-11-30 18:45:17.014 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" inherits from generated column but specifies identity 2025-11-30 18:45:17.014 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS IDENTITY) INHERITS (gtest1); 2025-11-30 18:45:17.015 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" inherits from generated column of different kind 2025-11-30 18:45:17.015 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Parent column is VIRTUAL, child column is STORED. 2025-11-30 18:45:17.015 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS (a * 22) STORED) INHERITS (gtest1); 2025-11-30 18:45:17.015 UTC client backend[45989] pg_regress/alter_generic ERROR: access method "btree" does not support ordering operators 2025-11-30 18:45:17.015 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf10 USING btree ADD OPERATOR 1 < (int4, int4) FOR ORDER BY float_ops; 2025-11-30 18:45:17.017 UTC client backend[46003] pg_regress/merge ERROR: MERGE_ACTION() can only be used in the RETURNING list of a MERGE command at character 8 2025-11-30 18:45:17.017 UTC client backend[46003] pg_regress/merge STATEMENT: SELECT merge_action() FROM sq_target; 2025-11-30 18:45:17.017 UTC client backend[46003] pg_regress/merge ERROR: MERGE_ACTION() can only be used in the RETURNING list of a MERGE command at character 54 2025-11-30 18:45:17.017 UTC client backend[46003] pg_regress/merge STATEMENT: UPDATE sq_target SET balance = balance + 1 RETURNING merge_action(); 2025-11-30 18:45:17.024 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not determine which collation to use for string comparison 2025-11-30 18:45:17.024 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:17.024 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test3 ORDER BY 2; 2025-11-30 18:45:17.026 UTC client backend[45989] pg_regress/alter_generic ERROR: ordering comparison functions must return integer 2025-11-30 18:45:17.026 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf12 USING btree ADD FUNCTION 1 fn_opf12(int4, int2); 2025-11-30 18:45:17.026 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "C" at character 48 2025-11-30 18:45:17.026 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:17.026 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 UNION SELECT a, b FROM collate_test3 ORDER BY 2; 2025-11-30 18:45:17.029 UTC client backend[45989] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:17.029 UTC client backend[45989] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf12 USING btree; 2025-11-30 18:45:17.030 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "C" at character 52 2025-11-30 18:45:17.030 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:17.030 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 INTERSECT SELECT a, b FROM collate_test3 ORDER BY 2; 2025-11-30 18:45:17.031 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "C" at character 49 2025-11-30 18:45:17.031 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:17.031 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 EXCEPT SELECT a, b FROM collate_test3 ORDER BY 2; 2025-11-30 18:45:17.031 UTC client backend[46005] pg_regress/without_overlaps ERROR: "idx_temporal3_uq" is not a unique index at character 29 2025-11-30 18:45:17.031 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-11-30 18:45:17.031 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 ADD CONSTRAINT temporal3_pk PRIMARY KEY USING INDEX idx_temporal3_uq; 2025-11-30 18:45:17.033 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: no collation was derived for column "b" with collatable type text 2025-11-30 18:45:17.033 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:17.033 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE test_u AS SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test3; 2025-11-30 18:45:17.034 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not determine which collation to use for string comparison 2025-11-30 18:45:17.034 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:17.034 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: select x < y from collate_test10; 2025-11-30 18:45:17.034 UTC client backend[45989] pg_regress/alter_generic ERROR: hash function 1 must return integer 2025-11-30 18:45:17.034 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf13 USING hash ADD FUNCTION 1 fn_opf13(int4); 2025-11-30 18:45:17.034 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "tr-x-icu" at character 47 2025-11-30 18:45:17.034 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-11-30 18:45:17.034 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: select x, y from collate_test10 order by x || y; 2025-11-30 18:45:17.035 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: recursive query "foo" column 1 has collation "en-x-icu" in non-recursive term but collation "de-x-icu" overall at character 37 2025-11-30 18:45:17.035 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation of the non-recursive term. 2025-11-30 18:45:17.035 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: WITH RECURSIVE foo(x) AS (SELECT x FROM (VALUES('a' COLLATE "en-x-icu"),('b')) t(x) UNION ALL SELECT (x || 'c') COLLATE "de-x-icu" FROM foo WHERE length(x) < 10) SELECT * FROM foo; 2025-11-30 18:45:17.035 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: syntax error at or near "COLLATE" at character 26 2025-11-30 18:45:17.035 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT CAST('42' AS text COLLATE "C"); 2025-11-30 18:45:17.035 UTC client backend[45989] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:17.035 UTC client backend[45989] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf13 USING hash; 2025-11-30 18:45:17.036 UTC client backend[46005] pg_regress/without_overlaps ERROR: "idx_temporal3_uq" is not a unique index at character 29 2025-11-30 18:45:17.036 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-11-30 18:45:17.036 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 ADD CONSTRAINT temporal3_uq UNIQUE USING INDEX idx_temporal3_uq; 2025-11-30 18:45:17.036 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" in child table must be a generated column 2025-11-30 18:45:17.036 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestxx_1 INHERIT gtest1; 2025-11-30 18:45:17.037 UTC client backend[46012] isolation/deadlock-soft-2/control connection LOG: disconnection: session time: 0:00:00.221 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.038 UTC client backend[46013] isolation/deadlock-soft-2/s1 LOG: disconnection: session time: 0:00:00.216 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.039 UTC client backend[46014] isolation/deadlock-soft-2/s2 LOG: disconnection: session time: 0:00:00.210 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.040 UTC client backend[46016] isolation/deadlock-soft-2/s3 LOG: disconnection: session time: 0:00:00.203 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.041 UTC client backend[46017] isolation/deadlock-soft-2/s4 LOG: disconnection: session time: 0:00:00.197 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.041 UTC client backend[46006] pg_regress/generated_virtual ERROR: inherited column "b" has a generation conflict 2025-11-30 18:45:17.041 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest0, gtesty); 2025-11-30 18:45:17.042 UTC client backend[45989] pg_regress/alter_generic ERROR: ordering comparison functions must have two arguments 2025-11-30 18:45:17.042 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf14 USING btree ADD FUNCTION 1 fn_opf14(int4); 2025-11-30 18:45:17.042 UTC client backend[45989] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:17.042 UTC client backend[45989] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf14 USING btree; 2025-11-30 18:45:17.044 UTC client backend[46006] pg_regress/generated_virtual ERROR: inherited column "b" has a generation conflict 2025-11-30 18:45:17.044 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-11-30 18:45:17.045 UTC client backend[45989] pg_regress/alter_generic ERROR: hash function 1 must have one argument 2025-11-30 18:45:17.045 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf15 USING hash ADD FUNCTION 1 fn_opf15(int4, int2); 2025-11-30 18:45:17.045 UTC client backend[45989] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:17.045 UTC client backend[45989] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf15 USING hash; 2025-11-30 18:45:17.046 UTC client backend[45989] pg_regress/alter_generic ERROR: associated data types must be specified for index support function 2025-11-30 18:45:17.046 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf16 USING gist ADD FUNCTION 1 btint42cmp(int4, int2); 2025-11-30 18:45:17.046 UTC client backend[45989] pg_regress/alter_generic ERROR: operator number 1 for (integer,integer) appears more than once 2025-11-30 18:45:17.046 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int4), OPERATOR 1 < (int4, int4); 2025-11-30 18:45:17.047 UTC client backend[45989] pg_regress/alter_generic ERROR: operator 1(integer,integer) already exists in operator family "alt_opf17" 2025-11-30 18:45:17.047 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int4); 2025-11-30 18:45:17.047 UTC client backend[45989] pg_regress/alter_generic ERROR: function number 1 for (integer,smallint) appears more than once 2025-11-30 18:45:17.047 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int2) , OPERATOR 2 <= (int4, int2) , OPERATOR 3 = (int4, int2) , OPERATOR 4 >= (int4, int2) , OPERATOR 5 > (int4, int2) , FUNCTION 1 btint42cmp(int4, int2) , FUNCTION 1 btint42cmp(int4, int2); 2025-11-30 18:45:17.049 UTC unrecognized[46041] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.049 UTC client backend[46041] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.049 UTC client backend[46041] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-parallel 2025-11-30 18:45:17.050 UTC client backend[46041] isolation/deadlock-parallel LOG: connection ready: setup total=2.725 ms, fork=1.167 ms, authentication=0.129 ms 2025-11-30 18:45:17.051 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" inherits conflicting generation expressions 2025-11-30 18:45:17.051 UTC client backend[46006] pg_regress/generated_virtual HINT: To resolve the conflict, specify a generation expression explicitly. 2025-11-30 18:45:17.051 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-11-30 18:45:17.051 UTC client backend[45989] pg_regress/alter_generic ERROR: operator 1(integer,smallint) already exists in operator family "alt_opf17" 2025-11-30 18:45:17.051 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int2) , OPERATOR 2 <= (int4, int2) , OPERATOR 3 = (int4, int2) , OPERATOR 4 >= (int4, int2) , OPERATOR 5 > (int4, int2) , FUNCTION 1 btint42cmp(int4, int2); 2025-11-30 18:45:17.052 UTC unrecognized[46042] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.052 UTC client backend[46042] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.052 UTC client backend[46042] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-parallel 2025-11-30 18:45:17.053 UTC client backend[46042] isolation/deadlock-parallel LOG: connection ready: setup total=2.082 ms, fork=0.709 ms, authentication=0.116 ms 2025-11-30 18:45:17.054 UTC client backend[45991] pg_regress/create_table_like ERROR: duplicate key value violates unique constraint "inhg_pkey" 2025-11-30 18:45:17.054 UTC client backend[45991] pg_regress/create_table_like DETAIL: Key (xx)=(10) already exists. 2025-11-30 18:45:17.054 UTC client backend[45991] pg_regress/create_table_like STATEMENT: INSERT INTO inhg VALUES (20, 10); 2025-11-30 18:45:17.056 UTC unrecognized[46043] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.056 UTC client backend[46043] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.056 UTC client backend[46043] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-parallel 2025-11-30 18:45:17.057 UTC client backend[46043] isolation/deadlock-parallel LOG: connection ready: setup total=3.061 ms, fork=1.705 ms, authentication=0.122 ms 2025-11-30 18:45:17.058 UTC client backend[45989] pg_regress/alter_generic ERROR: operator 1(integer,integer) does not exist in operator family "alt_opf18" 2025-11-30 18:45:17.058 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree DROP OPERATOR 1 (int4, int4); 2025-11-30 18:45:17.059 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not determine which collation to use for string comparison 2025-11-30 18:45:17.059 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-11-30 18:45:17.059 UTC client backend[45999] pg_regress/collate.icu.utf8 CONTEXT: PL/pgSQL function mylt2(text,text) line 6 at RETURN 2025-11-30 18:45:17.059 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT mylt2('a', 'B' collate "C") as fail; 2025-11-30 18:45:17.061 UTC client backend[45991] pg_regress/create_table_like ERROR: multiple primary keys for table "inhg" are not allowed 2025-11-30 18:45:17.061 UTC client backend[45991] pg_regress/create_table_like STATEMENT: /* Multiple primary keys creation should fail */ CREATE TABLE inhg (x text, LIKE inhx INCLUDING INDEXES, PRIMARY KEY(x)); 2025-11-30 18:45:17.061 UTC unrecognized[46044] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.061 UTC client backend[46044] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.061 UTC client backend[46044] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-parallel 2025-11-30 18:45:17.063 UTC client backend[45989] pg_regress/alter_generic ERROR: ordering equal image functions must not be cross-type 2025-11-30 18:45:17.063 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree ADD FUNCTION 4 (int4, int2) btequalimage(oid); 2025-11-30 18:45:17.063 UTC client backend[45989] pg_regress/alter_generic ERROR: btree skip support functions must not be cross-type 2025-11-30 18:45:17.063 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree ADD FUNCTION 6 (int4, int2) btint4skipsupport(internal); 2025-11-30 18:45:17.063 UTC client backend[45989] pg_regress/alter_generic ERROR: function 2(integer,integer) does not exist in operator family "alt_opf18" 2025-11-30 18:45:17.063 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree DROP FUNCTION 2 (int4, int4); 2025-11-30 18:45:17.063 UTC client backend[46044] isolation/deadlock-parallel LOG: connection ready: setup total=5.067 ms, fork=2.892 ms, authentication=0.141 ms 2025-11-30 18:45:17.066 UTC unrecognized[46045] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.067 UTC client backend[46005] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_rng_pk" 2025-11-30 18:45:17.067 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)) conflicts with key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)). 2025-11-30 18:45:17.067 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng ADD CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.067 UTC client backend[46045] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.067 UTC client backend[46045] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/deadlock-parallel 2025-11-30 18:45:17.068 UTC client backend[46045] isolation/deadlock-parallel LOG: connection ready: setup total=3.815 ms, fork=1.509 ms, authentication=0.114 ms 2025-11-30 18:45:17.069 UTC client backend[45989] pg_regress/alter_generic ERROR: function test_opclass_options_func(internal, text[], boolean) does not exist 2025-11-30 18:45:17.069 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf19 USING btree ADD FUNCTION 5 test_opclass_options_func(internal, text[], bool); 2025-11-30 18:45:17.069 UTC client backend[45989] pg_regress/alter_generic ERROR: invalid operator class options parsing function 2025-11-30 18:45:17.069 UTC client backend[45989] pg_regress/alter_generic HINT: Valid signature of operator class options parsing function is (internal) RETURNS void. 2025-11-30 18:45:17.069 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf19 USING btree ADD FUNCTION 5 (int4) btint42cmp(int4, int2); 2025-11-30 18:45:17.069 UTC client backend[45989] pg_regress/alter_generic ERROR: left and right associated data types for operator class options parsing functions must match 2025-11-30 18:45:17.069 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf19 USING btree ADD FUNCTION 5 (int4, int2) btint42cmp(int4, int2); 2025-11-30 18:45:17.069 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer 2025-11-30 18:45:17.069 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX collate_test1_idx5 ON collate_test1 (a COLLATE "C"); 2025-11-30 18:45:17.070 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer at character 54 2025-11-30 18:45:17.070 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX collate_test1_idx6 ON collate_test1 ((a COLLATE "C")); 2025-11-30 18:45:17.071 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng" 2025-11-30 18:45:17.071 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng ADD CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.072 UTC client backend[45989] pg_regress/alter_generic ERROR: statistics object "alt_stat2" already exists in schema "alt_nsp1" 2025-11-30 18:45:17.072 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat1 RENAME TO alt_stat2; 2025-11-30 18:45:17.072 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:17.072 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat2 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:17.076 UTC client backend[45991] pg_regress/create_table_like ERROR: duplicate key value violates unique constraint "inhg_x_key" 2025-11-30 18:45:17.076 UTC client backend[45991] pg_regress/create_table_like DETAIL: Key (x)=(15) already exists. 2025-11-30 18:45:17.076 UTC client backend[45991] pg_regress/create_table_like STATEMENT: INSERT INTO inhg (xx, yy, x) VALUES ('foo', 10, 15); 2025-11-30 18:45:17.077 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation "test0" already exists 2025-11-30 18:45:17.077 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION test0 FROM "C"; 2025-11-30 18:45:17.078 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: parameter "locale" must be specified 2025-11-30 18:45:17.078 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION test3 (provider = icu, lc_collate = 'en_US.utf8'); 2025-11-30 18:45:17.078 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng_pk" 2025-11-30 18:45:17.078 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)). 2025-11-30 18:45:17.078 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2018-01-01', '2018-01-05')); 2025-11-30 18:45:17.078 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: ICU locale "nonsense-nowhere" has unknown language "nonsense" 2025-11-30 18:45:17.078 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: To disable ICU locale validation, set the parameter "icu_validation_level" to "disabled". 2025-11-30 18:45:17.078 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testx (provider = icu, locale = 'nonsense-nowhere'); 2025-11-30 18:45:17.078 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_rng" violates not-null constraint 2025-11-30 18:45:17.078 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains (null, [2018-01-01,2018-01-05)). 2025-11-30 18:45:17.078 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES (NULL, daterange('2018-01-01', '2018-01-05')); 2025-11-30 18:45:17.079 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_rng" violates not-null constraint 2025-11-30 18:45:17.079 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains ([3,4), null). 2025-11-30 18:45:17.079 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[3,4)', NULL); 2025-11-30 18:45:17.079 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng" 2025-11-30 18:45:17.079 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[3,4)', 'empty'); 2025-11-30 18:45:17.085 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng_pk" 2025-11-30 18:45:17.085 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-03-05,2018-05-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-03-03,2018-04-04)). 2025-11-30 18:45:17.085 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[1,2)', valid_at = daterange('2018-03-05', '2018-05-05') WHERE id = '[21,22)'; 2025-11-30 18:45:17.086 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_rng" violates not-null constraint 2025-11-30 18:45:17.086 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains (null, [2018-03-05,2018-05-05)). 2025-11-30 18:45:17.086 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = NULL, valid_at = daterange('2018-03-05', '2018-05-05') WHERE id = '[21,22)'; 2025-11-30 18:45:17.086 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_rng" violates not-null constraint 2025-11-30 18:45:17.086 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains ([1,2), null). 2025-11-30 18:45:17.086 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[1,2)', valid_at = NULL WHERE id = '[21,22)'; 2025-11-30 18:45:17.087 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng" 2025-11-30 18:45:17.087 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[1,2)', valid_at = 'empty' WHERE id = '[21,22)'; 2025-11-30 18:45:17.087 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not convert locale name "@colStrength=primary;nonsense=yes" to language tag: U_ILLEGAL_ARGUMENT_ERROR 2025-11-30 18:45:17.087 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testx (provider = icu, locale = '@colStrength=primary;nonsense=yes'); 2025-11-30 18:45:17.088 UTC client backend[45999] pg_regress/collate.icu.utf8 WARNING: could not convert locale name "@colStrength=primary;nonsense=yes" to language tag: U_ILLEGAL_ARGUMENT_ERROR 2025-11-30 18:45:17.089 UTC client backend[45999] pg_regress/collate.icu.utf8 WARNING: ICU locale "nonsense-nowhere" has unknown language "nonsense" 2025-11-30 18:45:17.089 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: To disable ICU locale validation, set the parameter "icu_validation_level" to "disabled". 2025-11-30 18:45:17.090 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of statistics object alt_stat3 2025-11-30 18:45:17.090 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat3 RENAME TO alt_stat4; 2025-11-30 18:45:17.090 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation "nonsense" for encoding "UTF8" does not exist 2025-11-30 18:45:17.090 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION test4 FROM nonsense; 2025-11-30 18:45:17.091 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation "test11" already exists in schema "collate_tests" 2025-11-30 18:45:17.091 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: ALTER COLLATION test0 RENAME TO test11; 2025-11-30 18:45:17.091 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation "test1" for encoding "UTF8" does not exist 2025-11-30 18:45:17.091 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: ALTER COLLATION test1 RENAME TO test22; 2025-11-30 18:45:17.092 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: role "nonsense" does not exist 2025-11-30 18:45:17.092 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: ALTER COLLATION test11 OWNER TO nonsense; 2025-11-30 18:45:17.092 UTC client backend[46005] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_rng3_uq" 2025-11-30 18:45:17.092 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)) conflicts with key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)). 2025-11-30 18:45:17.092 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng3 ADD CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.094 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-11-30 18:45:17.094 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng3 ADD CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.095 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation "test0" for encoding "UTF8" does not exist 2025-11-30 18:45:17.095 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: DROP COLLATION test0; 2025-11-30 18:45:17.097 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng3_uq" 2025-11-30 18:45:17.097 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)). 2025-11-30 18:45:17.097 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng3 (id, valid_at) VALUES ('[1,2)', daterange('2018-01-01', '2018-01-05')); 2025-11-30 18:45:17.097 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-11-30 18:45:17.097 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng3 (id, valid_at) VALUES ('[3,4)', 'empty'); 2025-11-30 18:45:17.100 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng3_uq" 2025-11-30 18:45:17.100 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-03-01,2018-05-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-03-03,2018-04-04)). 2025-11-30 18:45:17.100 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng3 SET valid_at = daterange('2018-03-01', '2018-05-05') WHERE id = '[1,2)' AND valid_at IS NULL; 2025-11-30 18:45:17.100 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-11-30 18:45:17.100 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng3 SET valid_at = 'empty' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-11-30 18:45:17.100 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-11-30 18:45:17.100 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng3 SET id = NULL, valid_at = 'empty' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of statistics object alt_stat3 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat3 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat2 OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of statistics object alt_stat3 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat3 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic ERROR: statistics object "alt_stat2" already exists in schema "alt_nsp2" 2025-11-30 18:45:17.102 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat2 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.104 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: cannot drop collation test0 because other objects depend on it 2025-11-30 18:45:17.104 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: column b of table collate_dep_test1 depends on collation test0 type collate_dep_dom1 depends on collation test0 column y of composite type collate_dep_test2 depends on collation test0 view collate_dep_test3 depends on collation test0 index collate_dep_test4i depends on collation test0 2025-11-30 18:45:17.104 UTC client backend[45999] pg_regress/collate.icu.utf8 HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:17.104 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: DROP COLLATION test0 RESTRICT; 2025-11-30 18:45:17.106 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-11-30 18:45:17.106 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:17.106 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: COPY gtest1 (a, b) TO stdout; 2025-11-30 18:45:17.108 UTC client backend[45989] pg_regress/alter_generic ERROR: text search dictionary "alt_ts_dict2" already exists in schema "alt_nsp1" 2025-11-30 18:45:17.108 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict1 RENAME TO alt_ts_dict2; 2025-11-30 18:45:17.108 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:17.108 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict2 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:17.109 UTC client backend[46005] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_mltrng_pk" 2025-11-30 18:45:17.109 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}) conflicts with key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}). 2025-11-30 18:45:17.109 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng ADD CONSTRAINT temporal_mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of text search dictionary alt_ts_dict3 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict3 RENAME TO alt_ts_dict4; 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of text search dictionary alt_ts_dict3 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict3 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict2 OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of text search dictionary alt_ts_dict3 2025-11-30 18:45:17.109 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict3 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.110 UTC client backend[45989] pg_regress/alter_generic ERROR: text search dictionary "alt_ts_dict2" already exists in schema "alt_nsp2" 2025-11-30 18:45:17.110 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict2 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.111 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng" 2025-11-30 18:45:17.111 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng ADD CONSTRAINT temporal_mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.111 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-11-30 18:45:17.111 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:17.111 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: COPY gtest1 (a, b) FROM stdin; 2025-11-30 18:45:17.112 UTC client backend[45989] pg_regress/alter_generic ERROR: text search configuration "alt_ts_conf2" already exists in schema "alt_nsp1" 2025-11-30 18:45:17.112 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf1 RENAME TO alt_ts_conf2; 2025-11-30 18:45:17.112 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-11-30 18:45:17.112 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf2 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:17.114 UTC client backend[46006] pg_regress/generated_virtual ERROR: generated columns are not supported in COPY FROM WHERE conditions 2025-11-30 18:45:17.114 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:17.114 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: COPY gtest1 FROM stdin WHERE b <> 10; 2025-11-30 18:45:17.114 UTC client backend[46006] pg_regress/generated_virtual ERROR: generated columns are not supported in COPY FROM WHERE conditions 2025-11-30 18:45:17.114 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:17.114 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: COPY gtest1 FROM stdin WHERE gtest1 IS NULL; 2025-11-30 18:45:17.114 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of text search configuration alt_ts_conf3 2025-11-30 18:45:17.114 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf3 RENAME TO alt_ts_conf4; 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of text search configuration alt_ts_conf3 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf3 OWNER TO regress_alter_generic_user2; 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf2 OWNER TO regress_alter_generic_user3; 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic ERROR: must be owner of text search configuration alt_ts_conf3 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf3 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.115 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng_pk" 2025-11-30 18:45:17.115 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}). 2025-11-30 18:45:17.115 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2018-01-01', '2018-01-05'))); 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic ERROR: text search configuration "alt_ts_conf2" already exists in schema "alt_nsp2" 2025-11-30 18:45:17.115 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf2 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.115 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_mltrng" violates not-null constraint 2025-11-30 18:45:17.115 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains (null, {[2018-01-01,2018-01-05)}). 2025-11-30 18:45:17.115 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES (NULL, datemultirange(daterange('2018-01-01', '2018-01-05'))); 2025-11-30 18:45:17.116 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_mltrng" violates not-null constraint 2025-11-30 18:45:17.116 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains ([3,4), null). 2025-11-30 18:45:17.116 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[3,4)', NULL); 2025-11-30 18:45:17.116 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng" 2025-11-30 18:45:17.116 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[3,4)', '{}'); 2025-11-30 18:45:17.116 UTC client backend[45989] pg_regress/alter_generic ERROR: text search template "alt_ts_temp2" already exists in schema "alt_nsp1" 2025-11-30 18:45:17.116 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH TEMPLATE alt_ts_temp1 RENAME TO alt_ts_temp2; 2025-11-30 18:45:17.116 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-11-30 18:45:17.116 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:17.116 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: COPY gtest3 (a, b) TO stdout; 2025-11-30 18:45:17.117 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-11-30 18:45:17.117 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-11-30 18:45:17.117 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: COPY gtest3 (a, b) FROM stdin; 2025-11-30 18:45:17.117 UTC client backend[45989] pg_regress/alter_generic ERROR: text search template "alt_ts_temp2" already exists in schema "alt_nsp2" 2025-11-30 18:45:17.117 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH TEMPLATE alt_ts_temp2 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.117 UTC client backend[45989] pg_regress/alter_generic ERROR: text search template parameter "Init" not recognized 2025-11-30 18:45:17.117 UTC client backend[45989] pg_regress/alter_generic STATEMENT: CREATE TEXT SEARCH TEMPLATE tstemp_case ("Init" = init_function); 2025-11-30 18:45:17.119 UTC client backend[45989] pg_regress/alter_generic ERROR: text search parser "alt_ts_prs2" already exists in schema "alt_nsp1" 2025-11-30 18:45:17.119 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH PARSER alt_ts_prs1 RENAME TO alt_ts_prs2; 2025-11-30 18:45:17.120 UTC client backend[45989] pg_regress/alter_generic ERROR: text search parser "alt_ts_prs2" already exists in schema "alt_nsp2" 2025-11-30 18:45:17.120 UTC client backend[45989] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH PARSER alt_ts_prs2 SET SCHEMA alt_nsp2; 2025-11-30 18:45:17.120 UTC client backend[45989] pg_regress/alter_generic ERROR: text search parser parameter "Start" not recognized 2025-11-30 18:45:17.120 UTC client backend[45989] pg_regress/alter_generic STATEMENT: CREATE TEXT SEARCH PARSER tspars_case ("Start" = start_function); 2025-11-30 18:45:17.126 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng_pk" 2025-11-30 18:45:17.126 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-03-05,2018-05-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-03-03,2018-04-04)}). 2025-11-30 18:45:17.126 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[1,2)', valid_at = datemultirange(daterange('2018-03-05', '2018-05-05')) WHERE id = '[21,22)'; 2025-11-30 18:45:17.127 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_mltrng" violates not-null constraint 2025-11-30 18:45:17.127 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains (null, {[2018-03-05,2018-05-05)}). 2025-11-30 18:45:17.127 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = NULL, valid_at = datemultirange(daterange('2018-03-05', '2018-05-05')) WHERE id = '[21,22)'; 2025-11-30 18:45:17.127 UTC client backend[46005] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_mltrng" violates not-null constraint 2025-11-30 18:45:17.127 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Failing row contains ([1,2), null). 2025-11-30 18:45:17.127 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[1,2)', valid_at = NULL WHERE id = '[21,22)'; 2025-11-30 18:45:17.128 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng" 2025-11-30 18:45:17.128 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[1,2)', valid_at = '{}' WHERE id = '[21,22)'; 2025-11-30 18:45:17.132 UTC client backend[46006] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a user-defined type 2025-11-30 18:45:17.132 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Virtual generated columns that make use of user-defined types are not yet supported. 2025-11-30 18:45:17.132 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest4 ( a int, b double_int GENERATED ALWAYS AS ((a * 2, a * 3)) VIRTUAL ); 2025-11-30 18:45:17.134 UTC client backend[46005] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_mltrng3_uq" 2025-11-30 18:45:17.134 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}) conflicts with key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}). 2025-11-30 18:45:17.134 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng3 ADD CONSTRAINT temporal_mltrng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.135 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-11-30 18:45:17.135 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng3 ADD CONSTRAINT temporal_mltrng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-11-30 18:45:17.139 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng3_uq" 2025-11-30 18:45:17.139 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}). 2025-11-30 18:45:17.139 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2018-01-01', '2018-01-05'))); 2025-11-30 18:45:17.139 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-11-30 18:45:17.139 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[3,4)', '{}'); 2025-11-30 18:45:17.139 UTC client backend[45989] pg_regress/alter_generic LOG: disconnection: session time: 0:00:00.483 user=postgres database=regression host=[local] 2025-11-30 18:45:17.140 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot drop column b of table gtest10 because other objects depend on it 2025-11-30 18:45:17.140 UTC client backend[46006] pg_regress/generated_virtual DETAIL: column c of table gtest10 depends on column b of table gtest10 2025-11-30 18:45:17.140 UTC client backend[46006] pg_regress/generated_virtual HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:17.140 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest10 DROP COLUMN b; 2025-11-30 18:45:17.142 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng3_uq" 2025-11-30 18:45:17.142 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-03-01,2018-05-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-03-03,2018-04-04)}). 2025-11-30 18:45:17.142 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng3 SET valid_at = datemultirange(daterange('2018-03-01', '2018-05-05')) WHERE id = '[1,2)' AND valid_at IS NULL; 2025-11-30 18:45:17.142 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not open collator for locale "und-u-kn-lower": U_ILLEGAL_ARGUMENT_ERROR 2025-11-30 18:45:17.142 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testcoll_error1 (provider = icu, locale = '@colNumeric=lower'); 2025-11-30 18:45:17.142 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-11-30 18:45:17.142 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng3 SET valid_at = '{}' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-11-30 18:45:17.143 UTC client backend[46005] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-11-30 18:45:17.143 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng3 SET id = NULL, valid_at = '{}' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-11-30 18:45:17.154 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not open collator for locale "und" with rules "!!wrong!!": U_INVALID_FORMAT_ERROR 2025-11-30 18:45:17.154 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testcoll_rulesx (provider = icu, locale = '', rules = '!!wrong!!'); 2025-11-30 18:45:17.161 UTC client backend[46006] pg_regress/generated_virtual ERROR: generation expression uses user-defined function at character 76 2025-11-30 18:45:17.161 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Virtual generated columns that make use of user-defined functions are not yet supported. 2025-11-30 18:45:17.161 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest12 (a int PRIMARY KEY, b int, c int GENERATED ALWAYS AS (gf1(b)) VIRTUAL); 2025-11-30 18:45:17.161 UTC client backend[46006] pg_regress/generated_virtual ERROR: permission denied for table gtest11 2025-11-30 18:45:17.161 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: SELECT a, b FROM gtest11; 2025-11-30 18:45:17.162 UTC client backend[46006] pg_regress/generated_virtual ERROR: permission denied for function gf1 2025-11-30 18:45:17.162 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: SELECT gf1(10); 2025-11-30 18:45:17.165 UTC client backend[46008] fdw_retry_check LOG: disconnection: session time: 0:00:00.432 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.167 UTC client backend[46009] fdw_692c90b2.ae34 LOG: disconnection: session time: 0:00:00.369 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.169 UTC parallel worker[46052] LOG: process 46052 still waiting for ShareLock on advisory lock [16387,0,1,1] after 11.070 ms 2025-11-30 18:45:17.169 UTC parallel worker[46052] DETAIL: Process holding the lock: 46042. Wait queue: 46046, 46051, 46052. 2025-11-30 18:45:17.169 UTC parallel worker[46052] CONTEXT: waiting for ShareLock on advisory lock [16387,0,1,1] 2025-11-30 18:45:17.169 UTC parallel worker[46052] STATEMENT: SET debug_parallel_query = on; SET parallel_setup_cost = 0; SET parallel_tuple_cost = 0; SET min_parallel_table_scan_size = 0; SET parallel_leader_participation = off; SET max_parallel_workers_per_gather = 3; SELECT sum(lock_share(1,x)) FROM bigt; SET debug_parallel_query = off; RESET parallel_setup_cost; RESET parallel_tuple_cost; SELECT lock_share(3,x) FROM bigt LIMIT 1; 2025-11-30 18:45:17.169 UTC client backend[46005] pg_regress/without_overlaps ERROR: column "valid_at" is in a primary key 2025-11-30 18:45:17.169 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 ALTER COLUMN valid_at DROP NOT NULL; 2025-11-30 18:45:17.170 UTC parallel worker[46051] LOG: process 46051 avoided deadlock for ShareLock on advisory lock [16387,0,1,1] by rearranging queue order after 13.759 ms 2025-11-30 18:45:17.170 UTC parallel worker[46051] DETAIL: Process holding the lock: 46042. Wait queue: 46046, 46051, 46052. 2025-11-30 18:45:17.170 UTC parallel worker[46051] CONTEXT: waiting for ShareLock on advisory lock [16387,0,1,1] 2025-11-30 18:45:17.170 UTC parallel worker[46051] STATEMENT: SET debug_parallel_query = on; SET parallel_setup_cost = 0; SET parallel_tuple_cost = 0; SET min_parallel_table_scan_size = 0; SET parallel_leader_participation = off; SET max_parallel_workers_per_gather = 3; SELECT sum(lock_share(1,x)) FROM bigt; SET debug_parallel_query = off; RESET parallel_setup_cost; RESET parallel_tuple_cost; SELECT lock_share(3,x) FROM bigt LIMIT 1; 2025-11-30 18:45:17.170 UTC parallel worker[46051] LOG: process 46051 still waiting for ShareLock on advisory lock [16387,0,1,1] after 13.759 ms 2025-11-30 18:45:17.170 UTC parallel worker[46051] DETAIL: Process holding the lock: 46042. Wait queue: 46046, 46051, 46052. 2025-11-30 18:45:17.170 UTC parallel worker[46051] CONTEXT: waiting for ShareLock on advisory lock [16387,0,1,1] 2025-11-30 18:45:17.170 UTC parallel worker[46051] STATEMENT: SET debug_parallel_query = on; SET parallel_setup_cost = 0; SET parallel_tuple_cost = 0; SET min_parallel_table_scan_size = 0; SET parallel_leader_participation = off; SET max_parallel_workers_per_gather = 3; SELECT sum(lock_share(1,x)) FROM bigt; SET debug_parallel_query = off; RESET parallel_setup_cost; RESET parallel_tuple_cost; SELECT lock_share(3,x) FROM bigt LIMIT 1; 2025-11-30 18:45:17.177 UTC client backend[44596] pg_regress/postgres_fdw ERROR: invalid value for string option "analyze_sampling": invalid 2025-11-30 18:45:17.177 UTC client backend[44596] pg_regress/postgres_fdw STATEMENT: ALTER SERVER loopback OPTIONS (analyze_sampling 'invalid'); 2025-11-30 18:45:17.178 UTC unrecognized[46053] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.178 UTC client backend[46053] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.178 UTC client backend[46053] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual ERROR: new row for relation "gtest20" violates check constraint "gtest20_b_check" 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (30, virtual). 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest20 (a) VALUES (30); 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual ERROR: ALTER TABLE / SET EXPRESSION is not supported for virtual generated columns in tables with check constraints 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest20" is a virtual generated column. 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20 ALTER COLUMN b SET EXPRESSION AS (a * 100); 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual ERROR: ALTER TABLE / SET EXPRESSION is not supported for virtual generated columns in tables with check constraints 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest20" is a virtual generated column. 2025-11-30 18:45:17.179 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20 ALTER COLUMN b SET EXPRESSION AS (a * 3); 2025-11-30 18:45:17.179 UTC client backend[46053] fdw_retry_check LOG: connection ready: setup total=2.075 ms, fork=0.711 ms, authentication=0.121 ms 2025-11-30 18:45:17.183 UTC client backend[46006] pg_regress/generated_virtual ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-11-30 18:45:17.183 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20a ADD CHECK (b < 50); 2025-11-30 18:45:17.185 UTC client backend[46053] fdw_retry_check LOG: disconnection: session time: 0:00:00.006 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.185 UTC client backend[46006] pg_regress/generated_virtual ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-11-30 18:45:17.185 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20a ADD COLUMN c float8 DEFAULT random() CHECK (b < 50); 2025-11-30 18:45:17.188 UTC parallel worker[46052] LOG: process 46052 acquired ShareLock on advisory lock [16387,0,1,1] after 29.576 ms 2025-11-30 18:45:17.188 UTC parallel worker[46052] CONTEXT: waiting for ShareLock on advisory lock [16387,0,1,1] 2025-11-30 18:45:17.188 UTC parallel worker[46052] STATEMENT: SET debug_parallel_query = on; SET parallel_setup_cost = 0; SET parallel_tuple_cost = 0; SET min_parallel_table_scan_size = 0; SET parallel_leader_participation = off; SET max_parallel_workers_per_gather = 3; SELECT sum(lock_share(1,x)) FROM bigt; SET debug_parallel_query = off; RESET parallel_setup_cost; RESET parallel_tuple_cost; SELECT lock_share(3,x) FROM bigt LIMIT 1; 2025-11-30 18:45:17.188 UTC parallel worker[46051] LOG: process 46051 acquired ShareLock on advisory lock [16387,0,1,1] after 30.412 ms 2025-11-30 18:45:17.188 UTC parallel worker[46051] CONTEXT: waiting for ShareLock on advisory lock [16387,0,1,1] 2025-11-30 18:45:17.188 UTC parallel worker[46051] STATEMENT: SET debug_parallel_query = on; SET parallel_setup_cost = 0; SET parallel_tuple_cost = 0; SET min_parallel_table_scan_size = 0; SET parallel_leader_participation = off; SET max_parallel_workers_per_gather = 3; SELECT sum(lock_share(1,x)) FROM bigt; SET debug_parallel_query = off; RESET parallel_setup_cost; RESET parallel_tuple_cost; SELECT lock_share(3,x) FROM bigt LIMIT 1; 2025-11-30 18:45:17.194 UTC client backend[46006] pg_regress/generated_virtual ERROR: check constraint "chk" of relation "gtest20b" is violated by some row 2025-11-30 18:45:17.194 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20b VALIDATE CONSTRAINT chk; 2025-11-30 18:45:17.196 UTC client backend[46003] pg_regress/merge ERROR: new row violates row-level security policy for table "pa_target" 2025-11-30 18:45:17.196 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO pa_target t USING pa_source s ON t.tid = s.sid AND t.tid IN (1,2,3,4) WHEN MATCHED THEN UPDATE SET tid = tid - 1; 2025-11-30 18:45:17.197 UTC client backend[46006] pg_regress/generated_virtual ERROR: new row for relation "gtest20c" violates check constraint "whole_row_check" 2025-11-30 18:45:17.197 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (null, virtual). 2025-11-30 18:45:17.197 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest20c VALUES (NULL); 2025-11-30 18:45:17.200 UTC client backend[46006] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21a" violates not-null constraint 2025-11-30 18:45:17.200 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-11-30 18:45:17.200 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21a (a) VALUES (0); 2025-11-30 18:45:17.200 UTC unrecognized[46054] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.203 UTC client backend[46006] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21ax" violates not-null constraint 2025-11-30 18:45:17.203 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-11-30 18:45:17.203 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21ax (a) VALUES (0); 2025-11-30 18:45:17.205 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "b" of relation "gtest21ax" contains null values 2025-11-30 18:45:17.205 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest21ax ALTER COLUMN b SET EXPRESSION AS (nullif(a, 1)); 2025-11-30 18:45:17.210 UTC client backend[46006] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21ax" violates not-null constraint 2025-11-30 18:45:17.210 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-11-30 18:45:17.210 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21ax (a) VALUES (0); 2025-11-30 18:45:17.212 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for operator class "text_pattern_ops" 2025-11-30 18:45:17.212 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX ON test3ci (x text_pattern_ops); 2025-11-30 18:45:17.215 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for ILIKE 2025-11-30 18:45:17.215 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3ci WHERE x ILIKE 'a%'; 2025-11-30 18:45:17.216 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-11-30 18:45:17.216 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3ci WHERE x SIMILAR TO 'a%'; 2025-11-30 18:45:17.216 UTC client backend[46054] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.216 UTC client backend[46054] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:17.216 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-11-30 18:45:17.216 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3ci WHERE x ~ 'a'; 2025-11-30 18:45:17.216 UTC client backend[46043] isolation/deadlock-parallel/d2 LOG: disconnection: session time: 0:00:00.160 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.216 UTC client backend[46042] isolation/deadlock-parallel/d1 LOG: disconnection: session time: 0:00:00.164 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.217 UTC client backend[46054] fdw_retry_check LOG: connection ready: setup total=17.251 ms, fork=0.583 ms, authentication=0.135 ms 2025-11-30 18:45:17.217 UTC client backend[46041] isolation/deadlock-parallel/control connection LOG: disconnection: session time: 0:00:00.168 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.218 UTC client backend[46044] isolation/deadlock-parallel/e1 LOG: disconnection: session time: 0:00:00.157 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.219 UTC client backend[46045] isolation/deadlock-parallel/e2 LOG: disconnection: session time: 0:00:00.153 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.223 UTC client backend[46006] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21b" violates not-null constraint 2025-11-30 18:45:17.223 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-11-30 18:45:17.223 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21b (a) VALUES (2), (0); 2025-11-30 18:45:17.223 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: duplicate key value violates unique constraint "test1ci_x_idx" 2025-11-30 18:45:17.223 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(ABC) already exists. 2025-11-30 18:45:17.223 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: INSERT INTO test1ci VALUES ('ABC'); 2025-11-30 18:45:17.223 UTC client backend[46006] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21b" violates not-null constraint 2025-11-30 18:45:17.223 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (null, virtual). 2025-11-30 18:45:17.223 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21b (a) VALUES (NULL); 2025-11-30 18:45:17.224 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not create unique index "test3ci_x_idx" 2025-11-30 18:45:17.224 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(abc) is duplicated. 2025-11-30 18:45:17.224 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE UNIQUE INDEX ON test3ci (x); 2025-11-30 18:45:17.229 UTC unrecognized[46057] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.229 UTC client backend[46057] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.229 UTC client backend[46057] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-1 2025-11-30 18:45:17.230 UTC client backend[46057] isolation/detach-partition-concurrently-1 LOG: connection ready: setup total=2.023 ms, fork=0.533 ms, authentication=0.120 ms 2025-11-30 18:45:17.232 UTC unrecognized[46058] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.232 UTC client backend[46058] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.232 UTC client backend[46058] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-1 2025-11-30 18:45:17.233 UTC client backend[46006] pg_regress/generated_virtual ERROR: null value in column "f3" of relation "gtestnn_child" violates not-null constraint 2025-11-30 18:45:17.233 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (1, 2, virtual). 2025-11-30 18:45:17.233 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtestnn_parent VALUES (1, 2, default); 2025-11-30 18:45:17.233 UTC client backend[46058] isolation/detach-partition-concurrently-1 LOG: connection ready: setup total=2.235 ms, fork=0.490 ms, authentication=0.144 ms 2025-11-30 18:45:17.233 UTC client backend[46006] pg_regress/generated_virtual ERROR: null value in column "f3" of relation "gtestnn_child" violates not-null constraint 2025-11-30 18:45:17.233 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Failing row contains (2, 10, virtual). 2025-11-30 18:45:17.233 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtestnn_parent VALUES (2, 10, default); 2025-11-30 18:45:17.233 UTC client backend[46054] fdw_retry_check LOG: disconnection: session time: 0:00:00.033 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.236 UTC unrecognized[46059] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.236 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "f3" of relation "gtestnn_child" contains null values 2025-11-30 18:45:17.236 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestnn_parent ALTER COLUMN f3 SET EXPRESSION AS (nullif(f1, 2) + nullif(f2, 11)); 2025-11-30 18:45:17.236 UTC client backend[46059] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.236 UTC client backend[46059] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:17.237 UTC client backend[46059] fdw_retry_check LOG: connection ready: setup total=1.941 ms, fork=0.580 ms, authentication=0.124 ms 2025-11-30 18:45:17.243 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "c" of relation "gtestnn_childdef" contains null values 2025-11-30 18:45:17.243 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestnn_parent ADD COLUMN c int NOT NULL GENERATED ALWAYS AS (nullif(f1, 14) + nullif(f2, 10)) VIRTUAL; 2025-11-30 18:45:17.243 UTC unrecognized[46060] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.243 UTC client backend[46059] fdw_retry_check LOG: disconnection: session time: 0:00:00.007 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.244 UTC client backend[46060] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.244 UTC client backend[46060] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-1 2025-11-30 18:45:17.245 UTC client backend[46060] isolation/detach-partition-concurrently-1 LOG: connection ready: setup total=5.389 ms, fork=3.701 ms, authentication=0.134 ms 2025-11-30 18:45:17.247 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for operator class "bpchar_pattern_ops" 2025-11-30 18:45:17.247 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX ON test3bpci (x bpchar_pattern_ops); 2025-11-30 18:45:17.249 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "c" of relation "gtestnn_child" contains null values 2025-11-30 18:45:17.249 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestnn_parent ADD COLUMN c int NOT NULL GENERATED ALWAYS AS (nullif(f1, 13) + nullif(f2, 5)) VIRTUAL; 2025-11-30 18:45:17.249 UTC unrecognized[46061] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.250 UTC client backend[46061] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.250 UTC client backend[46061] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-1 2025-11-30 18:45:17.251 UTC client backend[46061] isolation/detach-partition-concurrently-1 LOG: connection ready: setup total=3.527 ms, fork=1.962 ms, authentication=0.129 ms 2025-11-30 18:45:17.256 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.256 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.256 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.256 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.257 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.257 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.258 UTC client backend[46006] pg_regress/generated_virtual ERROR: unique constraints on virtual generated columns are not supported 2025-11-30 18:45:17.258 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest22a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a / 2) VIRTUAL UNIQUE); 2025-11-30 18:45:17.260 UTC client backend[46006] pg_regress/generated_virtual ERROR: primary keys on virtual generated columns are not supported 2025-11-30 18:45:17.260 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest22b (a int, b int GENERATED ALWAYS AS (a / 2) VIRTUAL, PRIMARY KEY (a, b)); 2025-11-30 18:45:17.261 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for ILIKE 2025-11-30 18:45:17.261 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3bpci WHERE x ILIKE 'a%'; 2025-11-30 18:45:17.261 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-11-30 18:45:17.261 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3bpci WHERE x SIMILAR TO 'a%'; 2025-11-30 18:45:17.262 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-11-30 18:45:17.262 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3bpci WHERE x ~ 'a'; 2025-11-30 18:45:17.264 UTC client backend[46003] pg_regress/merge ERROR: no partition of relation "pa_target" found for row 2025-11-30 18:45:17.264 UTC client backend[46003] pg_regress/merge DETAIL: Partition key of the failing row contains (tid) = (1). 2025-11-30 18:45:17.264 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO pa_target t USING pa_source s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT VALUES (s.sid); 2025-11-30 18:45:17.266 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: duplicate key value violates unique constraint "test1bpci_x_idx" 2025-11-30 18:45:17.266 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(ABC) already exists. 2025-11-30 18:45:17.266 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: INSERT INTO test1bpci VALUES ('ABC'); 2025-11-30 18:45:17.267 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: could not create unique index "test3bpci_x_idx" 2025-11-30 18:45:17.267 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(abc) is duplicated. 2025-11-30 18:45:17.267 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE UNIQUE INDEX ON test3bpci (x); 2025-11-30 18:45:17.267 UTC client backend[46006] pg_regress/generated_virtual ERROR: invalid ON UPDATE action for foreign key constraint containing generated column 2025-11-30 18:45:17.267 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23x (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL REFERENCES gtest23a (x) ON UPDATE CASCADE); 2025-11-30 18:45:17.270 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.270 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.271 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.271 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.271 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.271 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.272 UTC unrecognized[46062] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.272 UTC client backend[46062] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.272 UTC client backend[46062] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:17.273 UTC client backend[46006] pg_regress/generated_virtual ERROR: invalid ON DELETE action for foreign key constraint containing generated column 2025-11-30 18:45:17.273 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23x (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL REFERENCES gtest23a (x) ON DELETE SET NULL); 2025-11-30 18:45:17.273 UTC client backend[46062] fdw_retry_check LOG: connection ready: setup total=3.216 ms, fork=1.657 ms, authentication=0.140 ms 2025-11-30 18:45:17.274 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.274 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal_rng_pk DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.275 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.275 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT ON CONSTRAINT temporal_rng_pk DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.276 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.276 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal_rng_pk DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.276 UTC client backend[46006] pg_regress/generated_virtual ERROR: foreign key constraints on virtual generated columns are not supported 2025-11-30 18:45:17.276 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL REFERENCES gtest23a (x)); 2025-11-30 18:45:17.278 UTC client backend[46006] pg_regress/generated_virtual ERROR: primary keys on virtual generated columns are not supported 2025-11-30 18:45:17.278 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23p (x int, y int GENERATED ALWAYS AS (x * 2) VIRTUAL, PRIMARY KEY (y)); 2025-11-30 18:45:17.280 UTC client backend[46006] pg_regress/generated_virtual ERROR: relation "gtest23p" does not exist 2025-11-30 18:45:17.280 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23q (a int PRIMARY KEY, b int REFERENCES gtest23p (y)); 2025-11-30 18:45:17.281 UTC client backend[46062] fdw_retry_check LOG: disconnection: session time: 0:00:00.009 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.282 UTC client backend[46006] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-11-30 18:45:17.282 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24 (a int PRIMARY KEY, b gtestdomain1 GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-11-30 18:45:17.285 UTC client backend[46006] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-11-30 18:45:17.285 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24r (a int PRIMARY KEY, b gtestdomain1range GENERATED ALWAYS AS (gtestdomain1range(a, a + 5)) VIRTUAL); 2025-11-30 18:45:17.287 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.287 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.287 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.287 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.287 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.287 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.289 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: LIKE pattern must not end with escape character 2025-11-30 18:45:17.289 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT 'foox' LIKE 'foo\' COLLATE ignore_accents; 2025-11-30 18:45:17.291 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.291 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.291 UTC client backend[46006] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-11-30 18:45:17.291 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest24at ADD COLUMN b gtestdomain1 GENERATED ALWAYS AS (a * 2) VIRTUAL; 2025-11-30 18:45:17.291 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.291 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.292 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.292 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.292 UTC unrecognized[46063] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.293 UTC client backend[46063] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.293 UTC client backend[46063] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_retry_check 2025-11-30 18:45:17.294 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: foreign key constraint "test10fk_x_fkey" cannot be implemented 2025-11-30 18:45:17.294 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: Key columns "x" of the referencing table and "x" of the referenced table have incompatible collations: "case_insensitive" and "case_sensitive". If either collation is nondeterministic, then both collations have to be the same. 2025-11-30 18:45:17.294 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE test10fk (x text COLLATE case_insensitive REFERENCES test10pk (x) ON UPDATE CASCADE ON DELETE CASCADE); 2025-11-30 18:45:17.295 UTC client backend[46063] fdw_retry_check LOG: connection ready: setup total=3.471 ms, fork=0.834 ms, authentication=0.133 ms 2025-11-30 18:45:17.297 UTC client backend[46006] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-11-30 18:45:17.297 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest24ata ALTER COLUMN b TYPE gtestdomain1; 2025-11-30 18:45:17.298 UTC client backend[46006] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-11-30 18:45:17.298 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24nn (a int, b gtestdomainnn GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-11-30 18:45:17.298 UTC client backend[46006] pg_regress/generated_virtual ERROR: generation expression uses user-defined type at character 85 2025-11-30 18:45:17.298 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Virtual generated columns that make use of user-defined types are not yet supported. 2025-11-30 18:45:17.298 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24xxx (a gtestdomain1, b gtestdomain1, c int GENERATED ALWAYS AS (greatest(a, b)) VIRTUAL); 2025-11-30 18:45:17.299 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: foreign key constraint "test11fk_x_fkey" cannot be implemented 2025-11-30 18:45:17.299 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: Key columns "x" of the referencing table and "x" of the referenced table have incompatible collations: "case_sensitive" and "case_insensitive". If either collation is nondeterministic, then both collations have to be the same. 2025-11-30 18:45:17.299 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE test11fk (x text COLLATE case_sensitive REFERENCES test11pk (x) ON UPDATE CASCADE ON DELETE CASCADE); 2025-11-30 18:45:17.301 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.301 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal3_uq DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.301 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.301 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT ON CONSTRAINT temporal3_uq DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.301 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.301 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal3_uq DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.301 UTC client backend[46006] pg_regress/generated_virtual ERROR: generated columns are not supported on typed tables 2025-11-30 18:45:17.301 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest28 OF gtest_type (f1 WITH OPTIONS GENERATED ALWAYS AS (f2 *2) VIRTUAL); 2025-11-30 18:45:17.308 UTC client backend[46063] fdw_retry_check LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.310 UTC client backend[45991] pg_regress/create_table_like ERROR: inherited column "a" has a storage parameter conflict 2025-11-30 18:45:17.310 UTC client backend[45991] pg_regress/create_table_like DETAIL: MAIN versus EXTENDED 2025-11-30 18:45:17.310 UTC client backend[45991] pg_regress/create_table_like STATEMENT: CREATE TABLE inh_error1 () INHERITS (ctlt1, ctlt4); 2025-11-30 18:45:17.310 UTC client backend[45991] pg_regress/create_table_like ERROR: column "a" has a storage parameter conflict 2025-11-30 18:45:17.310 UTC client backend[45991] pg_regress/create_table_like DETAIL: MAIN versus EXTENDED 2025-11-30 18:45:17.310 UTC client backend[45991] pg_regress/create_table_like STATEMENT: CREATE TABLE inh_error2 (LIKE ctlt4 INCLUDING STORAGE) INHERITS (ctlt1); 2025-11-30 18:45:17.312 UTC unrecognized[46064] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.313 UTC client backend[46064] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.313 UTC client backend[46064] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_conn_check 2025-11-30 18:45:17.314 UTC client backend[46064] fdw_conn_check LOG: connection ready: setup total=2.676 ms, fork=0.559 ms, authentication=0.142 ms 2025-11-30 18:45:17.315 UTC client backend[46006] pg_regress/generated_virtual ERROR: child column "f3" specifies generation expression 2025-11-30 18:45:17.315 UTC client backend[46006] pg_regress/generated_virtual HINT: A child table column cannot be generated unless its parent column is. 2025-11-30 18:45:17.315 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child PARTITION OF gtest_parent ( f3 WITH OPTIONS GENERATED ALWAYS AS (f2 * 2) VIRTUAL ) FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-11-30 18:45:17.317 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "f3" in child table must not be a generated column 2025-11-30 18:45:17.317 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-11-30 18:45:17.319 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.319 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.320 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: update or delete on table "test12pk" violates RESTRICT setting of foreign key constraint "test12fk_b_fkey" on table "test12fk" 2025-11-30 18:45:17.320 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(abc) is referenced from table "test12fk". 2025-11-30 18:45:17.320 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: UPDATE test12pk SET x = 'ABC' WHERE x = 'abc'; 2025-11-30 18:45:17.321 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.321 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.322 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.322 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.331 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "f3" inherits from generated column but specifies default 2025-11-30 18:45:17.331 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 DEFAULT 42 -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:17.331 UTC client backend[46006] pg_regress/generated_virtual ERROR: identity columns are not supported on partitions 2025-11-30 18:45:17.331 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 WITH OPTIONS GENERATED ALWAYS AS IDENTITY -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:17.331 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "f3" inherits from generated column of different kind 2025-11-30 18:45:17.331 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Parent column is VIRTUAL, child column is STORED. 2025-11-30 18:45:17.331 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 GENERATED ALWAYS AS (f2 * 2) STORED -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:17.333 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "f3" in child table must be a generated column 2025-11-30 18:45:17.333 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:17.333 UTC client backend[46064] fdw_conn_check FATAL: terminating connection due to administrator command 2025-11-30 18:45:17.333 UTC client backend[46064] fdw_conn_check LOG: disconnection: session time: 0:00:00.021 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.336 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "f3" in child table must be a generated column 2025-11-30 18:45:17.336 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:17.337 UTC client backend[44596] pg_regress/postgres_fdw LOG: disconnection: session time: 0:00:10.758 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.341 UTC client backend[46006] pg_regress/generated_virtual ERROR: table "gtest_child3" being attached contains an identity column "f3" 2025-11-30 18:45:17.341 UTC client backend[46006] pg_regress/generated_virtual DETAIL: The new partition may not contain an identity column. 2025-11-30 18:45:17.341 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:17.341 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.341 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.342 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.342 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.343 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.343 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.345 UTC unrecognized[46067] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.345 UTC client backend[46067] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.345 UTC client backend[46067] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=pg_regress/query_cancel 2025-11-30 18:45:17.346 UTC client backend[46067] pg_regress/query_cancel LOG: connection ready: setup total=2.526 ms, fork=0.354 ms, authentication=0.121 ms 2025-11-30 18:45:17.347 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "f3" inherits from generated column of different kind 2025-11-30 18:45:17.347 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Parent column is VIRTUAL, child column is STORED. 2025-11-30 18:45:17.347 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-11-30 18:45:17.350 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.350 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng_pk DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.352 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.352 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng_pk DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.352 UTC unrecognized[46068] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.353 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.353 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng_pk DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.354 UTC client backend[46068] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.354 UTC client backend[46068] [unknown] LOG: connection authorized: user=postgres database=regression_postgres_fdw application_name=fdw_conn_check 2025-11-30 18:45:17.354 UTC client backend[46068] fdw_conn_check LOG: connection ready: setup total=3.581 ms, fork=1.538 ms, authentication=0.120 ms 2025-11-30 18:45:17.360 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.360 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.360 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.360 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.360 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.360 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-11-30 18:45:17.364 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.364 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.365 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.365 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.365 UTC client backend[46005] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-30 18:45:17.365 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.367 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.367 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng3_uq DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-11-30 18:45:17.368 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.368 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng3_uq DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-11-30 18:45:17.368 UTC client backend[46005] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-11-30 18:45:17.368 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng3_uq DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-11-30 18:45:17.383 UTC client backend[46005] pg_regress/without_overlaps ERROR: cannot drop column valid_at of table temporal3 because other objects depend on it 2025-11-30 18:45:17.383 UTC client backend[46005] pg_regress/without_overlaps DETAIL: constraint temporal_fk_rng2rng_fk on table temporal_fk_rng2rng depends on column valid_at of table temporal3 2025-11-30 18:45:17.383 UTC client backend[46005] pg_regress/without_overlaps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:17.383 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 DROP COLUMN valid_at; 2025-11-30 18:45:17.397 UTC client backend[46067] pg_regress/query_cancel ERROR: canceling statement due to statement timeout 2025-11-30 18:45:17.397 UTC client backend[46067] pg_regress/query_cancel STATEMENT: SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d; 2025-11-30 18:45:17.398 UTC unrecognized[46069] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.398 UTC client backend[46068] fdw_conn_check ERROR: canceling statement due to user request 2025-11-30 18:45:17.398 UTC client backend[46068] fdw_conn_check STATEMENT: FETCH 100 FROM c2 2025-11-30 18:45:17.400 UTC client backend[46067] pg_regress/query_cancel LOG: disconnection: session time: 0:00:00.056 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.401 UTC client backend[46068] fdw_conn_check LOG: disconnection: session time: 0:00:00.049 user=postgres database=regression_postgres_fdw host=[local] 2025-11-30 18:45:17.409 UTC client backend[45991] pg_regress/create_table_like ERROR: cannot add NO INHERIT constraint to partitioned table "noinh_con_copy1_parted" 2025-11-30 18:45:17.409 UTC client backend[45991] pg_regress/create_table_like STATEMENT: CREATE TABLE noinh_con_copy1_parted (LIKE noinh_con_copy INCLUDING ALL) PARTITION BY LIST (a); 2025-11-30 18:45:17.411 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key constraint "temporal_fk_rng2rng_fk2" cannot be implemented 2025-11-30 18:45:17.411 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key columns "valid_at" of the referencing table and "valid_at" of the referenced table are of incompatible types: int4range and daterange. 2025-11-30 18:45:17.411 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at int4range, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk2 PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk2 FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng (id, PERIOD valid_at) ); 2025-11-30 18:45:17.415 UTC client backend[45991] pg_regress/create_table_like ERROR: relation "ctlseq1" is invalid in LIKE clause at character 27 2025-11-30 18:45:17.415 UTC client backend[45991] pg_regress/create_table_like DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:17.415 UTC client backend[45991] pg_regress/create_table_like STATEMENT: CREATE TABLE ctlt10 (LIKE ctlseq1); 2025-11-30 18:45:17.417 UTC client backend[46003] pg_regress/merge ERROR: new row violates row-level security policy for table "measurement" 2025-11-30 18:45:17.417 UTC client backend[46003] pg_regress/merge STATEMENT: MERGE INTO measurement m USING (VALUES (1, '01-17-2007'::date)) nm(city_id, logdate) ON (m.city_id = nm.city_id and m.logdate=nm.logdate) WHEN NOT MATCHED THEN INSERT (city_id, logdate, peaktemp, unitsales) VALUES (city_id - 1, logdate, NULL, 100); 2025-11-30 18:45:17.425 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-11-30 18:45:17.425 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng (id, valid_at) ); 2025-11-30 18:45:17.428 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key must use PERIOD when referencing a primary key using WITHOUT OVERLAPS 2025-11-30 18:45:17.428 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_rng (id, valid_at) ); 2025-11-30 18:45:17.435 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.435 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_rng (id, PERIOD valid_at) ); 2025-11-30 18:45:17.439 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.439 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_rng ); 2025-11-30 18:45:17.443 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-11-30 18:45:17.443 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng (id) ); 2025-11-30 18:45:17.447 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.447 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id) REFERENCES temporal_rng (id, PERIOD valid_at) ); 2025-11-30 18:45:17.458 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.458 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id) REFERENCES temporal_rng ); 2025-11-30 18:45:17.460 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-11-30 18:45:17.460 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_rng (id, PERIOD id) ); 2025-11-30 18:45:17.471 UTC client backend[46003] pg_regress/merge LOG: disconnection: session time: 0:00:00.799 user=postgres database=regression host=[local] 2025-11-30 18:45:17.477 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation of DEFAULT expression conflicts with RETURNING clause at character 60 2025-11-30 18:45:17.477 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: "C" versus "case_insensitive" 2025-11-30 18:45:17.477 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT JSON_VALUE('{"a": "A"}', '$.a' RETURNING d1 DEFAULT 'C'::d2 ON EMPTY) = 'a'; 2025-11-30 18:45:17.477 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation of DEFAULT expression conflicts with RETURNING clause at character 60 2025-11-30 18:45:17.477 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: "C" versus "case_insensitive" 2025-11-30 18:45:17.477 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT JSON_VALUE('{"a": "A"}', '$.a' RETURNING d1 DEFAULT 'C' COLLATE "C" ON EMPTY) = 'a'; 2025-11-30 18:45:17.478 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation of DEFAULT expression conflicts with RETURNING clause at character 60 2025-11-30 18:45:17.478 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: "C" versus "case_insensitive" 2025-11-30 18:45:17.478 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT JSON_VALUE('{"a": "A"}', '$.c' RETURNING d1 DEFAULT 'A'::d2 ON EMPTY) = 'a'; 2025-11-30 18:45:17.478 UTC client backend[45999] pg_regress/collate.icu.utf8 ERROR: collation of DEFAULT expression conflicts with RETURNING clause at character 60 2025-11-30 18:45:17.478 UTC client backend[45999] pg_regress/collate.icu.utf8 DETAIL: "C" versus "case_insensitive" 2025-11-30 18:45:17.478 UTC client backend[45999] pg_regress/collate.icu.utf8 STATEMENT: SELECT JSON_VALUE('{"a": "A"}', '$.c' RETURNING d1 DEFAULT 'A' COLLATE "C" ON EMPTY) = 'a'; 2025-11-30 18:45:17.498 UTC client backend[45991] pg_regress/create_table_like LOG: disconnection: session time: 0:00:00.832 user=postgres database=regression host=[local] 2025-11-30 18:45:17.507 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column in partition key at character 127 2025-11-30 18:45:17.507 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:17.507 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) VIRTUAL) PARTITION BY RANGE (f3); 2025-11-30 18:45:17.508 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column in partition key at character 127 2025-11-30 18:45:17.508 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:17.508 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) VIRTUAL) PARTITION BY RANGE ((f3)); 2025-11-30 18:45:17.509 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column in partition key at character 127 2025-11-30 18:45:17.509 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:17.509 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) VIRTUAL) PARTITION BY RANGE ((f3 * 3)); 2025-11-30 18:45:17.510 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column in partition key at character 127 2025-11-30 18:45:17.510 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:17.510 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) VIRTUAL) PARTITION BY RANGE ((gtest_part_key)); 2025-11-30 18:45:17.511 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column in partition key at character 127 2025-11-30 18:45:17.511 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "f3" is a generated column. 2025-11-30 18:45:17.511 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) VIRTUAL) PARTITION BY RANGE ((gtest_part_key is not null)); 2025-11-30 18:45:17.515 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot use generated column "b" in column generation expression 2025-11-30 18:45:17.515 UTC client backend[46006] pg_regress/generated_virtual DETAIL: A generated column cannot reference another generated column. 2025-11-30 18:45:17.515 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (b * 4) VIRTUAL; 2025-11-30 18:45:17.516 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "z" does not exist 2025-11-30 18:45:17.516 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (z * 4) VIRTUAL; 2025-11-30 18:45:17.519 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key constraint "temporal_fk_rng2rng_fk" cannot be implemented 2025-11-30 18:45:17.519 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key columns "valid_at" of the referencing table and "valid_at" of the referenced table are of incompatible types: tsrange and daterange. 2025-11-30 18:45:17.519 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng; 2025-11-30 18:45:17.527 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-11-30 18:45:17.527 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk2 FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_rng (id, PERIOD id); 2025-11-30 18:45:17.528 UTC client backend[46061] isolation/detach-partition-concurrently-1/s3 ERROR: no partition of relation "d_listp" found for row 2025-11-30 18:45:17.528 UTC client backend[46061] isolation/detach-partition-concurrently-1/s3 DETAIL: Partition key of the failing row contains (a) = (2). 2025-11-30 18:45:17.528 UTC client backend[46061] isolation/detach-partition-concurrently-1/s3 STATEMENT: INSERT INTO d_listp VALUES (2); 2025-11-30 18:45:17.534 UTC client backend[45999] pg_regress/collate.icu.utf8 LOG: disconnection: session time: 0:00:00.862 user=postgres database=regression host=[local] 2025-11-30 18:45:17.535 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot alter type of a column used by a generated column 2025-11-30 18:45:17.535 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "a" is used by generated column "x". 2025-11-30 18:45:17.535 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE text; 2025-11-30 18:45:17.538 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-11-30 18:45:17.538 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2018-01-02,2018-04-01)) is not present in table "temporal_rng". 2025-11-30 18:45:17.538 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng; 2025-11-30 18:45:17.542 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-11-30 18:45:17.542 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2018-01-02,2018-04-01)) is not present in table "temporal_rng". 2025-11-30 18:45:17.542 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_fk_rng2rng (id, valid_at, parent_id) VALUES ('[2,3)', daterange('2018-01-02', '2018-04-01'), '[1,2)'); 2025-11-30 18:45:17.545 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot specify USING when altering type of generated column at character 34 2025-11-30 18:45:17.545 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "x" is a generated column. 2025-11-30 18:45:17.545 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x TYPE boolean USING x <> 0; 2025-11-30 18:45:17.545 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "x" of relation "gtest27" is a generated column 2025-11-30 18:45:17.545 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x DROP DEFAULT; 2025-11-30 18:45:17.545 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-11-30 18:45:17.545 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2018-01-02,2018-05-01)) is not present in table "temporal_rng". 2025-11-30 18:45:17.545 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_rng2rng SET valid_at = daterange('2018-01-02', '2018-05-01') WHERE id = '[1,2)'; 2025-11-30 18:45:17.546 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-11-30 18:45:17.546 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([8,9), [2018-01-02,2018-02-20)) is not present in table "temporal_rng". 2025-11-30 18:45:17.546 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_rng2rng SET parent_id = '[8,9)' WHERE id = '[1,2)'; 2025-11-30 18:45:17.548 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "x" of relation "gtest27" contains null values 2025-11-30 18:45:17.548 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 DROP COLUMN x, ALTER COLUMN a TYPE bigint, ALTER COLUMN b TYPE bigint, ADD COLUMN x bigint GENERATED ALWAYS AS ((a + b) * 2) VIRTUAL NOT NULL; 2025-11-30 18:45:17.549 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.549 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.549 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-11-30 18:45:17.559 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot alter type of a column used by a generated column 2025-11-30 18:45:17.559 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "a" is used by generated column "x". 2025-11-30 18:45:17.559 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE float8, ALTER COLUMN b TYPE float8; 2025-11-30 18:45:17.566 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.566 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-03-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.566 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[2,3)', valid_at = daterange('2018-01-15', '2018-03-01') WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-11-30 18:45:17.567 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.567 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-03-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.567 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[2,3)' WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-11-30 18:45:17.570 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.570 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.570 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET valid_at = daterange('2016-01-01', '2016-02-01') WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-11-30 18:45:17.572 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.572 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.572 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-11-30 18:45:17.573 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.573 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.573 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[7,8)' WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-11-30 18:45:17.575 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "a" of relation "gtest29" is not a generated column 2025-11-30 18:45:17.575 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a SET EXPRESSION AS (a * 3); 2025-11-30 18:45:17.575 UTC client backend[46006] pg_regress/generated_virtual ERROR: column "a" of relation "gtest29" is not a generated column 2025-11-30 18:45:17.575 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a DROP EXPRESSION; 2025-11-30 18:45:17.578 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.578 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON UPDATE RESTRICT; 2025-11-30 18:45:17.584 UTC client backend[46006] pg_regress/generated_virtual ERROR: ALTER TABLE / DROP EXPRESSION is not supported for virtual generated columns 2025-11-30 18:45:17.584 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest29" is a virtual generated column. 2025-11-30 18:45:17.584 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest29 ALTER COLUMN b DROP EXPRESSION; 2025-11-30 18:45:17.584 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-11-30 18:45:17.584 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:17.584 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest29 (a, b) VALUES (6, 66); 2025-11-30 18:45:17.587 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.587 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.587 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_rng WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-11-30 18:45:17.589 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-11-30 18:45:17.589 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-11-30 18:45:17.589 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-11-30 18:45:17.594 UTC client backend[46006] pg_regress/generated_virtual ERROR: ALTER TABLE / DROP EXPRESSION is not supported for virtual generated columns 2025-11-30 18:45:17.594 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest30" is a virtual generated column. 2025-11-30 18:45:17.594 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest30 ALTER COLUMN b DROP EXPRESSION; 2025-11-30 18:45:17.594 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON DELETE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.594 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE RESTRICT; 2025-11-30 18:45:17.596 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.596 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE CASCADE ON UPDATE CASCADE; 2025-11-30 18:45:17.597 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.597 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE SET NULL ON UPDATE SET NULL; 2025-11-30 18:45:17.600 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.600 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ALTER COLUMN parent_id SET DEFAULT '[-1,-1]', ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE SET DEFAULT ON UPDATE SET DEFAULT; 2025-11-30 18:45:17.608 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key constraint "temporal_fk_mltrng2mltrng_fk2" cannot be implemented 2025-11-30 18:45:17.608 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key columns "valid_at" of the referencing table and "valid_at" of the referenced table are of incompatible types: int4multirange and datemultirange. 2025-11-30 18:45:17.608 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at int4multirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk2 PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk2 FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at) ); 2025-11-30 18:45:17.613 UTC client backend[46006] pg_regress/generated_virtual ERROR: ALTER TABLE / DROP EXPRESSION must be applied to child tables too 2025-11-30 18:45:17.613 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE ONLY gtest30 ALTER COLUMN b DROP EXPRESSION; 2025-11-30 18:45:17.618 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-11-30 18:45:17.618 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, valid_at) ); 2025-11-30 18:45:17.621 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key must use PERIOD when referencing a primary key using WITHOUT OVERLAPS 2025-11-30 18:45:17.621 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_mltrng (id, valid_at) ); 2025-11-30 18:45:17.624 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.624 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at) ); 2025-11-30 18:45:17.627 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.627 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_mltrng ); 2025-11-30 18:45:17.628 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot drop generation expression from inherited column 2025-11-30 18:45:17.628 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest30_1 ALTER COLUMN b DROP EXPRESSION; 2025-11-30 18:45:17.630 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-11-30 18:45:17.630 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id) ); 2025-11-30 18:45:17.631 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-11-30 18:45:17.631 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-11-30 18:45:17.633 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.633 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id) REFERENCES temporal_mltrng (id, PERIOD valid_at) ); 2025-11-30 18:45:17.643 UTC client backend[46006] pg_regress/generated_virtual ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-11-30 18:45:17.643 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-11-30 18:45:17.644 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-11-30 18:45:17.644 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id) REFERENCES temporal_mltrng ); 2025-11-30 18:45:17.647 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-11-30 18:45:17.647 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_mltrng (id, PERIOD id) ); 2025-11-30 18:45:17.649 UTC client backend[46006] pg_regress/generated_virtual ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-11-30 18:45:17.649 UTC client backend[46006] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-11-30 18:45:17.649 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TRIGGER gtest2a BEFORE INSERT OR UPDATE ON gtest26 FOR EACH ROW WHEN (NEW.b < 0) -- error EXECUTE PROCEDURE gtest_trigger_func(); 2025-11-30 18:45:17.649 UTC client backend[46006] pg_regress/generated_virtual ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-11-30 18:45:17.649 UTC client backend[46006] pg_regress/generated_virtual DETAIL: A whole-row reference is used and the table contains generated columns. 2025-11-30 18:45:17.649 UTC client backend[46006] pg_regress/generated_virtual STATEMENT: CREATE TRIGGER gtest2b BEFORE INSERT OR UPDATE ON gtest26 FOR EACH ROW WHEN (NEW.* IS NOT NULL) -- error EXECUTE PROCEDURE gtest_trigger_func(); 2025-11-30 18:45:17.690 UTC client backend[46005] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-11-30 18:45:17.690 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_mltrng2mltrng ADD CONSTRAINT temporal_fk_mltrng2mltrng_fk2 FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_mltrng (id, PERIOD id); 2025-11-30 18:45:17.699 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-11-30 18:45:17.699 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2018-01-02,2018-04-01)}) is not present in table "temporal_mltrng". 2025-11-30 18:45:17.699 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_mltrng2mltrng ADD CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at); 2025-11-30 18:45:17.704 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-11-30 18:45:17.704 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2018-01-02,2018-04-01)}) is not present in table "temporal_mltrng". 2025-11-30 18:45:17.704 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_fk_mltrng2mltrng (id, valid_at, parent_id) VALUES ('[2,3)', datemultirange(daterange('2018-01-02', '2018-04-01')), '[1,2)'); 2025-11-30 18:45:17.707 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-11-30 18:45:17.707 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2018-01-02,2018-05-01)}) is not present in table "temporal_mltrng". 2025-11-30 18:45:17.707 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_mltrng2mltrng SET valid_at = datemultirange(daterange('2018-01-02', '2018-05-01')) WHERE id = '[1,2)'; 2025-11-30 18:45:17.708 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-11-30 18:45:17.708 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([8,9), {[2018-01-02,2018-02-20)}) is not present in table "temporal_mltrng". 2025-11-30 18:45:17.708 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_mltrng2mltrng SET parent_id = '[8,9)' WHERE id = '[1,2)'; 2025-11-30 18:45:17.711 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.711 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.711 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-11-30 18:45:17.714 UTC client backend[46006] pg_regress/generated_virtual LOG: disconnection: session time: 0:00:01.033 user=postgres database=regression host=[local] 2025-11-30 18:45:17.728 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.728 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-03-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.728 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[2,3)', valid_at = datemultirange(daterange('2018-01-15', '2018-03-01')) WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-11-30 18:45:17.729 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.729 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-03-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.729 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[2,3)' WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-11-30 18:45:17.732 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.732 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.732 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET valid_at = datemultirange(daterange('2016-01-01', '2016-02-01')) WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-11-30 18:45:17.734 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.734 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.734 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-11-30 18:45:17.735 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.735 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.735 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[7,8)' WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-11-30 18:45:17.738 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.738 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_mltrng2mltrng ADD CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at) ON UPDATE RESTRICT; 2025-11-30 18:45:17.747 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.747 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.747 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_mltrng WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-11-30 18:45:17.749 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-11-30 18:45:17.749 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-11-30 18:45:17.749 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-11-30 18:45:17.778 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk" 2025-11-30 18:45:17.778 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2010-01-01,2010-02-15)) is not present in table "temporal_partitioned_rng". 2025-11-30 18:45:17.778 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_rng2rng (id, valid_at, parent_id) VALUES ('[3,4)', daterange('2010-01-01', '2010-02-15'), '[1,2)'); 2025-11-30 18:45:17.779 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk" 2025-11-30 18:45:17.779 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([3,4), [2000-01-01,2000-02-15)) is not present in table "temporal_partitioned_rng". 2025-11-30 18:45:17.779 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_rng2rng (id, valid_at, parent_id) VALUES ('[3,4)', daterange('2000-01-01', '2000-02-15'), '[3,4)'); 2025-11-30 18:45:17.784 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "tfkp1_pkey" 2025-11-30 18:45:17.784 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2000-01-01,2000-04-01)) conflicts with existing key (id, valid_at)=([1,2), [2000-01-01,2000-04-01)). 2025-11-30 18:45:17.784 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_fk_rng2rng SET valid_at = daterange('2000-01-01', '2000-04-01') WHERE id = '[1,2)'; 2025-11-30 18:45:17.795 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk_1" on table "temporal_partitioned_fk_rng2rng" 2025-11-30 18:45:17.795 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_partitioned_fk_rng2rng". 2025-11-30 18:45:17.795 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_rng SET valid_at = daterange('2016-01-01', '2016-02-01') WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-11-30 18:45:17.801 UTC client backend[46057] isolation/detach-partition-concurrently-1/control connection LOG: disconnection: session time: 0:00:00.572 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.801 UTC client backend[46058] isolation/detach-partition-concurrently-1/s1 LOG: disconnection: session time: 0:00:00.569 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.801 UTC client backend[46061] isolation/detach-partition-concurrently-1/s3 LOG: disconnection: session time: 0:00:00.552 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.802 UTC client backend[46060] isolation/detach-partition-concurrently-1/s2 LOG: disconnection: session time: 0:00:00.559 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:17.805 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk_1" on table "temporal_partitioned_fk_rng2rng" 2025-11-30 18:45:17.805 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_partitioned_fk_rng2rng". 2025-11-30 18:45:17.805 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_partitioned_rng WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-11-30 18:45:17.807 UTC unrecognized[46073] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.807 UTC client backend[46073] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.807 UTC client backend[46073] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-2 2025-11-30 18:45:17.808 UTC client backend[46073] isolation/detach-partition-concurrently-2 LOG: connection ready: setup total=1.942 ms, fork=0.457 ms, authentication=0.123 ms 2025-11-30 18:45:17.809 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.809 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_rng2rng DROP CONSTRAINT temporal_partitioned_fk_rng2rng_fk, ADD CONSTRAINT temporal_partitioned_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_rng ON DELETE CASCADE ON UPDATE CASCADE; 2025-11-30 18:45:17.810 UTC unrecognized[46074] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.810 UTC client backend[46074] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.810 UTC client backend[46074] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-2 2025-11-30 18:45:17.811 UTC client backend[46074] isolation/detach-partition-concurrently-2 LOG: connection ready: setup total=1.878 ms, fork=0.547 ms, authentication=0.103 ms 2025-11-30 18:45:17.812 UTC unrecognized[46075] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.812 UTC client backend[46075] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.812 UTC client backend[46075] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-2 2025-11-30 18:45:17.813 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.813 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_rng2rng DROP CONSTRAINT temporal_partitioned_fk_rng2rng_fk, ADD CONSTRAINT temporal_partitioned_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_rng ON DELETE SET NULL ON UPDATE SET NULL; 2025-11-30 18:45:17.813 UTC client backend[46075] isolation/detach-partition-concurrently-2 LOG: connection ready: setup total=1.712 ms, fork=0.382 ms, authentication=0.100 ms 2025-11-30 18:45:17.815 UTC unrecognized[46076] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.815 UTC client backend[46076] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.815 UTC client backend[46076] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-2 2025-11-30 18:45:17.816 UTC client backend[46076] isolation/detach-partition-concurrently-2 LOG: connection ready: setup total=1.748 ms, fork=0.377 ms, authentication=0.105 ms 2025-11-30 18:45:17.817 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.817 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_rng2rng ALTER COLUMN parent_id SET DEFAULT '[-1,-1]', DROP CONSTRAINT temporal_partitioned_fk_rng2rng_fk, ADD CONSTRAINT temporal_partitioned_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_rng ON DELETE SET DEFAULT ON UPDATE SET DEFAULT; 2025-11-30 18:45:17.843 UTC client backend[46076] isolation/detach-partition-concurrently-2/s3 ERROR: insert or update on table "d_lp_fk_r" violates foreign key constraint "d_lp_fk_r_a_fkey" 2025-11-30 18:45:17.843 UTC client backend[46076] isolation/detach-partition-concurrently-2/s3 DETAIL: Key (a)=(1) is not present in table "d_lp_fk". 2025-11-30 18:45:17.843 UTC client backend[46076] isolation/detach-partition-concurrently-2/s3 STATEMENT: INSERT INTO d_lp_fk_r VALUES (1); 2025-11-30 18:45:17.860 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk" 2025-11-30 18:45:17.860 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2010-01-01,2010-02-15)}) is not present in table "temporal_partitioned_mltrng". 2025-11-30 18:45:17.860 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_mltrng2mltrng (id, valid_at, parent_id) VALUES ('[3,4)', datemultirange(daterange('2010-01-01', '2010-02-15')), '[1,2)'); 2025-11-30 18:45:17.861 UTC client backend[46005] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk" 2025-11-30 18:45:17.861 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([3,4), {[2000-01-01,2000-02-15)}) is not present in table "temporal_partitioned_mltrng". 2025-11-30 18:45:17.861 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_mltrng2mltrng (id, valid_at, parent_id) VALUES ('[3,4)', datemultirange(daterange('2000-01-01', '2000-02-15')), '[3,4)'); 2025-11-30 18:45:17.867 UTC client backend[46005] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "tfkp1_pkey" 2025-11-30 18:45:17.867 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2000-01-01,2000-04-01)}) conflicts with existing key (id, valid_at)=([1,2), {[2000-01-01,2000-04-01)}). 2025-11-30 18:45:17.867 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_fk_mltrng2mltrng SET valid_at = datemultirange(daterange('2000-01-01', '2000-04-01')) WHERE id = '[1,2)'; 2025-11-30 18:45:17.878 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk_2" on table "temporal_partitioned_fk_mltrng2mltrng" 2025-11-30 18:45:17.878 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_partitioned_fk_mltrng2mltrng". 2025-11-30 18:45:17.878 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_mltrng SET valid_at = datemultirange(daterange('2016-01-01', '2016-02-01')) WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-11-30 18:45:17.887 UTC client backend[46005] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk_2" on table "temporal_partitioned_fk_mltrng2mltrng" 2025-11-30 18:45:17.887 UTC client backend[46005] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_partitioned_fk_mltrng2mltrng". 2025-11-30 18:45:17.887 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_partitioned_mltrng WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-11-30 18:45:17.891 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.891 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_mltrng2mltrng DROP CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk, ADD CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_mltrng ON DELETE CASCADE ON UPDATE CASCADE; 2025-11-30 18:45:17.895 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.895 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_mltrng2mltrng DROP CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk, ADD CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_mltrng ON DELETE SET NULL ON UPDATE SET NULL; 2025-11-30 18:45:17.899 UTC client backend[46005] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-11-30 18:45:17.899 UTC client backend[46005] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_mltrng2mltrng ALTER COLUMN parent_id SET DEFAULT '[0,1)', DROP CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk, ADD CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_mltrng ON DELETE SET DEFAULT ON UPDATE SET DEFAULT; 2025-11-30 18:45:17.913 UTC client backend[46005] pg_regress/without_overlaps LOG: disconnection: session time: 0:00:01.240 user=postgres database=regression host=[local] 2025-11-30 18:45:17.929 UTC client backend[46075] isolation/detach-partition-concurrently-2/s2 ERROR: removing partition "d_lp_fk_1" violates foreign key constraint "d_lp_fk_r_a_fkey_1" 2025-11-30 18:45:17.929 UTC client backend[46075] isolation/detach-partition-concurrently-2/s2 DETAIL: Key (a)=(1) is still referenced from table "d_lp_fk_r". 2025-11-30 18:45:17.929 UTC client backend[46075] isolation/detach-partition-concurrently-2/s2 STATEMENT: ALTER TABLE d_lp_fk DETACH PARTITION d_lp_fk_1 CONCURRENTLY; 2025-11-30 18:45:17.940 UTC unrecognized[46105] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.941 UTC client backend[46105] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.941 UTC client backend[46105] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/psql 2025-11-30 18:45:17.941 UTC unrecognized[46104] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.941 UTC client backend[46104] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.941 UTC client backend[46104] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rules 2025-11-30 18:45:17.942 UTC unrecognized[46107] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.942 UTC client backend[46105] pg_regress/psql LOG: connection ready: setup total=4.452 ms, fork=1.854 ms, authentication=0.137 ms 2025-11-30 18:45:17.942 UTC unrecognized[46106] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.942 UTC client backend[46104] pg_regress/rules LOG: connection ready: setup total=5.198 ms, fork=3.804 ms, authentication=0.106 ms 2025-11-30 18:45:17.942 UTC client backend[46107] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.942 UTC client backend[46107] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/psql_crosstab 2025-11-30 18:45:17.942 UTC client backend[46106] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.942 UTC client backend[46106] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/psql_pipeline 2025-11-30 18:45:17.943 UTC client backend[46107] pg_regress/psql_crosstab LOG: connection ready: setup total=4.858 ms, fork=1.089 ms, authentication=0.149 ms 2025-11-30 18:45:17.943 UTC client backend[46106] pg_regress/psql_pipeline LOG: connection ready: setup total=5.666 ms, fork=1.694 ms, authentication=0.137 ms 2025-11-30 18:45:17.943 UTC client backend[46105] pg_regress/psql ERROR: there is no parameter $1 at character 8 2025-11-30 18:45:17.943 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT $1, $2 2025-11-30 18:45:17.944 UTC unrecognized[46109] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.944 UTC client backend[46109] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.944 UTC client backend[46109] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats_ext 2025-11-30 18:45:17.944 UTC unrecognized[46110] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.945 UTC client backend[46110] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.945 UTC client backend[46110] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/amutils 2025-11-30 18:45:17.945 UTC client backend[46109] pg_regress/stats_ext LOG: connection ready: setup total=4.734 ms, fork=3.246 ms, authentication=0.117 ms 2025-11-30 18:45:17.946 UTC client backend[46110] pg_regress/amutils LOG: connection ready: setup total=3.667 ms, fork=2.182 ms, authentication=0.110 ms 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql ERROR: column "foo" does not exist at character 8 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT foo 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql ERROR: cannot insert multiple commands into a prepared statement 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT 1 ; SELECT 2 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql ERROR: bind message supplies 1 parameters, but prepared statement "" requires 2 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT $1, $2 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql ERROR: prepared statement "stmt2" does not exist 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql ERROR: bind message supplies 1 parameters, but prepared statement "stmt3" requires 2 2025-11-30 18:45:17.946 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT $1, $2 2025-11-30 18:45:17.948 UTC unrecognized[46111] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.948 UTC client backend[46111] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.948 UTC client backend[46111] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.windows.win1252 2025-11-30 18:45:17.949 UTC client backend[46111] pg_regress/collate.windows.win1252 LOG: connection ready: setup total=6.695 ms, fork=1.052 ms, authentication=0.114 ms 2025-11-30 18:45:17.952 UTC unrecognized[46108] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:17.953 UTC client backend[46111] pg_regress/collate.windows.win1252 LOG: disconnection: session time: 0:00:00.009 user=postgres database=regression host=[local] 2025-11-30 18:45:17.953 UTC client backend[46108] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:17.953 UTC client backend[46108] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.linux.utf8 2025-11-30 18:45:17.954 UTC client backend[46108] pg_regress/collate.linux.utf8 LOG: connection ready: setup total=13.924 ms, fork=8.385 ms, authentication=0.118 ms 2025-11-30 18:45:17.956 UTC client backend[46104] pg_regress/rules ERROR: rule "rtest_v1_bad" for relation "rtest_v1" does not exist 2025-11-30 18:45:17.956 UTC client backend[46104] pg_regress/rules STATEMENT: COMMENT ON RULE rtest_v1_bad ON rtest_v1 IS 'bad rule'; 2025-11-30 18:45:17.957 UTC client backend[46108] pg_regress/collate.linux.utf8 LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression host=[local] 2025-11-30 18:45:17.958 UTC client backend[46109] pg_regress/stats_ext ERROR: syntax error at or near ";" at character 22 2025-11-30 18:45:17.958 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst; 2025-11-30 18:45:17.959 UTC client backend[46109] pg_regress/stats_ext ERROR: syntax error at or near ";" at character 30 2025-11-30 18:45:17.959 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a, b; 2025-11-30 18:45:17.960 UTC client backend[46109] pg_regress/stats_ext ERROR: syntax error at or near "FROM" at character 23 2025-11-30 18:45:17.960 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst FROM sometab; 2025-11-30 18:45:17.961 UTC client backend[46109] pg_regress/stats_ext ERROR: relation "nonexistent" does not exist 2025-11-30 18:45:17.961 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a, b FROM nonexistent; 2025-11-30 18:45:17.961 UTC client backend[46109] pg_regress/stats_ext ERROR: column "a" does not exist 2025-11-30 18:45:17.961 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a, b FROM ext_stats_test; 2025-11-30 18:45:17.961 UTC client backend[46105] pg_regress/psql ERROR: syntax error at end of input at character 12 2025-11-30 18:45:17.961 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT 1 + 2025-11-30 18:45:17.961 UTC client backend[46105] pg_regress/psql ERROR: relation "bububu" does not exist at character 7 2025-11-30 18:45:17.961 UTC client backend[46105] pg_regress/psql STATEMENT: TABLE bububu; 2025-11-30 18:45:17.962 UTC client backend[46105] pg_regress/psql ERROR: syntax error at or near "bogus" at character 1 2025-11-30 18:45:17.962 UTC client backend[46105] pg_regress/psql STATEMENT: bogus; 2025-11-30 18:45:17.962 UTC client backend[46106] pg_regress/psql_pipeline ERROR: could not determine data type of parameter $1 2025-11-30 18:45:17.962 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT $2 2025-11-30 18:45:17.963 UTC client backend[46109] pg_regress/stats_ext ERROR: duplicate column name in statistics definition 2025-11-30 18:45:17.963 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON x, x, y FROM ext_stats_test; 2025-11-30 18:45:17.963 UTC client backend[46109] pg_regress/stats_ext ERROR: cannot have more than 8 columns in statistics 2025-11-30 18:45:17.963 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON x, x, y, x, x, y, x, x, y FROM ext_stats_test; 2025-11-30 18:45:17.964 UTC client backend[46109] pg_regress/stats_ext ERROR: cannot have more than 8 columns in statistics 2025-11-30 18:45:17.964 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON x, x, y, x, x, (x || 'x'), (y + 1), (x || 'x'), (x || 'x'), (y + 1) FROM ext_stats_test; 2025-11-30 18:45:17.964 UTC client backend[46109] pg_regress/stats_ext ERROR: cannot have more than 8 columns in statistics 2025-11-30 18:45:17.964 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (x || 'x'), (x || 'x'), (y + 1), (x || 'x'), (x || 'x'), (y + 1), (x || 'x'), (x || 'x'), (y + 1) FROM ext_stats_test; 2025-11-30 18:45:17.965 UTC client backend[46110] pg_regress/amutils LOG: disconnection: session time: 0:00:00.020 user=postgres database=regression host=[local] 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline ERROR: bind message supplies 1 parameters, but prepared statement "" requires 0 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT $1; 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline ERROR: duplicate key value violates unique constraint "psql_pipeline_pkey" 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline DETAIL: Key (a)=(1) already exists. 2025-11-30 18:45:17.965 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: INSERT INTO psql_pipeline VALUES ($1) 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext ERROR: duplicate expression in statistics definition 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (x || 'x'), (x || 'x'), y FROM ext_stats_test; 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext ERROR: unrecognized statistics kind "unrecognized" 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (unrecognized) ON x, y FROM ext_stats_test; 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext ERROR: CREATE STATISTICS only supports relation names in the FROM clause 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a FROM (VALUES (x)) AS foo; 2025-11-30 18:45:17.966 UTC client backend[46106] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-11-30 18:45:17.966 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext ERROR: CREATE STATISTICS only supports relation names in the FROM clause 2025-11-30 18:45:17.966 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a FROM foo NATURAL JOIN bar; 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext ERROR: CREATE STATISTICS only supports relation names in the FROM clause 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a FROM (SELECT * FROM ext_stats_test) AS foo; 2025-11-30 18:45:17.967 UTC client backend[46106] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-11-30 18:45:17.967 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext ERROR: CREATE STATISTICS only supports relation names in the FROM clause 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a FROM ext_stats_test s TABLESAMPLE system (x); 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext ERROR: CREATE STATISTICS only supports relation names in the FROM clause 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a FROM XMLTABLE('foo' PASSING 'bar' COLUMNS a text); 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext ERROR: CREATE STATISTICS only supports relation names in the FROM clause 2025-11-30 18:45:17.967 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a FROM JSON_TABLE(jsonb '123', '$' COLUMNS (item int)); 2025-11-30 18:45:17.968 UTC client backend[46106] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-11-30 18:45:17.968 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-11-30 18:45:17.968 UTC client backend[46109] pg_regress/stats_ext ERROR: CREATE STATISTICS only supports relation names in the FROM clause 2025-11-30 18:45:17.968 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS alt_stat2 ON a FROM tftest(1); 2025-11-30 18:45:17.968 UTC client backend[46106] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-11-30 18:45:17.968 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-11-30 18:45:17.969 UTC client backend[46109] pg_regress/stats_ext ERROR: extended statistics require at least 2 columns 2025-11-30 18:45:17.969 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (y) FROM ext_stats_test; 2025-11-30 18:45:17.969 UTC client backend[46109] pg_regress/stats_ext ERROR: syntax error at or near "+" at character 28 2025-11-30 18:45:17.969 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON y + z FROM ext_stats_test; 2025-11-30 18:45:17.969 UTC client backend[46109] pg_regress/stats_ext ERROR: syntax error at or near "," at character 28 2025-11-30 18:45:17.969 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (x, y) FROM ext_stats_test; 2025-11-30 18:45:17.969 UTC client backend[46106] pg_regress/psql_pipeline WARNING: SET LOCAL can only be used in transaction blocks 2025-11-30 18:45:17.969 UTC client backend[46106] pg_regress/psql_pipeline ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:17.969 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: REINDEX TABLE CONCURRENTLY psql_pipeline 2025-11-30 18:45:17.972 UTC client backend[46107] pg_regress/psql_crosstab LOG: disconnection: session time: 0:00:00.032 user=postgres database=regression host=[local] 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on z from ext_stats_test1; 2025-11-30 18:45:17.974 UTC client backend[46105] pg_regress/psql ERROR: table "gexec_test" does not exist 2025-11-30 18:45:17.974 UTC client backend[46105] pg_regress/psql STATEMENT: drop table gexec_test 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (z) from ext_stats_test1; 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (z+1) from ext_stats_test1; 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (ndistinct) ON z from ext_stats_test1; 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on tableoid from ext_stats_test1; 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-11-30 18:45:17.974 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (tableoid) from ext_stats_test1; 2025-11-30 18:45:17.975 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-11-30 18:45:17.975 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (tableoid::int+1) from ext_stats_test1; 2025-11-30 18:45:17.975 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-11-30 18:45:17.975 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (ndistinct) ON xmin from ext_stats_test1; 2025-11-30 18:45:17.976 UTC client backend[46109] pg_regress/stats_ext ERROR: column "w" cannot be used in statistics because its type xid has no default btree operator class 2025-11-30 18:45:17.976 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (ndistinct) ON w from ext_stats_test1; 2025-11-30 18:45:17.977 UTC client backend[46106] pg_regress/psql_pipeline ERROR: SAVEPOINT can only be used in transaction blocks 2025-11-30 18:45:17.977 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: SAVEPOINT a 2025-11-30 18:45:17.978 UTC client backend[46109] pg_regress/stats_ext ERROR: must be owner of statistics object ab1_a_b_stats 2025-11-30 18:45:17.978 UTC client backend[46109] pg_regress/stats_ext STATEMENT: COMMENT ON STATISTICS ab1_a_b_stats IS 'changed comment'; 2025-11-30 18:45:17.978 UTC client backend[46109] pg_regress/stats_ext ERROR: must be owner of statistics object ab1_a_b_stats 2025-11-30 18:45:17.978 UTC client backend[46109] pg_regress/stats_ext STATEMENT: DROP STATISTICS ab1_a_b_stats; 2025-11-30 18:45:17.978 UTC client backend[46109] pg_regress/stats_ext ERROR: must be owner of statistics object ab1_a_b_stats 2025-11-30 18:45:17.978 UTC client backend[46109] pg_regress/stats_ext STATEMENT: ALTER STATISTICS ab1_a_b_stats RENAME TO ab1_a_b_stats_new; 2025-11-30 18:45:17.979 UTC client backend[46106] pg_regress/psql_pipeline ERROR: LOCK TABLE can only be used in transaction blocks 2025-11-30 18:45:17.979 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: LOCK psql_pipeline 2025-11-30 18:45:17.980 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics object "stats_ext_temp" does not exist 2025-11-30 18:45:17.980 UTC client backend[46109] pg_regress/stats_ext STATEMENT: DROP STATISTICS stats_ext_temp; 2025-11-30 18:45:17.983 UTC client backend[46106] pg_regress/psql_pipeline ERROR: VACUUM cannot run inside a transaction block 2025-11-30 18:45:17.983 UTC client backend[46106] pg_regress/psql_pipeline STATEMENT: VACUUM psql_pipeline 2025-11-30 18:45:17.991 UTC client backend[46106] pg_regress/psql_pipeline LOG: disconnection: session time: 0:00:00.051 user=postgres database=regression host=[local] 2025-11-30 18:45:18.004 UTC client backend[46076] isolation/detach-partition-concurrently-2/s3 ERROR: insert or update on table "d_lp_fk_r" violates foreign key constraint "d_lp_fk_r_a_fkey" 2025-11-30 18:45:18.004 UTC client backend[46076] isolation/detach-partition-concurrently-2/s3 DETAIL: Key (a)=(1) is not present in table "d_lp_fk". 2025-11-30 18:45:18.004 UTC client backend[46076] isolation/detach-partition-concurrently-2/s3 STATEMENT: INSERT INTO d_lp_fk_r VALUES (1); 2025-11-30 18:45:18.007 UTC client backend[46109] pg_regress/stats_ext WARNING: statistics object "public.ab1_a_b_stats" could not be computed for relation "public.ab1" 2025-11-30 18:45:18.022 UTC client backend[46073] isolation/detach-partition-concurrently-2/control connection LOG: disconnection: session time: 0:00:00.215 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:18.024 UTC client backend[46074] isolation/detach-partition-concurrently-2/s1 LOG: disconnection: session time: 0:00:00.214 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:18.025 UTC client backend[46075] isolation/detach-partition-concurrently-2/s2 LOG: disconnection: session time: 0:00:00.212 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:18.025 UTC client backend[46076] isolation/detach-partition-concurrently-2/s3 LOG: disconnection: session time: 0:00:00.211 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:18.026 UTC client backend[46109] pg_regress/stats_ext WARNING: statistics object "public.ab1_a_b_stats" could not be computed for relation "public.ab1" 2025-11-30 18:45:18.029 UTC client backend[46109] pg_regress/stats_ext ERROR: statistics object "ab1_a_b_stats" does not exist 2025-11-30 18:45:18.029 UTC client backend[46109] pg_regress/stats_ext STATEMENT: ALTER STATISTICS ab1_a_b_stats SET STATISTICS 0; 2025-11-30 18:45:18.031 UTC unrecognized[46114] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:18.032 UTC client backend[46114] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:18.032 UTC client backend[46114] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-3 2025-11-30 18:45:18.033 UTC client backend[46114] isolation/detach-partition-concurrently-3 LOG: connection ready: setup total=2.002 ms, fork=0.401 ms, authentication=0.126 ms 2025-11-30 18:45:18.034 UTC unrecognized[46115] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:18.035 UTC client backend[46115] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:18.035 UTC client backend[46115] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-3 2025-11-30 18:45:18.035 UTC client backend[46115] isolation/detach-partition-concurrently-3 LOG: connection ready: setup total=1.794 ms, fork=0.381 ms, authentication=0.115 ms 2025-11-30 18:45:18.037 UTC unrecognized[46116] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:18.037 UTC client backend[46116] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:18.037 UTC client backend[46116] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-3 2025-11-30 18:45:18.038 UTC client backend[46116] isolation/detach-partition-concurrently-3 LOG: connection ready: setup total=1.789 ms, fork=0.393 ms, authentication=0.111 ms 2025-11-30 18:45:18.057 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.057 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1152 2025-11-30 18:45:18.057 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.058 UTC client backend[46115] isolation/detach-partition-concurrently-3/s1 ERROR: cannot alter partition "d3_listp1" with an incomplete detach 2025-11-30 18:45:18.058 UTC client backend[46115] isolation/detach-partition-concurrently-3/s1 HINT: Use ALTER TABLE ... DETACH PARTITION ... FINALIZE to complete the pending detach operation. 2025-11-30 18:45:18.058 UTC client backend[46115] isolation/detach-partition-concurrently-3/s1 STATEMENT: ALTER TABLE d3_listp1 ALTER a DROP NOT NULL; 2025-11-30 18:45:18.076 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.076 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1155 2025-11-30 18:45:18.076 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.076 UTC client backend[46115] isolation/detach-partition-concurrently-3/s1 ERROR: no partition of relation "d3_listp" found for row 2025-11-30 18:45:18.076 UTC client backend[46115] isolation/detach-partition-concurrently-3/s1 DETAIL: Partition key of the failing row contains (a) = (1). 2025-11-30 18:45:18.076 UTC client backend[46115] isolation/detach-partition-concurrently-3/s1 STATEMENT: INSERT INTO d3_listp VALUES (1); 2025-11-30 18:45:18.094 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.094 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1156 2025-11-30 18:45:18.094 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.104 UTC client backend[46109] pg_regress/stats_ext ERROR: cannot define statistics for relation "ti" 2025-11-30 18:45:18.104 UTC client backend[46109] pg_regress/stats_ext DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:18.104 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s2 ON a, b FROM tststats.ti; 2025-11-30 18:45:18.104 UTC client backend[46109] pg_regress/stats_ext ERROR: cannot define statistics for relation "s" 2025-11-30 18:45:18.104 UTC client backend[46109] pg_regress/stats_ext DETAIL: This operation is not supported for sequences. 2025-11-30 18:45:18.104 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s3 ON a, b FROM tststats.s; 2025-11-30 18:45:18.105 UTC client backend[46109] pg_regress/stats_ext ERROR: cannot define statistics for relation "v" 2025-11-30 18:45:18.105 UTC client backend[46109] pg_regress/stats_ext DETAIL: This operation is not supported for views. 2025-11-30 18:45:18.105 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s4 ON a, b FROM tststats.v; 2025-11-30 18:45:18.105 UTC client backend[46109] pg_regress/stats_ext ERROR: cannot define statistics for relation "ty" 2025-11-30 18:45:18.105 UTC client backend[46109] pg_regress/stats_ext DETAIL: This operation is not supported for composite types. 2025-11-30 18:45:18.105 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s6 ON a, b FROM tststats.ty; 2025-11-30 18:45:18.112 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.112 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1158 2025-11-30 18:45:18.112 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.129 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.129 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1160 2025-11-30 18:45:18.129 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp2 CONCURRENTLY; 2025-11-30 18:45:18.147 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.147 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1162 2025-11-30 18:45:18.147 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp2 CONCURRENTLY; 2025-11-30 18:45:18.165 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.165 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1164 2025-11-30 18:45:18.165 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.174 UTC client backend[46104] pg_regress/rules ERROR: INSERT with ON CONFLICT clause cannot be used with table that has INSERT or UPDATE rules 2025-11-30 18:45:18.174 UTC client backend[46104] pg_regress/rules STATEMENT: insert into shoelace values ('sl10', 1000, 'magenta', 40.0, 'inch', 0.0) on conflict do nothing; 2025-11-30 18:45:18.184 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.184 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1167 2025-11-30 18:45:18.184 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.185 UTC client backend[46104] pg_regress/rules ERROR: column "f1" does not exist at character 110 2025-11-30 18:45:18.185 UTC client backend[46104] pg_regress/rules DETAIL: There are columns named "f1", but they are in tables that cannot be referenced from this part of the query. 2025-11-30 18:45:18.185 UTC client backend[46104] pg_regress/rules HINT: Try using a table-qualified name. 2025-11-30 18:45:18.185 UTC client backend[46104] pg_regress/rules STATEMENT: create rule rules_foorule as on insert to rules_foo where f1 < 100 do instead insert into rules_foo2 values (f1); 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql ERROR: bar 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql STATEMENT: do $$ begin raise notice 'foo'; raise exception 'bar'; end $$; 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql ERROR: bar 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql STATEMENT: do $$ begin raise notice 'foo'; raise exception 'bar'; end $$; 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql ERROR: bar 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE 2025-11-30 18:45:18.190 UTC client backend[46105] pg_regress/psql STATEMENT: do $$ begin raise notice 'foo'; raise exception 'bar'; end $$; 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql ERROR: syntax error at or near ";" at character 15 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT 1 UNION; 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql ERROR: table "this_table_does_not_exist" does not exist 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql STATEMENT: DROP TABLE this_table_does_not_exist; 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql ERROR: syntax error at or near ";" at character 15 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT 1 UNION; 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql ERROR: division by zero 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT 1/0; 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql ERROR: syntax error at end of input at character 13 2025-11-30 18:45:18.191 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT 4 AS 2025-11-30 18:45:18.193 UTC client backend[46105] pg_regress/psql ERROR: division by zero 2025-11-30 18:45:18.193 UTC client backend[46105] pg_regress/psql STATEMENT: select 1/(15-unique2) from tenk1 order by unique2 limit 19; 2025-11-30 18:45:18.203 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.203 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1170 2025-11-30 18:45:18.203 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.203 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: partition "d3_listp1" already pending detach in partitioned table "public.d3_listp" 2025-11-30 18:45:18.203 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 HINT: Use ALTER TABLE ... DETACH PARTITION ... FINALIZE to complete the pending detach operation. 2025-11-30 18:45:18.203 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp2 CONCURRENTLY; 2025-11-30 18:45:18.221 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.221 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1171 2025-11-30 18:45:18.221 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.249 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.249 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1172 2025-11-30 18:45:18.249 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.267 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.267 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1174 2025-11-30 18:45:18.267 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.273 UTC client backend[46104] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3c_fkey" 2025-11-30 18:45:18.273 UTC client backend[46104] pg_regress/rules DETAIL: Key (id3a, id3c)=(1, 13) is not present in table "rule_and_refint_t2". 2025-11-30 18:45:18.273 UTC client backend[46104] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 11, 13, 'row5'); 2025-11-30 18:45:18.273 UTC client backend[46104] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-11-30 18:45:18.273 UTC client backend[46104] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-11-30 18:45:18.273 UTC client backend[46104] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row6'); 2025-11-30 18:45:18.274 UTC client backend[46104] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-11-30 18:45:18.274 UTC client backend[46104] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-11-30 18:45:18.274 UTC client backend[46104] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row6') on conflict do nothing; 2025-11-30 18:45:18.275 UTC client backend[46104] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-11-30 18:45:18.275 UTC client backend[46104] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-11-30 18:45:18.275 UTC client backend[46104] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row6') on conflict (id3a, id3b, id3c) do update set id3b = excluded.id3b; 2025-11-30 18:45:18.275 UTC client backend[46104] pg_regress/rules ERROR: INSERT with ON CONFLICT clause cannot be used with table that has INSERT or UPDATE rules 2025-11-30 18:45:18.275 UTC client backend[46104] pg_regress/rules STATEMENT: insert into shoelace values ('sl9', 0, 'pink', 35.0, 'inch', 0.0) on conflict (sl_name) do update set sl_avail = excluded.sl_avail; 2025-11-30 18:45:18.280 UTC client backend[46104] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3c_fkey" 2025-11-30 18:45:18.280 UTC client backend[46104] pg_regress/rules DETAIL: Key (id3a, id3c)=(1, 13) is not present in table "rule_and_refint_t2". 2025-11-30 18:45:18.280 UTC client backend[46104] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 11, 13, 'row7'); 2025-11-30 18:45:18.284 UTC client backend[46104] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-11-30 18:45:18.284 UTC client backend[46104] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-11-30 18:45:18.284 UTC client backend[46104] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row8'); 2025-11-30 18:45:18.285 UTC client backend[46104] pg_regress/rules ERROR: cannot drop rule _RETURN on view rules_fooview because view rules_fooview requires it 2025-11-30 18:45:18.285 UTC client backend[46104] pg_regress/rules HINT: You can drop view rules_fooview instead. 2025-11-30 18:45:18.285 UTC client backend[46104] pg_regress/rules STATEMENT: drop rule "_RETURN" on rules_fooview; 2025-11-30 18:45:18.288 UTC client backend[46104] pg_regress/rules ERROR: relation "rules_fooview" cannot have ON SELECT rules 2025-11-30 18:45:18.288 UTC client backend[46104] pg_regress/rules DETAIL: This operation is not supported for tables. 2025-11-30 18:45:18.288 UTC client backend[46104] pg_regress/rules STATEMENT: create rule "_RETURN" as on select to rules_fooview do instead select 1 as x, 'aaa'::text as y; 2025-11-30 18:45:18.290 UTC client backend[46104] pg_regress/rules ERROR: relation "rules_fooview" cannot have ON SELECT rules 2025-11-30 18:45:18.290 UTC client backend[46104] pg_regress/rules DETAIL: This operation is not supported for partitioned tables. 2025-11-30 18:45:18.290 UTC client backend[46104] pg_regress/rules STATEMENT: create rule "_RETURN" as on select to rules_fooview do instead select 1 as x, 'aaa'::text as y; 2025-11-30 18:45:18.292 UTC client backend[46104] pg_regress/rules ERROR: relation "rules_fooview_part" cannot have ON SELECT rules 2025-11-30 18:45:18.292 UTC client backend[46104] pg_regress/rules DETAIL: This operation is not supported for tables. 2025-11-30 18:45:18.292 UTC client backend[46104] pg_regress/rules STATEMENT: create rule "_RETURN" as on select to rules_fooview_part do instead select 1 as x, 'aaa'::text as y; 2025-11-30 18:45:18.297 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.297 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1176 2025-11-30 18:45:18.297 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.325 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.325 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1178 2025-11-30 18:45:18.325 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.343 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.343 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1180 2025-11-30 18:45:18.343 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.352 UTC client backend[46105] pg_regress/psql ERROR: relation "ac_test" does not exist at character 15 2025-11-30 18:45:18.352 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT * FROM ac_test; 2025-11-30 18:45:18.353 UTC client backend[46105] pg_regress/psql ERROR: invalid input syntax for type integer: "foo" at character 30 2025-11-30 18:45:18.353 UTC client backend[46105] pg_regress/psql STATEMENT: INSERT INTO oer_test VALUES ('foo'); 2025-11-30 18:45:18.354 UTC client backend[46104] pg_regress/rules ERROR: relation "old" in FOR UPDATE clause not found in FROM clause at character 120 2025-11-30 18:45:18.354 UTC client backend[46104] pg_regress/rules STATEMENT: create or replace rule r1 as on update to rules_base do instead select * from rules_base where f1 = 11 for update of old; 2025-11-30 18:45:18.358 UTC client backend[46105] pg_regress/psql ERROR: relation "notexists" does not exist at character 15 2025-11-30 18:45:18.358 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT * FROM notexists; 2025-11-30 18:45:18.359 UTC client backend[46105] pg_regress/psql ERROR: syntax error at or near ";" at character 23 2025-11-30 18:45:18.359 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT 5 ; SELECT 6 + ; SELECT warn('6.5') ; SELECT 7 ; 2025-11-30 18:45:18.359 UTC client backend[46105] pg_regress/psql ERROR: division by zero 2025-11-30 18:45:18.359 UTC client backend[46105] pg_regress/psql STATEMENT: BEGIN ; SELECT 8 AS eight ; SELECT 9/0 AS nine ; ROLLBACK ; SELECT 10 AS ten ; 2025-11-30 18:45:18.372 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.372 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1182 2025-11-30 18:45:18.372 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.389 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.389 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1183 2025-11-30 18:45:18.389 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.391 UTC client backend[46105] pg_regress/psql ERROR: type "no_such_type" does not exist at character 20 2025-11-30 18:45:18.391 UTC client backend[46105] pg_regress/psql STATEMENT: CREATE TABLE bla(s NO_SUCH_TYPE); 2025-11-30 18:45:18.393 UTC client backend[46105] pg_regress/psql ERROR: error oops! 2025-11-30 18:45:18.393 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-11-30 18:45:18.393 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT psql_error('oops!'); 2025-11-30 18:45:18.395 UTC client backend[46105] pg_regress/psql ERROR: error boum! 2025-11-30 18:45:18.395 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-11-30 18:45:18.395 UTC client backend[46105] pg_regress/psql STATEMENT: INSERT INTO bla VALUES ('Rosalyn') ; -- will rollback SELECT 'before error' AS show ; -- will show nevertheless! SELECT psql_error('boum!') ; -- failure SELECT 'after error' AS noshow; 2025-11-30 18:45:18.395 UTC client backend[46105] pg_regress/psql ERROR: error bam! 2025-11-30 18:45:18.395 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-11-30 18:45:18.395 UTC client backend[46105] pg_regress/psql STATEMENT: INSERT INTO bla(s) VALUES ('Moe') ; -- will rollback SELECT psql_error('bam!'); 2025-11-30 18:45:18.397 UTC client backend[46105] pg_regress/psql ERROR: error bad! 2025-11-30 18:45:18.397 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-11-30 18:45:18.397 UTC client backend[46105] pg_regress/psql STATEMENT: SELECT psql_error('bad!'); 2025-11-30 18:45:18.397 UTC client backend[46105] pg_regress/psql ERROR: error bad! 2025-11-30 18:45:18.397 UTC client backend[46105] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-11-30 18:45:18.397 UTC client backend[46105] pg_regress/psql STATEMENT: INSERT INTO bla VALUES ('Mum') ; -- will rollback SELECT COUNT(*) AS "#mum" FROM bla WHERE s = 'Mum' ; -- but be counted here SELECT psql_error('bad!'); 2025-11-30 18:45:18.418 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.418 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 CONTEXT: waiting for ShareLock on virtual transaction 45/1185 2025-11-30 18:45:18.418 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 STATEMENT: ALTER TABLE d3_listp DETACH PARTITION d3_listp1 CONCURRENTLY; 2025-11-30 18:45:18.428 UTC client backend[46104] pg_regress/rules ERROR: rule "insertrule" for relation "rule_v1" does not exist 2025-11-30 18:45:18.428 UTC client backend[46104] pg_regress/rules STATEMENT: ALTER RULE InsertRule ON rule_v1 RENAME TO NewInsertRule; 2025-11-30 18:45:18.428 UTC client backend[46104] pg_regress/rules ERROR: rule "_RETURN" for relation "rule_v1" already exists 2025-11-30 18:45:18.428 UTC client backend[46104] pg_regress/rules STATEMENT: ALTER RULE NewInsertRule ON rule_v1 RENAME TO "_RETURN"; 2025-11-30 18:45:18.428 UTC client backend[46104] pg_regress/rules ERROR: renaming an ON SELECT rule is not allowed 2025-11-30 18:45:18.428 UTC client backend[46104] pg_regress/rules STATEMENT: ALTER RULE "_RETURN" ON rule_v1 RENAME TO abc; 2025-11-30 18:45:18.432 UTC client backend[46114] isolation/detach-partition-concurrently-3/control connection LOG: disconnection: session time: 0:00:00.400 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:18.433 UTC client backend[46115] isolation/detach-partition-concurrently-3/s1 LOG: disconnection: session time: 0:00:00.399 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:18.434 UTC client backend[46116] isolation/detach-partition-concurrently-3/s2 LOG: disconnection: session time: 0:00:00.397 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:18.441 UTC unrecognized[46119] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:18.441 UTC client backend[46119] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:18.441 UTC client backend[46119] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-4 2025-11-30 18:45:18.442 UTC client backend[46119] isolation/detach-partition-concurrently-4 LOG: connection ready: setup total=2.031 ms, fork=0.422 ms, authentication=0.131 ms 2025-11-30 18:45:18.444 UTC unrecognized[46120] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:18.444 UTC client backend[46120] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:18.444 UTC client backend[46120] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-4 2025-11-30 18:45:18.445 UTC client backend[46120] isolation/detach-partition-concurrently-4 LOG: connection ready: setup total=1.849 ms, fork=0.408 ms, authentication=0.118 ms 2025-11-30 18:45:18.446 UTC unrecognized[46121] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:18.447 UTC client backend[46121] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:18.447 UTC client backend[46121] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-4 2025-11-30 18:45:18.448 UTC client backend[46121] isolation/detach-partition-concurrently-4 LOG: connection ready: setup total=1.762 ms, fork=0.394 ms, authentication=0.121 ms 2025-11-30 18:45:18.449 UTC unrecognized[46122] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:18.449 UTC client backend[46122] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:18.449 UTC client backend[46122] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/detach-partition-concurrently-4 2025-11-30 18:45:18.450 UTC client backend[46122] isolation/detach-partition-concurrently-4 LOG: connection ready: setup total=1.643 ms, fork=0.344 ms, authentication=0.102 ms 2025-11-30 18:45:18.479 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.479 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for ShareLock on virtual transaction 71/1434 2025-11-30 18:45:18.479 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:18.480 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.480 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.480 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.493 UTC client backend[46104] pg_regress/rules ERROR: cannot execute MERGE on relation "rule_merge1" 2025-11-30 18:45:18.493 UTC client backend[46104] pg_regress/rules DETAIL: MERGE is not supported for relations with rules. 2025-11-30 18:45:18.493 UTC client backend[46104] pg_regress/rules STATEMENT: MERGE INTO rule_merge1 t USING (SELECT 1 AS a) s ON t.a = s.a WHEN MATCHED AND t.a < 2 THEN UPDATE SET b = b || ' updated by merge' WHEN MATCHED AND t.a > 2 THEN DELETE WHEN NOT MATCHED THEN INSERT VALUES (s.a, ''); 2025-11-30 18:45:18.513 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.513 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.513 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.516 UTC client backend[46104] pg_regress/rules ERROR: permission denied for table ruletest_t3 2025-11-30 18:45:18.516 UTC client backend[46104] pg_regress/rules STATEMENT: UPDATE ruletest_t1 t1 SET x = 0 FROM ruletest_t3 t3 WHERE t1.x = t3.x; 2025-11-30 18:45:18.525 UTC client backend[46104] pg_regress/rules LOG: disconnection: session time: 0:00:00.584 user=postgres database=regression host=[local] 2025-11-30 18:45:18.546 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.546 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for ShareLock on virtual transaction 71/1436 2025-11-30 18:45:18.546 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:18.546 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.546 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.546 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.578 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.578 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.578 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.610 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.610 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for ShareLock on virtual transaction 71/1438 2025-11-30 18:45:18.610 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:18.611 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.611 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.611 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.633 UTC client backend[46105] pg_regress/psql LOG: disconnection: session time: 0:00:00.694 user=postgres database=regression host=[local] 2025-11-30 18:45:18.652 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.652 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.652 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.685 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.685 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for ShareLock on virtual transaction 71/1440 2025-11-30 18:45:18.685 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:18.686 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.686 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.686 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.728 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.728 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.728 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.785 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.785 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.785 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.807 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.807 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.807 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.829 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.829 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.829 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.850 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.850 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.850 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:18.879 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:18.879 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for AccessExclusiveLock on relation 53264 of database 16387 2025-11-30 18:45:18.879 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:18.880 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.880 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.880 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: update d4_fk set a = 1 where current of f; 2025-11-30 18:45:18.910 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.910 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.910 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: update d4_fk set a = 1 where current of f; 2025-11-30 18:45:18.942 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: removing partition "d4_primary1" violates foreign key constraint "d4_fk_a_fkey_1" 2025-11-30 18:45:18.942 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 DETAIL: Key (a)=(1) is still referenced from table "d4_fk". 2025-11-30 18:45:18.942 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:18.974 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:18.974 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:18.974 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:19.027 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:19.027 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:19.027 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:19.048 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:19.048 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for ShareLock on virtual transaction 71/1450 2025-11-30 18:45:19.048 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:19.089 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:19.089 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:19.089 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:19.142 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:19.142 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for ShareLock on virtual transaction 71/1452 2025-11-30 18:45:19.142 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:19.144 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:19.144 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:19.144 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:19.174 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 ERROR: canceling statement due to user request 2025-11-30 18:45:19.174 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 CONTEXT: waiting for ShareLock on virtual transaction 71/1453 2025-11-30 18:45:19.174 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 STATEMENT: alter table d4_primary detach partition d4_primary1 concurrently; 2025-11-30 18:45:19.175 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 ERROR: insert or update on table "d4_fk" violates foreign key constraint "d4_fk_a_fkey" 2025-11-30 18:45:19.175 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 DETAIL: Key (a)=(1) is not present in table "d4_primary". 2025-11-30 18:45:19.175 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 STATEMENT: insert into d4_fk values (1); 2025-11-30 18:45:19.176 UTC client backend[46119] isolation/detach-partition-concurrently-4/control connection LOG: disconnection: session time: 0:00:00.734 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.176 UTC client backend[46120] isolation/detach-partition-concurrently-4/s1 LOG: disconnection: session time: 0:00:00.732 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.177 UTC client backend[46122] isolation/detach-partition-concurrently-4/s3 LOG: disconnection: session time: 0:00:00.728 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.177 UTC client backend[46121] isolation/detach-partition-concurrently-4/s2 LOG: disconnection: session time: 0:00:00.731 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.182 UTC unrecognized[46125] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.183 UTC client backend[46125] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.183 UTC client backend[46125] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-contention 2025-11-30 18:45:19.184 UTC client backend[46125] isolation/fk-contention LOG: connection ready: setup total=2.150 ms, fork=0.545 ms, authentication=0.130 ms 2025-11-30 18:45:19.185 UTC unrecognized[46126] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.186 UTC client backend[46126] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.186 UTC client backend[46126] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-contention 2025-11-30 18:45:19.187 UTC client backend[46126] isolation/fk-contention LOG: connection ready: setup total=2.076 ms, fork=0.479 ms, authentication=0.127 ms 2025-11-30 18:45:19.188 UTC unrecognized[46127] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.188 UTC client backend[46127] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.188 UTC client backend[46127] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-contention 2025-11-30 18:45:19.189 UTC client backend[46127] isolation/fk-contention LOG: connection ready: setup total=1.676 ms, fork=0.343 ms, authentication=0.111 ms 2025-11-30 18:45:19.224 UTC client backend[46125] isolation/fk-contention/control connection LOG: disconnection: session time: 0:00:00.042 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.224 UTC client backend[46127] isolation/fk-contention/s2 LOG: disconnection: session time: 0:00:00.036 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.224 UTC client backend[46126] isolation/fk-contention/s1 LOG: disconnection: session time: 0:00:00.039 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.230 UTC unrecognized[46130] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.230 UTC client backend[46130] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.230 UTC client backend[46130] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-deadlock 2025-11-30 18:45:19.231 UTC client backend[46130] isolation/fk-deadlock LOG: connection ready: setup total=1.929 ms, fork=0.379 ms, authentication=0.125 ms 2025-11-30 18:45:19.232 UTC unrecognized[46131] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.233 UTC client backend[46131] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.233 UTC client backend[46131] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-deadlock 2025-11-30 18:45:19.234 UTC client backend[46131] isolation/fk-deadlock LOG: connection ready: setup total=1.771 ms, fork=0.361 ms, authentication=0.113 ms 2025-11-30 18:45:19.235 UTC unrecognized[46132] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.236 UTC client backend[46132] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.236 UTC client backend[46132] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-deadlock 2025-11-30 18:45:19.237 UTC client backend[46132] isolation/fk-deadlock LOG: connection ready: setup total=2.077 ms, fork=0.613 ms, authentication=0.114 ms 2025-11-30 18:45:19.349 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-11-30 18:45:19.349 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl; 2025-11-30 18:45:19.350 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-11-30 18:45:19.350 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl WHERE a = 1 and tststats.priv_test_tbl.* > (1, 1) is not null; 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl WHERE a <<< 0 AND b <<< 0; 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl WHERE a <<< 0 OR b <<< 0; 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl t WHERE a <<< 0 AND (b <<< 0 OR t.* <<< (1, 1) IS NOT NULL); 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-11-30 18:45:19.352 UTC client backend[46109] pg_regress/stats_ext STATEMENT: DELETE FROM tststats.priv_test_tbl WHERE a <<< 0 AND b <<< 0; 2025-11-30 18:45:19.359 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_parent_tbl 2025-11-30 18:45:19.359 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_parent_tbl WHERE a <<< 0 AND b <<< 0; 2025-11-30 18:45:19.360 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_parent_tbl 2025-11-30 18:45:19.360 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_parent_tbl WHERE a <<< 0 OR b <<< 0; 2025-11-30 18:45:19.360 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_parent_tbl 2025-11-30 18:45:19.360 UTC client backend[46109] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_parent_tbl t WHERE a <<< 0 AND (b <<< 0 OR t.* <<< (1, 1) IS NOT NULL); 2025-11-30 18:45:19.361 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for table priv_test_parent_tbl 2025-11-30 18:45:19.361 UTC client backend[46109] pg_regress/stats_ext STATEMENT: DELETE FROM tststats.priv_test_parent_tbl WHERE a <<< 0 AND b <<< 0; 2025-11-30 18:45:19.389 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for schema sts_sch1 2025-11-30 18:45:19.389 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS ON a, b, c FROM sts_sch1.tbl; 2025-11-30 18:45:19.389 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for schema sts_sch2 2025-11-30 18:45:19.389 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS sts_sch2.fail ON a, b, c FROM sts_sch1.tbl; 2025-11-30 18:45:19.390 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for schema sts_sch2 2025-11-30 18:45:19.390 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS sts_sch2.fail ON a, b, c FROM sts_sch1.tbl; 2025-11-30 18:45:19.391 UTC client backend[46109] pg_regress/stats_ext ERROR: permission denied for schema sts_sch1 2025-11-30 18:45:19.391 UTC client backend[46109] pg_regress/stats_ext STATEMENT: CREATE STATISTICS ON a, b, c FROM sts_sch1.tbl; 2025-11-30 18:45:19.497 UTC client backend[46130] isolation/fk-deadlock/control connection LOG: disconnection: session time: 0:00:00.267 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.497 UTC client backend[46132] isolation/fk-deadlock/s2 LOG: disconnection: session time: 0:00:00.262 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.497 UTC client backend[46131] isolation/fk-deadlock/s1 LOG: disconnection: session time: 0:00:00.265 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.503 UTC unrecognized[46135] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.503 UTC client backend[46135] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.503 UTC client backend[46135] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-deadlock2 2025-11-30 18:45:19.504 UTC client backend[46135] isolation/fk-deadlock2 LOG: connection ready: setup total=1.941 ms, fork=0.422 ms, authentication=0.118 ms 2025-11-30 18:45:19.506 UTC unrecognized[46136] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.506 UTC client backend[46136] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.506 UTC client backend[46136] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-deadlock2 2025-11-30 18:45:19.507 UTC client backend[46136] isolation/fk-deadlock2 LOG: connection ready: setup total=1.609 ms, fork=0.323 ms, authentication=0.109 ms 2025-11-30 18:45:19.508 UTC unrecognized[46137] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.508 UTC client backend[46137] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.508 UTC client backend[46137] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-deadlock2 2025-11-30 18:45:19.509 UTC client backend[46137] isolation/fk-deadlock2 LOG: connection ready: setup total=1.532 ms, fork=0.321 ms, authentication=0.094 ms 2025-11-30 18:45:19.712 UTC client backend[46109] pg_regress/stats_ext LOG: disconnection: session time: 0:00:01.768 user=postgres database=regression host=[local] 2025-11-30 18:45:19.728 UTC unrecognized[46149] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.729 UTC client backend[46149] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.729 UTC client backend[46149] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_parallel 2025-11-30 18:45:19.730 UTC client backend[46149] pg_regress/select_parallel LOG: connection ready: setup total=1.905 ms, fork=0.370 ms, authentication=0.126 ms 2025-11-30 18:45:19.733 UTC client backend[46135] isolation/fk-deadlock2/control connection LOG: disconnection: session time: 0:00:00.230 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.733 UTC client backend[46137] isolation/fk-deadlock2/s2 LOG: disconnection: session time: 0:00:00.225 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.733 UTC client backend[46136] isolation/fk-deadlock2/s1 LOG: disconnection: session time: 0:00:00.227 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:19.739 UTC unrecognized[46155] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.739 UTC client backend[46155] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.739 UTC client backend[46155] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-partitioned-1 2025-11-30 18:45:19.740 UTC client backend[46155] isolation/fk-partitioned-1 LOG: connection ready: setup total=1.709 ms, fork=0.329 ms, authentication=0.107 ms 2025-11-30 18:45:19.741 UTC unrecognized[46156] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.742 UTC client backend[46156] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.742 UTC client backend[46156] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-partitioned-1 2025-11-30 18:45:19.742 UTC client backend[46156] isolation/fk-partitioned-1 LOG: connection ready: setup total=1.575 ms, fork=0.291 ms, authentication=0.096 ms 2025-11-30 18:45:19.744 UTC unrecognized[46160] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:19.744 UTC client backend[46160] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:19.744 UTC client backend[46160] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-partitioned-1 2025-11-30 18:45:19.745 UTC client backend[46160] isolation/fk-partitioned-1 LOG: connection ready: setup total=1.682 ms, fork=0.331 ms, authentication=0.109 ms 2025-11-30 18:45:19.763 UTC client backend[46160] isolation/fk-partitioned-1/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:19.763 UTC client backend[46160] isolation/fk-partitioned-1/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:19.763 UTC client backend[46160] isolation/fk-partitioned-1/s2 STATEMENT: alter table pfk attach partition pfk1 for values in (1); 2025-11-30 18:45:19.781 UTC client backend[46160] isolation/fk-partitioned-1/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:19.781 UTC client backend[46160] isolation/fk-partitioned-1/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:19.781 UTC client backend[46160] isolation/fk-partitioned-1/s2 STATEMENT: alter table pfk attach partition pfk1 for values in (1); 2025-11-30 18:45:19.810 UTC client backend[46160] isolation/fk-partitioned-1/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:19.810 UTC client backend[46160] isolation/fk-partitioned-1/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:19.810 UTC client backend[46160] isolation/fk-partitioned-1/s2 STATEMENT: alter table pfk attach partition pfk1 for values in (1); 2025-11-30 18:45:19.828 UTC client backend[46160] isolation/fk-partitioned-1/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:19.828 UTC client backend[46160] isolation/fk-partitioned-1/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:19.828 UTC client backend[46160] isolation/fk-partitioned-1/s2 STATEMENT: alter table pfk attach partition pfk1 for values in (1); 2025-11-30 18:45:19.860 UTC client backend[46160] isolation/fk-partitioned-1/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:19.860 UTC client backend[46160] isolation/fk-partitioned-1/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:19.860 UTC client backend[46160] isolation/fk-partitioned-1/s2 STATEMENT: alter table pfk attach partition pfk1 for values in (1); 2025-11-30 18:45:19.890 UTC client backend[46156] isolation/fk-partitioned-1/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:19.890 UTC client backend[46156] isolation/fk-partitioned-1/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:19.890 UTC client backend[46156] isolation/fk-partitioned-1/s1 STATEMENT: delete from ppk1 where a = 1; 2025-11-30 18:45:19.911 UTC client backend[46156] isolation/fk-partitioned-1/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:19.911 UTC client backend[46156] isolation/fk-partitioned-1/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:19.911 UTC client backend[46156] isolation/fk-partitioned-1/s1 STATEMENT: delete from ppk1 where a = 1; 2025-11-30 18:45:19.930 UTC client backend[46160] isolation/fk-partitioned-1/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:19.930 UTC client backend[46160] isolation/fk-partitioned-1/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:19.930 UTC client backend[46160] isolation/fk-partitioned-1/s2 STATEMENT: alter table pfk attach partition pfk1 for values in (1); 2025-11-30 18:45:19.958 UTC client backend[46160] isolation/fk-partitioned-1/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:19.958 UTC client backend[46160] isolation/fk-partitioned-1/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:19.958 UTC client backend[46160] isolation/fk-partitioned-1/s2 STATEMENT: alter table pfk attach partition pfk1 for values in (1); 2025-11-30 18:45:19.987 UTC client backend[46156] isolation/fk-partitioned-1/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:19.987 UTC client backend[46156] isolation/fk-partitioned-1/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:19.987 UTC client backend[46156] isolation/fk-partitioned-1/s1 STATEMENT: delete from ppk1 where a = 1; 2025-11-30 18:45:20.007 UTC client backend[46156] isolation/fk-partitioned-1/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:20.007 UTC client backend[46156] isolation/fk-partitioned-1/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:20.007 UTC client backend[46156] isolation/fk-partitioned-1/s1 STATEMENT: delete from ppk1 where a = 1; 2025-11-30 18:45:20.037 UTC client backend[46156] isolation/fk-partitioned-1/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:20.037 UTC client backend[46156] isolation/fk-partitioned-1/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:20.037 UTC client backend[46156] isolation/fk-partitioned-1/s1 STATEMENT: delete from ppk1 where a = 1; 2025-11-30 18:45:20.056 UTC client backend[46156] isolation/fk-partitioned-1/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:20.056 UTC client backend[46156] isolation/fk-partitioned-1/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:20.056 UTC client backend[46156] isolation/fk-partitioned-1/s1 STATEMENT: delete from ppk1 where a = 1; 2025-11-30 18:45:20.075 UTC client backend[46156] isolation/fk-partitioned-1/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:20.075 UTC client backend[46156] isolation/fk-partitioned-1/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:20.075 UTC client backend[46156] isolation/fk-partitioned-1/s1 STATEMENT: delete from ppk1 where a = 1; 2025-11-30 18:45:20.081 UTC client backend[46155] isolation/fk-partitioned-1/control connection LOG: disconnection: session time: 0:00:00.342 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.081 UTC client backend[46160] isolation/fk-partitioned-1/s2 LOG: disconnection: session time: 0:00:00.337 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.083 UTC client backend[46156] isolation/fk-partitioned-1/s1 LOG: disconnection: session time: 0:00:00.341 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.088 UTC unrecognized[46272] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.088 UTC client backend[46272] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.088 UTC client backend[46272] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-partitioned-2 2025-11-30 18:45:20.089 UTC client backend[46272] isolation/fk-partitioned-2 LOG: connection ready: setup total=2.347 ms, fork=0.628 ms, authentication=0.141 ms 2025-11-30 18:45:20.091 UTC unrecognized[46273] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.092 UTC client backend[46273] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.092 UTC client backend[46273] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-partitioned-2 2025-11-30 18:45:20.092 UTC client backend[46273] isolation/fk-partitioned-2 LOG: connection ready: setup total=2.039 ms, fork=0.573 ms, authentication=0.122 ms 2025-11-30 18:45:20.094 UTC unrecognized[46274] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.094 UTC client backend[46274] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.094 UTC client backend[46274] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-partitioned-2 2025-11-30 18:45:20.095 UTC client backend[46274] isolation/fk-partitioned-2 LOG: connection ready: setup total=1.878 ms, fork=0.453 ms, authentication=0.123 ms 2025-11-30 18:45:20.124 UTC client backend[46274] isolation/fk-partitioned-2/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:20.124 UTC client backend[46274] isolation/fk-partitioned-2/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:20.124 UTC client backend[46274] isolation/fk-partitioned-2/s2 STATEMENT: insert into pfk values (1); 2025-11-30 18:45:20.156 UTC client backend[46274] isolation/fk-partitioned-2/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.156 UTC client backend[46274] isolation/fk-partitioned-2/s2 CONTEXT: SQL statement "SELECT 1 FROM "public"."ppk" x WHERE "a" OPERATOR(pg_catalog.=) $1 FOR KEY SHARE OF x" 2025-11-30 18:45:20.156 UTC client backend[46274] isolation/fk-partitioned-2/s2 STATEMENT: insert into pfk values (1); 2025-11-30 18:45:20.185 UTC client backend[46274] isolation/fk-partitioned-2/s2 ERROR: insert or update on table "pfk1" violates foreign key constraint "pfk_a_fkey" 2025-11-30 18:45:20.185 UTC client backend[46274] isolation/fk-partitioned-2/s2 DETAIL: Key (a)=(1) is not present in table "ppk". 2025-11-30 18:45:20.185 UTC client backend[46274] isolation/fk-partitioned-2/s2 STATEMENT: insert into pfk values (1); 2025-11-30 18:45:20.216 UTC client backend[46274] isolation/fk-partitioned-2/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.216 UTC client backend[46274] isolation/fk-partitioned-2/s2 CONTEXT: SQL statement "SELECT 1 FROM "public"."ppk" x WHERE "a" OPERATOR(pg_catalog.=) $1 FOR KEY SHARE OF x" 2025-11-30 18:45:20.216 UTC client backend[46274] isolation/fk-partitioned-2/s2 STATEMENT: insert into pfk values (1); 2025-11-30 18:45:20.251 UTC client backend[46273] isolation/fk-partitioned-2/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:20.251 UTC client backend[46273] isolation/fk-partitioned-2/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:20.251 UTC client backend[46273] isolation/fk-partitioned-2/s1 STATEMENT: delete from ppk where a = 1; 2025-11-30 18:45:20.285 UTC client backend[46273] isolation/fk-partitioned-2/s1 ERROR: update or delete on table "ppk1" violates foreign key constraint "pfk_a_fkey_1" on table "pfk" 2025-11-30 18:45:20.285 UTC client backend[46273] isolation/fk-partitioned-2/s1 DETAIL: Key (a)=(1) is still referenced from table "pfk". 2025-11-30 18:45:20.285 UTC client backend[46273] isolation/fk-partitioned-2/s1 STATEMENT: delete from ppk where a = 1; 2025-11-30 18:45:20.292 UTC client backend[46272] isolation/fk-partitioned-2/control connection LOG: disconnection: session time: 0:00:00.203 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.292 UTC client backend[46274] isolation/fk-partitioned-2/s2 LOG: disconnection: session time: 0:00:00.197 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.292 UTC client backend[46273] isolation/fk-partitioned-2/s1 LOG: disconnection: session time: 0:00:00.200 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.297 UTC unrecognized[46370] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.297 UTC client backend[46370] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.297 UTC client backend[46370] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot 2025-11-30 18:45:20.298 UTC client backend[46370] isolation/fk-snapshot LOG: connection ready: setup total=1.888 ms, fork=0.346 ms, authentication=0.135 ms 2025-11-30 18:45:20.301 UTC unrecognized[46375] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.301 UTC client backend[46375] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.301 UTC client backend[46375] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot 2025-11-30 18:45:20.302 UTC client backend[46375] isolation/fk-snapshot LOG: connection ready: setup total=1.877 ms, fork=0.309 ms, authentication=0.133 ms 2025-11-30 18:45:20.303 UTC unrecognized[46376] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.304 UTC client backend[46376] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.304 UTC client backend[46376] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot 2025-11-30 18:45:20.304 UTC client backend[46376] isolation/fk-snapshot LOG: connection ready: setup total=1.727 ms, fork=0.355 ms, authentication=0.108 ms 2025-11-30 18:45:20.320 UTC parallel worker[46381] ERROR: invalid input syntax for type smallint: "BAAAAAabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcd" 2025-11-30 18:45:20.320 UTC parallel worker[46381] STATEMENT: select (stringu1 || repeat('abcd', 5000))::int2 from tenk1 where unique1 = 1; 2025-11-30 18:45:20.320 UTC client backend[46149] pg_regress/select_parallel ERROR: invalid input syntax for type smallint: "BAAAAAabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcd" 2025-11-30 18:45:20.320 UTC client backend[46149] pg_regress/select_parallel CONTEXT: parallel worker 2025-11-30 18:45:20.320 UTC client backend[46149] pg_regress/select_parallel STATEMENT: select (stringu1 || repeat('abcd', 5000))::int2 from tenk1 where unique1 = 1; 2025-11-30 18:45:20.321 UTC postmaster[43401] LOG: background worker "parallel worker" (PID 46381) exited with exit code 1 2025-11-30 18:45:20.328 UTC client backend[46375] isolation/fk-snapshot/s1 ERROR: insert or update on table "fk_parted_pk_2" violates foreign key constraint "fk_parted_pk_a_fkey" 2025-11-30 18:45:20.328 UTC client backend[46375] isolation/fk-snapshot/s1 DETAIL: Key (a)=(2) is not present in table "pk_noparted". 2025-11-30 18:45:20.328 UTC client backend[46375] isolation/fk-snapshot/s1 STATEMENT: INSERT INTO fk_parted_pk VALUES (2); 2025-11-30 18:45:20.352 UTC client backend[46149] pg_regress/select_parallel ERROR: division by zero 2025-11-30 18:45:20.352 UTC client backend[46149] pg_regress/select_parallel CONTEXT: SQL function "set_role_and_error" statement 1 2025-11-30 18:45:20.352 UTC client backend[46149] pg_regress/select_parallel STATEMENT: select set_role_and_error(0); 2025-11-30 18:45:20.359 UTC parallel worker[46389] ERROR: division by zero 2025-11-30 18:45:20.359 UTC parallel worker[46389] CONTEXT: SQL function "set_role_and_error" statement 1 2025-11-30 18:45:20.359 UTC parallel worker[46389] STATEMENT: select set_role_and_error(0); 2025-11-30 18:45:20.359 UTC client backend[46149] pg_regress/select_parallel ERROR: division by zero 2025-11-30 18:45:20.359 UTC client backend[46149] pg_regress/select_parallel CONTEXT: SQL function "set_role_and_error" statement 1 parallel worker 2025-11-30 18:45:20.359 UTC client backend[46149] pg_regress/select_parallel STATEMENT: select set_role_and_error(0); 2025-11-30 18:45:20.360 UTC postmaster[43401] LOG: background worker "parallel worker" (PID 46389) exited with exit code 1 2025-11-30 18:45:20.367 UTC client backend[46149] pg_regress/select_parallel LOG: disconnection: session time: 0:00:00.639 user=postgres database=regression host=[local] 2025-11-30 18:45:20.373 UTC unrecognized[46392] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.373 UTC client backend[46392] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.373 UTC client backend[46392] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/write_parallel 2025-11-30 18:45:20.374 UTC client backend[46392] pg_regress/write_parallel LOG: connection ready: setup total=1.763 ms, fork=0.329 ms, authentication=0.111 ms 2025-11-30 18:45:20.455 UTC client backend[46392] pg_regress/write_parallel LOG: disconnection: session time: 0:00:00.082 user=postgres database=regression host=[local] 2025-11-30 18:45:20.461 UTC unrecognized[46421] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.461 UTC client backend[46421] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.461 UTC client backend[46421] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/vacuum_parallel 2025-11-30 18:45:20.462 UTC client backend[46421] pg_regress/vacuum_parallel LOG: connection ready: setup total=2.043 ms, fork=0.553 ms, authentication=0.118 ms 2025-11-30 18:45:20.503 UTC client backend[46376] isolation/fk-snapshot/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.503 UTC client backend[46376] isolation/fk-snapshot/s2 CONTEXT: SQL statement "DELETE FROM "public"."fk_parted_pk" WHERE $1 OPERATOR(pg_catalog.=) "a"" 2025-11-30 18:45:20.503 UTC client backend[46376] isolation/fk-snapshot/s2 STATEMENT: DELETE FROM pk_noparted WHERE a = 2; 2025-11-30 18:45:20.542 UTC client backend[46421] pg_regress/vacuum_parallel LOG: disconnection: session time: 0:00:00.081 user=postgres database=regression host=[local] 2025-11-30 18:45:20.545 UTC client backend[46376] isolation/fk-snapshot/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.545 UTC client backend[46376] isolation/fk-snapshot/s2 CONTEXT: SQL statement "UPDATE ONLY "public"."fk_noparted_sn" SET "a" = NULL WHERE $1 OPERATOR(pg_catalog.=) "a"" 2025-11-30 18:45:20.545 UTC client backend[46376] isolation/fk-snapshot/s2 STATEMENT: DELETE FROM pk_noparted WHERE a = 2; 2025-11-30 18:45:20.548 UTC unrecognized[46425] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.549 UTC client backend[46425] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.549 UTC client backend[46425] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/maintain_every 2025-11-30 18:45:20.550 UTC client backend[46425] pg_regress/maintain_every LOG: connection ready: setup total=2.087 ms, fork=0.467 ms, authentication=0.133 ms 2025-11-30 18:45:20.557 UTC client backend[46370] isolation/fk-snapshot/control connection LOG: disconnection: session time: 0:00:00.259 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.557 UTC client backend[46376] isolation/fk-snapshot/s2 LOG: disconnection: session time: 0:00:00.253 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.557 UTC client backend[46375] isolation/fk-snapshot/s1 LOG: disconnection: session time: 0:00:00.256 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "char_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "float8_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "int2_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "int4_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "int8_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "point_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "text_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "varchar_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "onek", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "onek2", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tenk1", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tenk2", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "road", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "person", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "emp", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "student", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "stud_emp", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_ln", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "ihighway", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_statistic", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_type", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "shighway", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_sub", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_div", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_mul", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_sqrt", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_log10", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_power_10_ln", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "numrange_test", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_foreign_table", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_authid", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "money_data", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "float4_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_statistic_ext_data", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "textrange_test", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "test_range_gist", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "test_range_spgist", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_input_test", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "test_range_excl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_user_mapping", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_subscription", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_typemod_test", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_attribute", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "path_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "line_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "timetz_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "date_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "time_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "box_tbl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_attrdef", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_constraint", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_inherits", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_index", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_operator", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_opfamily", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_opclass", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_amop", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_proc", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_amproc", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_language", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_largeobject_metadata", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_data", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_aggregate", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_statistic_ext", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_rewrite", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_trigger", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_event_trigger", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_description", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_cast", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_enum", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_namespace", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_conversion", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_db_role_setting", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_tablespace", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_auth_members", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_shdepend", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_shdescription", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_config", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_config_map", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_dict", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_add", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_parser", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_template", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_extension", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_foreign_data_wrapper", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_foreign_server", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_policy", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_replication_origin", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_default_acl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_init_privs", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_seclabel", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_shseclabel", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_collation", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_parameter_acl", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_partitioned_table", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_range", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_transform", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_sequence", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_publication", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_publication_namespace", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_publication_rel", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_subscription_rel", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_largeobject", skipping it 2025-11-30 18:45:20.559 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sql_features", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sql_implementation_info", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sql_parts", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sql_sizing", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "num_result", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "bit_defaults", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "inet_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "polygon_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "interval_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "lseg_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "circle_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "quad_poly_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "infinite_interval_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "timestamp_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "nummultirange_test", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "quad_box_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "quad_box_tbl_ord_seq1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "quad_box_tbl_ord_seq2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "reservations", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "timestamptz_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tab_core_types", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_def", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_defd", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted11", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted12", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted4", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_def1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_def2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "city", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "b_star", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "d_star", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "f_star", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "a_star", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "c_star", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "e_star", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "extra_wide_table", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "ramp", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "quad_point_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "real_city", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_reg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_unique1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_unique2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_pk", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_box", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_box_pk", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "view_base_table", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "kd_point_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "radix_text_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "slow_emp4000", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "fast_emp4000", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "array_index_op_test", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "func_index_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "dupindexcols", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "arrtest", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "default_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "array_op_test", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "b", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "c", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "aggtest", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "log_table", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "main_table", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "defaultexpr_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "check_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "ne_check_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "a", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "d", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "check2_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "insert_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "past_inh_parent", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "past_parted", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_am", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "persons", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "persons2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "persons3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_tbl_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_tblas_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_c_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_tblmv_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_a_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_b_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_d_heap2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_class", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_database", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "copy_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "hash_i4_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "hash_name_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "hash_txt_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "hash_f8_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "invalid_check_con_child", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "invalid_check_con", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "cc1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "cc2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pp1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "xacttest", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "bt_i4_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "bt_name_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "bt_txt_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "bt_f8_heap", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "subselect_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "btree_tall_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "delete_test_table", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "dedup_unique_test_table", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "regress_constr_partition1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "regress_constr_partitioned", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "cnn_uq", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl6_1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_lk", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_lk2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_lk3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_cld", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_cld2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_cld3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl5_child", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl5", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl6", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl1_copy", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p1_1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p2_2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "constr_child", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "constr_parent", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "constr_child2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "constr_parent2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl1_upg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_child_upg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_parent_upg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_1_upg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_upg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_2_upg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_3_upg", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "constr_child3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "constr_parent3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "regress_notnull2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "regress_notnull1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "agg_data_2k", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "agg_data_20k", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_t", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brin_summarize", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brinopers", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gist_point_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "test_tablesample", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest0", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sk", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "emp1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sj", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t1", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t2", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t3", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t4", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_point_tbl", skipping it 2025-11-30 18:45:20.560 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brintest", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gin_test_tbl", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_box_tbl", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "bug_16784", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gs_data_1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtesty", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest4", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest9", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest10", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest11", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest13", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_bb", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tm", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tvm", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tmm", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_text_tbl", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_domain_tbl", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_unlogged_tbl", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest5", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest17", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest18", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest3", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest6", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest7", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest7a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest7c", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest7b", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brin_test", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestx", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_3", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_4", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_y", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_tableoid", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tvmm", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tvvm", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest7e", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest7d", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20b", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20c", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21b", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22b", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22c", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1_p1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1_p2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1_p1_like", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pitest2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pitest2_p2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "itest14", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "identity_dump_logged", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "identity_dump_unlogged", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest23p", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest23q", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24r", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24nn", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_parent", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child3", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest25", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest27", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest29", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30_1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest26", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28b", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "datdba_only", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rls_tbl", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rls_tbl_force", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brintest_multi", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brintest_bloom", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brinopers_bloom", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brinopers_multi", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brin_summarize_bloom", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brin_test_bloom", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brin_summarize_multi", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "brin_test_multi", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest0", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "inhf", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "point_table", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "inhx", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "hobbies_r", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "equipment_r", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtesty", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestx", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_3", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_4", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_y", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_tableoid", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20b", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20c", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21b", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestnn_parent", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestnn_child", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_rng", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtestnn_childdef", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22c", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest23a", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24at", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24ata", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_parent", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child3", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest29", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30_1", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest25", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest27", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "pg_depend", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk2_rng2rng", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_rng2", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk_rng2rng", skipping it 2025-11-30 18:45:20.561 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_mltrng2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_mltrng", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk2_mltrng2mltrng", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk_mltrng2mltrng", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_comp", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_unitfact", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "shoe_data", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "unit", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_log", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_data", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_arrive", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_ok", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest26", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28a", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28b", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_order2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t7", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t8", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t9", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t4", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t6", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_order1", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn3", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn4", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn1", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view1", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view3", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view4", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t5", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t1", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t3", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_interface", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_admin", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_system", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_person", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_emplog", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_empmass", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_emp", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "ruletest_tbl2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "ruletest_tbl", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rule_and_refint_t1", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rule_and_refint_t2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rule_and_refint_t3", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "ndistinct", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "functional_dependencies", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mcv_lists_arrays", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mcv_lists_bool", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "mcv_lists", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rules_log", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rules_src", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rule_merge2", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "rule_merge1", skipping it 2025-11-30 18:45:20.562 UTC client backend[46425] pg_regress/maintain_every WARNING: permission denied to analyze "parallel_vacuum_table", skipping it 2025-11-30 18:45:20.563 UTC unrecognized[46428] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.563 UTC client backend[46428] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.563 UTC client backend[46428] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot-2 2025-11-30 18:45:20.564 UTC client backend[46428] isolation/fk-snapshot-2 LOG: connection ready: setup total=2.051 ms, fork=0.558 ms, authentication=0.131 ms 2025-11-30 18:45:20.565 UTC client backend[46425] pg_regress/maintain_every LOG: disconnection: session time: 0:00:00.016 user=postgres database=regression host=[local] 2025-11-30 18:45:20.566 UTC unrecognized[46430] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.566 UTC client backend[46430] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.566 UTC client backend[46430] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot-2 2025-11-30 18:45:20.567 UTC client backend[46430] isolation/fk-snapshot-2 LOG: connection ready: setup total=1.765 ms, fork=0.343 ms, authentication=0.118 ms 2025-11-30 18:45:20.568 UTC unrecognized[46433] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.569 UTC client backend[46433] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.569 UTC client backend[46433] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot-2 2025-11-30 18:45:20.570 UTC client backend[46433] isolation/fk-snapshot-2 LOG: connection ready: setup total=1.751 ms, fork=0.369 ms, authentication=0.114 ms 2025-11-30 18:45:20.570 UTC unrecognized[46435] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.570 UTC unrecognized[46434] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.571 UTC client backend[46435] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.571 UTC client backend[46435] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/subscription 2025-11-30 18:45:20.571 UTC client backend[46434] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.571 UTC client backend[46434] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/publication 2025-11-30 18:45:20.572 UTC client backend[46435] pg_regress/subscription LOG: connection ready: setup total=1.777 ms, fork=0.314 ms, authentication=0.125 ms 2025-11-30 18:45:20.572 UTC client backend[46434] pg_regress/publication LOG: connection ready: setup total=2.361 ms, fork=0.564 ms, authentication=0.159 ms 2025-11-30 18:45:20.573 UTC client backend[46435] pg_regress/subscription ERROR: syntax error at or near ";" at character 53 2025-11-30 18:45:20.573 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'foo'; 2025-11-30 18:45:20.573 UTC client backend[46435] pg_regress/subscription ERROR: syntax error at or near "PUBLICATION" at character 37 2025-11-30 18:45:20.573 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub PUBLICATION foo; 2025-11-30 18:45:20.573 UTC client backend[46435] pg_regress/subscription ERROR: CREATE SUBSCRIPTION ... WITH (create_slot = true) cannot run inside a transaction block 2025-11-30 18:45:20.573 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'testconn' PUBLICATION testpub WITH (create_slot); 2025-11-30 18:45:20.573 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.573 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.574 UTC client backend[46435] pg_regress/subscription ERROR: invalid connection string syntax: missing "=" after "testconn" in connection info string 2025-11-30 18:45:20.574 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'testconn' PUBLICATION testpub; 2025-11-30 18:45:20.574 UTC client backend[46435] pg_regress/subscription ERROR: publication name "foo" used more than once 2025-11-30 18:45:20.574 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION foo, testpub, foo WITH (connect = false); 2025-11-30 18:45:20.575 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.575 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.576 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.576 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication ERROR: unrecognized publication parameter: "foo" 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (foo); 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication ERROR: unrecognized value for publication option "publish": "cluster" 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish = 'cluster, vacuum'); 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication ERROR: conflicting or redundant options at character 75 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish_via_partition_root = 'true', publish_via_partition_root = '0'); 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication ERROR: conflicting or redundant options at character 74 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish_generated_columns = stored, publish_generated_columns = none); 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication ERROR: invalid value for publication parameter "publish_generated_columns": "foo" 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication DETAIL: Valid values are "none" and "stored". 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish_generated_columns = foo); 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication ERROR: invalid value for publication parameter "publish_generated_columns": "" 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication DETAIL: Valid values are "none" and "stored". 2025-11-30 18:45:20.577 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish_generated_columns); 2025-11-30 18:45:20.580 UTC client backend[46435] pg_regress/subscription ERROR: subscription "regress_testsub" already exists 2025-11-30 18:45:20.580 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false); 2025-11-30 18:45:20.580 UTC client backend[46435] pg_regress/subscription ERROR: permission denied to create subscription 2025-11-30 18:45:20.580 UTC client backend[46435] pg_regress/subscription DETAIL: Only roles with privileges of the "pg_create_subscription" role may create subscriptions. 2025-11-30 18:45:20.580 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION foo WITH (connect = false); 2025-11-30 18:45:20.580 UTC client backend[46435] pg_regress/subscription ERROR: connect = false and copy_data = true are mutually exclusive options 2025-11-30 18:45:20.580 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, copy_data = true); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: connect = false and enabled = true are mutually exclusive options 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, enabled = true); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: connect = false and create_slot = true are mutually exclusive options 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, create_slot = true); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: slot_name = NONE and enabled = true are mutually exclusive options 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, enabled = true); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: slot_name = NONE and create_slot = true are mutually exclusive options 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, enabled = false, create_slot = true); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: subscription with slot_name = NONE must also set enabled = false 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: subscription with slot_name = NONE must also set create_slot = false 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, enabled = false); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: subscription with slot_name = NONE must also set enabled = false 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, create_slot = false); 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: cannot enable subscription that does not have a slot name 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub3 ENABLE; 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: ALTER SUBSCRIPTION ... REFRESH PUBLICATION is not allowed for disabled subscriptions 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub3 REFRESH PUBLICATION; 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription ERROR: unrecognized origin value: "foo" 2025-11-30 18:45:20.581 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub4 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, connect = false, origin = foo); 2025-11-30 18:45:20.582 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.582 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.585 UTC client backend[46435] pg_regress/subscription ERROR: invalid connection string syntax: invalid connection option "i_dont_exist" 2025-11-30 18:45:20.585 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub5 CONNECTION 'i_dont_exist=param' PUBLICATION testpub; 2025-11-30 18:45:20.585 UTC client backend[46435] pg_regress/subscription ERROR: subscription "regress_testsub5" could not connect to the publisher: invalid port number: "-1" 2025-11-30 18:45:20.585 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub5 CONNECTION 'port=-1' PUBLICATION testpub; 2025-11-30 18:45:20.585 UTC client backend[46435] pg_regress/subscription ERROR: invalid connection string syntax: missing "=" after "foobar" in connection info string 2025-11-30 18:45:20.585 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub CONNECTION 'foobar'; 2025-11-30 18:45:20.587 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.587 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.587 UTC client backend[46435] pg_regress/subscription ERROR: replication slot name "" is too short 2025-11-30 18:45:20.587 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET (slot_name = ''); 2025-11-30 18:45:20.587 UTC client backend[46435] pg_regress/subscription ERROR: subscription "regress_doesnotexist" does not exist 2025-11-30 18:45:20.587 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_doesnotexist CONNECTION 'dbname=regress_doesnotexist2'; 2025-11-30 18:45:20.587 UTC client backend[46435] pg_regress/subscription ERROR: unrecognized subscription parameter: "create_slot" 2025-11-30 18:45:20.587 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET (create_slot = false); 2025-11-30 18:45:20.588 UTC client backend[46435] pg_regress/subscription ERROR: invalid WAL location (LSN): 0/0 2025-11-30 18:45:20.588 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SKIP (lsn = '0/0'); 2025-11-30 18:45:20.589 UTC client backend[46435] pg_regress/subscription ERROR: must be owner of subscription regress_testsub 2025-11-30 18:45:20.589 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub RENAME TO regress_testsub_dummy; 2025-11-30 18:45:20.590 UTC client backend[46435] pg_regress/subscription ERROR: invalid value for parameter "synchronous_commit": "foobar" 2025-11-30 18:45:20.590 UTC client backend[46435] pg_regress/subscription HINT: Available values: local, remote_write, remote_apply, on, off. 2025-11-30 18:45:20.590 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub_foo SET (synchronous_commit = foobar); 2025-11-30 18:45:20.591 UTC client backend[46435] pg_regress/subscription ERROR: DROP SUBSCRIPTION cannot run inside a transaction block 2025-11-30 18:45:20.591 UTC client backend[46435] pg_regress/subscription STATEMENT: DROP SUBSCRIPTION regress_testsub; 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication DETAIL: Tables or sequences cannot be added to or dropped from FOR ALL TABLES publications. 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables ADD TABLE testpub_tbl2; 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication DETAIL: Tables or sequences cannot be added to or dropped from FOR ALL TABLES publications. 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables DROP TABLE testpub_tbl2; 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication DETAIL: Tables or sequences cannot be added to or dropped from FOR ALL TABLES publications. 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables SET TABLE pub_test.testpub_nopk; 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication DETAIL: Schemas cannot be added to or dropped from FOR ALL TABLES publications. 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables ADD TABLES IN SCHEMA pub_test; 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication DETAIL: Schemas cannot be added to or dropped from FOR ALL TABLES publications. 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables DROP TABLES IN SCHEMA pub_test; 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication DETAIL: Schemas cannot be added to or dropped from FOR ALL TABLES publications. 2025-11-30 18:45:20.591 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables SET TABLES IN SCHEMA pub_test; 2025-11-30 18:45:20.591 UTC client backend[46435] pg_regress/subscription ERROR: subscription "regress_testsub" does not exist 2025-11-30 18:45:20.591 UTC client backend[46435] pg_regress/subscription STATEMENT: DROP SUBSCRIPTION regress_testsub; 2025-11-30 18:45:20.591 UTC client backend[46435] pg_regress/subscription ERROR: binary requires a Boolean value 2025-11-30 18:45:20.591 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, binary = foo); 2025-11-30 18:45:20.592 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.592 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.592 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.592 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.593 UTC client backend[46435] pg_regress/subscription ERROR: streaming requires a Boolean value or "parallel" 2025-11-30 18:45:20.593 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, streaming = foo); 2025-11-30 18:45:20.593 UTC client backend[46430] isolation/fk-snapshot-2/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_fkey" on table "child" 2025-11-30 18:45:20.593 UTC client backend[46430] isolation/fk-snapshot-2/s1 DETAIL: Key (parent_id)=(1) is still referenced from table "child". 2025-11-30 18:45:20.593 UTC client backend[46430] isolation/fk-snapshot-2/s1 STATEMENT: DELETE FROM parent WHERE parent_id = 1; 2025-11-30 18:45:20.593 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.593 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.595 UTC client backend[46435] pg_regress/subscription ERROR: publication "testpub" is already in subscription "regress_testsub" 2025-11-30 18:45:20.595 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub ADD PUBLICATION testpub WITH (refresh = false); 2025-11-30 18:45:20.595 UTC client backend[46435] pg_regress/subscription ERROR: publication name "testpub1" used more than once 2025-11-30 18:45:20.595 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub ADD PUBLICATION testpub1, testpub1 WITH (refresh = false); 2025-11-30 18:45:20.595 UTC client backend[46435] pg_regress/subscription ERROR: publication "testpub1" is already in subscription "regress_testsub" 2025-11-30 18:45:20.595 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub ADD PUBLICATION testpub1, testpub2 WITH (refresh = false); 2025-11-30 18:45:20.596 UTC client backend[46435] pg_regress/subscription ERROR: publication name "testpub1" used more than once 2025-11-30 18:45:20.596 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub DROP PUBLICATION testpub1, testpub1 WITH (refresh = false); 2025-11-30 18:45:20.596 UTC client backend[46435] pg_regress/subscription ERROR: cannot drop all the publications from a subscription 2025-11-30 18:45:20.596 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub DROP PUBLICATION testpub, testpub1, testpub2 WITH (refresh = false); 2025-11-30 18:45:20.596 UTC client backend[46435] pg_regress/subscription ERROR: publication "testpub3" is not in subscription "regress_testsub" 2025-11-30 18:45:20.596 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub DROP PUBLICATION testpub3 WITH (refresh = false); 2025-11-30 18:45:20.597 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.597 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.597 UTC client backend[46435] pg_regress/subscription ERROR: ALTER SUBSCRIPTION with refresh cannot run inside a transaction block 2025-11-30 18:45:20.597 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET PUBLICATION mypub WITH (refresh = true); 2025-11-30 18:45:20.597 UTC client backend[46435] pg_regress/subscription ERROR: ALTER SUBSCRIPTION ... REFRESH PUBLICATION cannot run inside a transaction block 2025-11-30 18:45:20.597 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub REFRESH PUBLICATION; 2025-11-30 18:45:20.598 UTC client backend[46435] pg_regress/subscription ERROR: ALTER SUBSCRIPTION with refresh cannot be executed from a function 2025-11-30 18:45:20.598 UTC client backend[46435] pg_regress/subscription CONTEXT: SQL function "func" statement 1 2025-11-30 18:45:20.598 UTC client backend[46435] pg_regress/subscription STATEMENT: SELECT func(); 2025-11-30 18:45:20.599 UTC logical replication apply worker[46436] FATAL: terminating logical replication worker due to administrator command 2025-11-30 18:45:20.600 UTC postmaster[43401] LOG: background worker "logical replication apply worker" (PID 46436) exited with exit code 1 2025-11-30 18:45:20.604 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.604 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.605 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.605 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.607 UTC client backend[46434] pg_regress/publication ERROR: invalid table name at character 71 2025-11-30 18:45:20.607 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_parsertst FOR TABLE pub_test.testpub_nopk, CURRENT_SCHEMA; 2025-11-30 18:45:20.607 UTC client backend[46434] pg_regress/publication ERROR: invalid schema name at character 64 2025-11-30 18:45:20.607 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_parsertst FOR TABLES IN SCHEMA foo, test.foo; 2025-11-30 18:45:20.609 UTC client backend[46435] pg_regress/subscription ERROR: two_phase requires a Boolean value 2025-11-30 18:45:20.609 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, two_phase = foo); 2025-11-30 18:45:20.610 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.610 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.611 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.611 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.611 UTC client backend[46434] pg_regress/publication ERROR: relation "testpub_nopk" is not part of the publication 2025-11-30 18:45:20.611 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_forschema DROP TABLE pub_test.testpub_nopk; 2025-11-30 18:45:20.612 UTC client backend[46435] pg_regress/subscription ERROR: disable_on_error requires a Boolean value 2025-11-30 18:45:20.612 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, disable_on_error = foo); 2025-11-30 18:45:20.612 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.612 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.614 UTC client backend[46435] pg_regress/subscription ERROR: retain_dead_tuples requires a Boolean value 2025-11-30 18:45:20.614 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, retain_dead_tuples = foo); 2025-11-30 18:45:20.614 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.614 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.615 UTC client backend[46435] pg_regress/subscription ERROR: max_retention_duration requires an integer value 2025-11-30 18:45:20.615 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, max_retention_duration = foo); 2025-11-30 18:45:20.615 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.615 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.616 UTC client backend[46435] pg_regress/subscription ERROR: permission denied for database regression 2025-11-30 18:45:20.616 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false); 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription ERROR: password is required 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription DETAIL: Non-superusers must provide a password in the connection string. 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false); 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription ERROR: password_required=false is superuser-only 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription HINT: Subscriptions with the password_required option set to false may only be created or modified by the superuser. 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, password_required = false); 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and alter the subscription to refresh publications. 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription ERROR: must be able to SET ROLE "regress_subscription_user" 2025-11-30 18:45:20.617 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub OWNER TO regress_subscription_user; 2025-11-30 18:45:20.618 UTC client backend[46433] isolation/fk-snapshot-2/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.618 UTC client backend[46433] isolation/fk-snapshot-2/s2 CONTEXT: SQL statement "SELECT 1 FROM ONLY "public"."parent" x WHERE "parent_id" OPERATOR(pg_catalog.=) $1 FOR KEY SHARE OF x" 2025-11-30 18:45:20.618 UTC client backend[46433] isolation/fk-snapshot-2/s2 STATEMENT: INSERT INTO child VALUES (1, 1); 2025-11-30 18:45:20.618 UTC client backend[46435] pg_regress/subscription ERROR: permission denied for database regression 2025-11-30 18:45:20.618 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub RENAME TO regress_testsub2; 2025-11-30 18:45:20.619 UTC client backend[46435] pg_regress/subscription ERROR: ALTER SUBSCRIPTION ... SET (failover) cannot run inside a transaction block 2025-11-30 18:45:20.619 UTC client backend[46435] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET (failover); 2025-11-30 18:45:20.620 UTC client backend[46435] pg_regress/subscription LOG: disconnection: session time: 0:00:00.049 user=postgres database=regression host=[local] 2025-11-30 18:45:20.640 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.640 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.641 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.641 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.642 UTC client backend[46430] isolation/fk-snapshot-2/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_fkey" on table "child" 2025-11-30 18:45:20.642 UTC client backend[46430] isolation/fk-snapshot-2/s1 DETAIL: Key (parent_id)=(1) is still referenced from table "child". 2025-11-30 18:45:20.642 UTC client backend[46430] isolation/fk-snapshot-2/s1 STATEMENT: DELETE FROM parent WHERE parent_id = 1; 2025-11-30 18:45:20.649 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.649 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.657 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.657 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.662 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.662 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.663 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.663 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.663 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.663 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.665 UTC client backend[46433] isolation/fk-snapshot-2/s2 ERROR: insert or update on table "child" violates foreign key constraint "child_parent_id_fkey" 2025-11-30 18:45:20.665 UTC client backend[46433] isolation/fk-snapshot-2/s2 DETAIL: Key (parent_id)=(1) is not present in table "parent". 2025-11-30 18:45:20.665 UTC client backend[46433] isolation/fk-snapshot-2/s2 STATEMENT: INSERT INTO child VALUES (1, 1); 2025-11-30 18:45:20.666 UTC client backend[46434] pg_regress/publication ERROR: invalid publication object list at character 90 2025-11-30 18:45:20.666 UTC client backend[46434] pg_regress/publication DETAIL: ALL TABLES can be specified only once. 2025-11-30 18:45:20.666 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION regress_pub_for_allsequences_alltables FOR ALL SEQUENCES, ALL TABLES, ALL TABLES; 2025-11-30 18:45:20.667 UTC client backend[46434] pg_regress/publication ERROR: invalid publication object list at character 90 2025-11-30 18:45:20.667 UTC client backend[46434] pg_regress/publication DETAIL: ALL SEQUENCES can be specified only once. 2025-11-30 18:45:20.667 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION regress_pub_for_allsequences_alltables FOR ALL SEQUENCES, ALL TABLES, ALL SEQUENCES; 2025-11-30 18:45:20.667 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.667 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.667 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.667 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.674 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_parted1" because it does not have a replica identity and publishes updates 2025-11-30 18:45:20.674 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:20.674 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_parted1 SET a = 1; 2025-11-30 18:45:20.677 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_parted2" because it does not have a replica identity and publishes updates 2025-11-30 18:45:20.677 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:20.677 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_parted2 SET a = 2; 2025-11-30 18:45:20.688 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.688 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.690 UTC client backend[46430] isolation/fk-snapshot-2/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_fkey" on table "child" 2025-11-30 18:45:20.690 UTC client backend[46430] isolation/fk-snapshot-2/s1 DETAIL: Key (parent_id)=(1) is still referenced from table "child". 2025-11-30 18:45:20.690 UTC client backend[46430] isolation/fk-snapshot-2/s1 STATEMENT: DELETE FROM parent WHERE parent_id = 1; 2025-11-30 18:45:20.714 UTC client backend[46433] isolation/fk-snapshot-2/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.714 UTC client backend[46433] isolation/fk-snapshot-2/s2 CONTEXT: SQL statement "SELECT 1 FROM ONLY "public"."parent" x WHERE "parent_id" OPERATOR(pg_catalog.=) $1 FOR KEY SHARE OF x" 2025-11-30 18:45:20.714 UTC client backend[46433] isolation/fk-snapshot-2/s2 STATEMENT: INSERT INTO child VALUES (1, 1); 2025-11-30 18:45:20.719 UTC client backend[46428] isolation/fk-snapshot-2/control connection LOG: disconnection: session time: 0:00:00.155 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.719 UTC client backend[46430] isolation/fk-snapshot-2/s1 LOG: disconnection: session time: 0:00:00.152 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.719 UTC client backend[46433] isolation/fk-snapshot-2/s2 LOG: disconnection: session time: 0:00:00.150 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:20.723 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.723 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.724 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.724 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.725 UTC unrecognized[46439] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.725 UTC client backend[46439] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.725 UTC client backend[46439] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot-3 2025-11-30 18:45:20.729 UTC client backend[46439] isolation/fk-snapshot-3 LOG: connection ready: setup total=5.061 ms, fork=0.509 ms, authentication=0.114 ms 2025-11-30 18:45:20.730 UTC unrecognized[46440] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.731 UTC client backend[46440] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.731 UTC client backend[46440] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot-3 2025-11-30 18:45:20.732 UTC client backend[46440] isolation/fk-snapshot-3 LOG: connection ready: setup total=2.041 ms, fork=0.380 ms, authentication=0.137 ms 2025-11-30 18:45:20.733 UTC unrecognized[46441] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:20.733 UTC client backend[46441] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:20.733 UTC client backend[46441] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/fk-snapshot-3 2025-11-30 18:45:20.734 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.734 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.734 UTC client backend[46441] isolation/fk-snapshot-3 LOG: connection ready: setup total=1.721 ms, fork=0.334 ms, authentication=0.115 ms 2025-11-30 18:45:20.737 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.737 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.740 UTC client backend[46434] pg_regress/publication ERROR: syntax error at or near "WHERE" at character 76 2025-11-30 18:45:20.740 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_syntax3 FOR TABLES IN SCHEMA testpub_rf_schema1 WHERE (a = 123); 2025-11-30 18:45:20.740 UTC client backend[46434] pg_regress/publication ERROR: WHERE clause not allowed for schema at character 77 2025-11-30 18:45:20.740 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_syntax3 FOR TABLES IN SCHEMA testpub_rf_schema1, testpub_rf_schema1 WHERE (a = 123); 2025-11-30 18:45:20.740 UTC client backend[46434] pg_regress/publication ERROR: conflicting or redundant WHERE clauses for table "testpub_rf_tbl1" 2025-11-30 18:45:20.740 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_rf_tbl1 WHERE (a = 1), testpub_rf_tbl1 WITH (publish = 'insert'); 2025-11-30 18:45:20.741 UTC client backend[46434] pg_regress/publication ERROR: conflicting or redundant WHERE clauses for table "testpub_rf_tbl1" 2025-11-30 18:45:20.741 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_rf_tbl1, testpub_rf_tbl1 WHERE (a = 2) WITH (publish = 'insert'); 2025-11-30 18:45:20.741 UTC client backend[46434] pg_regress/publication ERROR: argument of PUBLICATION WHERE must be type boolean, not type integer at character 61 2025-11-30 18:45:20.741 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 SET TABLE testpub_rf_tbl3 WHERE (1234); 2025-11-30 18:45:20.741 UTC client backend[46434] pg_regress/publication ERROR: aggregate functions are not allowed in WHERE at character 65 2025-11-30 18:45:20.741 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 SET TABLE testpub_rf_tbl3 WHERE (e < AVG(e)); 2025-11-30 18:45:20.742 UTC client backend[46434] pg_regress/publication ERROR: invalid publication WHERE expression at character 62 2025-11-30 18:45:20.742 UTC client backend[46434] pg_regress/publication DETAIL: User-defined operators are not allowed. 2025-11-30 18:45:20.742 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl3 WHERE (e =#> 27); 2025-11-30 18:45:20.743 UTC client backend[46434] pg_regress/publication ERROR: invalid publication WHERE expression at character 66 2025-11-30 18:45:20.743 UTC client backend[46434] pg_regress/publication DETAIL: User-defined or built-in mutable functions are not allowed. 2025-11-30 18:45:20.743 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 ADD TABLE testpub_rf_tbl1 WHERE (a >= testpub_rf_func2()); 2025-11-30 18:45:20.744 UTC client backend[46434] pg_regress/publication ERROR: invalid publication WHERE expression at character 65 2025-11-30 18:45:20.744 UTC client backend[46434] pg_regress/publication DETAIL: User-defined or built-in mutable functions are not allowed. 2025-11-30 18:45:20.744 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 ADD TABLE testpub_rf_tbl1 WHERE (a < random()); 2025-11-30 18:45:20.745 UTC client backend[46434] pg_regress/publication ERROR: invalid publication WHERE expression at character 61 2025-11-30 18:45:20.745 UTC client backend[46434] pg_regress/publication DETAIL: User-defined collations are not allowed. 2025-11-30 18:45:20.745 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 ADD TABLE testpub_rf_tbl1 WHERE (b < '2' COLLATE user_collation); 2025-11-30 18:45:20.756 UTC client backend[46434] pg_regress/publication ERROR: invalid publication WHERE expression at character 53 2025-11-30 18:45:20.756 UTC client backend[46434] pg_regress/publication DETAIL: User-defined types are not allowed. 2025-11-30 18:45:20.756 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE rf_bug WHERE (status = 'open') WITH (publish = 'insert'); 2025-11-30 18:45:20.759 UTC client backend[46434] pg_regress/publication ERROR: invalid publication WHERE expression at character 62 2025-11-30 18:45:20.759 UTC client backend[46434] pg_regress/publication DETAIL: Only columns, constants, built-in operators, built-in data types, built-in collations, and immutable built-in functions are allowed. 2025-11-30 18:45:20.759 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl1 WHERE (a IN (SELECT generate_series(1,5))); 2025-11-30 18:45:20.759 UTC client backend[46434] pg_regress/publication ERROR: invalid publication WHERE expression at character 77 2025-11-30 18:45:20.759 UTC client backend[46434] pg_regress/publication DETAIL: System columns are not allowed. 2025-11-30 18:45:20.759 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl1 WHERE ('(0,1)'::tid = ctid); 2025-11-30 18:45:20.760 UTC client backend[46440] isolation/fk-snapshot-3/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_valid_at_fkey" on table "child" 2025-11-30 18:45:20.760 UTC client backend[46440] isolation/fk-snapshot-3/s1 DETAIL: Key (id, valid_at)=([1,2), [01-01-2020,01-01-2030)) is still referenced from table "child". 2025-11-30 18:45:20.760 UTC client backend[46440] isolation/fk-snapshot-3/s1 STATEMENT: DELETE FROM parent WHERE id = '[1,2)'; 2025-11-30 18:45:20.766 UTC client backend[46434] pg_regress/publication ERROR: cannot use a WHERE clause when removing a table from a publication 2025-11-30 18:45:20.766 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 DROP TABLE testpub_rf_tbl1 WHERE (e < 27); 2025-11-30 18:45:20.767 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.767 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.771 UTC client backend[46434] pg_regress/publication ERROR: generation expression uses user-defined function at character 89 2025-11-30 18:45:20.771 UTC client backend[46434] pg_regress/publication DETAIL: Virtual generated columns that make use of user-defined functions are not yet supported. 2025-11-30 18:45:20.771 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE TABLE testpub_rf_tbl6 (id int PRIMARY KEY, x int, y int GENERATED ALWAYS AS (x * testpub_rf_func2()) VIRTUAL); 2025-11-30 18:45:20.771 UTC client backend[46434] pg_regress/publication ERROR: relation "testpub_rf_tbl6" does not exist 2025-11-30 18:45:20.771 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub7 FOR TABLE testpub_rf_tbl6 WHERE (y > 100); 2025-11-30 18:45:20.774 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.774 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.774 UTC client backend[46434] pg_regress/publication ERROR: ALTER TABLE / SET EXPRESSION is not supported for virtual generated columns in tables that are part of a publication 2025-11-30 18:45:20.774 UTC client backend[46434] pg_regress/publication DETAIL: Column "y" of relation "testpub_rf_tbl7" is a virtual generated column. 2025-11-30 18:45:20.774 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER TABLE testpub_rf_tbl7 ALTER COLUMN y SET EXPRESSION AS (x * testpub_rf_func2()); 2025-11-30 18:45:20.783 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.783 UTC client backend[46441] isolation/fk-snapshot-3/s2 CONTEXT: SQL statement "SELECT 1 FROM (SELECT "valid_at" AS r FROM ONLY "public"."parent" x WHERE "id"::pg_catalog.anyrange OPERATOR(pg_catalog.=) $1::pg_catalog.anyrange AND "valid_at"::pg_catalog.anyrange OPERATOR(pg_catalog.&&) $2::pg_catalog.anyrange FOR KEY SHARE OF x) x1 HAVING $2::pg_catalog.anyrange OPERATOR(pg_catalog.<@) pg_catalog.range_agg(x1.r)" 2025-11-30 18:45:20.783 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:20.796 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.796 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.799 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.799 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.799 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.800 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.800 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.800 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.801 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-11-30 18:45:20.801 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.801 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-11-30 18:45:20.805 UTC client backend[46440] isolation/fk-snapshot-3/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_valid_at_fkey" on table "child" 2025-11-30 18:45:20.805 UTC client backend[46440] isolation/fk-snapshot-3/s1 DETAIL: Key (id, valid_at)=([1,2), [01-01-2020,01-01-2030)) is still referenced from table "child". 2025-11-30 18:45:20.805 UTC client backend[46440] isolation/fk-snapshot-3/s1 STATEMENT: DELETE FROM parent WHERE id = '[1,2)'; 2025-11-30 18:45:20.806 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.806 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.806 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.807 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.807 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.807 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.808 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-11-30 18:45:20.808 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.808 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-11-30 18:45:20.813 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.813 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.813 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.815 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-11-30 18:45:20.815 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.815 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-11-30 18:45:20.817 UTC client backend[46434] pg_regress/publication ERROR: cannot use publication WHERE clause for relation "rf_tbl_abcd_part_pk" 2025-11-30 18:45:20.817 UTC client backend[46434] pg_regress/publication DETAIL: WHERE clause cannot be used for a partitioned table when publish_via_partition_root is false. 2025-11-30 18:45:20.817 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET TABLE rf_tbl_abcd_part_pk WHERE (a > 99); 2025-11-30 18:45:20.820 UTC client backend[46434] pg_regress/publication ERROR: cannot set parameter "publish_via_partition_root" to false for publication "testpub6" 2025-11-30 18:45:20.820 UTC client backend[46434] pg_regress/publication DETAIL: The publication contains a WHERE clause for partitioned table "rf_tbl_abcd_part_pk", which is not allowed when "publish_via_partition_root" is false. 2025-11-30 18:45:20.820 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET (PUBLISH_VIA_PARTITION_ROOT=0); 2025-11-30 18:45:20.823 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-11-30 18:45:20.823 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.823 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-11-30 18:45:20.824 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-11-30 18:45:20.824 UTC client backend[46434] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-11-30 18:45:20.824 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-11-30 18:45:20.828 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: insert or update on table "child" violates foreign key constraint "child_parent_id_valid_at_fkey" 2025-11-30 18:45:20.828 UTC client backend[46441] isolation/fk-snapshot-3/s2 DETAIL: Key (parent_id, valid_at)=([1,2), [01-01-2020,01-01-2025)) is not present in table "parent". 2025-11-30 18:45:20.828 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:20.834 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.834 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.835 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-11-30 18:45:20.835 UTC client backend[46434] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-11-30 18:45:20.835 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-11-30 18:45:20.836 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-11-30 18:45:20.836 UTC client backend[46434] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-11-30 18:45:20.836 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-11-30 18:45:20.837 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.837 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.841 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.841 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.842 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-11-30 18:45:20.842 UTC client backend[46434] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-11-30 18:45:20.842 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-11-30 18:45:20.843 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.843 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.843 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-11-30 18:45:20.843 UTC client backend[46434] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-11-30 18:45:20.843 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-11-30 18:45:20.845 UTC client backend[46434] pg_regress/publication ERROR: conflicting or redundant column lists for table "testpub_tbl1" 2025-11-30 18:45:20.845 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_tbl1 (a), testpub_tbl1 WITH (publish = 'insert'); 2025-11-30 18:45:20.845 UTC client backend[46434] pg_regress/publication ERROR: conflicting or redundant column lists for table "testpub_tbl1" 2025-11-30 18:45:20.845 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_tbl1, testpub_tbl1 (a) WITH (publish = 'insert'); 2025-11-30 18:45:20.846 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.846 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.846 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.846 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.850 UTC client backend[46434] pg_regress/publication ERROR: column "x" of relation "testpub_tbl5" does not exist 2025-11-30 18:45:20.850 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, x); 2025-11-30 18:45:20.851 UTC client backend[46440] isolation/fk-snapshot-3/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_valid_at_fkey" on table "child" 2025-11-30 18:45:20.851 UTC client backend[46440] isolation/fk-snapshot-3/s1 DETAIL: Key (id, valid_at)=([1,2), [01-01-2020,01-01-2030)) is still referenced from table "child". 2025-11-30 18:45:20.851 UTC client backend[46440] isolation/fk-snapshot-3/s1 STATEMENT: DELETE FROM parent WHERE id = '[1,2)'; 2025-11-30 18:45:20.851 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl5" 2025-11-30 18:45:20.851 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.851 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl5 SET a = 1; 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication ERROR: cannot use system column "ctid" in publication column list 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, ctid); 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication ERROR: cannot use system column "ctid" in publication column list 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable SET TABLE testpub_tbl1 (id, ctid); 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication ERROR: duplicate column "a" in publication column list 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, a); 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication ERROR: duplicate column "a" in publication column list 2025-11-30 18:45:20.852 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable SET TABLE testpub_tbl5 (a, a); 2025-11-30 18:45:20.853 UTC client backend[46434] pg_regress/publication ERROR: cannot drop column c of table testpub_tbl5 because other objects depend on it 2025-11-30 18:45:20.853 UTC client backend[46434] pg_regress/publication DETAIL: publication of table testpub_tbl5 in publication testpub_fortable depends on column c of table testpub_tbl5 2025-11-30 18:45:20.853 UTC client backend[46434] pg_regress/publication HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:20.853 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER TABLE testpub_tbl5 DROP COLUMN c; 2025-11-30 18:45:20.857 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl5" 2025-11-30 18:45:20.857 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.857 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl5 SET a = 1; 2025-11-30 18:45:20.858 UTC client backend[46434] pg_regress/publication ERROR: cannot use virtual generated column "e" in publication column list 2025-11-30 18:45:20.858 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, e); 2025-11-30 18:45:20.860 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl5" 2025-11-30 18:45:20.860 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.860 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl5 SET a = 1; 2025-11-30 18:45:20.860 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.860 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.867 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl5d" because it does not have a replica identity and publishes updates 2025-11-30 18:45:20.867 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:20.867 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl5d SET a = 1; 2025-11-30 18:45:20.872 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl6" 2025-11-30 18:45:20.872 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.872 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl6 SET a = 1; 2025-11-30 18:45:20.875 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.875 UTC client backend[46441] isolation/fk-snapshot-3/s2 CONTEXT: SQL statement "SELECT 1 FROM (SELECT "valid_at" AS r FROM ONLY "public"."parent" x WHERE "id"::pg_catalog.anyrange OPERATOR(pg_catalog.=) $1::pg_catalog.anyrange AND "valid_at"::pg_catalog.anyrange OPERATOR(pg_catalog.&&) $2::pg_catalog.anyrange FOR KEY SHARE OF x) x1 HAVING $2::pg_catalog.anyrange OPERATOR(pg_catalog.<@) pg_catalog.range_agg(x1.r)" 2025-11-30 18:45:20.875 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:20.919 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.919 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.923 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-11-30 18:45:20.923 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.923 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-11-30 18:45:20.925 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-11-30 18:45:20.925 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.925 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-11-30 18:45:20.927 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-11-30 18:45:20.927 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.927 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-11-30 18:45:20.930 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-11-30 18:45:20.930 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.930 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-11-30 18:45:20.945 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-11-30 18:45:20.945 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.945 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-11-30 18:45:20.946 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl8_0" 2025-11-30 18:45:20.946 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.946 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-11-30 18:45:20.946 UTC client backend[46434] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-11-30 18:45:20.946 UTC client backend[46434] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-11-30 18:45:20.946 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_tbl9 FOR TABLES IN SCHEMA public, TABLE public.testpub_tbl7(a); 2025-11-30 18:45:20.948 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.948 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.949 UTC client backend[46434] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-11-30 18:45:20.949 UTC client backend[46434] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-11-30 18:45:20.949 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 ADD TABLE public.testpub_tbl7(a); 2025-11-30 18:45:20.950 UTC client backend[46434] pg_regress/publication ERROR: cannot add schema to publication "testpub_tbl9" 2025-11-30 18:45:20.950 UTC client backend[46434] pg_regress/publication DETAIL: Schemas cannot be added if any tables that specify a column list are already part of the publication. 2025-11-30 18:45:20.950 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 ADD TABLES IN SCHEMA public; 2025-11-30 18:45:20.950 UTC client backend[46434] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-11-30 18:45:20.950 UTC client backend[46434] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-11-30 18:45:20.950 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 SET TABLES IN SCHEMA public, TABLE public.testpub_tbl7(a); 2025-11-30 18:45:20.951 UTC client backend[46434] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-11-30 18:45:20.951 UTC client backend[46434] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-11-30 18:45:20.951 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 ADD TABLES IN SCHEMA public, TABLE public.testpub_tbl7(a); 2025-11-30 18:45:20.962 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.962 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.966 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:20.966 UTC client backend[46441] isolation/fk-snapshot-3/s2 CONTEXT: SQL statement "SELECT 1 FROM (SELECT "valid_at" AS r FROM ONLY "public"."parent" x WHERE "id"::pg_catalog.anyrange OPERATOR(pg_catalog.=) $1::pg_catalog.anyrange AND "valid_at"::pg_catalog.anyrange OPERATOR(pg_catalog.&&) $2::pg_catalog.anyrange FOR KEY SHARE OF x) x1 HAVING $2::pg_catalog.anyrange OPERATOR(pg_catalog.<@) pg_catalog.range_agg(x1.r)" 2025-11-30 18:45:20.966 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:20.988 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:20.988 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:20.992 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.992 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.992 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.993 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.993 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.993 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.994 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" because it does not have a replica identity and publishes updates 2025-11-30 18:45:20.994 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:20.994 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-11-30 18:45:20.996 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:20.996 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.996 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:20.997 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-11-30 18:45:20.997 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:20.997 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-11-30 18:45:20.999 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" because it does not have a replica identity and publishes updates 2025-11-30 18:45:20.999 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:20.999 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:21.000 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.000 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.000 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:21.001 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.001 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.001 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-11-30 18:45:21.005 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-11-30 18:45:21.005 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:21.005 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-11-30 18:45:21.008 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-11-30 18:45:21.008 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:21.008 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-11-30 18:45:21.009 UTC client backend[46434] pg_regress/publication ERROR: cannot use column list for relation "public.rf_tbl_abcd_part_pk" in publication "testpub6" 2025-11-30 18:45:21.009 UTC client backend[46434] pg_regress/publication DETAIL: Column lists cannot be specified for partitioned tables when publish_via_partition_root is false. 2025-11-30 18:45:21.009 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET TABLE rf_tbl_abcd_part_pk (a); 2025-11-30 18:45:21.012 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:21.012 UTC client backend[46441] isolation/fk-snapshot-3/s2 CONTEXT: SQL statement "SELECT 1 FROM (SELECT "valid_at" AS r FROM ONLY "public"."parent" x WHERE "id"::pg_catalog.anyrange OPERATOR(pg_catalog.=) $1::pg_catalog.anyrange AND "valid_at"::pg_catalog.anyrange OPERATOR(pg_catalog.&&) $2::pg_catalog.anyrange FOR KEY SHARE OF x) x1 HAVING $2::pg_catalog.anyrange OPERATOR(pg_catalog.<@) pg_catalog.range_agg(x1.r)" 2025-11-30 18:45:21.012 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:21.013 UTC client backend[46434] pg_regress/publication ERROR: cannot set parameter "publish_via_partition_root" to false for publication "testpub6" 2025-11-30 18:45:21.013 UTC client backend[46434] pg_regress/publication DETAIL: The publication contains a column list for partitioned table "rf_tbl_abcd_part_pk", which is not allowed when "publish_via_partition_root" is false. 2025-11-30 18:45:21.013 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET (PUBLISH_VIA_PARTITION_ROOT=0); 2025-11-30 18:45:21.015 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-11-30 18:45:21.015 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:21.015 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-11-30 18:45:21.017 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-11-30 18:45:21.017 UTC client backend[46434] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-11-30 18:45:21.017 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-11-30 18:45:21.024 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.024 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.025 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_tbl4" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.025 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.025 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE testpub_tbl4 set a = 3; 2025-11-30 18:45:21.026 UTC client backend[46434] pg_regress/publication ERROR: cannot add relation "testpub_view" to publication 2025-11-30 18:45:21.026 UTC client backend[46434] pg_regress/publication DETAIL: This operation is not supported for views. 2025-11-30 18:45:21.026 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_fortbl FOR TABLE testpub_view; 2025-11-30 18:45:21.027 UTC client backend[46434] pg_regress/publication ERROR: cannot add relation "testpub_temptbl" to publication 2025-11-30 18:45:21.027 UTC client backend[46434] pg_regress/publication DETAIL: This operation is not supported for temporary tables. 2025-11-30 18:45:21.027 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_fortemptbl FOR TABLE testpub_temptbl; 2025-11-30 18:45:21.029 UTC client backend[46434] pg_regress/publication ERROR: cannot add relation "testpub_unloggedtbl" to publication 2025-11-30 18:45:21.029 UTC client backend[46434] pg_regress/publication DETAIL: This operation is not supported for unlogged tables. 2025-11-30 18:45:21.029 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forunloggedtbl FOR TABLE testpub_unloggedtbl; 2025-11-30 18:45:21.030 UTC client backend[46434] pg_regress/publication ERROR: cannot add relation "pg_publication" to publication 2025-11-30 18:45:21.030 UTC client backend[46434] pg_regress/publication DETAIL: This operation is not supported for system tables. 2025-11-30 18:45:21.030 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forsystemtbl FOR TABLE pg_publication; 2025-11-30 18:45:21.031 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.031 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.031 UTC client backend[46434] pg_regress/publication ERROR: relation "testpub_tbl1" is already member of publication "testpub_fortbl" 2025-11-30 18:45:21.031 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortbl ADD TABLE testpub_tbl1; 2025-11-30 18:45:21.031 UTC client backend[46434] pg_regress/publication ERROR: publication "testpub_fortbl" already exists 2025-11-30 18:45:21.031 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_fortbl FOR TABLE testpub_tbl1; 2025-11-30 18:45:21.033 UTC client backend[46434] pg_regress/publication ERROR: cannot add relation "testpub_view" to publication 2025-11-30 18:45:21.033 UTC client backend[46434] pg_regress/publication DETAIL: This operation is not supported for views. 2025-11-30 18:45:21.033 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_default ADD TABLE testpub_view; 2025-11-30 18:45:21.035 UTC client backend[46440] isolation/fk-snapshot-3/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_valid_at_fkey" on table "child" 2025-11-30 18:45:21.035 UTC client backend[46440] isolation/fk-snapshot-3/s1 DETAIL: Key (id, valid_at)=([1,2), [01-01-2020,01-01-2030)) is still referenced from table "child". 2025-11-30 18:45:21.035 UTC client backend[46440] isolation/fk-snapshot-3/s1 STATEMENT: UPDATE parent SET valid_at = '[2020-01-01,2024-01-01)' WHERE id = '[1,2)'; 2025-11-30 18:45:21.057 UTC client backend[46434] pg_regress/publication ERROR: relation "testpub_nopk" is not part of the publication 2025-11-30 18:45:21.057 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_default DROP TABLE pub_test.testpub_nopk; 2025-11-30 18:45:21.058 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: insert or update on table "child" violates foreign key constraint "child_parent_id_valid_at_fkey" 2025-11-30 18:45:21.058 UTC client backend[46441] isolation/fk-snapshot-3/s2 DETAIL: Key (parent_id, valid_at)=([1,2), [01-01-2020,01-01-2025)) is not present in table "parent". 2025-11-30 18:45:21.058 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:21.070 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_addpk" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.070 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.070 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_test.testpub_addpk SET id = 2; 2025-11-30 18:45:21.073 UTC client backend[46434] pg_regress/publication ERROR: permission denied for database regression 2025-11-30 18:45:21.073 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub2; 2025-11-30 18:45:21.073 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.073 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication ERROR: must be superuser to create FOR TABLES IN SCHEMA publication 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub3 FOR TABLES IN SCHEMA pub_test; 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication ERROR: must be owner of table testpub_tbl1 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub2 ADD TABLE testpub_tbl1; 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication ERROR: must be superuser to add or set schemas 2025-11-30 18:45:21.074 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub3 ADD TABLES IN SCHEMA pub_test; 2025-11-30 18:45:21.077 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.077 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.078 UTC client backend[46434] pg_regress/publication ERROR: permission denied to change owner of publication "testpub4" 2025-11-30 18:45:21.078 UTC client backend[46434] pg_regress/publication HINT: The owner of a FOR ALL TABLES or ALL SEQUENCES or TABLES IN SCHEMA publication must be a superuser. 2025-11-30 18:45:21.078 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub4 owner to regress_publication_user2; 2025-11-30 18:45:21.081 UTC client backend[46440] isolation/fk-snapshot-3/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_valid_at_fkey" on table "child" 2025-11-30 18:45:21.081 UTC client backend[46440] isolation/fk-snapshot-3/s1 DETAIL: Key (id, valid_at)=([1,2), [01-01-2020,01-01-2030)) is still referenced from table "child". 2025-11-30 18:45:21.081 UTC client backend[46440] isolation/fk-snapshot-3/s1 STATEMENT: UPDATE parent SET valid_at = '[2020-01-01,2024-01-01)' WHERE id = '[1,2)'; 2025-11-30 18:45:21.084 UTC client backend[46434] pg_regress/publication ERROR: must be owner of publication testpub_default 2025-11-30 18:45:21.084 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_default RENAME TO testpub_dummy; 2025-11-30 18:45:21.097 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.097 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.100 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.100 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.103 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.103 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.104 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.104 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.104 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:21.104 UTC client backend[46441] isolation/fk-snapshot-3/s2 CONTEXT: SQL statement "SELECT 1 FROM (SELECT "valid_at" AS r FROM ONLY "public"."parent" x WHERE "id"::pg_catalog.anyrange OPERATOR(pg_catalog.=) $1::pg_catalog.anyrange AND "valid_at"::pg_catalog.anyrange OPERATOR(pg_catalog.&&) $2::pg_catalog.anyrange FOR KEY SHARE OF x) x1 HAVING $2::pg_catalog.anyrange OPERATOR(pg_catalog.<@) pg_catalog.range_agg(x1.r)" 2025-11-30 18:45:21.104 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:21.106 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.106 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.107 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.107 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.108 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.108 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication ERROR: no schema has been selected for CURRENT_SCHEMA 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema FOR TABLES IN SCHEMA CURRENT_SCHEMA; 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication ERROR: invalid publication object list at character 43 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication DETAIL: One of TABLE or TABLES IN SCHEMA must be specified before a standalone table or schema name. 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema1 FOR CURRENT_SCHEMA; 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication ERROR: syntax error at or near "CURRENT_SCHEMA" at character 49 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema1 FOR TABLE CURRENT_SCHEMA; 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema FOR TABLES IN SCHEMA non_existent_schema; 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication ERROR: cannot add schema "pg_catalog" to publication 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication DETAIL: This operation is not supported for system schemas. 2025-11-30 18:45:21.118 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema FOR TABLES IN SCHEMA pg_catalog; 2025-11-30 18:45:21.119 UTC client backend[46434] pg_regress/publication ERROR: schema "testpub_view" does not exist 2025-11-30 18:45:21.119 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub1_forschema1 FOR TABLES IN SCHEMA testpub_view; 2025-11-30 18:45:21.127 UTC client backend[46434] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-11-30 18:45:21.127 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA non_existent_schema; 2025-11-30 18:45:21.128 UTC client backend[46440] isolation/fk-snapshot-3/s1 ERROR: update or delete on table "parent" violates foreign key constraint "child_parent_id_valid_at_fkey" on table "child" 2025-11-30 18:45:21.128 UTC client backend[46440] isolation/fk-snapshot-3/s1 DETAIL: Key (id, valid_at)=([1,2), [01-01-2020,01-01-2030)) is still referenced from table "child". 2025-11-30 18:45:21.128 UTC client backend[46440] isolation/fk-snapshot-3/s1 STATEMENT: UPDATE parent SET valid_at = '[2020-01-01,2024-01-01)' WHERE id = '[1,2)'; 2025-11-30 18:45:21.129 UTC client backend[46434] pg_regress/publication ERROR: schema "pub_test1" is already member of publication "testpub1_forschema" 2025-11-30 18:45:21.129 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA pub_test1; 2025-11-30 18:45:21.134 UTC client backend[46434] pg_regress/publication ERROR: tables from schema "pub_test2" are not part of the publication 2025-11-30 18:45:21.134 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema DROP TABLES IN SCHEMA pub_test2; 2025-11-30 18:45:21.136 UTC client backend[46434] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-11-30 18:45:21.136 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema DROP TABLES IN SCHEMA non_existent_schema; 2025-11-30 18:45:21.142 UTC client backend[46434] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-11-30 18:45:21.142 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema SET TABLES IN SCHEMA non_existent_schema; 2025-11-30 18:45:21.146 UTC client backend[46434] pg_regress/publication ERROR: syntax error at or near "(" at character 63 2025-11-30 18:45:21.146 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA foo (a, b); 2025-11-30 18:45:21.147 UTC client backend[46434] pg_regress/publication ERROR: column specification not allowed for schema at character 64 2025-11-30 18:45:21.147 UTC client backend[46434] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA foo, bar (a, b); 2025-11-30 18:45:21.151 UTC client backend[46441] isolation/fk-snapshot-3/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:21.151 UTC client backend[46441] isolation/fk-snapshot-3/s2 CONTEXT: SQL statement "SELECT 1 FROM (SELECT "valid_at" AS r FROM ONLY "public"."parent" x WHERE "id"::pg_catalog.anyrange OPERATOR(pg_catalog.=) $1::pg_catalog.anyrange AND "valid_at"::pg_catalog.anyrange OPERATOR(pg_catalog.&&) $2::pg_catalog.anyrange FOR KEY SHARE OF x) x1 HAVING $2::pg_catalog.anyrange OPERATOR(pg_catalog.<@) pg_catalog.range_agg(x1.r)" 2025-11-30 18:45:21.151 UTC client backend[46441] isolation/fk-snapshot-3/s2 STATEMENT: INSERT INTO child VALUES ('[1,2)', '[2020-01-01,2025-01-01)', '[1,2)'); 2025-11-30 18:45:21.152 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "tbl" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.152 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.152 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_test1.tbl SET id = 2; 2025-11-30 18:45:21.154 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "tbl" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.154 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.154 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_test1.tbl SET id = 2; 2025-11-30 18:45:21.156 UTC client backend[46439] isolation/fk-snapshot-3/control connection LOG: disconnection: session time: 0:00:00.431 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:21.156 UTC client backend[46441] isolation/fk-snapshot-3/s2 LOG: disconnection: session time: 0:00:00.422 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:21.156 UTC client backend[46440] isolation/fk-snapshot-3/s1 LOG: disconnection: session time: 0:00:00.425 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:21.158 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.158 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.159 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "child_parent1" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.159 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.159 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_testpart1.parent1 set a = 1; 2025-11-30 18:45:21.159 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "child_parent1" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.159 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.159 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_testpart2.child_parent1 set a = 1; 2025-11-30 18:45:21.161 UTC unrecognized[46444] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.162 UTC client backend[46444] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.162 UTC client backend[46444] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/subxid-overflow 2025-11-30 18:45:21.163 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.163 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.163 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "child_parent1" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.163 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.163 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_testpart2.child_parent1 set a = 1; 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "child_parent2" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_testpart2.parent2 set a = 1; 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "child_parent2" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication STATEMENT: UPDATE pub_testpart1.child_parent2 set a = 1; 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.164 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.166 UTC client backend[46444] isolation/subxid-overflow LOG: connection ready: setup total=5.175 ms, fork=0.540 ms, authentication=0.120 ms 2025-11-30 18:45:21.167 UTC unrecognized[46445] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.168 UTC client backend[46445] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.168 UTC client backend[46445] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/subxid-overflow 2025-11-30 18:45:21.169 UTC client backend[46445] isolation/subxid-overflow LOG: connection ready: setup total=2.200 ms, fork=0.501 ms, authentication=0.138 ms 2025-11-30 18:45:21.169 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.169 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.170 UTC unrecognized[46446] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.170 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.170 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.171 UTC client backend[46446] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.171 UTC client backend[46446] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/subxid-overflow 2025-11-30 18:45:21.171 UTC client backend[46446] isolation/subxid-overflow LOG: connection ready: setup total=1.797 ms, fork=0.390 ms, authentication=0.110 ms 2025-11-30 18:45:21.173 UTC unrecognized[46447] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.173 UTC client backend[46447] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.173 UTC client backend[46447] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/subxid-overflow 2025-11-30 18:45:21.174 UTC client backend[46447] isolation/subxid-overflow LOG: connection ready: setup total=1.764 ms, fork=0.327 ms, authentication=0.123 ms 2025-11-30 18:45:21.174 UTC client backend[46434] pg_regress/publication ERROR: invalid publication object list at character 38 2025-11-30 18:45:21.174 UTC client backend[46434] pg_regress/publication DETAIL: One of TABLE or TABLES IN SCHEMA must be specified before a standalone table or schema name. 2025-11-30 18:45:21.174 UTC client backend[46434] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_error FOR pub_test2.tbl1; 2025-11-30 18:45:21.194 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.194 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.197 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.197 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.203 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.203 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.206 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.206 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.209 UTC client backend[46444] isolation/subxid-overflow/control connection LOG: disconnection: session time: 0:00:00.048 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:21.209 UTC client backend[46445] isolation/subxid-overflow/s1 LOG: disconnection: session time: 0:00:00.042 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:21.209 UTC client backend[46446] isolation/subxid-overflow/s2 LOG: disconnection: session time: 0:00:00.039 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:21.209 UTC client backend[46447] isolation/subxid-overflow/s3 LOG: disconnection: session time: 0:00:00.036 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:21.216 UTC unrecognized[46450] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.216 UTC client backend[46450] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.216 UTC client backend[46450] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual 2025-11-30 18:45:21.217 UTC client backend[46450] isolation/eval-plan-qual LOG: connection ready: setup total=1.962 ms, fork=0.379 ms, authentication=0.129 ms 2025-11-30 18:45:21.218 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.218 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.219 UTC unrecognized[46451] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.219 UTC client backend[46451] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.219 UTC client backend[46451] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual 2025-11-30 18:45:21.220 UTC client backend[46451] isolation/eval-plan-qual LOG: connection ready: setup total=1.916 ms, fork=0.351 ms, authentication=0.125 ms 2025-11-30 18:45:21.222 UTC unrecognized[46452] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.222 UTC client backend[46452] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.222 UTC client backend[46452] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual 2025-11-30 18:45:21.223 UTC client backend[46452] isolation/eval-plan-qual LOG: connection ready: setup total=1.999 ms, fork=0.510 ms, authentication=0.117 ms 2025-11-30 18:45:21.224 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.224 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.224 UTC unrecognized[46453] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.225 UTC client backend[46453] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.225 UTC client backend[46453] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual 2025-11-30 18:45:21.225 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.225 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.228 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.228 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.229 UTC client backend[46453] isolation/eval-plan-qual LOG: connection ready: setup total=5.064 ms, fork=0.474 ms, authentication=0.094 ms 2025-11-30 18:45:21.231 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.231 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.247 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.247 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.248 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_insert_onconfl_no_ri" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.248 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.248 UTC client backend[46434] pg_regress/publication STATEMENT: INSERT INTO testpub_insert_onconfl_no_ri VALUES (1, 1) ON CONFLICT (a) DO UPDATE SET b = 2; 2025-11-30 18:45:21.249 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_insert_onconfl_part_no_ri" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.249 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.249 UTC client backend[46434] pg_regress/publication STATEMENT: INSERT INTO testpub_insert_onconfl_parted VALUES (1, 1) ON CONFLICT (a) DO UPDATE SET b = 2; 2025-11-30 18:45:21.256 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.256 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.257 UTC client backend[46434] pg_regress/publication ERROR: cannot update table "testpub_merge_no_ri" because it does not have a replica identity and publishes updates 2025-11-30 18:45:21.257 UTC client backend[46434] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.257 UTC client backend[46434] pg_regress/publication STATEMENT: MERGE INTO testpub_merge_no_ri USING testpub_merge_pk s ON s.a >= 1 WHEN MATCHED THEN UPDATE SET b = s.b; 2025-11-30 18:45:21.257 UTC client backend[46434] pg_regress/publication ERROR: cannot delete from table "testpub_merge_no_ri" because it does not have a replica identity and publishes deletes 2025-11-30 18:45:21.257 UTC client backend[46434] pg_regress/publication HINT: To enable deleting from the table, set REPLICA IDENTITY using ALTER TABLE. 2025-11-30 18:45:21.257 UTC client backend[46434] pg_regress/publication STATEMENT: MERGE INTO testpub_merge_no_ri USING testpub_merge_pk s ON s.a >= 1 WHEN MATCHED THEN DELETE; 2025-11-30 18:45:21.265 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.265 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.266 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.266 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.266 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.266 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.267 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.267 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.269 UTC client backend[46434] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:21.269 UTC client backend[46434] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:21.269 UTC client backend[46434] pg_regress/publication LOG: disconnection: session time: 0:00:00.698 user=postgres database=regression host=[local] 2025-11-30 18:45:21.286 UTC unrecognized[46475] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.286 UTC client backend[46475] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.286 UTC client backend[46475] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/dependency 2025-11-30 18:45:21.287 UTC unrecognized[46474] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.287 UTC client backend[46474] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.287 UTC client backend[46474] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/portals_p2 2025-11-30 18:45:21.290 UTC unrecognized[46480] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.290 UTC client backend[46480] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.290 UTC client backend[46480] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/functional_deps 2025-11-30 18:45:21.291 UTC client backend[46475] pg_regress/dependency LOG: connection ready: setup total=14.118 ms, fork=5.700 ms, authentication=0.116 ms 2025-11-30 18:45:21.291 UTC unrecognized[46476] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.292 UTC client backend[46476] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.292 UTC client backend[46476] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_views 2025-11-30 18:45:21.292 UTC client backend[46474] pg_regress/portals_p2 LOG: connection ready: setup total=17.245 ms, fork=10.694 ms, authentication=0.099 ms 2025-11-30 18:45:21.293 UTC client backend[46476] pg_regress/select_views LOG: connection ready: setup total=15.210 ms, fork=5.509 ms, authentication=0.107 ms 2025-11-30 18:45:21.293 UTC unrecognized[46478] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.294 UTC client backend[46478] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.294 UTC client backend[46478] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/combocid 2025-11-30 18:45:21.295 UTC client backend[46478] pg_regress/combocid LOG: connection ready: setup total=14.194 ms, fork=5.278 ms, authentication=0.110 ms 2025-11-30 18:45:21.295 UTC unrecognized[46479] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.295 UTC client backend[46480] pg_regress/functional_deps LOG: connection ready: setup total=12.570 ms, fork=5.970 ms, authentication=0.094 ms 2025-11-30 18:45:21.295 UTC client backend[46479] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.295 UTC client backend[46479] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/bitmapops 2025-11-30 18:45:21.296 UTC client backend[46479] pg_regress/bitmapops LOG: connection ready: setup total=15.345 ms, fork=5.079 ms, authentication=0.121 ms 2025-11-30 18:45:21.296 UTC unrecognized[46483] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.297 UTC unrecognized[46481] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.297 UTC client backend[46481] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.297 UTC client backend[46481] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/foreign_data 2025-11-30 18:45:21.297 UTC unrecognized[46477] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.298 UTC client backend[46477] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.298 UTC client backend[46477] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/foreign_key 2025-11-30 18:45:21.298 UTC client backend[46481] pg_regress/foreign_data LOG: connection ready: setup total=14.680 ms, fork=9.617 ms, authentication=0.111 ms 2025-11-30 18:45:21.298 UTC unrecognized[46484] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.299 UTC client backend[46477] pg_regress/foreign_key LOG: connection ready: setup total=20.971 ms, fork=18.582 ms, authentication=0.105 ms 2025-11-30 18:45:21.299 UTC client backend[46484] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.299 UTC client backend[46484] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/indirect_toast 2025-11-30 18:45:21.299 UTC unrecognized[46482] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.299 UTC client backend[46482] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.299 UTC client backend[46482] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/xmlmap 2025-11-30 18:45:21.299 UTC client backend[46484] pg_regress/indirect_toast LOG: connection ready: setup total=12.862 ms, fork=7.210 ms, authentication=0.104 ms 2025-11-30 18:45:21.300 UTC unrecognized[46487] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.300 UTC client backend[46482] pg_regress/xmlmap LOG: connection ready: setup total=16.336 ms, fork=12.621 ms, authentication=0.102 ms 2025-11-30 18:45:21.300 UTC client backend[46487] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.300 UTC client backend[46487] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/advisory_lock 2025-11-30 18:45:21.301 UTC client backend[46487] pg_regress/advisory_lock LOG: connection ready: setup total=8.129 ms, fork=5.175 ms, authentication=0.100 ms 2025-11-30 18:45:21.301 UTC unrecognized[46488] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.297 UTC client backend[46483] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.301 UTC client backend[46483] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/guc 2025-11-30 18:45:21.302 UTC client backend[46488] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.302 UTC client backend[46488] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tsearch 2025-11-30 18:45:21.302 UTC client backend[46483] pg_regress/guc LOG: connection ready: setup total=17.285 ms, fork=0.787 ms, authentication=4.895 ms 2025-11-30 18:45:21.303 UTC unrecognized[46485] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.303 UTC client backend[46485] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.303 UTC client backend[46485] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/cluster 2025-11-30 18:45:21.304 UTC client backend[46488] pg_regress/tsearch LOG: connection ready: setup total=10.561 ms, fork=5.027 ms, authentication=0.104 ms 2025-11-30 18:45:21.304 UTC client backend[46485] pg_regress/cluster LOG: connection ready: setup total=11.652 ms, fork=4.610 ms, authentication=0.104 ms 2025-11-30 18:45:21.304 UTC unrecognized[46489] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.304 UTC client backend[46489] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.304 UTC client backend[46489] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tsdicts 2025-11-30 18:45:21.305 UTC client backend[46489] pg_regress/tsdicts LOG: connection ready: setup total=11.922 ms, fork=3.444 ms, authentication=0.110 ms 2025-11-30 18:45:21.306 UTC unrecognized[46490] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.307 UTC client backend[46490] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.307 UTC client backend[46490] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats_rewrite 2025-11-30 18:45:21.308 UTC client backend[46490] pg_regress/stats_rewrite LOG: connection ready: setup total=10.627 ms, fork=6.120 ms, authentication=0.105 ms 2025-11-30 18:45:21.311 UTC unrecognized[46486] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.311 UTC client backend[46486] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.311 UTC client backend[46486] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/equivclass 2025-11-30 18:45:21.312 UTC client backend[46486] pg_regress/equivclass LOG: connection ready: setup total=19.690 ms, fork=4.356 ms, authentication=0.109 ms 2025-11-30 18:45:21.316 UTC client backend[46480] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-11-30 18:45:21.316 UTC client backend[46480] pg_regress/functional_deps STATEMENT: SELECT id, keywords, title, body, created FROM articles GROUP BY title; 2025-11-30 18:45:21.316 UTC client backend[46480] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-11-30 18:45:21.316 UTC client backend[46480] pg_regress/functional_deps STATEMENT: SELECT id, keywords, title, body, created FROM articles GROUP BY body; 2025-11-30 18:45:21.316 UTC unrecognized[46491] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:21.317 UTC client backend[46491] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:21.317 UTC client backend[46491] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/window 2025-11-30 18:45:21.318 UTC client backend[46483] pg_regress/guc ERROR: invalid value for parameter "IntervalStyle": "asd" 2025-11-30 18:45:21.318 UTC client backend[46483] pg_regress/guc HINT: Available values: postgres, postgres_verbose, sql_standard, iso_8601. 2025-11-30 18:45:21.318 UTC client backend[46483] pg_regress/guc STATEMENT: SET intervalstyle to 'asd'; 2025-11-30 18:45:21.322 UTC client backend[46480] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-11-30 18:45:21.322 UTC client backend[46480] pg_regress/functional_deps STATEMENT: SELECT id, keywords, title, body, created FROM articles GROUP BY keywords; 2025-11-30 18:45:21.325 UTC client backend[46483] pg_regress/guc ERROR: syntax error at or near "," at character 23 2025-11-30 18:45:21.325 UTC client backend[46483] pg_regress/guc STATEMENT: SET search_path = null, null; 2025-11-30 18:45:21.326 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-11-30 18:45:21.326 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-11-30 18:45:21.326 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-11-30 18:45:21.326 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-11-30 18:45:21.327 UTC client backend[46483] pg_regress/guc ERROR: NULL is an invalid value for enable_seqscan 2025-11-30 18:45:21.327 UTC client backend[46483] pg_regress/guc STATEMENT: SET enable_seqscan = null; 2025-11-30 18:45:21.328 UTC client backend[46483] pg_regress/guc WARNING: SET LOCAL can only be used in transaction blocks 2025-11-30 18:45:21.330 UTC client backend[46491] pg_regress/window LOG: connection ready: setup total=32.523 ms, fork=15.166 ms, authentication=0.106 ms 2025-11-30 18:45:21.331 UTC client backend[46480] pg_regress/functional_deps ERROR: column "a.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-11-30 18:45:21.331 UTC client backend[46480] pg_regress/functional_deps STATEMENT: SELECT a.id, a.keywords, a.title, a.body, a.created FROM articles AS a, articles_in_category AS aic WHERE a.id = aic.article_id AND aic.category_id in (14,62,70,53,138) GROUP BY aic.article_id, aic.category_id; 2025-11-30 18:45:21.331 UTC client backend[46483] pg_regress/guc WARNING: SET LOCAL can only be used in transaction blocks 2025-11-30 18:45:21.333 UTC client backend[46480] pg_regress/functional_deps ERROR: column "a.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-11-30 18:45:21.333 UTC client backend[46480] pg_regress/functional_deps STATEMENT: SELECT a.id, a.keywords, a.title, a.body, a.created FROM articles AS a JOIN articles_in_category AS aic ON a.id = aic.article_id WHERE aic.category_id in (14,62,70,53,138) GROUP BY aic.article_id, aic.category_id; 2025-11-30 18:45:21.335 UTC client backend[46480] pg_regress/functional_deps ERROR: column "aic.changed" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-11-30 18:45:21.335 UTC client backend[46480] pg_regress/functional_deps STATEMENT: SELECT aic.changed FROM articles AS a JOIN articles_in_category AS aic ON a.id = aic.article_id WHERE aic.category_id in (14,62,70,53,138) GROUP BY aic.article_id; 2025-11-30 18:45:21.341 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.341 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(1) is not present in table "pktable". 2025-11-30 18:45:21.341 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE FKTABLE ALTER CONSTRAINT fktable_ftest1_fkey ENFORCED; 2025-11-30 18:45:21.342 UTC client backend[46475] pg_regress/dependency ERROR: role "regress_dep_user" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.342 UTC client backend[46475] pg_regress/dependency DETAIL: privileges for table deptest 2025-11-30 18:45:21.342 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP USER regress_dep_user; 2025-11-30 18:45:21.351 UTC client backend[46475] pg_regress/dependency ERROR: role "regress_dep_group" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.351 UTC client backend[46475] pg_regress/dependency DETAIL: privileges for table deptest 2025-11-30 18:45:21.351 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP GROUP regress_dep_group; 2025-11-30 18:45:21.352 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-11-30 18:45:21.354 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.354 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(3) is not present in table "pktable". 2025-11-30 18:45:21.354 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (3, 4); 2025-11-30 18:45:21.361 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-11-30 18:45:21.363 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.363 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(100) is not present in table "pktable". 2025-11-30 18:45:21.363 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2); 2025-11-30 18:45:21.370 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-11-30 18:45:21.374 UTC client backend[46487] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-11-30 18:45:21.378 UTC client backend[46481] pg_regress/foreign_data ERROR: function bar(text[], oid) does not exist 2025-11-30 18:45:21.378 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo VALIDATOR bar; 2025-11-30 18:45:21.380 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" already exists 2025-11-30 18:45:21.380 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.395 UTC client backend[46477] pg_regress/foreign_key ERROR: constraint "constrname_wrong" for table "fktable" does not exist 2025-11-30 18:45:21.395 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMENT ON CONSTRAINT constrname_wrong ON FKTABLE IS 'fk constraint comment'; 2025-11-30 18:45:21.395 UTC client backend[46475] pg_regress/dependency ERROR: role "regress_dep_user" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.395 UTC client backend[46475] pg_regress/dependency DETAIL: privileges for table deptest 2025-11-30 18:45:21.395 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP USER regress_dep_user; 2025-11-30 18:45:21.399 UTC client backend[46481] pg_regress/foreign_data ERROR: option "testing" provided more than once 2025-11-30 18:45:21.399 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo OPTIONS (testing '1', testing '2'); 2025-11-30 18:45:21.400 UTC client backend[46475] pg_regress/dependency ERROR: role "regress_dep_user3" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.400 UTC client backend[46475] pg_regress/dependency DETAIL: owner of sequence deptest_f1_seq owner of table deptest 2025-11-30 18:45:21.400 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP USER regress_dep_user3; 2025-11-30 18:45:21.404 UTC client backend[46474] pg_regress/portals_p2 LOG: disconnection: session time: 0:00:00.118 user=postgres database=regression host=[local] 2025-11-30 18:45:21.413 UTC client backend[46489] pg_regress/tsdicts ERROR: invalid affix alias "GJUS" 2025-11-30 18:45:21.413 UTC client backend[46489] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY hunspell_err ( Template=ispell, DictFile=ispell_sample, AffFile=hunspell_sample_long ); 2025-11-30 18:45:21.413 UTC client backend[46489] pg_regress/tsdicts ERROR: invalid affix flag "SZ\" 2025-11-30 18:45:21.413 UTC client backend[46489] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY hunspell_err ( Template=ispell, DictFile=ispell_sample, AffFile=hunspell_sample_num ); 2025-11-30 18:45:21.414 UTC client backend[46489] pg_regress/tsdicts ERROR: invalid affix alias "302,301,202,303" 2025-11-30 18:45:21.414 UTC client backend[46489] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY hunspell_err ( Template=ispell, DictFile=hunspell_sample_num, AffFile=hunspell_sample_long ); 2025-11-30 18:45:21.416 UTC client backend[46489] pg_regress/tsdicts ERROR: casesensitive requires a Boolean value 2025-11-30 18:45:21.416 UTC client backend[46489] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH DICTIONARY synonym (CaseSensitive = 2); 2025-11-30 18:45:21.417 UTC client backend[46480] pg_regress/functional_deps ERROR: column "p.name" must appear in the GROUP BY clause or be used in an aggregate function at character 20 2025-11-30 18:45:21.417 UTC client backend[46480] pg_regress/functional_deps STATEMENT: SELECT product_id, p.name, (sum(s.units) * p.price) AS sales FROM products p LEFT JOIN sales s USING (product_id) GROUP BY product_id; 2025-11-30 18:45:21.422 UTC client backend[46487] pg_regress/advisory_lock LOG: disconnection: session time: 0:00:00.123 user=postgres database=regression host=[local] 2025-11-30 18:45:21.428 UTC client backend[46482] pg_regress/xmlmap LOG: disconnection: session time: 0:00:00.131 user=postgres database=regression host=[local] 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc ERROR: invalid value for parameter "seq_page_cost": "NaN" 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc STATEMENT: SET seq_page_cost TO 'NaN'; 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc ERROR: 10000 ms is outside the valid range for parameter "vacuum_cost_delay" (0 ms .. 100 ms) 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc STATEMENT: SET vacuum_cost_delay TO '10s'; 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc ERROR: unrecognized configuration parameter "no_such_variable" 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc STATEMENT: SET no_such_variable TO 42; 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc ERROR: unrecognized configuration parameter "custom.my_guc" 2025-11-30 18:45:21.436 UTC client backend[46483] pg_regress/guc STATEMENT: SHOW custom.my_guc; 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc ERROR: invalid configuration parameter name "custom.bad-guc" 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc DETAIL: Custom parameter names must be two or more simple identifiers separated by dots. 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc STATEMENT: SET custom."bad-guc" = 42; 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc ERROR: unrecognized configuration parameter "custom.bad-guc" 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc STATEMENT: SHOW custom."bad-guc"; 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc ERROR: invalid configuration parameter name "special.weird name" 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc DETAIL: Custom parameter names must be two or more simple identifiers separated by dots. 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc STATEMENT: SET special."weird name" = 'foo'; 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc ERROR: unrecognized configuration parameter "special.weird name" 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc STATEMENT: SHOW special."weird name"; 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc WARNING: invalid configuration parameter name "plpgsql.extra_foo_warnings", removing it 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc DETAIL: "plpgsql" is now a reserved prefix. 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc ERROR: invalid configuration parameter name "plpgsql.extra_foo_warnings" 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc DETAIL: "plpgsql" is a reserved prefix. 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc STATEMENT: SET plpgsql.extra_foo_warnings = true; 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc ERROR: unrecognized configuration parameter "plpgsql.extra_foo_warnings" 2025-11-30 18:45:21.437 UTC client backend[46483] pg_regress/guc STATEMENT: SHOW plpgsql.extra_foo_warnings; 2025-11-30 18:45:21.446 UTC client backend[46489] pg_regress/tsdicts ERROR: unrecognized Ispell parameter: "DictFile" 2025-11-30 18:45:21.446 UTC client backend[46489] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY tsdict_case ( Template = ispell, "DictFile" = ispell_sample, "AffFile" = ispell_sample ); 2025-11-30 18:45:21.447 UTC client backend[46489] pg_regress/tsdicts ERROR: token type "not_a_token" does not exist 2025-11-30 18:45:21.447 UTC client backend[46489] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst DROP MAPPING FOR not_a_token, not_a_token; 2025-11-30 18:45:21.447 UTC client backend[46489] pg_regress/tsdicts ERROR: token type "not_a_token" does not exist 2025-11-30 18:45:21.447 UTC client backend[46489] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst DROP MAPPING IF EXISTS FOR not_a_token, not_a_token; 2025-11-30 18:45:21.447 UTC client backend[46489] pg_regress/tsdicts ERROR: mapping for token type "word" does not exist 2025-11-30 18:45:21.447 UTC client backend[46489] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst DROP MAPPING FOR word; 2025-11-30 18:45:21.448 UTC client backend[46489] pg_regress/tsdicts ERROR: token type "not_a_token" does not exist 2025-11-30 18:45:21.448 UTC client backend[46489] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst ADD MAPPING FOR not_a_token WITH ispell; 2025-11-30 18:45:21.449 UTC client backend[46489] pg_regress/tsdicts LOG: disconnection: session time: 0:00:00.151 user=postgres database=regression host=[local] 2025-11-30 18:45:21.454 UTC client backend[46480] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 33 2025-11-30 18:45:21.454 UTC client backend[46480] pg_regress/functional_deps STATEMENT: CREATE TEMP VIEW fdv1 AS SELECT id, keywords, title, body, created FROM articles GROUP BY body; 2025-11-30 18:45:21.455 UTC client backend[46478] pg_regress/combocid LOG: disconnection: session time: 0:00:00.168 user=postgres database=regression host=[local] 2025-11-30 18:45:21.456 UTC client backend[46480] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-11-30 18:45:21.456 UTC client backend[46480] pg_regress/functional_deps DETAIL: view fdv1 depends on constraint articles_pkey on table articles 2025-11-30 18:45:21.456 UTC client backend[46480] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.456 UTC client backend[46480] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-11-30 18:45:21.458 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-11-30 18:45:21.458 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(100, 2) is not present in table "pktable". 2025-11-30 18:45:21.458 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2, 4); 2025-11-30 18:45:21.459 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-11-30 18:45:21.459 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(2, 2) is not present in table "pktable". 2025-11-30 18:45:21.459 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (2, 2, 4); 2025-11-30 18:45:21.459 UTC client backend[46480] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-11-30 18:45:21.459 UTC client backend[46480] pg_regress/functional_deps DETAIL: view fdv2 depends on constraint articles_pkey on table articles 2025-11-30 18:45:21.459 UTC client backend[46480] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.459 UTC client backend[46480] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-11-30 18:45:21.461 UTC client backend[46480] pg_regress/functional_deps ERROR: cannot drop constraint articles_in_category_pkey on table articles_in_category because other objects depend on it 2025-11-30 18:45:21.461 UTC client backend[46480] pg_regress/functional_deps DETAIL: view fdv2 depends on constraint articles_in_category_pkey on table articles_in_category 2025-11-30 18:45:21.461 UTC client backend[46480] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.461 UTC client backend[46480] pg_regress/functional_deps STATEMENT: ALTER TABLE articles_in_category DROP CONSTRAINT articles_in_category_pkey RESTRICT; 2025-11-30 18:45:21.461 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-11-30 18:45:21.461 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:21.461 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (NULL, 2, 4); 2025-11-30 18:45:21.462 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-11-30 18:45:21.462 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:21.462 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, NULL, 4); 2025-11-30 18:45:21.462 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to create foreign-data wrapper "foo" 2025-11-30 18:45:21.462 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to create a foreign-data wrapper. 2025-11-30 18:45:21.462 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.464 UTC client backend[46480] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-11-30 18:45:21.464 UTC client backend[46480] pg_regress/functional_deps DETAIL: view fdv3 depends on constraint articles_pkey on table articles 2025-11-30 18:45:21.464 UTC client backend[46480] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.464 UTC client backend[46480] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-11-30 18:45:21.466 UTC client backend[46480] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-11-30 18:45:21.466 UTC client backend[46480] pg_regress/functional_deps DETAIL: view fdv4 depends on constraint articles_pkey on table articles 2025-11-30 18:45:21.466 UTC client backend[46480] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.466 UTC client backend[46480] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-11-30 18:45:21.467 UTC client backend[46481] pg_regress/foreign_data ERROR: function invalid_fdw_handler must return type fdw_handler 2025-11-30 18:45:21.467 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER test_fdw HANDLER invalid_fdw_handler; 2025-11-30 18:45:21.469 UTC client backend[46481] pg_regress/foreign_data ERROR: conflicting or redundant options at character 63 2025-11-30 18:45:21.469 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER test_fdw HANDLER test_fdw_handler HANDLER invalid_fdw_handler; 2025-11-30 18:45:21.469 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-11-30 18:45:21.469 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:21.469 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE FKTABLE SET ftest1 = NULL WHERE ftest1 = 1; 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency ERROR: permission denied to drop objects 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user1" may drop objects owned by it. 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP OWNED BY regress_dep_user1; 2025-11-30 18:45:21.470 UTC client backend[46481] pg_regress/foreign_data ERROR: invalid option "nonexistent" 2025-11-30 18:45:21.470 UTC client backend[46481] pg_regress/foreign_data HINT: There are no valid options in this context. 2025-11-30 18:45:21.470 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (nonexistent 'fdw'); 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency ERROR: permission denied to drop objects 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user2" may drop objects owned by it. 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP OWNED BY regress_dep_user0, regress_dep_user2; 2025-11-30 18:45:21.470 UTC client backend[46481] pg_regress/foreign_data ERROR: syntax error at or near ";" at character 31 2025-11-30 18:45:21.470 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency ERROR: permission denied to reassign objects 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user1" may reassign objects to it. 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency STATEMENT: REASSIGN OWNED BY regress_dep_user0 TO regress_dep_user1; 2025-11-30 18:45:21.470 UTC client backend[46481] pg_regress/foreign_data ERROR: function bar(text[], oid) does not exist 2025-11-30 18:45:21.470 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo VALIDATOR bar; 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency ERROR: permission denied to reassign objects 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user1" may reassign objects owned by it. 2025-11-30 18:45:21.470 UTC client backend[46475] pg_regress/dependency STATEMENT: REASSIGN OWNED BY regress_dep_user1 TO regress_dep_user0; 2025-11-30 18:45:21.474 UTC client backend[46481] pg_regress/foreign_data ERROR: option "c" not found 2025-11-30 18:45:21.474 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (SET c '4'); 2025-11-30 18:45:21.474 UTC client backend[46481] pg_regress/foreign_data ERROR: option "c" not found 2025-11-30 18:45:21.474 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (DROP c); 2025-11-30 18:45:21.477 UTC client backend[46480] pg_regress/functional_deps ERROR: column "articles.keywords" must appear in the GROUP BY clause or be used in an aggregate function at character 29 2025-11-30 18:45:21.477 UTC client backend[46480] pg_regress/functional_deps STATEMENT: EXECUTE foo; 2025-11-30 18:45:21.492 UTC client backend[46481] pg_regress/foreign_data ERROR: option "b" provided more than once 2025-11-30 18:45:21.492 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (b '4'); 2025-11-30 18:45:21.494 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-11-30 18:45:21.494 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-11-30 18:45:21.494 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (ADD d '5'); 2025-11-30 18:45:21.496 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to change owner of foreign-data wrapper "foo" 2025-11-30 18:45:21.496 UTC client backend[46481] pg_regress/foreign_data HINT: The owner of a foreign-data wrapper must be a superuser. 2025-11-30 18:45:21.496 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OWNER TO regress_test_role; 2025-11-30 18:45:21.496 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-11-30 18:45:21.496 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-11-30 18:45:21.496 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (ADD e '6'); 2025-11-30 18:45:21.530 UTC client backend[46481] pg_regress/foreign_data ERROR: function invalid_fdw_handler must return type fdw_handler 2025-11-30 18:45:21.530 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo HANDLER invalid_fdw_handler; 2025-11-30 18:45:21.534 UTC client backend[46480] pg_regress/functional_deps LOG: disconnection: session time: 0:00:00.245 user=postgres database=regression host=[local] 2025-11-30 18:45:21.544 UTC client backend[46475] pg_regress/dependency ERROR: role "regress_dep_user1" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.544 UTC client backend[46475] pg_regress/dependency DETAIL: privileges for database regression privileges for table deptest1 owner of default privileges on new relations belonging to role regress_dep_user1 in schema deptest 2025-11-30 18:45:21.544 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP USER regress_dep_user1; 2025-11-30 18:45:21.547 UTC client backend[46481] pg_regress/foreign_data ERROR: conflicting or redundant options at character 57 2025-11-30 18:45:21.547 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo HANDLER test_fdw_handler HANDLER anything; 2025-11-30 18:45:21.547 UTC client backend[46475] pg_regress/dependency ERROR: role "regress_dep_user2" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.547 UTC client backend[46475] pg_regress/dependency DETAIL: owner of schema deptest owner of sequence deptest_a_seq owner of table deptest owner of function deptest_func() owner of type deptest_enum owner of type deptest_range owner of table deptest2 owner of sequence ss1 owner of type deptest_t 2025-11-30 18:45:21.547 UTC client backend[46475] pg_regress/dependency STATEMENT: DROP USER regress_dep_user2; 2025-11-30 18:45:21.548 UTC client backend[46483] pg_regress/guc ERROR: division by zero 2025-11-30 18:45:21.548 UTC client backend[46483] pg_regress/guc CONTEXT: SQL statement "SELECT 1/$1" PL/pgSQL function myfunc(integer) line 4 at PERFORM 2025-11-30 18:45:21.548 UTC client backend[46483] pg_regress/guc STATEMENT: select myfunc(0); 2025-11-30 18:45:21.549 UTC client backend[46481] pg_regress/foreign_data WARNING: changing the foreign-data wrapper handler can change behavior of existing foreign tables 2025-11-30 18:45:21.549 UTC client backend[46483] pg_regress/guc ERROR: unrecognized configuration parameter "nosuch.setting" 2025-11-30 18:45:21.549 UTC client backend[46483] pg_regress/guc STATEMENT: select current_setting('nosuch.setting'); 2025-11-30 18:45:21.549 UTC client backend[46483] pg_regress/guc ERROR: unrecognized configuration parameter "nosuch.setting" 2025-11-30 18:45:21.549 UTC client backend[46483] pg_regress/guc STATEMENT: select current_setting('nosuch.setting', false); 2025-11-30 18:45:21.549 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "nonexistent" does not exist 2025-11-30 18:45:21.549 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER nonexistent; 2025-11-30 18:45:21.551 UTC client backend[46483] pg_regress/guc ERROR: invalid value for parameter "default_text_search_config": "no_such_config" 2025-11-30 18:45:21.551 UTC client backend[46483] pg_regress/guc STATEMENT: create function func_with_bad_set() returns int as $$ select 1 $$ language sql set default_text_search_config = no_such_config; 2025-11-30 18:45:21.551 UTC client backend[46481] pg_regress/foreign_data ERROR: role "regress_test_role_super" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.551 UTC client backend[46481] pg_regress/foreign_data DETAIL: owner of foreign-data wrapper foo 2025-11-30 18:45:21.551 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP ROLE regress_test_role_super; 2025-11-30 18:45:21.551 UTC client backend[46483] pg_regress/guc ERROR: invalid value for parameter "default_text_search_config": "no_such_config" 2025-11-30 18:45:21.551 UTC client backend[46483] pg_regress/guc STATEMENT: select func_with_bad_set(); 2025-11-30 18:45:21.551 UTC client backend[46483] pg_regress/guc ERROR: tables declared WITH OIDS are not supported 2025-11-30 18:45:21.551 UTC client backend[46483] pg_regress/guc STATEMENT: set default_with_oids to t; 2025-11-30 18:45:21.555 UTC client backend[46481] pg_regress/foreign_data ERROR: user mapping for "regress_foreign_data_user" already exists for server "s1" 2025-11-30 18:45:21.555 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR current_user SERVER s1; 2025-11-30 18:45:21.560 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot drop foreign-data wrapper foo because other objects depend on it 2025-11-30 18:45:21.560 UTC client backend[46481] pg_regress/foreign_data DETAIL: server s1 depends on foreign-data wrapper foo user mapping for regress_foreign_data_user on server s1 depends on server s1 2025-11-30 18:45:21.560 UTC client backend[46481] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.560 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.560 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign-data wrapper foo 2025-11-30 18:45:21.560 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo CASCADE; 2025-11-30 18:45:21.566 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" does not exist 2025-11-30 18:45:21.566 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE SERVER s1 FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.566 UTC client backend[46481] pg_regress/foreign_data ERROR: server "s1" already exists 2025-11-30 18:45:21.566 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE SERVER s1 FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.568 UTC client backend[46481] pg_regress/foreign_data ERROR: invalid option "foo" 2025-11-30 18:45:21.568 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE SERVER s8 FOREIGN DATA WRAPPER postgresql OPTIONS (foo '1'); 2025-11-30 18:45:21.577 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-11-30 18:45:21.577 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE SERVER t1 FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.579 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-11-30 18:45:21.579 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(100, 2) is not present in table "pktable". 2025-11-30 18:45:21.579 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2, 4); 2025-11-30 18:45:21.587 UTC client backend[46475] pg_regress/dependency LOG: disconnection: session time: 0:00:00.303 user=postgres database=regression host=[local] 2025-11-30 18:45:21.592 UTC client backend[46483] pg_regress/guc LOG: disconnection: session time: 0:00:00.305 user=postgres database=regression host=[local] 2025-11-30 18:45:21.592 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-11-30 18:45:21.592 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(2, 2) is not present in table "pktable". 2025-11-30 18:45:21.592 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (2, 2, 4); 2025-11-30 18:45:21.594 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-11-30 18:45:21.594 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:21.594 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (NULL, 2, 4); 2025-11-30 18:45:21.595 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-11-30 18:45:21.595 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:21.595 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, NULL, 4); 2025-11-30 18:45:21.604 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-11-30 18:45:21.604 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE SERVER t2 FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.604 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table pktable because other objects depend on it 2025-11-30 18:45:21.604 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint constrname2 on table fktable depends on table pktable 2025-11-30 18:45:21.604 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.604 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE PKTABLE; 2025-11-30 18:45:21.606 UTC client backend[46481] pg_regress/foreign_data ERROR: syntax error at or near ";" at character 16 2025-11-30 18:45:21.606 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s0; 2025-11-30 18:45:21.606 UTC client backend[46481] pg_regress/foreign_data ERROR: server "s0" does not exist 2025-11-30 18:45:21.606 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s0 OPTIONS (a '1'); 2025-11-30 18:45:21.609 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s1 2025-11-30 18:45:21.609 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 VERSION '1.1'; 2025-11-30 18:45:21.609 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s1 2025-11-30 18:45:21.609 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 OWNER TO regress_test_role; 2025-11-30 18:45:21.610 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-11-30 18:45:21.610 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 OWNER TO regress_test_role2; 2025-11-30 18:45:21.610 UTC client backend[46481] pg_regress/foreign_data ERROR: invalid option "foo" 2025-11-30 18:45:21.610 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s8 OPTIONS (foo '1'); 2025-11-30 18:45:21.610 UTC client backend[46481] pg_regress/foreign_data ERROR: must be able to SET ROLE "regress_test_indirect" 2025-11-30 18:45:21.610 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 OWNER TO regress_test_indirect; 2025-11-30 18:45:21.611 UTC client backend[46481] pg_regress/foreign_data ERROR: role "regress_test_indirect" cannot be dropped because some objects depend on it 2025-11-30 18:45:21.611 UTC client backend[46481] pg_regress/foreign_data DETAIL: privileges for foreign-data wrapper foo owner of server s1 2025-11-30 18:45:21.611 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP ROLE regress_test_indirect; 2025-11-30 18:45:21.614 UTC client backend[46491] pg_regress/window ERROR: argument of ROWS must not contain variables at character 40 2025-11-30 18:45:21.614 UTC client backend[46491] pg_regress/window STATEMENT: SELECT sum(unique1) over (rows between unbounded.x preceding and unbounded.x following), unique1, four FROM tenk1, (values (1)) as unbounded(x) WHERE unique1 < 10; 2025-11-30 18:45:21.615 UTC client backend[46481] pg_regress/foreign_data ERROR: server "nonexistent" does not exist 2025-11-30 18:45:21.615 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP SERVER nonexistent; 2025-11-30 18:45:21.616 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s2 2025-11-30 18:45:21.616 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP SERVER s2; 2025-11-30 18:45:21.622 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot drop server s3 because other objects depend on it 2025-11-30 18:45:21.622 UTC client backend[46481] pg_regress/foreign_data DETAIL: user mapping for regress_foreign_data_user on server s3 depends on server s3 2025-11-30 18:45:21.622 UTC client backend[46481] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:21.622 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP SERVER s3; 2025-11-30 18:45:21.628 UTC client backend[46481] pg_regress/foreign_data ERROR: role "regress_test_missing_role" does not exist 2025-11-30 18:45:21.628 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR regress_test_missing_role SERVER s1; 2025-11-30 18:45:21.628 UTC client backend[46488] pg_regress/tsearch ERROR: unrecognized parameter "foo" 2025-11-30 18:45:21.628 UTC client backend[46488] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(foo=1)); 2025-11-30 18:45:21.629 UTC client backend[46481] pg_regress/foreign_data ERROR: server "s1" does not exist 2025-11-30 18:45:21.629 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR current_user SERVER s1; 2025-11-30 18:45:21.629 UTC client backend[46488] pg_regress/tsearch ERROR: value 0 out of bounds for option "siglen" 2025-11-30 18:45:21.629 UTC client backend[46488] pg_regress/tsearch DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:21.629 UTC client backend[46488] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=0)); 2025-11-30 18:45:21.629 UTC client backend[46481] pg_regress/foreign_data ERROR: user mapping for "regress_foreign_data_user" already exists for server "s4" 2025-11-30 18:45:21.629 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR user SERVER s4; 2025-11-30 18:45:21.629 UTC client backend[46488] pg_regress/tsearch ERROR: value 2048 out of bounds for option "siglen" 2025-11-30 18:45:21.629 UTC client backend[46488] pg_regress/tsearch DETAIL: Valid values are between "1" and "2024". 2025-11-30 18:45:21.629 UTC client backend[46488] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=2048)); 2025-11-30 18:45:21.630 UTC client backend[46488] pg_regress/tsearch ERROR: unrecognized parameter "foo" 2025-11-30 18:45:21.630 UTC client backend[46488] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=100,foo='bar')); 2025-11-30 18:45:21.630 UTC client backend[46488] pg_regress/tsearch ERROR: parameter "siglen" specified more than once 2025-11-30 18:45:21.630 UTC client backend[46488] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=100, siglen = 200)); 2025-11-30 18:45:21.630 UTC client backend[46481] pg_regress/foreign_data ERROR: invalid option "username" 2025-11-30 18:45:21.630 UTC client backend[46481] pg_regress/foreign_data HINT: Perhaps you meant the option "user". 2025-11-30 18:45:21.630 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR user SERVER s8 OPTIONS (username 'test', password 'secret'); 2025-11-30 18:45:21.634 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign server s7 2025-11-30 18:45:21.634 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR current_user SERVER s7; 2025-11-30 18:45:21.635 UTC client backend[46486] pg_regress/equivclass LOG: disconnection: session time: 0:00:00.338 user=postgres database=regression host=[local] 2025-11-30 18:45:21.637 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s8 2025-11-30 18:45:21.637 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR public SERVER s8; 2025-11-30 18:45:21.639 UTC client backend[46481] pg_regress/foreign_data ERROR: role "regress_test_missing_role" does not exist 2025-11-30 18:45:21.639 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR regress_test_missing_role SERVER s4 OPTIONS (gotcha 'true'); 2025-11-30 18:45:21.639 UTC client backend[46485] pg_regress/cluster ERROR: insert or update on table "clstr_tst" violates foreign key constraint "clstr_tst_con" 2025-11-30 18:45:21.639 UTC client backend[46485] pg_regress/cluster DETAIL: Key (b)=(1111) is not present in table "clstr_tst_s". 2025-11-30 18:45:21.639 UTC client backend[46485] pg_regress/cluster STATEMENT: INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail'); 2025-11-30 18:45:21.639 UTC client backend[46481] pg_regress/foreign_data ERROR: server "ss4" does not exist 2025-11-30 18:45:21.639 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR user SERVER ss4 OPTIONS (gotcha 'true'); 2025-11-30 18:45:21.639 UTC client backend[46481] pg_regress/foreign_data ERROR: user mapping for "public" does not exist for server "s5" 2025-11-30 18:45:21.639 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR public SERVER s5 OPTIONS (gotcha 'true'); 2025-11-30 18:45:21.640 UTC client backend[46481] pg_regress/foreign_data ERROR: invalid option "username" 2025-11-30 18:45:21.640 UTC client backend[46481] pg_regress/foreign_data HINT: Perhaps you meant the option "user". 2025-11-30 18:45:21.640 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR current_user SERVER s8 OPTIONS (username 'test'); 2025-11-30 18:45:21.640 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-11-30 18:45:21.640 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR public SERVER s4 OPTIONS (ADD modified '1'); 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data ERROR: role "regress_test_missing_role" does not exist 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR regress_test_missing_role SERVER s4; 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data ERROR: server "ss4" does not exist 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR user SERVER ss4; 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data ERROR: user mapping for "public" does not exist for server "s7" 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR public SERVER s7; 2025-11-30 18:45:21.642 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.642 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_float4, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_float4 range between 1.1 preceding and 'NaN' following); 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s8 2025-11-30 18:45:21.642 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR public SERVER s8; 2025-11-30 18:45:21.644 UTC client backend[46481] pg_regress/foreign_data ERROR: syntax error at or near ";" at character 28 2025-11-30 18:45:21.644 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 (); 2025-11-30 18:45:21.645 UTC client backend[46481] pg_regress/foreign_data ERROR: server "no_server" does not exist 2025-11-30 18:45:21.645 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 () SERVER no_server; 2025-11-30 18:45:21.645 UTC client backend[46481] pg_regress/foreign_data ERROR: primary key constraints are not supported on foreign tables at character 67 2025-11-30 18:45:21.645 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 ( c1 integer OPTIONS ("param 1" 'val1') PRIMARY KEY, c2 text OPTIONS (param2 'val2', param3 'val3'), c3 date ) SERVER s0 OPTIONS (delimiter ',', quote '"', "be quoted" 'value'); 2025-11-30 18:45:21.647 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.647 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_float8, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_float8 range between 1.1 preceding and 'NaN' following); 2025-11-30 18:45:21.647 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign key constraints are not supported on foreign tables at character 67 2025-11-30 18:45:21.647 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 ( c1 integer OPTIONS ("param 1" 'val1') REFERENCES ref_table (id), c2 text OPTIONS (param2 'val2', param3 'val3'), c3 date ) SERVER s0 OPTIONS (delimiter ',', quote '"', "be quoted" 'value'); 2025-11-30 18:45:21.649 UTC client backend[46481] pg_regress/foreign_data ERROR: unique constraints are not supported on foreign tables at character 137 2025-11-30 18:45:21.649 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 ( c1 integer OPTIONS ("param 1" 'val1') NOT NULL, c2 text OPTIONS (param2 'val2', param3 'val3'), c3 date, UNIQUE (c3) ) SERVER s0 OPTIONS (delimiter ',', quote '"', "be quoted" 'value'); 2025-11-30 18:45:21.650 UTC client backend[46491] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type numeric and offset type double precision at character 158 2025-11-30 18:45:21.650 UTC client backend[46491] pg_regress/window HINT: Cast the offset value to an appropriate type. 2025-11-30 18:45:21.650 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_numeric, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_numeric range between 1 preceding and 1.1::float8 following); 2025-11-30 18:45:21.652 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.652 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(100) is not present in table "pktable". 2025-11-30 18:45:21.652 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2); 2025-11-30 18:45:21.652 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.652 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_numeric, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_numeric range between 1.1 preceding and 'NaN' following); 2025-11-30 18:45:21.654 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-11-30 18:45:21.654 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ptest1)=(1) is still referenced from table "fktable". 2025-11-30 18:45:21.654 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM PKTABLE WHERE ptest1=1; 2025-11-30 18:45:21.655 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.655 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_time, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_time desc range between '-70 min' preceding and '2 hours' following); 2025-11-30 18:45:21.656 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-11-30 18:45:21.656 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ptest1)=(2) is still referenced from table "fktable". 2025-11-30 18:45:21.656 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE PKTABLE SET ptest1=0 WHERE ptest1=2; 2025-11-30 18:45:21.656 UTC client backend[46479] pg_regress/bitmapops LOG: disconnection: session time: 0:00:00.370 user=postgres database=regression host=[local] 2025-11-30 18:45:21.659 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.659 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_time, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_time range between '-infinity'::interval following and 'infinity'::interval following); 2025-11-30 18:45:21.661 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.661 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_timetz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timetz desc range between '70 min' preceding and '-2 hours' following); 2025-11-30 18:45:21.662 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.662 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_timetz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timetz range between 'infinity'::interval following and '-infinity'::interval following); 2025-11-30 18:45:21.663 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.663 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_interval, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_interval desc range between '-1 year' preceding and '1 year' following); 2025-11-30 18:45:21.668 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" 2025-11-30 18:45:21.668 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:21.668 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) REFERENCES PKTABLE MATCH FULL; 2025-11-30 18:45:21.674 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create index on relation "ft1" 2025-11-30 18:45:21.674 UTC client backend[46481] pg_regress/foreign_data DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:21.674 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE INDEX id_ft1_c2 ON ft1 (c2); 2025-11-30 18:45:21.674 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "dummy" has no handler 2025-11-30 18:45:21.674 UTC client backend[46481] pg_regress/foreign_data STATEMENT: SELECT * FROM ft1; 2025-11-30 18:45:21.675 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "dummy" has no handler 2025-11-30 18:45:21.675 UTC client backend[46481] pg_regress/foreign_data STATEMENT: EXPLAIN SELECT * FROM ft1; 2025-11-30 18:45:21.675 UTC client backend[46484] pg_regress/indirect_toast LOG: disconnection: session time: 0:00:00.381 user=postgres database=regression host=[local] 2025-11-30 18:45:21.679 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1" 2025-11-30 18:45:21.679 UTC client backend[46481] pg_regress/foreign_data DETAIL: Table "lt1" contains partitions that are foreign tables. 2025-11-30 18:45:21.679 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE UNIQUE INDEX ON lt1 (a); 2025-11-30 18:45:21.682 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1" 2025-11-30 18:45:21.682 UTC client backend[46481] pg_regress/foreign_data DETAIL: Table "lt1" contains partitions that are foreign tables. 2025-11-30 18:45:21.682 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1 ADD PRIMARY KEY (a); 2025-11-30 18:45:21.684 UTC client backend[46485] pg_regress/cluster ERROR: there is no previously clustered index for table "clstr_2" 2025-11-30 18:45:21.684 UTC client backend[46485] pg_regress/cluster STATEMENT: CLUSTER clstr_2; 2025-11-30 18:45:21.686 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-11-30 18:45:21.686 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-11-30 18:45:21.686 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-11-30 18:45:21.687 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.687 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_interval, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_interval range between '-infinity'::interval following and 'infinity'::interval following); 2025-11-30 18:45:21.688 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "constrname3" on table "fktable" 2025-11-30 18:45:21.688 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ptest1, ptest2, ptest3)=(1, 2, 3) is still referenced from table "fktable". 2025-11-30 18:45:21.688 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE PKTABLE set ptest2=5 where ptest2=2; 2025-11-30 18:45:21.690 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.690 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_timestamptz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamptz desc range between '1 year' preceding and '-1 year' following); 2025-11-30 18:45:21.691 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "constrname3" on table "fktable" 2025-11-30 18:45:21.691 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ptest1, ptest2, ptest3)=(1, 2, 3) is still referenced from table "fktable". 2025-11-30 18:45:21.691 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM PKTABLE where ptest1=1 and ptest2=2 and ptest3=3; 2025-11-30 18:45:21.693 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.693 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_timestamptz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamptz range between '-infinity'::interval following and 'infinity'::interval following); 2025-11-30 18:45:21.698 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create foreign partition of partitioned table "lt1" 2025-11-30 18:45:21.698 UTC client backend[46481] pg_regress/foreign_data DETAIL: Table "lt1" contains indexes that are unique. 2025-11-30 18:45:21.698 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft_part1 PARTITION OF lt1 FOR VALUES FROM (0) TO (1000) SERVER s0; 2025-11-30 18:45:21.698 UTC client backend[46485] pg_regress/cluster WARNING: permission denied to cluster "pg_toast_826", skipping it 2025-11-30 18:45:21.698 UTC client backend[46485] pg_regress/cluster WARNING: permission denied to cluster "clstr_2", skipping it 2025-11-30 18:45:21.700 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot attach foreign table "ft_part2" as partition of partitioned table "lt1" 2025-11-30 18:45:21.700 UTC client backend[46481] pg_regress/foreign_data DETAIL: Partitioned table "lt1" contains unique indexes. 2025-11-30 18:45:21.700 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1 ATTACH PARTITION ft_part2 FOR VALUES FROM (1000) TO (2000); 2025-11-30 18:45:21.703 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.703 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_timestamp, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamp desc range between '-1 year' preceding and '1 year' following); 2025-11-30 18:45:21.707 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.707 UTC client backend[46491] pg_regress/window STATEMENT: select id, f_timestamp, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamp range between '-infinity'::interval following and 'infinity'::interval following); 2025-11-30 18:45:21.707 UTC client backend[46491] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING requires exactly one ORDER BY column at character 25 2025-11-30 18:45:21.707 UTC client backend[46491] pg_regress/window STATEMENT: select sum(salary) over (order by enroll_date, salary range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.709 UTC client backend[46491] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING requires exactly one ORDER BY column at character 25 2025-11-30 18:45:21.709 UTC client backend[46491] pg_regress/window STATEMENT: select sum(salary) over (range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.710 UTC client backend[46491] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type text at character 57 2025-11-30 18:45:21.710 UTC client backend[46491] pg_regress/window STATEMENT: select sum(salary) over (order by depname range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.711 UTC client backend[46491] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type date and offset type integer at character 66 2025-11-30 18:45:21.711 UTC client backend[46491] pg_regress/window HINT: Cast the offset value to an appropriate type. 2025-11-30 18:45:21.711 UTC client backend[46491] pg_regress/window STATEMENT: select max(enroll_date) over (order by enroll_date range between 1 preceding and 2 following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.711 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.711 UTC client backend[46491] pg_regress/window STATEMENT: select max(enroll_date) over (order by salary range between -1 preceding and 2 following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.711 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.711 UTC client backend[46491] pg_regress/window STATEMENT: select max(enroll_date) over (order by salary range between 1 preceding and -2 following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.714 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1" 2025-11-30 18:45:21.714 UTC client backend[46481] pg_regress/foreign_data DETAIL: Table "lt1" contains partitions that are foreign tables. 2025-11-30 18:45:21.714 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE UNIQUE INDEX ON lt1 (a); 2025-11-30 18:45:21.717 UTC client backend[46491] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type integer and offset type interval at character 61 2025-11-30 18:45:21.717 UTC client backend[46491] pg_regress/window HINT: Cast the offset value to an appropriate type. 2025-11-30 18:45:21.717 UTC client backend[46491] pg_regress/window STATEMENT: select max(enroll_date) over (order by salary range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.718 UTC client backend[46491] pg_regress/window ERROR: invalid preceding or following size in window function 2025-11-30 18:45:21.718 UTC client backend[46491] pg_regress/window STATEMENT: select max(enroll_date) over (order by enroll_date range between '1 year'::interval preceding and '-2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-11-30 18:45:21.719 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1_part1" 2025-11-30 18:45:21.719 UTC client backend[46481] pg_regress/foreign_data DETAIL: Table "lt1_part1" contains partitions that are foreign tables. 2025-11-30 18:45:21.719 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1 ADD PRIMARY KEY (a); 2025-11-30 18:45:21.723 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-11-30 18:45:21.723 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-11-30 18:45:21.723 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-11-30 18:45:21.726 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create foreign partition of partitioned table "lt1_part1" 2025-11-30 18:45:21.726 UTC client backend[46481] pg_regress/foreign_data DETAIL: Table "lt1_part1" contains indexes that are unique. 2025-11-30 18:45:21.726 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft_part_1_1 PARTITION OF lt1_part1 FOR VALUES FROM (0) TO (100) SERVER s0; 2025-11-30 18:45:21.730 UTC client backend[46476] pg_regress/select_views LOG: disconnection: session time: 0:00:00.447 user=postgres database=regression host=[local] 2025-11-30 18:45:21.731 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot attach foreign table "ft_part_1_2" as partition of partitioned table "lt1_part1" 2025-11-30 18:45:21.731 UTC client backend[46481] pg_regress/foreign_data DETAIL: Partitioned table "lt1_part1" contains unique indexes. 2025-11-30 18:45:21.731 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1_part1 ATTACH PARTITION ft_part_1_2 FOR VALUES FROM (100) TO (200); 2025-11-30 18:45:21.737 UTC client backend[46491] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING requires exactly one ORDER BY column at character 25 2025-11-30 18:45:21.737 UTC client backend[46491] pg_regress/window STATEMENT: select f1, sum(f1) over (partition by f1 range between 1 preceding and 1 following) from t1 where f1 = f2; 2025-11-30 18:45:21.740 UTC client backend[46490] pg_regress/stats_rewrite LOG: disconnection: session time: 0:00:00.436 user=postgres database=regression host=[local] 2025-11-30 18:45:21.742 UTC client backend[46491] pg_regress/window ERROR: GROUPS mode requires an ORDER BY clause at character 25 2025-11-30 18:45:21.742 UTC client backend[46491] pg_regress/window STATEMENT: select f1, sum(f1) over (partition by f1 groups between 1 preceding and 1 following) from t1 where f1 = f2; 2025-11-30 18:45:21.746 UTC client backend[46491] pg_regress/window ERROR: window functions are not allowed in window definitions at character 30 2025-11-30 18:45:21.746 UTC client backend[46491] pg_regress/window STATEMENT: SELECT rank() OVER (ORDER BY rank() OVER (ORDER BY random())); 2025-11-30 18:45:21.747 UTC client backend[46491] pg_regress/window ERROR: window functions are not allowed in WHERE at character 31 2025-11-30 18:45:21.747 UTC client backend[46491] pg_regress/window STATEMENT: SELECT * FROM empsalary WHERE row_number() OVER (ORDER BY salary) < 10; 2025-11-30 18:45:21.747 UTC client backend[46491] pg_regress/window ERROR: window functions are not allowed in JOIN conditions at character 45 2025-11-30 18:45:21.747 UTC client backend[46491] pg_regress/window STATEMENT: SELECT * FROM empsalary INNER JOIN tenk1 ON row_number() OVER (ORDER BY salary) < 10; 2025-11-30 18:45:21.748 UTC client backend[46491] pg_regress/window ERROR: window functions are not allowed in GROUP BY at character 8 2025-11-30 18:45:21.748 UTC client backend[46491] pg_regress/window STATEMENT: SELECT rank() OVER (ORDER BY 1), count(*) FROM empsalary GROUP BY 1; 2025-11-30 18:45:21.749 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-11-30 18:45:21.749 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-11-30 18:45:21.749 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-11-30 18:45:21.755 UTC client backend[46481] pg_regress/foreign_data ERROR: "ft1" is not a table 2025-11-30 18:45:21.755 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER COLUMN c8 TYPE char(10) USING '0'; 2025-11-30 18:45:21.757 UTC client backend[46491] pg_regress/window ERROR: syntax error at or near "ORDER" at character 28 2025-11-30 18:45:21.757 UTC client backend[46491] pg_regress/window STATEMENT: SELECT * FROM rank() OVER (ORDER BY random()); 2025-11-30 18:45:21.758 UTC client backend[46491] pg_regress/window ERROR: window functions are not allowed in WHERE at character 30 2025-11-30 18:45:21.758 UTC client backend[46491] pg_regress/window STATEMENT: DELETE FROM empsalary WHERE (rank() OVER (ORDER BY random())) > 10; 2025-11-30 18:45:21.759 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot alter system column "xmin" 2025-11-30 18:45:21.759 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER COLUMN xmin OPTIONS (ADD p1 'v1'); 2025-11-30 18:45:21.759 UTC client backend[46491] pg_regress/window ERROR: window functions are not allowed in RETURNING at character 33 2025-11-30 18:45:21.759 UTC client backend[46491] pg_regress/window STATEMENT: DELETE FROM empsalary RETURNING rank() OVER (ORDER BY random()); 2025-11-30 18:45:21.760 UTC client backend[46491] pg_regress/window ERROR: window "w" is already defined at character 72 2025-11-30 18:45:21.760 UTC client backend[46491] pg_regress/window STATEMENT: SELECT count(*) OVER w FROM tenk1 WINDOW w AS (ORDER BY unique1), w AS (ORDER BY unique1); 2025-11-30 18:45:21.761 UTC client backend[46491] pg_regress/window ERROR: syntax error at or near "ORDER" at character 40 2025-11-30 18:45:21.761 UTC client backend[46491] pg_regress/window STATEMENT: SELECT rank() OVER (PARTITION BY four, ORDER BY ten) FROM tenk1; 2025-11-30 18:45:21.761 UTC client backend[46491] pg_regress/window ERROR: count(*) must be used to call a parameterless aggregate function at character 8 2025-11-30 18:45:21.761 UTC client backend[46491] pg_regress/window STATEMENT: SELECT count() OVER () FROM tenk1; 2025-11-30 18:45:21.763 UTC client backend[46491] pg_regress/window ERROR: OVER specified, but generate_series is not a window function nor an aggregate function at character 8 2025-11-30 18:45:21.763 UTC client backend[46491] pg_regress/window STATEMENT: SELECT generate_series(1, 100) OVER () FROM empsalary; 2025-11-30 18:45:21.767 UTC client backend[46491] pg_regress/window ERROR: argument of ntile must be greater than zero 2025-11-30 18:45:21.767 UTC client backend[46491] pg_regress/window STATEMENT: SELECT ntile(0) OVER (ORDER BY ten), ten, four FROM tenk1; 2025-11-30 18:45:21.771 UTC client backend[46491] pg_regress/window ERROR: argument of nth_value must be greater than zero 2025-11-30 18:45:21.771 UTC client backend[46491] pg_regress/window STATEMENT: SELECT nth_value(four, 0) OVER (ORDER BY ten), ten, four FROM tenk1; 2025-11-30 18:45:21.775 UTC client backend[46485] pg_regress/cluster ERROR: cannot cluster on invalid index "clstrpart_only_idx" 2025-11-30 18:45:21.775 UTC client backend[46485] pg_regress/cluster STATEMENT: CLUSTER clstrpart USING clstrpart_only_idx; 2025-11-30 18:45:21.781 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-11-30 18:45:21.781 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-11-30 18:45:21.781 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-11-30 18:45:21.782 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot alter foreign table "ft1" because column "use_ft1_column_type.x" uses its row type 2025-11-30 18:45:21.782 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER COLUMN c8 SET DATA TYPE integer; 2025-11-30 18:45:21.783 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-11-30 18:45:21.783 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(0, -1, -2) is not present in table "pktable". 2025-11-30 18:45:21.783 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE PKTABLE set ptest2=5 where ptest2=2; 2025-11-30 18:45:21.791 UTC client backend[46481] pg_regress/foreign_data ERROR: primary key constraints are not supported on foreign tables at character 29 2025-11-30 18:45:21.791 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ADD PRIMARY KEY (c7); 2025-11-30 18:45:21.792 UTC client backend[46481] pg_regress/foreign_data ERROR: ALTER action ALTER CONSTRAINT cannot be performed on relation "ft1" 2025-11-30 18:45:21.792 UTC client backend[46481] pg_regress/foreign_data DETAIL: This operation is not supported for foreign tables. 2025-11-30 18:45:21.792 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER CONSTRAINT ft1_c9_check DEFERRABLE; 2025-11-30 18:45:21.793 UTC client backend[46481] pg_regress/foreign_data ERROR: constraint "no_const" of relation "ft1" does not exist 2025-11-30 18:45:21.793 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 DROP CONSTRAINT no_const; 2025-11-30 18:45:21.794 UTC client backend[46481] pg_regress/foreign_data ERROR: column "no_column" of relation "ft1" does not exist 2025-11-30 18:45:21.794 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 DROP COLUMN no_column; 2025-11-30 18:45:21.798 UTC client backend[46481] pg_regress/foreign_data ERROR: relation "ft1" does not exist 2025-11-30 18:45:21.798 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 SET TABLESPACE ts; 2025-11-30 18:45:21.798 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot move an owned sequence into another schema 2025-11-30 18:45:21.798 UTC client backend[46481] pg_regress/foreign_data DETAIL: Sequence "ft1_c11_seq" is linked to table "ft1". 2025-11-30 18:45:21.798 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SEQUENCE foreign_schema.ft1_c11_seq SET SCHEMA public; 2025-11-30 18:45:21.802 UTC client backend[46477] pg_regress/foreign_key ERROR: column "bar" referenced in foreign key constraint does not exist 2025-11-30 18:45:21.802 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (tid int, id int, foo int, FOREIGN KEY (tid, id) REFERENCES PKTABLE ON DELETE SET NULL (bar)); 2025-11-30 18:45:21.804 UTC client backend[46477] pg_regress/foreign_key ERROR: column "foo" referenced in ON DELETE SET action must be part of foreign key 2025-11-30 18:45:21.804 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (tid int, id int, foo int, FOREIGN KEY (tid, id) REFERENCES PKTABLE ON DELETE SET NULL (foo)); 2025-11-30 18:45:21.805 UTC client backend[46477] pg_regress/foreign_key ERROR: a column list with SET NULL is only supported for ON DELETE actions at character 91 2025-11-30 18:45:21.805 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (tid int, id int, foo int, FOREIGN KEY (tid, foo) REFERENCES PKTABLE ON UPDATE SET NULL (foo)); 2025-11-30 18:45:21.810 UTC client backend[46485] pg_regress/cluster ERROR: there is no previously clustered index for table "clstrpart" 2025-11-30 18:45:21.810 UTC client backend[46485] pg_regress/cluster STATEMENT: CLUSTER clstrpart; 2025-11-30 18:45:21.811 UTC client backend[46485] pg_regress/cluster ERROR: cannot mark index clustered in partitioned table 2025-11-30 18:45:21.811 UTC client backend[46485] pg_regress/cluster STATEMENT: ALTER TABLE clstrpart SET WITHOUT CLUSTER; 2025-11-30 18:45:21.811 UTC client backend[46485] pg_regress/cluster ERROR: cannot mark index clustered in partitioned table 2025-11-30 18:45:21.811 UTC client backend[46485] pg_regress/cluster STATEMENT: ALTER TABLE clstrpart CLUSTER ON clstrpart_idx; 2025-11-30 18:45:21.825 UTC client backend[46485] pg_regress/cluster ERROR: permission denied for table ptnowner 2025-11-30 18:45:21.825 UTC client backend[46485] pg_regress/cluster STATEMENT: CLUSTER ptnowner USING ptnowner_i_idx; 2025-11-30 18:45:21.827 UTC client backend[46477] pg_regress/foreign_key ERROR: column "ftest2" referenced in foreign key constraint does not exist 2025-11-30 18:45:21.827 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL1 ( ftest1 int, CONSTRAINT fkfail1 FOREIGN KEY (ftest2) REFERENCES PKTABLE); 2025-11-30 18:45:21.828 UTC client backend[46477] pg_regress/foreign_key ERROR: column "ptest2" referenced in foreign key constraint does not exist 2025-11-30 18:45:21.828 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL2 ( ftest1 int, CONSTRAINT fkfail1 FOREIGN KEY (ftest1) REFERENCES PKTABLE(ptest2)); 2025-11-30 18:45:21.829 UTC client backend[46485] pg_regress/cluster WARNING: permission denied to cluster "ptnowner2", skipping it 2025-11-30 18:45:21.829 UTC client backend[46477] pg_regress/foreign_key ERROR: system columns cannot be used in foreign keys 2025-11-30 18:45:21.829 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL3 ( ftest1 int, CONSTRAINT fkfail1 FOREIGN KEY (tableoid) REFERENCES PKTABLE(someoid)); 2025-11-30 18:45:21.834 UTC client backend[46491] pg_regress/window ERROR: interval out of range 2025-11-30 18:45:21.834 UTC client backend[46491] pg_regress/window STATEMENT: SELECT x, avg(x) OVER(ROWS BETWEEN CURRENT ROW AND 2 FOLLOWING) FROM (VALUES (NULL::interval), ('3 days'::interval), ('infinity'::timestamptz - now()), ('6 days'::interval), ('-infinity'::interval)) v(x); 2025-11-30 18:45:21.835 UTC client backend[46491] pg_regress/window ERROR: interval out of range 2025-11-30 18:45:21.835 UTC client backend[46491] pg_regress/window STATEMENT: SELECT x, sum(x) OVER(ROWS BETWEEN CURRENT ROW AND 2 FOLLOWING) FROM (VALUES (NULL::interval), ('3 days'::interval), ('infinity'::timestamptz - now()), ('6 days'::interval), ('-infinity'::interval)) v(x); 2025-11-30 18:45:21.837 UTC client backend[46477] pg_regress/foreign_key ERROR: system columns cannot be used in foreign keys 2025-11-30 18:45:21.837 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL4 ( ftest1 oid, CONSTRAINT fkfail1 FOREIGN KEY (ftest1) REFERENCES PKTABLE(tableoid)); 2025-11-30 18:45:21.850 UTC client backend[46477] pg_regress/foreign_key ERROR: there is no unique constraint matching given keys for referenced table "pktable" 2025-11-30 18:45:21.850 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL1 (ftest1 int REFERENCES pktable(ptest1)); 2025-11-30 18:45:21.850 UTC client backend[46477] pg_regress/foreign_key ERROR: table "fktable_fail1" does not exist 2025-11-30 18:45:21.850 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE FKTABLE_FAIL1; 2025-11-30 18:45:21.855 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-11-30 18:45:21.855 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.855 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 inet REFERENCES pktable); 2025-11-30 18:45:21.856 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-11-30 18:45:21.856 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.856 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 inet REFERENCES pktable(ptest1)); 2025-11-30 18:45:21.862 UTC client backend[46481] pg_regress/foreign_data WARNING: changing the foreign-data wrapper validator can cause the options for dependent objects to become invalid 2025-11-30 18:45:21.862 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to create foreign-data wrapper "foobar" 2025-11-30 18:45:21.862 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to create a foreign-data wrapper. 2025-11-30 18:45:21.862 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foobar; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (gotcha 'true'); 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to change owner of foreign-data wrapper "foo" 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to change owner of a foreign-data wrapper. 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OWNER TO regress_unprivileged_role; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign-data wrapper foo 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN DATA WRAPPER foo TO regress_test_role; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE SERVER s9 FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s4 VERSION '0.5'; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s4 OWNER TO regress_unprivileged_role; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP SERVER s4; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign server s4 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN SERVER s4 TO regress_test_role; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR public SERVER s4; 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR regress_test_role SERVER s6 OPTIONS (gotcha 'true'); 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-11-30 18:45:21.863 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR regress_test_role SERVER s6; 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to create foreign-data wrapper "foobar" 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to create a foreign-data wrapper. 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foobar; 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (gotcha 'true'); 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign-data wrapper foo 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.864 UTC client backend[46481] pg_regress/foreign_data WARNING: no privileges were granted for "postgresql" 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s6 VERSION '0.5'; 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP SERVER s6; 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign server s6 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN SERVER s6 TO regress_test_role; 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR public SERVER s6; 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR regress_test_role SERVER s6 OPTIONS (gotcha 'true'); 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-11-30 18:45:21.865 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR regress_test_role SERVER s6; 2025-11-30 18:45:21.866 UTC client backend[46481] pg_regress/foreign_data ERROR: dependent privileges exist 2025-11-30 18:45:21.866 UTC client backend[46481] pg_regress/foreign_data HINT: Use CASCADE to revoke them too. 2025-11-30 18:45:21.866 UTC client backend[46481] pg_regress/foreign_data STATEMENT: REVOKE USAGE ON FOREIGN DATA WRAPPER foo FROM regress_unprivileged_role; 2025-11-30 18:45:21.866 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-11-30 18:45:21.866 UTC client backend[46481] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN DATA WRAPPER foo TO regress_test_role; 2025-11-30 18:45:21.866 UTC client backend[46481] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-11-30 18:45:21.866 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE SERVER s10 FOREIGN DATA WRAPPER foo; 2025-11-30 18:45:21.868 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.868 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-11-30 18:45:21.868 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES(43); 2025-11-30 18:45:21.874 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s9 2025-11-30 18:45:21.874 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER SERVER s9 VERSION '1.2'; 2025-11-30 18:45:21.875 UTC client backend[46481] pg_regress/foreign_data WARNING: no privileges were granted for "s9" 2025-11-30 18:45:21.876 UTC client backend[46481] pg_regress/foreign_data ERROR: must be owner of foreign server s9 2025-11-30 18:45:21.876 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP SERVER s9 CASCADE; 2025-11-30 18:45:21.876 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.876 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-11-30 18:45:21.876 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE FKTABLE SET ftest1 = ftest1 + 1; 2025-11-30 18:45:21.879 UTC client backend[46488] pg_regress/tsearch LOG: disconnection: session time: 0:00:00.581 user=postgres database=regression host=[local] 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window ERROR: aggregate functions do not accept RESPECT/IGNORE NULLS at character 8 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window STATEMENT: SELECT sum(orbit) RESPECT NULLS OVER () FROM planets; 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window ERROR: aggregate functions do not accept RESPECT/IGNORE NULLS at character 8 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window STATEMENT: SELECT sum(orbit) IGNORE NULLS OVER () FROM planets; 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window ERROR: function row_number does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window STATEMENT: SELECT row_number() RESPECT NULLS OVER () FROM planets; 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window ERROR: function row_number does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.880 UTC client backend[46491] pg_regress/window STATEMENT: SELECT row_number() IGNORE NULLS OVER () FROM planets; 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window ERROR: function rank does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window STATEMENT: SELECT rank() RESPECT NULLS OVER () FROM planets; 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window ERROR: function rank does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window STATEMENT: SELECT rank() IGNORE NULLS OVER () FROM planets; 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window ERROR: function dense_rank does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window STATEMENT: SELECT dense_rank() RESPECT NULLS OVER () FROM planets; 2025-11-30 18:45:21.881 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-11-30 18:45:21.881 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: numeric and integer. 2025-11-30 18:45:21.881 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 numeric REFERENCES pktable); 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window ERROR: function dense_rank does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.881 UTC client backend[46491] pg_regress/window STATEMENT: SELECT dense_rank() IGNORE NULLS OVER () FROM planets; 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window ERROR: function percent_rank does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window STATEMENT: SELECT percent_rank() RESPECT NULLS OVER () FROM planets; 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window ERROR: function percent_rank does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window STATEMENT: SELECT percent_rank() IGNORE NULLS OVER () FROM planets; 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window ERROR: function cume_dist does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window STATEMENT: SELECT cume_dist() RESPECT NULLS OVER () FROM planets; 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window ERROR: function cume_dist does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.882 UTC client backend[46491] pg_regress/window STATEMENT: SELECT cume_dist() IGNORE NULLS OVER () FROM planets; 2025-11-30 18:45:21.883 UTC client backend[46491] pg_regress/window ERROR: function ntile does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.883 UTC client backend[46491] pg_regress/window STATEMENT: SELECT ntile(1) RESPECT NULLS OVER () FROM planets; 2025-11-30 18:45:21.883 UTC client backend[46491] pg_regress/window ERROR: function ntile does not allow RESPECT/IGNORE NULLS 2025-11-30 18:45:21.883 UTC client backend[46491] pg_regress/window STATEMENT: SELECT ntile(1) IGNORE NULLS OVER () FROM planets; 2025-11-30 18:45:21.887 UTC client backend[46481] pg_regress/foreign_data ERROR: "foreign_table_1" is a foreign table 2025-11-30 18:45:21.887 UTC client backend[46481] pg_regress/foreign_data DETAIL: Triggers on foreign tables cannot have transition tables. 2025-11-30 18:45:21.887 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE TRIGGER trigtest_after_stmt_tt AFTER INSERT OR UPDATE OR DELETE -- ERROR ON foreign_schema.foreign_table_1 REFERENCING NEW TABLE AS new_table FOR EACH STATEMENT EXECUTE PROCEDURE dummy_trigger(); 2025-11-30 18:45:21.888 UTC client backend[46481] pg_regress/foreign_data ERROR: "foreign_table_1" is a foreign table 2025-11-30 18:45:21.888 UTC client backend[46481] pg_regress/foreign_data DETAIL: Foreign tables cannot have constraint triggers. 2025-11-30 18:45:21.888 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE CONSTRAINT TRIGGER trigtest_constraint AFTER INSERT OR UPDATE OR DELETE ON foreign_schema.foreign_table_1 FOR EACH ROW EXECUTE PROCEDURE dummy_trigger(); 2025-11-30 18:45:21.889 UTC client backend[46491] pg_regress/window LOG: disconnection: session time: 0:00:00.576 user=postgres database=regression host=[local] 2025-11-30 18:45:21.891 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.891 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-11-30 18:45:21.891 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES(43); 2025-11-30 18:45:21.892 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.892 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-11-30 18:45:21.892 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE FKTABLE SET ftest1 = ftest1 + 1; 2025-11-30 18:45:21.900 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:21.900 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: cidr and integer. 2025-11-30 18:45:21.900 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 cidr, ftest2 timestamp, FOREIGN KEY(ftest1, ftest2) REFERENCES pktable); 2025-11-30 18:45:21.902 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:21.902 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: cidr and integer. 2025-11-30 18:45:21.902 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 cidr, ftest2 timestamp, FOREIGN KEY(ftest1, ftest2) REFERENCES pktable(ptest1, ptest2)); 2025-11-30 18:45:21.904 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-11-30 18:45:21.904 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.904 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 int, ftest2 inet, FOREIGN KEY(ftest2, ftest1) REFERENCES pktable); 2025-11-30 18:45:21.905 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-11-30 18:45:21.905 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.905 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 int, ftest2 inet, FOREIGN KEY(ftest2, ftest1) REFERENCES pktable(ptest1, ptest2)); 2025-11-30 18:45:21.907 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:21.907 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest2" of the referenced table are of incompatible types: integer and inet. 2025-11-30 18:45:21.907 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 int, ftest2 inet, FOREIGN KEY(ftest1, ftest2) REFERENCES pktable(ptest2, ptest1)); 2025-11-30 18:45:21.936 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest3_ptest4_fkey" cannot be implemented 2025-11-30 18:45:21.936 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ptest3" of the referencing table and "ptest2" of the referenced table are of incompatible types: integer and inet. 2025-11-30 18:45:21.936 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE PKTABLE (ptest1 int, ptest2 inet, ptest3 int, ptest4 inet, PRIMARY KEY(ptest1, ptest2), FOREIGN KEY(ptest3, ptest4) REFERENCES pktable(ptest2, ptest1)); 2025-11-30 18:45:21.939 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest4_ptest3_fkey" cannot be implemented 2025-11-30 18:45:21.939 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ptest4" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.939 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE PKTABLE (ptest1 int, ptest2 inet, ptest3 int, ptest4 inet, PRIMARY KEY(ptest1, ptest2), FOREIGN KEY(ptest4, ptest3) REFERENCES pktable(ptest1, ptest2)); 2025-11-30 18:45:21.942 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest4_ptest3_fkey" cannot be implemented 2025-11-30 18:45:21.942 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ptest4" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.942 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TABLE PKTABLE (ptest1 int, ptest2 inet, ptest3 int, ptest4 inet, PRIMARY KEY(ptest1, ptest2), FOREIGN KEY(ptest4, ptest3) REFERENCES pktable); 2025-11-30 18:45:21.944 UTC client backend[46485] pg_regress/cluster LOG: disconnection: session time: 0:00:00.647 user=postgres database=regression host=[local] 2025-11-30 18:45:21.950 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:21.950 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1)=(3) is not present in table "pktable". 2025-11-30 18:45:21.950 UTC client backend[46477] pg_regress/foreign_key STATEMENT: insert into fktable(ftest1) values (3); 2025-11-30 18:45:21.952 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-11-30 18:45:21.952 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (base1)=(3) is still referenced from table "fktable". 2025-11-30 18:45:21.952 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from pktable where base1>2; 2025-11-30 18:45:21.953 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-11-30 18:45:21.953 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (base1)=(3) is still referenced from table "fktable". 2025-11-30 18:45:21.953 UTC client backend[46477] pg_regress/foreign_key STATEMENT: update pktable set base1=base1*4; 2025-11-30 18:45:21.961 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" 2025-11-30 18:45:21.961 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(3, 1) is not present in table "pktable". 2025-11-30 18:45:21.961 UTC client backend[46477] pg_regress/foreign_key STATEMENT: insert into fktable(ftest1, ftest2) values (3, 1); 2025-11-30 18:45:21.963 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" on table "fktable" 2025-11-30 18:45:21.963 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(3, 1) is still referenced from table "fktable". 2025-11-30 18:45:21.963 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from pktable where base1>2; 2025-11-30 18:45:21.964 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" on table "fktable" 2025-11-30 18:45:21.964 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(3, 1) is still referenced from table "fktable". 2025-11-30 18:45:21.964 UTC client backend[46477] pg_regress/foreign_key STATEMENT: update pktable set base1=base1*4; 2025-11-30 18:45:21.978 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "pktable" violates foreign key constraint "pktable_base2_ptest2_fkey" 2025-11-30 18:45:21.978 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (base2, ptest2)=(3, 2) is not present in table "pktable". 2025-11-30 18:45:21.978 UTC client backend[46477] pg_regress/foreign_key STATEMENT: insert into pktable (base1, ptest1, base2, ptest2) values (2, 3, 3, 2); 2025-11-30 18:45:21.979 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "pktable_base2_ptest2_fkey" on table "pktable" 2025-11-30 18:45:21.979 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(2, 2) is still referenced from table "pktable". 2025-11-30 18:45:21.979 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from pktable where base1=2; 2025-11-30 18:45:21.979 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "pktable_base2_ptest2_fkey" on table "pktable" 2025-11-30 18:45:21.979 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(1, 1) is still referenced from table "pktable". 2025-11-30 18:45:21.979 UTC client backend[46477] pg_regress/foreign_key STATEMENT: update pktable set base1=3 where base1=1; 2025-11-30 18:45:21.990 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:21.990 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "base1" of the referenced table are of incompatible types: cidr and integer. 2025-11-30 18:45:21.990 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 cidr, ftest2 int[], foreign key (ftest1, ftest2) references pktable); 2025-11-30 18:45:21.992 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:21.992 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "base1" of the referenced table are of incompatible types: cidr and integer. 2025-11-30 18:45:21.992 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 cidr, ftest2 int[], foreign key (ftest1, ftest2) references pktable(base1, ptest1)); 2025-11-30 18:45:21.993 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-11-30 18:45:21.993 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.993 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 int, ftest2 inet, foreign key(ftest2, ftest1) references pktable); 2025-11-30 18:45:21.995 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-11-30 18:45:21.995 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:21.995 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 int, ftest2 inet, foreign key(ftest2, ftest1) references pktable(base1, ptest1)); 2025-11-30 18:45:21.997 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:21.997 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: integer and inet. 2025-11-30 18:45:21.997 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 int, ftest2 inet, foreign key(ftest1, ftest2) references pktable(ptest1, base1)); 2025-11-30 18:45:22.004 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "pktable_base2_ptest2_fkey" cannot be implemented 2025-11-30 18:45:22.004 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ptest2" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet[] and inet. 2025-11-30 18:45:22.004 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet[], primary key(base1, ptest1), foreign key(base2, ptest2) references pktable(base1, ptest1)) inherits (pktable_base); 2025-11-30 18:45:22.007 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "pktable_base2_ptest2_fkey" cannot be implemented 2025-11-30 18:45:22.007 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "base2" of the referencing table and "ptest1" of the referenced table are of incompatible types: integer and inet. 2025-11-30 18:45:22.007 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet, primary key(base1, ptest1), foreign key(base2, ptest2) references pktable(ptest1, base1)) inherits (pktable_base); 2025-11-30 18:45:22.011 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest2_base2_fkey" cannot be implemented 2025-11-30 18:45:22.011 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ptest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:22.011 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet, primary key(base1, ptest1), foreign key(ptest2, base2) references pktable(base1, ptest1)) inherits (pktable_base); 2025-11-30 18:45:22.014 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest2_base2_fkey" cannot be implemented 2025-11-30 18:45:22.014 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "ptest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-11-30 18:45:22.014 UTC client backend[46477] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet, primary key(base1, ptest1), foreign key(ptest2, base2) references pktable(base1, ptest1)) inherits (pktable_base); 2025-11-30 18:45:22.014 UTC client backend[46477] pg_regress/foreign_key ERROR: table "pktable" does not exist 2025-11-30 18:45:22.014 UTC client backend[46477] pg_regress/foreign_key STATEMENT: drop table pktable; 2025-11-30 18:45:22.021 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.021 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(10) is not present in table "pktable". 2025-11-30 18:45:22.021 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fktable VALUES (5, 10); 2025-11-30 18:45:22.023 UTC client backend[46481] pg_regress/foreign_data ERROR: "ft2" is not a table 2025-11-30 18:45:22.023 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt1 ALTER COLUMN c8 TYPE char(10) USING '0'; 2025-11-30 18:45:22.034 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.034 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(1000) is not present in table "pktable". 2025-11-30 18:45:22.034 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fktable VALUES (500, 1000); 2025-11-30 18:45:22.043 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.043 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(2000) is not present in table "pktable". 2025-11-30 18:45:22.043 UTC client backend[46477] pg_regress/foreign_key STATEMENT: SET CONSTRAINTS ALL IMMEDIATE; 2025-11-30 18:45:22.043 UTC client backend[46477] pg_regress/foreign_key ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-11-30 18:45:22.043 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO pktable VALUES (2000, 3); 2025-11-30 18:45:22.053 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.053 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(200) is not present in table "pktable". 2025-11-30 18:45:22.053 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:22.067 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fk_2_3" cannot be implemented 2025-11-30 18:45:22.067 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "x2" of the referencing table and "id3" of the referenced table are of incompatible types: character varying and real. 2025-11-30 18:45:22.067 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_2_3 FOREIGN KEY (x2) REFERENCES pktable(id3); 2025-11-30 18:45:22.067 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fk_2_1" cannot be implemented 2025-11-30 18:45:22.067 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "x2" of the referencing table and "id1" of the referenced table are of incompatible types: character varying and integer. 2025-11-30 18:45:22.067 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_2_1 FOREIGN KEY (x2) REFERENCES pktable(id1); 2025-11-30 18:45:22.068 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fk_3_1" cannot be implemented 2025-11-30 18:45:22.068 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "x3" of the referencing table and "id1" of the referenced table are of incompatible types: real and integer. 2025-11-30 18:45:22.068 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_3_1 FOREIGN KEY (x3) REFERENCES pktable(id1); 2025-11-30 18:45:22.068 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fk_1_2" cannot be implemented 2025-11-30 18:45:22.068 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "x1" of the referencing table and "id2" of the referenced table are of incompatible types: integer and character varying. 2025-11-30 18:45:22.068 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_1_2 FOREIGN KEY (x1) REFERENCES pktable(id2); 2025-11-30 18:45:22.082 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fk_123_231" cannot be implemented 2025-11-30 18:45:22.082 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "x1" of the referencing table and "id2" of the referenced table are of incompatible types: integer and character varying. 2025-11-30 18:45:22.082 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_123_231 FOREIGN KEY (x1,x2,x3) REFERENCES pktable(id2,id3,id1); 2025-11-30 18:45:22.082 UTC client backend[46477] pg_regress/foreign_key ERROR: foreign key constraint "fk_241_132" cannot be implemented 2025-11-30 18:45:22.082 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key columns "x2" of the referencing table and "id1" of the referenced table are of incompatible types: character varying and integer. 2025-11-30 18:45:22.082 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_241_132 FOREIGN KEY (x2,x4,x1) REFERENCES pktable(id1,id3,id2); 2025-11-30 18:45:22.101 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.101 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-11-30 18:45:22.101 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:22.103 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.103 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-11-30 18:45:22.103 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:22.105 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.105 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-11-30 18:45:22.105 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:22.106 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot drop foreign table ft2 because other objects depend on it 2025-11-30 18:45:22.106 UTC client backend[46481] pg_regress/foreign_data DETAIL: table ct3 depends on foreign table ft2 foreign table ft3 depends on foreign table ft2 2025-11-30 18:45:22.106 UTC client backend[46481] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:22.106 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP FOREIGN TABLE ft2; 2025-11-30 18:45:22.106 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.106 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-11-30 18:45:22.106 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:22.109 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_fk_fkey" on table "fktable" 2025-11-30 18:45:22.109 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id)=(5) is still referenced from table "fktable". 2025-11-30 18:45:22.109 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pktable SET id = 10 WHERE id = 5; 2025-11-30 18:45:22.110 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-11-30 18:45:22.110 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-11-30 18:45:22.110 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fktable VALUES (0, 20); 2025-11-30 18:45:22.110 UTC client backend[46481] pg_regress/foreign_data ERROR: child table is missing constraint "fd_pt1chk2" 2025-11-30 18:45:22.110 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft2 INHERIT fd_pt1; 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key ERROR: constraint declared INITIALLY DEFERRED must be DEFERRABLE at character 69 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey NOT DEFERRABLE INITIALLY DEFERRED; 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key ERROR: constraint "fktable_fk_fkey" of relation "fktable" is not a not-null constraint 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey NO INHERIT; 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key ERROR: constraints cannot be altered to be NOT VALID at character 54 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey NOT VALID; 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key ERROR: conflicting constraint properties at character 63 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey ENFORCED NOT ENFORCED; 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key ERROR: multiple ENFORCED/NOT ENFORCED clauses not allowed at character 64 2025-11-30 18:45:22.113 UTC client backend[46477] pg_regress/foreign_key STATEMENT: CREATE TEMP TABLE fktable2 (fk int references pktable ENFORCED NOT ENFORCED); 2025-11-30 18:45:22.148 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "defp" violates foreign key constraint "defc_f1_fkey" on table "defc" 2025-11-30 18:45:22.148 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(0) is still referenced from table "defc". 2025-11-30 18:45:22.148 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from defp where f1 = 0; 2025-11-30 18:45:22.151 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "defp" violates foreign key constraint "defc_f1_fkey" on table "defc" 2025-11-30 18:45:22.151 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(1) is still referenced from table "defc". 2025-11-30 18:45:22.151 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from defp where f1 = 1; 2025-11-30 18:45:22.159 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pp" violates foreign key constraint "cc_f1_fkey" on table "cc" 2025-11-30 18:45:22.159 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(13) is still referenced from table "cc". 2025-11-30 18:45:22.159 UTC client backend[46477] pg_regress/foreign_key STATEMENT: update pp set f1=f1+1; 2025-11-30 18:45:22.160 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pp" violates foreign key constraint "cc_f1_fkey" on table "cc" 2025-11-30 18:45:22.160 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(13) is still referenced from table "cc". 2025-11-30 18:45:22.160 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from pp where f1 = 13; 2025-11-30 18:45:22.169 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pp" violates RESTRICT setting of foreign key constraint "cc_f1_fkey" on table "cc" 2025-11-30 18:45:22.169 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(13) is referenced from table "cc". 2025-11-30 18:45:22.169 UTC client backend[46477] pg_regress/foreign_key STATEMENT: update pp set f1=f1+1; 2025-11-30 18:45:22.170 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pp" violates RESTRICT setting of foreign key constraint "cc_f1_fkey" on table "cc" 2025-11-30 18:45:22.170 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(13) is referenced from table "cc". 2025-11-30 18:45:22.170 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from pp where f1 = 13; 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 FROM SERVER s9 INTO public; 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 LIMIT TO (t1) FROM SERVER s9 INTO public; 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 EXCEPT (t1) FROM SERVER s9 INTO public; 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 EXCEPT (t1, t2) FROM SERVER s9 INTO public OPTIONS (option1 'value1', option2 'value2'); 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data ERROR: foreign table "no_table" does not exist 2025-11-30 18:45:22.188 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP FOREIGN TABLE no_table; 2025-11-30 18:45:22.190 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable2" violates foreign key constraint "fktable2_d_e_fkey" on table "fktable2" 2025-11-30 18:45:22.190 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (d, e)=(4, 5) is still referenced from table "fktable2". 2025-11-30 18:45:22.190 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from pktable2; 2025-11-30 18:45:22.190 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pktable2" violates foreign key constraint "fktable2_d_e_fkey" on table "fktable2" 2025-11-30 18:45:22.190 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (d, e)=(4, 5) is still referenced from table "fktable2". 2025-11-30 18:45:22.190 UTC client backend[46477] pg_regress/foreign_key STATEMENT: update pktable2 set d = 5; 2025-11-30 18:45:22.191 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot drop desired object(s) because other objects depend on them 2025-11-30 18:45:22.191 UTC client backend[46481] pg_regress/foreign_data DETAIL: user mapping for regress_test_role on server s5 depends on server s5 2025-11-30 18:45:22.191 UTC client backend[46481] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:22.191 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP OWNED BY regress_test_role2; 2025-11-30 18:45:22.217 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fktable2" violates foreign key constraint "fktable2_f1_fkey" 2025-11-30 18:45:22.217 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(2) is not present in table "pktable2". 2025-11-30 18:45:22.217 UTC client backend[46477] pg_regress/foreign_key STATEMENT: commit; 2025-11-30 18:45:22.217 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot ALTER TABLE "fktable2" because it has pending trigger events 2025-11-30 18:45:22.217 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fktable2 drop constraint fktable2_f1_fkey; 2025-11-30 18:45:22.218 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot ALTER TABLE "pktable2" because it has pending trigger events 2025-11-30 18:45:22.218 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fktable2 drop constraint fktable2_f1_fkey; 2025-11-30 18:45:22.226 UTC client backend[46481] pg_regress/foreign_data ERROR: table "fd_pt2_1" contains column "c4" not found in parent "fd_pt2" 2025-11-30 18:45:22.226 UTC client backend[46481] pg_regress/foreign_data DETAIL: The new partition may contain only the columns present in parent. 2025-11-30 18:45:22.226 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2 ATTACH PARTITION fd_pt2_1 FOR VALUES IN (1); 2025-11-30 18:45:22.256 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot use ONLY for foreign key on partitioned table "fk_partitioned_fk" referencing relation "fk_notpartitioned_pk" 2025-11-30 18:45:22.256 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE ONLY fk_partitioned_fk ADD FOREIGN KEY (a, b) REFERENCES fk_notpartitioned_pk; 2025-11-30 18:45:22.256 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.256 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(500, 501) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.256 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (500, 501); 2025-11-30 18:45:22.257 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.257 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(500, 501) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.257 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_1 (a,b) VALUES (500, 501); 2025-11-30 18:45:22.258 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.258 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(1500, 1501) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.258 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (1500, 1501); 2025-11-30 18:45:22.258 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.258 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(1500, 1501) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.258 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_2 (a,b) VALUES (1500, 1501); 2025-11-30 18:45:22.259 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.259 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2500, 2502) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.259 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (2500, 2502); 2025-11-30 18:45:22.259 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.259 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2500, 2502) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.259 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_3 (a,b) VALUES (2500, 2502); 2025-11-30 18:45:22.260 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_0" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.260 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2501, 2503) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.260 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (2501, 2503); 2025-11-30 18:45:22.260 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_0" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.260 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2501, 2503) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.260 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_3 (a,b) VALUES (2501, 2503); 2025-11-30 18:45:22.264 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.264 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2502, 2503) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.264 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE fk_partitioned_fk SET a = a + 1 WHERE a = 2501; 2025-11-30 18:45:22.266 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" on table "fk_partitioned_fk" 2025-11-30 18:45:22.266 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(500, 501) is still referenced from table "fk_partitioned_fk". 2025-11-30 18:45:22.266 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET b = 502 WHERE a = 500; 2025-11-30 18:45:22.267 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot add column to a partition 2025-11-30 18:45:22.267 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2_1 ADD c4 char; 2025-11-30 18:45:22.267 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" on table "fk_partitioned_fk" 2025-11-30 18:45:22.267 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(1500, 1501) is still referenced from table "fk_partitioned_fk". 2025-11-30 18:45:22.267 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET b = 1502 WHERE a = 1500; 2025-11-30 18:45:22.268 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" on table "fk_partitioned_fk" 2025-11-30 18:45:22.268 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2500, 2502) is still referenced from table "fk_partitioned_fk". 2025-11-30 18:45:22.268 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET b = 2504 WHERE a = 2500; 2025-11-30 18:45:22.288 UTC client backend[46481] pg_regress/foreign_data ERROR: column "c1" is marked NOT NULL in parent table 2025-11-30 18:45:22.288 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2_1 ALTER c1 DROP NOT NULL; 2025-11-30 18:45:22.309 UTC client backend[46481] pg_regress/foreign_data ERROR: column "c2" in child table "fd_pt2_1" must be marked NOT NULL 2025-11-30 18:45:22.309 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2 ATTACH PARTITION fd_pt2_1 FOR VALUES IN (1); 2025-11-30 18:45:22.329 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_fkey" on table "fk_partitioned_fk" 2025-11-30 18:45:22.329 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk_partitioned_fk". 2025-11-30 18:45:22.329 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM fk_notpartitioned_pk WHERE a = 1; 2025-11-30 18:45:22.331 UTC client backend[46481] pg_regress/foreign_data ERROR: child table is missing constraint "fd_pt2chk1" 2025-11-30 18:45:22.331 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2 ATTACH PARTITION fd_pt2_1 FOR VALUES IN (1); 2025-11-30 18:45:22.337 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2025-11-30 18:45:22.337 UTC client backend[46481] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE foreign_part PARTITION OF temp_parted DEFAULT SERVER s0; 2025-11-30 18:45:22.338 UTC client backend[46481] pg_regress/foreign_data ERROR: cannot attach a permanent relation as partition of temporary relation "temp_parted" 2025-11-30 18:45:22.338 UTC client backend[46481] pg_regress/foreign_data STATEMENT: ALTER TABLE temp_parted ATTACH PARTITION foreign_part DEFAULT; 2025-11-30 18:45:22.340 UTC client backend[46481] pg_regress/foreign_data ERROR: role "regress_test_role" cannot be dropped because some objects depend on it 2025-11-30 18:45:22.340 UTC client backend[46481] pg_regress/foreign_data DETAIL: privileges for foreign-data wrapper foo privileges for server s4 owner of user mapping for regress_test_role on server s6 2025-11-30 18:45:22.340 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP ROLE regress_test_role; 2025-11-30 18:45:22.343 UTC client backend[46481] pg_regress/foreign_data ERROR: role "regress_unprivileged_role" cannot be dropped because some objects depend on it 2025-11-30 18:45:22.343 UTC client backend[46481] pg_regress/foreign_data DETAIL: privileges for foreign-data wrapper postgresql 2025-11-30 18:45:22.343 UTC client backend[46481] pg_regress/foreign_data STATEMENT: DROP ROLE regress_unprivileged_role; 2025-11-30 18:45:22.345 UTC unrecognized[46494] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:22.346 UTC client backend[46494] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:22.346 UTC client backend[46494] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/foreign_data 2025-11-30 18:45:22.347 UTC client backend[46494] pg_regress/foreign_data LOG: connection ready: setup total=2.024 ms, fork=0.483 ms, authentication=0.123 ms 2025-11-30 18:45:22.347 UTC client backend[46481] pg_regress/foreign_data LOG: disconnection: session time: 0:00:01.053 user=postgres database=regression host=[local] 2025-11-30 18:45:22.349 UTC client backend[46494] pg_regress/foreign_data LOG: disconnection: session time: 0:00:00.003 user=postgres database=regression host=[local] 2025-11-30 18:45:22.357 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2" violates foreign key constraint "fk_partitioned_fk_2_a_b_fkey" 2025-11-30 18:45:22.357 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(1000, 1000) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.357 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk ATTACH PARTITION fk_partitioned_fk_2 FOR VALUES FROM (1000,1000) TO (2000,2000); 2025-11-30 18:45:22.458 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.458 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2502, 2503) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.458 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a, b) VALUES (2502, 2503); 2025-11-30 18:45:22.458 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.458 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2502, 2503) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.458 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_3 (a, b) VALUES (2502, 2503); 2025-11-30 18:45:22.466 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_full_1" violates foreign key constraint "fk_partitioned_fk_full_x_y_fkey" 2025-11-30 18:45:22.466 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:22.466 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk_full ADD FOREIGN KEY (x, y) REFERENCES fk_notpartitioned_pk MATCH FULL; 2025-11-30 18:45:22.470 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_full_1" violates foreign key constraint "fk_partitioned_fk_full_x_y_fkey" 2025-11-30 18:45:22.470 UTC client backend[46477] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-11-30 18:45:22.470 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_full VALUES (1, NULL); 2025-11-30 18:45:22.490 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.490 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2501, 142857) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.490 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET a = 1500 WHERE a = 2502; 2025-11-30 18:45:22.498 UTC client backend[46452] isolation/eval-plan-qual/s2 ERROR: tuple to be updated was already modified by an operation triggered by the current command 2025-11-30 18:45:22.498 UTC client backend[46452] isolation/eval-plan-qual/s2 HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-11-30 18:45:22.498 UTC client backend[46452] isolation/eval-plan-qual/s2 STATEMENT: WITH doup AS (UPDATE accounts SET balance = balance + 1100 WHERE accountid = 'checking' RETURNING *, update_checking(999)) UPDATE accounts a SET balance = doup.balance + 100 FROM doup RETURNING *; 2025-11-30 18:45:22.581 UTC client backend[46477] pg_regress/foreign_key ERROR: constraint "fk_partitioned_fk_a_b_fkey" enforceability conflicts with constraint "fk_part_con" on relation "fk_partitioned_fk_2" 2025-11-30 18:45:22.581 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk ATTACH PARTITION fk_partitioned_fk_2 FOR VALUES IN (1500,1502); 2025-11-30 18:45:22.591 UTC client backend[46452] isolation/eval-plan-qual/s2 ERROR: tuple to be deleted was already modified by an operation triggered by the current command 2025-11-30 18:45:22.591 UTC client backend[46452] isolation/eval-plan-qual/s2 HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-11-30 18:45:22.591 UTC client backend[46452] isolation/eval-plan-qual/s2 STATEMENT: WITH doup AS (UPDATE accounts SET balance = balance + 1100 WHERE accountid = 'checking' RETURNING *, update_checking(999)) DELETE FROM accounts a USING doup RETURNING *; 2025-11-30 18:45:22.711 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.711 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(1600, 601) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.711 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk ATTACH PARTITION fk_partitioned_fk_2 FOR VALUES IN (1600); 2025-11-30 18:45:22.722 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot attach table "fk_partitioned_pk_6" as a partition because it is referenced by foreign key "fk_partitioned_fk_6_a_fkey" 2025-11-30 18:45:22.722 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk_6 ATTACH PARTITION fk_partitioned_pk_6 FOR VALUES IN (1); 2025-11-30 18:45:22.751 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot ALTER TABLE "fk_partitioned_pk_61" because it is being used by active queries in this session 2025-11-30 18:45:22.751 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk_6 ATTACH PARTITION fk_partitioned_pk_6 FOR VALUES IN (1); 2025-11-30 18:45:22.761 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "other_partitioned_fk_1" violates foreign key constraint "other_partitioned_fk_a_b_fkey" 2025-11-30 18:45:22.761 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a, b)=(2048, 1) is not present in table "fk_notpartitioned_pk". 2025-11-30 18:45:22.761 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table other_partitioned_fk add foreign key (a, b) references fk_notpartitioned_pk(a, b); 2025-11-30 18:45:22.804 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey" 2025-11-30 18:45:22.804 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id_abc)=(5) is not present in table "parted_self_fk". 2025-11-30 18:45:22.804 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO parted_self_fk VALUES (4, 5); 2025-11-30 18:45:22.806 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey_1" on table "parted_self_fk" 2025-11-30 18:45:22.806 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id)=(1) is still referenced from table "parted_self_fk". 2025-11-30 18:45:22.806 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM parted_self_fk WHERE id = 1 RETURNING *; 2025-11-30 18:45:22.817 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "part2_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey" 2025-11-30 18:45:22.817 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id_abc)=(9) is not present in table "parted_self_fk". 2025-11-30 18:45:22.817 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO part2_self_fk VALUES (16, 9); 2025-11-30 18:45:22.819 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey_5" on table "part2_self_fk" 2025-11-30 18:45:22.819 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id)=(2) is still referenced from table "part2_self_fk". 2025-11-30 18:45:22.819 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM parted_self_fk WHERE id = 2 RETURNING *; 2025-11-30 18:45:22.826 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "part2_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey" 2025-11-30 18:45:22.826 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id_abc)=(9) is not present in table "parted_self_fk". 2025-11-30 18:45:22.826 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO parted_self_fk VALUES (16, 9); 2025-11-30 18:45:22.828 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey_1" on table "parted_self_fk" 2025-11-30 18:45:22.828 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id)=(3) is still referenced from table "parted_self_fk". 2025-11-30 18:45:22.828 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM parted_self_fk WHERE id = 3 RETURNING *; 2025-11-30 18:45:22.895 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_1_a_fkey" of relation "fk_part_1" 2025-11-30 18:45:22.895 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_1 drop constraint fk_part_1_a_fkey; 2025-11-30 18:45:22.918 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_23_a_fkey" of relation "fk_part_23" 2025-11-30 18:45:22.918 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_23 drop constraint fk_part_23_a_fkey; 2025-11-30 18:45:22.918 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_23_a_fkey" of relation "fk_part_23_2" 2025-11-30 18:45:22.918 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_23_2 drop constraint fk_part_23_a_fkey; 2025-11-30 18:45:22.931 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_a_fkey" of relation "fk_part_4" 2025-11-30 18:45:22.931 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_4 drop constraint fk_part_a_fkey; 2025-11-30 18:45:22.947 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_a_fkey" of relation "fk_part_56" 2025-11-30 18:45:22.947 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_56 drop constraint fk_part_a_fkey; 2025-11-30 18:45:22.947 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_a_fkey" of relation "fk_part_56_5" 2025-11-30 18:45:22.947 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_56_5 drop constraint fk_part_a_fkey; 2025-11-30 18:45:22.956 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_part_1_1" violates foreign key constraint "fk_part_a_fkey" 2025-11-30 18:45:22.956 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pkey". 2025-11-30 18:45:22.956 UTC client backend[46477] pg_regress/foreign_key STATEMENT: insert into fkpart1.fk_part values (1); 2025-11-30 18:45:22.959 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pkey" violates foreign key constraint "fk_part_a_fkey" on table "fk_part" 2025-11-30 18:45:22.959 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk_part". 2025-11-30 18:45:22.959 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from fkpart1.pkey where a = 1; 2025-11-30 18:45:22.963 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_part_1_2" violates foreign key constraint "fk_part_a_fkey" 2025-11-30 18:45:22.963 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(2) is not present in table "pkey". 2025-11-30 18:45:22.963 UTC client backend[46477] pg_regress/foreign_key STATEMENT: insert into fkpart1.fk_part_1 values (2); 2025-11-30 18:45:22.964 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pkey" violates foreign key constraint "fk_part_a_fkey" on table "fk_part_1" 2025-11-30 18:45:22.964 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk_part_1". 2025-11-30 18:45:22.964 UTC client backend[46477] pg_regress/foreign_key STATEMENT: delete from fkpart1.pkey where a = 1; 2025-11-30 18:45:22.974 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fkey" of relation "fk_part_1" 2025-11-30 18:45:22.974 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart2.fk_part_1 drop constraint fkey; 2025-11-30 18:45:22.974 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "my_fkey" of relation "fk_part_1_1" 2025-11-30 18:45:22.974 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart2.fk_part_1_1 drop constraint my_fkey; 2025-11-30 18:45:22.977 UTC client backend[46477] pg_regress/foreign_key ERROR: constraint "my_fkey" of relation "fk_part_1_1" does not exist 2025-11-30 18:45:22.977 UTC client backend[46477] pg_regress/foreign_key STATEMENT: alter table fkpart2.fk_part_1_1 drop constraint my_fkey; 2025-11-30 18:45:23.059 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk1" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.059 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pk". 2025-11-30 18:45:23.059 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (1); 2025-11-30 18:45:23.060 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk2" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.060 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1000) is not present in table "pk". 2025-11-30 18:45:23.060 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (1000); 2025-11-30 18:45:23.061 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk2" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.061 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(2000) is not present in table "pk". 2025-11-30 18:45:23.061 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (2000); 2025-11-30 18:45:23.061 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk2" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.061 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(3000) is not present in table "pk". 2025-11-30 18:45:23.061 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (3000); 2025-11-30 18:45:23.062 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk3" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.062 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(4000) is not present in table "pk". 2025-11-30 18:45:23.062 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (4000); 2025-11-30 18:45:23.064 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk3" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.064 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(4500) is not present in table "pk". 2025-11-30 18:45:23.064 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (4500); 2025-11-30 18:45:23.070 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk1" violates foreign key constraint "fk_a_fkey_1" on table "fk" 2025-11-30 18:45:23.070 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk". 2025-11-30 18:45:23.070 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 1; 2025-11-30 18:45:23.071 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk2" violates foreign key constraint "fk_a_fkey_2" on table "fk" 2025-11-30 18:45:23.071 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "fk". 2025-11-30 18:45:23.071 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 1000; 2025-11-30 18:45:23.072 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk3" violates foreign key constraint "fk_a_fkey_3" on table "fk" 2025-11-30 18:45:23.072 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(2000) is still referenced from table "fk". 2025-11-30 18:45:23.072 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 2000; 2025-11-30 18:45:23.073 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk4" violates foreign key constraint "fk_a_fkey_4" on table "fk" 2025-11-30 18:45:23.073 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(3000) is still referenced from table "fk". 2025-11-30 18:45:23.073 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 3000; 2025-11-30 18:45:23.075 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk51" violates foreign key constraint "fk_a_fkey_6" on table "fk" 2025-11-30 18:45:23.075 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(4000) is still referenced from table "fk". 2025-11-30 18:45:23.075 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 4000; 2025-11-30 18:45:23.076 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk52" violates foreign key constraint "fk_a_fkey_7" on table "fk" 2025-11-30 18:45:23.076 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(4500) is still referenced from table "fk". 2025-11-30 18:45:23.076 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 4500; 2025-11-30 18:45:23.077 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk1" violates foreign key constraint "fk_a_fkey_1" on table "fk" 2025-11-30 18:45:23.077 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk". 2025-11-30 18:45:23.077 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 2 WHERE a = 1; 2025-11-30 18:45:23.079 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk2" violates foreign key constraint "fk_a_fkey_2" on table "fk" 2025-11-30 18:45:23.079 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "fk". 2025-11-30 18:45:23.079 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 1002 WHERE a = 1000; 2025-11-30 18:45:23.080 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk3" violates foreign key constraint "fk_a_fkey_3" on table "fk" 2025-11-30 18:45:23.080 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(2000) is still referenced from table "fk". 2025-11-30 18:45:23.080 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 2002 WHERE a = 2000; 2025-11-30 18:45:23.081 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk4" violates foreign key constraint "fk_a_fkey_4" on table "fk" 2025-11-30 18:45:23.081 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(3000) is still referenced from table "fk". 2025-11-30 18:45:23.081 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 3002 WHERE a = 3000; 2025-11-30 18:45:23.082 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk51" violates foreign key constraint "fk_a_fkey_6" on table "fk" 2025-11-30 18:45:23.082 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(4000) is still referenced from table "fk". 2025-11-30 18:45:23.082 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 4002 WHERE a = 4000; 2025-11-30 18:45:23.084 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk52" violates foreign key constraint "fk_a_fkey_7" on table "fk" 2025-11-30 18:45:23.084 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(4500) is still referenced from table "fk". 2025-11-30 18:45:23.084 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 4502 WHERE a = 4500; 2025-11-30 18:45:23.172 UTC client backend[46477] pg_regress/foreign_key ERROR: removing partition "droppk_d" violates foreign key constraint "dropfk_a_fkey_5" 2025-11-30 18:45:23.172 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(2000) is still referenced from table "dropfk". 2025-11-30 18:45:23.172 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk DETACH PARTITION droppk_d; 2025-11-30 18:45:23.173 UTC client backend[46477] pg_regress/foreign_key ERROR: removing partition "droppk2_d" violates foreign key constraint "dropfk_a_fkey_4" 2025-11-30 18:45:23.173 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1500) is still referenced from table "dropfk". 2025-11-30 18:45:23.173 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk2 DETACH PARTITION droppk2_d; 2025-11-30 18:45:23.174 UTC client backend[46477] pg_regress/foreign_key ERROR: removing partition "droppk1" violates foreign key constraint "dropfk_a_fkey_1" 2025-11-30 18:45:23.174 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "dropfk". 2025-11-30 18:45:23.174 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk DETACH PARTITION droppk1; 2025-11-30 18:45:23.175 UTC client backend[46477] pg_regress/foreign_key ERROR: removing partition "droppk2" violates foreign key constraint "dropfk_a_fkey_2" 2025-11-30 18:45:23.175 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "dropfk". 2025-11-30 18:45:23.175 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk DETACH PARTITION droppk2; 2025-11-30 18:45:23.176 UTC client backend[46477] pg_regress/foreign_key ERROR: removing partition "droppk21" violates foreign key constraint "dropfk_a_fkey_3" 2025-11-30 18:45:23.176 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "dropfk". 2025-11-30 18:45:23.176 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk2 DETACH PARTITION droppk21; 2025-11-30 18:45:23.178 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk_d because other objects depend on it 2025-11-30 18:45:23.178 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk_d 2025-11-30 18:45:23.178 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.178 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk_d; 2025-11-30 18:45:23.179 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk2_d because other objects depend on it 2025-11-30 18:45:23.179 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2_d 2025-11-30 18:45:23.179 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.179 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2_d; 2025-11-30 18:45:23.180 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk1 because other objects depend on it 2025-11-30 18:45:23.180 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk1 2025-11-30 18:45:23.180 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.180 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk1; 2025-11-30 18:45:23.182 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk2 because other objects depend on it 2025-11-30 18:45:23.182 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2 2025-11-30 18:45:23.182 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.182 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2; 2025-11-30 18:45:23.183 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk21 because other objects depend on it 2025-11-30 18:45:23.183 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk21 2025-11-30 18:45:23.183 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.183 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk21; 2025-11-30 18:45:23.185 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk_d because other objects depend on it 2025-11-30 18:45:23.185 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk_d 2025-11-30 18:45:23.185 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.185 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk_d; 2025-11-30 18:45:23.186 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk2_d because other objects depend on it 2025-11-30 18:45:23.186 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2_d 2025-11-30 18:45:23.186 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.186 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2_d; 2025-11-30 18:45:23.187 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk1 because other objects depend on it 2025-11-30 18:45:23.187 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk1 2025-11-30 18:45:23.187 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.187 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk1; 2025-11-30 18:45:23.191 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop table droppk2 because other objects depend on it 2025-11-30 18:45:23.191 UTC client backend[46477] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2 2025-11-30 18:45:23.191 UTC client backend[46477] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:23.191 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2; 2025-11-30 18:45:23.236 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk4" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.236 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(50) is not present in table "pk". 2025-11-30 18:45:23.236 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk ATTACH PARTITION fk4 FOR VALUES IN (50); 2025-11-30 18:45:23.252 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.252 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pk". 2025-11-30 18:45:23.252 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk VALUES (1); 2025-11-30 18:45:23.254 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk" violates foreign key constraint "fk_a_fkey" 2025-11-30 18:45:23.254 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pk". 2025-11-30 18:45:23.254 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:23.293 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot alter constraint "ref_f1_f2_fkey" on relation "ref22" 2025-11-30 18:45:23.293 UTC client backend[46477] pg_regress/foreign_key DETAIL: Constraint "ref_f1_f2_fkey" is derived from constraint "ref_f1_f2_fkey" of relation "ref". 2025-11-30 18:45:23.293 UTC client backend[46477] pg_regress/foreign_key HINT: You may alter the constraint it derives from instead. 2025-11-30 18:45:23.293 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE ref22 ALTER CONSTRAINT ref_f1_f2_fkey DEFERRABLE INITIALLY IMMEDIATE; 2025-11-30 18:45:23.347 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot alter constraint "ref_f1_f2_fkey_1" on relation "ref" 2025-11-30 18:45:23.347 UTC client backend[46477] pg_regress/foreign_key DETAIL: Constraint "ref_f1_f2_fkey_1" is derived from constraint "ref_f1_f2_fkey" of relation "ref". 2025-11-30 18:45:23.347 UTC client backend[46477] pg_regress/foreign_key HINT: You may alter the constraint it derives from instead. 2025-11-30 18:45:23.347 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE ref ALTER CONSTRAINT ref_f1_f2_fkey_1 DEFERRABLE INITIALLY DEFERRED; 2025-11-30 18:45:23.502 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk11" violates RESTRICT setting of foreign key constraint "fk_a_fkey_2" on table "fk" 2025-11-30 18:45:23.502 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(20) is referenced from table "fk". 2025-11-30 18:45:23.502 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 20; 2025-11-30 18:45:23.503 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "pk" violates RESTRICT setting of foreign key constraint "fk_a_fkey" on table "fk" 2025-11-30 18:45:23.503 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (a)=(30) is referenced from table "fk". 2025-11-30 18:45:23.503 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 90 WHERE a = 30; 2025-11-30 18:45:23.535 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot ALTER TABLE "tbl2_p1" because it has pending trigger events 2025-11-30 18:45:23.535 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fkpart8.tbl2 DROP CONSTRAINT tbl2_f1_fkey; 2025-11-30 18:45:23.592 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "tbl1" violates foreign key constraint "tbl2_f1_fkey" on table "tbl2" 2025-11-30 18:45:23.592 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(0) is still referenced from table "tbl2". 2025-11-30 18:45:23.592 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:23.597 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "tbl3" violates foreign key constraint "tbl4_f1_fkey" on table "tbl4" 2025-11-30 18:45:23.597 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(-2) is still referenced from table "tbl4". 2025-11-30 18:45:23.597 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:23.609 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "tbl3" violates foreign key constraint "tbl5_f1_fkey" on table "tbl5" 2025-11-30 18:45:23.609 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(-2) is still referenced from table "tbl5". 2025-11-30 18:45:23.609 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE fkpart10.tbl3 SET f1 = f1 * -3; 2025-11-30 18:45:23.613 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "tbl3" violates foreign key constraint "tbl4_f1_fkey" on table "tbl4" 2025-11-30 18:45:23.613 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (f1)=(-2) is still referenced from table "tbl4". 2025-11-30 18:45:23.613 UTC client backend[46477] pg_regress/foreign_key STATEMENT: COMMIT; 2025-11-30 18:45:23.699 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot move tuple across partitions when a non-root ancestor of the source partition is directly referenced in a foreign key 2025-11-30 18:45:23.699 UTC client backend[46477] pg_regress/foreign_key DETAIL: A foreign key points to ancestor "pk1" but not the root ancestor "pk". 2025-11-30 18:45:23.699 UTC client backend[46477] pg_regress/foreign_key HINT: Consider defining the foreign key on table "pk". 2025-11-30 18:45:23.699 UTC client backend[46477] pg_regress/foreign_key STATEMENT: UPDATE fkpart11.pk SET a = a - 1; 2025-11-30 18:45:23.714 UTC client backend[46452] isolation/eval-plan-qual/s2 ERROR: tuple to be locked was already moved to another partition due to concurrent update 2025-11-30 18:45:23.714 UTC client backend[46452] isolation/eval-plan-qual/s2 STATEMENT: with u as (update another_parttbl set a = 1 returning another_parttbl.*) update parttbl p set a = u.a from u where p.a = u.a and p.c = 1 returning p.*; 2025-11-30 18:45:23.836 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_r_2_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey" 2025-11-30 18:45:23.836 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (p_id, p_jd)=(2, 1) is not present in table "fk_p". 2025-11-30 18:45:23.836 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_r VALUES (2, 2, 1); 2025-11-30 18:45:23.865 UTC client backend[46477] pg_regress/foreign_key ERROR: insert or update on table "fk_r_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey" 2025-11-30 18:45:23.865 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (p_id, p_jd)=(1, 2) is not present in table "fk_p". 2025-11-30 18:45:23.865 UTC client backend[46477] pg_regress/foreign_key STATEMENT: INSERT INTO fk_r_1 (id, p_id, p_jd) VALUES (2, 1, 2); 2025-11-30 18:45:23.868 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "fk_p_1_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey_7" on table "fk_r_1" 2025-11-30 18:45:23.868 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id, jd)=(1, 1) is still referenced from table "fk_r_1". 2025-11-30 18:45:23.868 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM fk_p; 2025-11-30 18:45:23.896 UTC client backend[46477] pg_regress/foreign_key ERROR: update or delete on table "fk_p_1_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey_2" on table "fk_r" 2025-11-30 18:45:23.896 UTC client backend[46477] pg_regress/foreign_key DETAIL: Key (id, jd)=(1, 1) is still referenced from table "fk_r". 2025-11-30 18:45:23.896 UTC client backend[46477] pg_regress/foreign_key STATEMENT: DELETE FROM fk_p; 2025-11-30 18:45:23.897 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_r_p_id_p_jd_fkey" of relation "fk_r_1" 2025-11-30 18:45:23.897 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_r_1 DROP CONSTRAINT fk_r_p_id_p_jd_fkey; 2025-11-30 18:45:23.897 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_r_p_id_p_jd_fkey_1" of relation "fk_r" 2025-11-30 18:45:23.897 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_r DROP CONSTRAINT fk_r_p_id_p_jd_fkey_1; 2025-11-30 18:45:23.897 UTC client backend[46477] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_r_p_id_p_jd_fkey" of relation "fk_r_2" 2025-11-30 18:45:23.897 UTC client backend[46477] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_r_2 DROP CONSTRAINT fk_r_p_id_p_jd_fkey; 2025-11-30 18:45:23.976 UTC client backend[46477] pg_regress/foreign_key LOG: disconnection: session time: 0:00:02.679 user=postgres database=regression host=[local] 2025-11-30 18:45:23.984 UTC unrecognized[46522] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.984 UTC client backend[46522] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.984 UTC client backend[46522] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/json 2025-11-30 18:45:23.985 UTC client backend[46522] pg_regress/json LOG: connection ready: setup total=3.807 ms, fork=2.148 ms, authentication=0.136 ms 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json DETAIL: Token "'" is invalid. 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: '... 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json STATEMENT: SELECT $$''$$::json; 2025-11-30 18:45:23.986 UTC unrecognized[46523] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json DETAIL: Token ""abc" is invalid. 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: "abc 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '"abc'::json; 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json DETAIL: Character with value 0x0a must be escaped. 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: "abc 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '"abc def"'::json; 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json DETAIL: Escape sequence "\v" is invalid. 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: "\v... 2025-11-30 18:45:23.986 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '"\v"'::json; 2025-11-30 18:45:23.986 UTC client backend[46523] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.986 UTC client backend[46523] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonb 2025-11-30 18:45:23.987 UTC client backend[46523] pg_regress/jsonb LOG: connection ready: setup total=4.976 ms, fork=3.176 ms, authentication=0.115 ms 2025-11-30 18:45:23.987 UTC unrecognized[46525] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.987 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.987 UTC client backend[46522] pg_regress/json DETAIL: Token "01" is invalid. 2025-11-30 18:45:23.987 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: 01 2025-11-30 18:45:23.987 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '01'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Token "1f2" is invalid. 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: 1f2 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '1f2'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Token "0.x1" is invalid. 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: 0.x1 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '0.x1'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Token "1.3ex100" is invalid. 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: 1.3ex100 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '1.3ex100'::json; 2025-11-30 18:45:23.988 UTC client backend[46525] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.988 UTC client backend[46525] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/json_encoding 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Expected JSON value, but found "]". 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: [1,2,] 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '[1,2,]'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: [1,2 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '[1,2'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: [1,[2] 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '[1,[2]'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Expected ":", but found "}". 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: {"abc"} 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{"abc"}'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Expected string or "}", but found "1". 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: {1... 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{1:"abc"}'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Expected ":", but found ",". 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: {"abc",... 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{"abc",1}'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Token "=" is invalid. 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: {"abc"=... 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{"abc"=1}'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Expected JSON value, but found ":". 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: {"abc"::... 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{"abc"::1}'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Expected "," or "}", but found ":". 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: {"abc":1:... 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{"abc":1:2}'::json; 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json DETAIL: Expected string, but found "3". 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: {"abc":1,3... 2025-11-30 18:45:23.988 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{"abc":1,3}'::json; 2025-11-30 18:45:23.988 UTC client backend[46525] pg_regress/json_encoding LOG: connection ready: setup total=5.497 ms, fork=2.566 ms, authentication=0.105 ms 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: stack depth limit exceeded 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT repeat('[', 10000)::json; 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: stack depth limit exceeded 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT repeat('{"a":', 10000)::json; 2025-11-30 18:45:23.989 UTC unrecognized[46526] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.989 UTC unrecognized[46528] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.989 UTC client backend[46526] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.989 UTC client backend[46526] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonb_jsonpath 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json DETAIL: Expected end of input, but found "false". 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: true false 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT 'true false'::json; 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json DETAIL: Expected end of input, but found ",". 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: true,... 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT 'true, false'::json; 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json DETAIL: Token "truf" is invalid. 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: truf 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT 'truf'::json; 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json DETAIL: Token "trues" is invalid. 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: trues 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT 'trues'::json; 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ''::json; 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 1: 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ' '::json; 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json DETAIL: Expected JSON value, but found ",". 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 3: "two":,... 2025-11-30 18:45:23.989 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{ "one": 1, "two":,"two", -- ERROR extraneous comma before field "two" "three": true}'::json; 2025-11-30 18:45:23.990 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.990 UTC client backend[46522] pg_regress/json DETAIL: Expected JSON value, but found "}". 2025-11-30 18:45:23.990 UTC client backend[46522] pg_regress/json CONTEXT: JSON data, line 4: ...yveryveryveryveryveryveryveryverylongfieldname":} 2025-11-30 18:45:23.990 UTC client backend[46522] pg_regress/json STATEMENT: SELECT '{ "one": 1, "two":"two", "averyveryveryveryveryveryveryveryveryverylongfieldname":}'::json; 2025-11-30 18:45:23.990 UTC client backend[46526] pg_regress/jsonb_jsonpath LOG: connection ready: setup total=5.017 ms, fork=0.711 ms, authentication=0.102 ms 2025-11-30 18:45:23.990 UTC client backend[46528] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.990 UTC client backend[46528] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sqljson_jsontable 2025-11-30 18:45:23.991 UTC unrecognized[46527] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.991 UTC client backend[46528] pg_regress/sqljson_jsontable LOG: connection ready: setup total=2.905 ms, fork=0.498 ms, authentication=0.111 ms 2025-11-30 18:45:23.991 UTC unrecognized[46524] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.992 UTC client backend[46527] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.992 UTC client backend[46527] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sqljson 2025-11-30 18:45:23.992 UTC unrecognized[46530] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.992 UTC client backend[46524] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.992 UTC client backend[46524] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonpath 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: syntax error at or near "(" at character 18 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT JSON_TABLE('[]', '$'); 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior at character 72 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause. 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') DEFAULT 1 ON ERROR); 2025-11-30 18:45:23.993 UTC unrecognized[46529] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior at character 72 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause. 2025-11-30 18:45:23.993 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') NULL ON ERROR); 2025-11-30 18:45:23.993 UTC client backend[46527] pg_regress/sqljson LOG: connection ready: setup total=7.672 ms, fork=4.663 ms, authentication=0.155 ms 2025-11-30 18:45:23.993 UTC client backend[46529] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.993 UTC client backend[46529] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sqljson_queryfuncs 2025-11-30 18:45:23.994 UTC client backend[46530] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:23.994 UTC client backend[46530] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonpath_encoding 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') ERROR ON ERROR); 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: js2 at character 63 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb'"1.23"', '$.a' as js2 COLUMNS (js2 int path '$')); 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: syntax error at or near ")" at character 45 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(NULL, '$' COLUMNS ()); 2025-11-30 18:45:23.994 UTC client backend[46529] pg_regress/sqljson_queryfuncs LOG: connection ready: setup total=4.734 ms, fork=3.097 ms, authentication=0.127 ms 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: JSON_TABLE function has 1 columns available but 2 columns specified 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE (NULL::jsonb, '$' COLUMNS (v1 timestamp)) AS f (v1, v2); 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: js2 at character 74 2025-11-30 18:45:23.994 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb'"1.23"', '$.a' COLUMNS (js2 int path '$', js2 int path '$')); 2025-11-30 18:45:23.995 UTC client backend[46530] pg_regress/jsonpath_encoding LOG: connection ready: setup total=4.146 ms, fork=0.979 ms, authentication=0.138 ms 2025-11-30 18:45:23.996 UTC client backend[46524] pg_regress/jsonpath LOG: connection ready: setup total=13.029 ms, fork=6.101 ms, authentication=0.115 ms 2025-11-30 18:45:23.996 UTC client backend[46527] pg_regress/sqljson ERROR: syntax error at or near ")" at character 13 2025-11-30 18:45:23.996 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON(); 2025-11-30 18:45:23.997 UTC client backend[46524] pg_regress/jsonpath ERROR: invalid input syntax for type jsonpath: "" at character 8 2025-11-30 18:45:23.997 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select ''::jsonpath; 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u" of jsonpath input at character 8 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u"'::jsonpath; 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u00" of jsonpath input at character 8 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u00"'::jsonpath; 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u000" of jsonpath input at character 8 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u000g"'::jsonpath; 2025-11-30 18:45:23.998 UTC client backend[46527] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 28 2025-11-30 18:45:23.998 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON('{ "a" : 1 } ' FORMAT JSON ENCODING UTF8); 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:23.998 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u0000"'::jsonpath; 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u" 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT '"\u"'::json; 2025-11-30 18:45:23.999 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:23.999 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-11-30 18:45:23.999 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '"\ud83d\ud83d"'::jsonpath; 2025-11-30 18:45:23.999 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.999 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "'" is invalid. 2025-11-30 18:45:23.999 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: '... 2025-11-30 18:45:23.999 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT $$''$$::jsonb; 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u00" 2025-11-30 18:45:23.999 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT '"\u00"'::json; 2025-11-30 18:45:23.999 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:23.999 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:23.999 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '"\ude04\ud83d"'::jsonpath; 2025-11-30 18:45:24.000 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.000 UTC client backend[46525] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-11-30 18:45:24.000 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u000g... 2025-11-30 18:45:24.000 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT '"\u000g"'::json; 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb DETAIL: Token ""abc" is invalid. 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: "abc 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '"abc'::jsonb; 2025-11-30 18:45:24.000 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:24.000 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.000 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '"\ud83dX"'::jsonpath; 2025-11-30 18:45:24.000 UTC client backend[46527] pg_regress/sqljson ERROR: cannot use non-string types with WITH UNIQUE KEYS clause at character 8 2025-11-30 18:45:24.000 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON(' 1 '::json WITH UNIQUE KEYS); 2025-11-30 18:45:24.000 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:24.000 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.000 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '"\ude04X"'::jsonpath; 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb DETAIL: Character with value 0x0a must be escaped. 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: "abc 2025-11-30 18:45:24.000 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '"abc def"'::jsonb; 2025-11-30 18:45:24.000 UTC client backend[46527] pg_regress/sqljson ERROR: cannot cast type integer to json at character 13 2025-11-30 18:45:24.000 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON(123); 2025-11-30 18:45:24.000 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:24.000 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_EXISTS(jsonb '1', 'strict $.a' ERROR ON ERROR); 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '"null \u0000 escape"'::jsonpath as not_unescaped; 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83d\ud83d... 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ud83d\ud83d" }' -> 'a'; 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb DETAIL: Escape sequence "\v" is invalid. 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: "\v... 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '"\v"'::jsonb; 2025-11-30 18:45:24.001 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-11-30 18:45:24.001 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON('{"a": 1, "a": 2}' WITH UNIQUE KEYS); 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ude04\ud83d" }' -> 'a'; 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u" of jsonpath input at character 8 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u"'::jsonpath; 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u00" of jsonpath input at character 8 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u00"'::jsonpath; 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83dX... 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ud83dX" }' -> 'a'; 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "01" is invalid. 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: 01 2025-11-30 18:45:24.001 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '01'::jsonb; 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u000" of jsonpath input at character 8 2025-11-30 18:45:24.001 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u000g"'::jsonpath; 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-11-30 18:45:24.001 UTC client backend[46525] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ude04X" }' -> 'a'; 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u0000"'::jsonpath; 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '$."\ud83d\ud83d"'::jsonpath; 2025-11-30 18:45:24.002 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.002 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "1f2" is invalid. 2025-11-30 18:45:24.002 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: 1f2 2025-11-30 18:45:24.002 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '1f2'::jsonb; 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.002 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '$."\ude04\ud83d"'::jsonpath; 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '$."\ud83dX"'::jsonpath; 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "0.x1" is invalid. 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: 0.x1 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '0.x1'::jsonb; 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '$."\ude04X"'::jsonpath; 2025-11-30 18:45:24.003 UTC client backend[46527] pg_regress/sqljson ERROR: syntax error at or near ")" at character 20 2025-11-30 18:45:24.003 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_SCALAR(); 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "1.3ex100" is invalid. 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: 1.3ex100 2025-11-30 18:45:24.003 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '1.3ex100'::jsonb; 2025-11-30 18:45:24.003 UTC client backend[46525] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence 2025-11-30 18:45:24.003 UTC client backend[46525] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:24.003 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "null \u0000... 2025-11-30 18:45:24.003 UTC client backend[46525] pg_regress/json_encoding STATEMENT: select json '{ "a": "null \u0000 escape" }' ->> 'a' as fails; 2025-11-30 18:45:24.003 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of bounds 2025-11-30 18:45:24.003 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1]', 'strict $[1]'); 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:24.003 UTC client backend[46530] pg_regress/jsonpath_encoding STATEMENT: select '$."null \u0000 escape"'::jsonpath as not_unescaped; 2025-11-30 18:45:24.004 UTC client backend[46530] pg_regress/jsonpath_encoding LOG: disconnection: session time: 0:00:00.012 user=postgres database=regression host=[local] 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u" 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT '"\u"'::jsonb; 2025-11-30 18:45:24.004 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.004 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected JSON value, but found "]". 2025-11-30 18:45:24.004 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: [1,2,] 2025-11-30 18:45:24.004 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '[1,2,]'::jsonb; 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u00" 2025-11-30 18:45:24.004 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT '"\u00"'::jsonb; 2025-11-30 18:45:24.004 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: could not coerce ON EMPTY expression (DEFAULT) to the RETURNING type 2025-11-30 18:45:24.004 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: value for domain jsonb_test_domain violates check constraint "jsonb_test_domain_check" 2025-11-30 18:45:24.004 UTC client backend[46528] 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-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: [1,2 2025-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '[1,2'::jsonb; 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u000g... 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT '"\u000g"'::jsonb; 2025-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: [1,[2] 2025-11-30 18:45:24.005 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '[1,[2]'::jsonb; 2025-11-30 18:45:24.005 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of integer range 2025-11-30 18:45:24.005 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1]', 'lax $[10000000000000000]'); 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u0000... 2025-11-30 18:45:24.005 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT '"\u0000"'::jsonb; 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected ":", but found "}". 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc"} 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{"abc"}'::jsonb; 2025-11-30 18:45:24.006 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "1.23" 2025-11-30 18:45:24.006 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"1.23"', '$' RETURNING int ERROR ON ERROR); 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected string or "}", but found "1". 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: {1... 2025-11-30 18:45:24.006 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{1:"abc"}'::jsonb; 2025-11-30 18:45:24.006 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-11-30 18:45:24.006 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-11-30 18:45:24.006 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83d\ud83d... 2025-11-30 18:45:24.006 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ud83d\ud83d" }' -> 'a'; 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected ":", but found ",". 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc",... 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{"abc",1}'::jsonb; 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ude04\ud83d" }' -> 'a'; 2025-11-30 18:45:24.007 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-11-30 18:45:24.007 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING char(2) ERROR ON ERROR); 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "=" is invalid. 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc"=... 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{"abc"=1}'::jsonb; 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83dX... 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ud83dX" }' -> 'a'; 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected JSON value, but found ":". 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc"::... 2025-11-30 18:45:24.007 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{"abc"::1}'::jsonb; 2025-11-30 18:45:24.007 UTC client backend[46527] pg_regress/sqljson ERROR: syntax error at or near ")" at character 23 2025-11-30 18:45:24.007 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE(); 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-11-30 18:45:24.007 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ude04X" }' -> 'a'; 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected "," or "}", but found ":". 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc":1:... 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{"abc":1:2}'::jsonb; 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected string, but found "3". 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc":1,3... 2025-11-30 18:45:24.008 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{"abc":1,3}'::jsonb; 2025-11-30 18:45:24.008 UTC client backend[46525] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence at character 14 2025-11-30 18:45:24.008 UTC client backend[46525] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:24.008 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "null \u0000... 2025-11-30 18:45:24.008 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "null \u0000 escape" }' as fails; 2025-11-30 18:45:24.009 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of integer range 2025-11-30 18:45:24.009 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1]', 'strict $[10000000000000000]'); 2025-11-30 18:45:24.009 UTC client backend[46527] pg_regress/sqljson ERROR: cannot use type jsonb in RETURNING clause of JSON_SERIALIZE() 2025-11-30 18:45:24.009 UTC client backend[46527] pg_regress/sqljson HINT: Try returning a string type or bytea. 2025-11-30 18:45:24.009 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('{ "a" : 1 } ' RETURNING jsonb); 2025-11-30 18:45:24.009 UTC client backend[46524] pg_regress/jsonpath ERROR: LAST is allowed only in array subscripts at character 8 2025-11-30 18:45:24.009 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select 'last'::jsonpath; 2025-11-30 18:45:24.009 UTC client backend[46523] pg_regress/jsonb ERROR: stack depth limit exceeded 2025-11-30 18:45:24.009 UTC client backend[46523] pg_regress/jsonb HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-11-30 18:45:24.009 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT repeat('[', 10000)::jsonb; 2025-11-30 18:45:24.009 UTC client backend[46524] pg_regress/jsonpath ERROR: LAST is allowed only in array subscripts at character 8 2025-11-30 18:45:24.009 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '$ ? (last > 0)'::jsonpath; 2025-11-30 18:45:24.009 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "aaa" 2025-11-30 18:45:24.009 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING int ERROR ON ERROR); 2025-11-30 18:45:24.010 UTC client backend[46523] pg_regress/jsonb ERROR: stack depth limit exceeded 2025-11-30 18:45:24.010 UTC client backend[46523] pg_regress/jsonb HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-11-30 18:45:24.010 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT repeat('{"a":', 10000)::jsonb; 2025-11-30 18:45:24.010 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1.t" of jsonpath input at character 8 2025-11-30 18:45:24.010 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1.type()'::jsonpath; 2025-11-30 18:45:24.010 UTC client backend[46527] pg_regress/sqljson ERROR: cannot set JSON encoding for non-bytea output types at character 35 2025-11-30 18:45:24.010 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING text FORMAT JSON ENCODING UTF8); 2025-11-30 18:45:24.010 UTC client backend[46525] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence at character 14 2025-11-30 18:45:24.010 UTC client backend[46525] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-11-30 18:45:24.010 UTC client backend[46525] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "null \u0000... 2025-11-30 18:45:24.010 UTC client backend[46525] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "null \u0000 escape" }' ->> 'a' as fails; 2025-11-30 18:45:24.010 UTC client backend[46527] pg_regress/sqljson ERROR: unrecognized JSON encoding: invalid_encoding at character 56 2025-11-30 18:45:24.010 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING text FORMAT JSON ENCODING INVALID_ENCODING); 2025-11-30 18:45:24.010 UTC client backend[46527] pg_regress/sqljson ERROR: unsupported JSON encoding at character 36 2025-11-30 18:45:24.010 UTC client backend[46527] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-11-30 18:45:24.010 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING bytea FORMAT JSON ENCODING UTF16); 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson ERROR: unsupported JSON encoding at character 36 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING bytea FORMAT JSON ENCODING UTF32); 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson ERROR: cannot use non-string types with explicit FORMAT JSON clause at character 37 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::int FORMAT JSON); 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 37 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::int FORMAT JSON ENCODING UTF8); 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 38 2025-11-30 18:45:24.011 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::json FORMAT JSON ENCODING UTF8); 2025-11-30 18:45:24.011 UTC client backend[46522] pg_regress/json ERROR: cannot call json_object_keys on a scalar 2025-11-30 18:45:24.011 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_object_keys(test_json) FROM test_json WHERE json_type = 'scalar'; 2025-11-30 18:45:24.012 UTC client backend[46527] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 39 2025-11-30 18:45:24.012 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::jsonb FORMAT JSON ENCODING UTF8); 2025-11-30 18:45:24.012 UTC client backend[46522] pg_regress/json ERROR: cannot call json_object_keys on an array 2025-11-30 18:45:24.012 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_object_keys(test_json) FROM test_json WHERE json_type = 'array'; 2025-11-30 18:45:24.012 UTC client backend[46527] pg_regress/sqljson ERROR: null value not allowed for object key 2025-11-30 18:45:24.012 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(NULL: 1); 2025-11-30 18:45:24.012 UTC client backend[46524] pg_regress/jsonpath ERROR: invalid regular expression: parentheses () not balanced at character 8 2025-11-30 18:45:24.012 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '$ ? (@ like_regex "(invalid pattern")'::jsonpath; 2025-11-30 18:45:24.012 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (NULL) to the RETURNING type 2025-11-30 18:45:24.012 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: domain sqljsonb_int_not_null does not allow null values 2025-11-30 18:45:24.012 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null); 2025-11-30 18:45:24.012 UTC client backend[46525] pg_regress/json_encoding LOG: disconnection: session time: 0:00:00.026 user=postgres database=regression host=[local] 2025-11-30 18:45:24.014 UTC client backend[46524] pg_regress/jsonpath ERROR: XQuery "x" flag (expanded regular expressions) is not implemented at character 8 2025-11-30 18:45:24.014 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '$ ? (@ like_regex "pattern" flag "xsms")'::jsonpath; 2025-11-30 18:45:24.014 UTC client backend[46527] pg_regress/sqljson ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.014 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(json '[1]': 123); 2025-11-30 18:45:24.014 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: domain sqljsonb_int_not_null does not allow null values 2025-11-30 18:45:24.014 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null ERROR ON ERROR); 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected end of input, but found "false". 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: true false 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT 'true false'::jsonb; 2025-11-30 18:45:24.014 UTC client backend[46527] pg_regress/sqljson ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.014 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(ARRAY[1,2,3]: 'aaa'); 2025-11-30 18:45:24.014 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: domain sqljsonb_int_not_null does not allow null values 2025-11-30 18:45:24.014 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null DEFAULT 2 ON EMPTY ERROR ON ERROR); 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected end of input, but found ",". 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: true,... 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT 'true, false'::jsonb; 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "truf" is invalid. 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: truf 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT 'truf'::jsonb; 2025-11-30 18:45:24.014 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: domain sqljsonb_int_not_null does not allow null values 2025-11-30 18:45:24.014 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', '$.a' RETURNING sqljsonb_int_not_null DEFAULT NULL ON EMPTY ERROR ON ERROR); 2025-11-30 18:45:24.014 UTC client backend[46524] pg_regress/jsonpath ERROR: invalid input syntax for type jsonpath at character 8 2025-11-30 18:45:24.014 UTC client backend[46524] pg_regress/jsonpath DETAIL: Unrecognized flag character "a" in LIKE_REGEX predicate. 2025-11-30 18:45:24.014 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '$ ? (@ like_regex "pattern" flag "a")'::jsonpath; 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb DETAIL: Token "trues" is invalid. 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: trues 2025-11-30 18:45:24.014 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT 'trues'::jsonb; 2025-11-30 18:45:24.015 UTC client backend[46524] pg_regress/jsonpath ERROR: @ is not allowed in root expressions at character 8 2025-11-30 18:45:24.015 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '@ + 1'::jsonpath; 2025-11-30 18:45:24.015 UTC client backend[46522] pg_regress/json ERROR: cannot get array length of a non-array 2025-11-30 18:45:24.015 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_array_length('{"f1":1,"f2":[5,6]}'); 2025-11-30 18:45:24.015 UTC client backend[46522] pg_regress/json ERROR: cannot get array length of a scalar 2025-11-30 18:45:24.015 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_array_length('4'); 2025-11-30 18:45:24.015 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "2" 2025-11-30 18:45:24.015 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '3': 1, repeat('x', 1000): 1, 2: repeat('a', 100) WITH UNIQUE); 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL WITH UNIQUE); 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL ABSENT ON NULL WITH UNIQUE); 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL NULL ON NULL WITH UNIQUE RETURNING jsonb); 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL ABSENT ON NULL WITH UNIQUE RETURNING jsonb); 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.016 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 NULL ON NULL WITH UNIQUE); 2025-11-30 18:45:24.017 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.017 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 ABSENT ON NULL WITH UNIQUE); 2025-11-30 18:45:24.017 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-11-30 18:45:24.017 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 ABSENT ON NULL WITH UNIQUE RETURNING jsonb); 2025-11-30 18:45:24.017 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.017 UTC client backend[46523] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:24.017 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: 2025-11-30 18:45:24.017 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ''::jsonb; 2025-11-30 18:45:24.018 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: value for domain rgb violates check constraint "rgb_check" 2025-11-30 18:45:24.018 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE('"purple"'::jsonb, 'lax $[*]' RETURNING rgb ERROR ON ERROR); 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 1: 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ' '::jsonb; 2025-11-30 18:45:24.018 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_VALUE must return single scalar item 2025-11-30 18:45:24.018 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '[]', '$' ERROR ON ERROR); 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected JSON value, but found ",". 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 3: "two":,... 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{ "one": 1, "two":,"two", -- ERROR extraneous comma before field "two" "three": true}'::jsonb; 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb DETAIL: Expected JSON value, but found "}". 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb CONTEXT: JSON data, line 4: ...yveryveryveryveryveryveryveryverylongfieldname":} 2025-11-30 18:45:24.018 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT '{ "one": 1, "two":"two", "averyveryveryveryveryveryveryveryveryverylongfieldname":}'::jsonb; 2025-11-30 18:45:24.018 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_VALUE must return single scalar item 2025-11-30 18:45:24.018 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '{}', '$' ERROR ON ERROR); 2025-11-30 18:45:24.019 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:24.019 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', 'strict $.a' ERROR ON ERROR); 2025-11-30 18:45:24.021 UTC client backend[46527] pg_regress/sqljson ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.021 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('happy'::mood: '123'::jsonb); 2025-11-30 18:45:24.022 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.022 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', 'lax $.a' ERROR ON EMPTY ERROR ON ERROR); 2025-11-30 18:45:24.023 UTC client backend[46527] pg_regress/sqljson ERROR: cannot set JSON encoding for non-bytea output types at character 34 2025-11-30 18:45:24.023 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING text FORMAT JSON ENCODING UTF8); 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson ERROR: unrecognized JSON encoding: invalid_encoding at character 55 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING text FORMAT JSON ENCODING INVALID_ENCODING); 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson ERROR: unsupported JSON encoding at character 35 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING bytea FORMAT JSON ENCODING UTF16); 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson ERROR: unsupported JSON encoding at character 35 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-11-30 18:45:24.024 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING bytea FORMAT JSON ENCODING UTF32); 2025-11-30 18:45:24.025 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:24.025 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_exists('[{"a": 1}, {"a": 2}, 3]', 'strict $[*].a', silent => false); 2025-11-30 18:45:24.026 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "00" of jsonpath input at character 8 2025-11-30 18:45:24.026 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '00'::jsonpath; 2025-11-30 18:45:24.026 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.026 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0755'::jsonpath; 2025-11-30 18:45:24.027 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:24.027 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $.a'); 2025-11-30 18:45:24.028 UTC client backend[46527] pg_regress/sqljson ERROR: subquery must return only one column at character 8 2025-11-30 18:45:24.028 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(SELECT FROM (VALUES (1)) foo(i)); 2025-11-30 18:45:24.028 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type timestamp: "[100,200,false]" 2025-11-30 18:45:24.028 UTC client backend[46522] 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-11-30 18:45:24.028 UTC client backend[46527] pg_regress/sqljson ERROR: subquery must return only one column at character 8 2025-11-30 18:45:24.028 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(SELECT i, i FROM (VALUES (1)) foo(i)); 2025-11-30 18:45:24.028 UTC client backend[46527] pg_regress/sqljson ERROR: subquery must return only one column at character 8 2025-11-30 18:45:24.028 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(SELECT * FROM (VALUES (1, 2)) foo(i, j)); 2025-11-30 18:45:24.028 UTC client backend[46522] pg_regress/json ERROR: domain js_int_not_null does not allow null values 2025-11-30 18:45:24.028 UTC client backend[46522] pg_regress/json STATEMENT: SELECT i FROM json_populate_record(NULL::jsrec_i_not_null, '{"x": 43.2}') q; 2025-11-30 18:45:24.028 UTC client backend[46522] pg_regress/json ERROR: domain js_int_not_null does not allow null values 2025-11-30 18:45:24.028 UTC client backend[46522] pg_regress/json STATEMENT: SELECT i FROM json_populate_record(NULL::jsrec_i_not_null, '{"i": null}') q; 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json HINT: See the value of key "ia". 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": 123}') q; 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json HINT: See the array element [1] of key "ia". 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": [[1], 2]}') q; 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json ERROR: malformed JSON array 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.029 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": [[1], [2, 3]]}') q; 2025-11-30 18:45:24.029 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath wildcard member accessor can only be applied to an object 2025-11-30 18:45:24.029 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $.*'); 2025-11-30 18:45:24.029 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1a" of jsonpath input at character 8 2025-11-30 18:45:24.029 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1a'::jsonpath; 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json HINT: See the value of key "ia1". 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia1 FROM json_populate_record(NULL::jsrec, '{"ia1": 123}') q; 2025-11-30 18:45:24.030 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1e" of jsonpath input at character 8 2025-11-30 18:45:24.030 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1e'::jsonpath; 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json HINT: See the value of key "ia1d". 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia1d FROM json_populate_record(NULL::jsrec, '{"ia1d": 123}') q; 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json ERROR: value for domain js_int_array_1d violates check constraint "js_int_array_1d_check" 2025-11-30 18:45:24.030 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia1d FROM json_populate_record(NULL::jsrec, '{"ia1d": [1, "2", null, 4]}') q; 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json ERROR: malformed JSON array 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia2 FROM json_populate_record(NULL::jsrec, '{"ia2": [[1, 2], [3]]}') q; 2025-11-30 18:45:24.031 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1.e" of jsonpath input at character 8 2025-11-30 18:45:24.031 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1.e'::jsonpath; 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json HINT: See the array element [1] of key "ia2". 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia2 FROM json_populate_record(NULL::jsrec, '{"ia2": [[1, 2], 3, 4]}') q; 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json ERROR: value for domain js_int_array_2d violates check constraint "js_int_array_2d_check" 2025-11-30 18:45:24.031 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ia2d FROM json_populate_record(NULL::jsrec, '{"ia2d": [[1, "2"], [null, 4]]}') q; 2025-11-30 18:45:24.031 UTC client backend[46527] pg_regress/sqljson ERROR: null value not allowed for object key 2025-11-30 18:45:24.031 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(NULL: 1); 2025-11-30 18:45:24.031 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1.2a" of jsonpath input at character 8 2025-11-30 18:45:24.031 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1.2a'::jsonpath; 2025-11-30 18:45:24.031 UTC client backend[46527] pg_regress/sqljson ERROR: field name must not be null 2025-11-30 18:45:24.031 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(NULL: 1 RETURNING jsonb); 2025-11-30 18:45:24.031 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.031 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', 'lax $.a' ERROR ON EMPTY DEFAULT '3' ON ERROR); 2025-11-30 18:45:24.031 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1.2e" of jsonpath input at character 8 2025-11-30 18:45:24.031 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1.2e'::jsonpath; 2025-11-30 18:45:24.031 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: only one FOR ORDINALITY column is allowed at character 69 2025-11-30 18:45:24.031 UTC client backend[46528] 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-11-30 18:45:24.031 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_VALUE must return single scalar item 2025-11-30 18:45:24.031 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '[1,2]', '$[*]' ERROR ON ERROR); 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json ERROR: malformed JSON array 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.032 UTC client backend[46522] 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-11-30 18:45:24.032 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:24.032 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.a'); 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json HINT: See the value of key "ta". 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ta FROM json_populate_record(NULL::jsrec, '{"ta": 123}') q; 2025-11-30 18:45:24.032 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid input syntax for type integer: "err" 2025-11-30 18:45:24.032 UTC client backend[46528] 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-11-30 18:45:24.032 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.032 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(k: v WITH UNIQUE KEYS) FROM (VALUES (1, 1), (1, NULL), (2, 2)) foo(k, v); 2025-11-30 18:45:24.032 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: " " 2025-11-30 18:45:24.032 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '[" "]', '$[*]' RETURNING int ERROR ON ERROR); 2025-11-30 18:45:24.032 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid input syntax for type integer: "err" 2025-11-30 18:45:24.032 UTC client backend[46528] 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-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json HINT: See the array element [1] of key "ta". 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ta FROM json_populate_record(NULL::jsrec, '{"ta": [[1, 2, 3], {"k": "v"}]}') q; 2025-11-30 18:45:24.032 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: no SQL/JSON item found for specified path of column "a" 2025-11-30 18:45:24.032 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int PATH '$.a' ERROR ON EMPTY)) jt; 2025-11-30 18:45:24.032 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.032 UTC client backend[46527] 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-11-30 18:45:24.032 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:24.032 UTC client backend[46528] 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-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json ERROR: value too long for type character(10) 2025-11-30 18:45:24.032 UTC client backend[46522] pg_regress/json STATEMENT: SELECT c FROM json_populate_record(NULL::jsrec, '{"c": "aaaaaaaaaaaaa"}') q; 2025-11-30 18:45:24.032 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: JSON object does not contain key "a" 2025-11-30 18:45:24.032 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', 'strict $.a'); 2025-11-30 18:45:24.033 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: cannot specify FORMAT JSON in RETURNING clause of JSON_VALUE() at character 55 2025-11-30 18:45:24.033 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '["1"]', '$[*]' RETURNING int FORMAT JSON); 2025-11-30 18:45:24.033 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: no SQL/JSON item found for specified path of column "a" 2025-11-30 18:45:24.033 UTC client backend[46528] 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-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json HINT: See the value of key "ca". 2025-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": 123}') q; 2025-11-30 18:45:24.033 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-11-30 18:45:24.033 UTC client backend[46527] 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-11-30 18:45:24.033 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1.2e3a" of jsonpath input at character 8 2025-11-30 18:45:24.033 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1.2e3a'::jsonpath; 2025-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json ERROR: value too long for type character(10) 2025-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": ["aaaaaaaaaaaaaaaa"]}') q; 2025-11-30 18:45:24.033 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array accessor can only be applied to an array 2025-11-30 18:45:24.033 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $[1]'); 2025-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json HINT: See the array element [1] of key "ca". 2025-11-30 18:45:24.033 UTC client backend[46522] pg_regress/json STATEMENT: SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": [[1, 2, 3], {"k": "v"}]}') q; 2025-11-30 18:45:24.033 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-11-30 18:45:24.033 UTC client backend[46527] 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-11-30 18:45:24.033 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath wildcard array accessor can only be applied to an array 2025-11-30 18:45:24.033 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $[*]'); 2025-11-30 18:45:24.034 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "0" 2025-11-30 18:45:24.034 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(mod(i,100): (i)::text FORMAT JSON WITH UNIQUE) FROM generate_series(0, 199) i; 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: invalid input syntax for type smallint: "false" 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a int2 EXISTS PATH '$.a')); 2025-11-30 18:45:24.034 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of bounds 2025-11-30 18:45:24.034 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $[1]'); 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: invalid input syntax for type bigint: "false" 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a int8 EXISTS PATH '$.a')); 2025-11-30 18:45:24.034 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: returning pseudo-types is not supported in SQL/JSON functions 2025-11-30 18:45:24.034 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '["1"]', '$[*]' RETURNING record); 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: invalid input syntax for type real: "false" 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a float4 EXISTS PATH '$.a')); 2025-11-30 18:45:24.034 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is not a single numeric value 2025-11-30 18:45:24.034 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $["a"]'); 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: value too long for type character(3) 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a char(3) EXISTS PATH '$.a')); 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: value too long for type character(3) 2025-11-30 18:45:24.034 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a char(3) EXISTS PATH '$.a' ERROR ON ERROR)); 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json HINT: See the value of key "jsa". 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json STATEMENT: SELECT jsa FROM json_populate_record(NULL::jsrec, '{"jsa": 123}') q; 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json ERROR: cannot call populate_composite on a scalar 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json STATEMENT: SELECT rec FROM json_populate_record(NULL::jsrec, '{"rec": 123}') q; 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json ERROR: cannot call populate_composite on an array 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json STATEMENT: SELECT rec FROM json_populate_record(NULL::jsrec, '{"rec": [1, 2]}') q; 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json HINT: See the value of key "reca". 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json STATEMENT: SELECT reca FROM json_populate_record(NULL::jsrec, '{"reca": 123}') q; 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json ERROR: cannot call populate_composite on a scalar 2025-11-30 18:45:24.035 UTC client backend[46522] pg_regress/json STATEMENT: SELECT reca FROM json_populate_record(NULL::jsrec, '{"reca": [1, 2]}') q; 2025-11-30 18:45:24.036 UTC client backend[46522] pg_regress/json ERROR: could not determine row type for result of json_populate_record 2025-11-30 18:45:24.036 UTC client backend[46522] pg_regress/json HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-11-30 18:45:24.036 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_populate_record(null::record, '{"x": 0, "y": 1}'); 2025-11-30 18:45:24.037 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-11-30 18:45:24.037 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: value for domain dint4_0 violates check constraint "dint4_0_check" 2025-11-30 18:45:24.037 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT a, a::bool FROM JSON_TABLE(jsonb '{"a":1}', '$' COLUMNS (a dint4_0 EXISTS PATH '$.b')); 2025-11-30 18:45:24.037 UTC client backend[46522] pg_regress/json ERROR: value for domain j_ordered_pair violates check constraint "j_ordered_pair_check" 2025-11-30 18:45:24.037 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_populate_record(row(1,2)::j_ordered_pair, '{"x": 1, "y": 0}'); 2025-11-30 18:45:24.037 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: value for domain dint4_0 violates check constraint "dint4_0_check" 2025-11-30 18:45:24.037 UTC client backend[46528] 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-11-30 18:45:24.037 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-11-30 18:45:24.037 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: value for domain dint4_0 violates check constraint "dint4_0_check" 2025-11-30 18:45:24.037 UTC client backend[46528] 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-11-30 18:45:24.038 UTC client backend[46522] pg_regress/json ERROR: invalid input syntax for type timestamp: "[100,200,300]" 2025-11-30 18:45:24.038 UTC client backend[46522] 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-11-30 18:45:24.039 UTC client backend[46522] pg_regress/json ERROR: could not determine row type for result of json_populate_recordset 2025-11-30 18:45:24.039 UTC client backend[46522] pg_regress/json HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-11-30 18:45:24.039 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_populate_recordset(null::record, '[{"x": 0, "y": 1}]'); 2025-11-30 18:45:24.039 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-11-30 18:45:24.039 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[12, {"a": 13}, {"b": 14}]', 'lax $[0 to 10 / 0].a'); 2025-11-30 18:45:24.039 UTC client backend[46522] pg_regress/json ERROR: could not determine row type for result of json_populate_recordset 2025-11-30 18:45:24.039 UTC client backend[46522] pg_regress/json HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-11-30 18:45:24.039 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_populate_recordset(null::record, '[]'); 2025-11-30 18:45:24.040 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 56 2025-11-30 18:45:24.040 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"world"', '$' COLUMNS (item text PATH '$' WITH WRAPPER OMIT QUOTES)); 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json ERROR: value for domain j_ordered_pair violates check constraint "j_ordered_pair_check" 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_populate_recordset(row(1,2)::j_ordered_pair, '[{"x": 1, "y": 0}]'); 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json DETAIL: Returned row contains 1 attribute, but query expects 2. 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json STATEMENT: select * from json_populate_recordset(row(0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-11-30 18:45:24.040 UTC client backend[46522] 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-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json DETAIL: Returned row contains 3 attributes, but query expects 2. 2025-11-30 18:45:24.040 UTC client backend[46522] 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-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-11-30 18:45:24.040 UTC client backend[46522] pg_regress/json STATEMENT: select * from json_populate_recordset(row(1000000000::int,50::int),'[{"b":"2"},{"a":"3"}]') q (a text, b text); 2025-11-30 18:45:24.040 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "1.234" 2025-11-30 18:45:24.040 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: select json_value('{"a": 1.234}', '$.a' returning int error on error); 2025-11-30 18:45:24.040 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: only string constants are supported in JSON_TABLE path specification at character 46 2025-11-30 18:45:24.040 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '{"a": 123}', '$' || '.' || 'a' COLUMNS (foo int)); 2025-11-30 18:45:24.041 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-11-30 18:45:24.041 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,2,3]', 'strict $[*].a'); 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: JSON path expression for column "b" must return single item when no wrapper is requested 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable HINT: Use the WITH WRAPPER clause to wrap SQL/JSON items into an array. 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('{"a": [{"b": "1"}, {"b": "2"}]}', '$' COLUMNS (b json path '$.a[*].b' ERROR ON ERROR)); 2025-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "0b" of jsonpath input at character 8 2025-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0b'::jsonpath; 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: a at character 90 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE( jsonb '[]', '$' AS a COLUMNS ( b int, NESTED PATH '$' AS a COLUMNS ( c int ) ) ) jt; 2025-11-30 18:45:24.041 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.041 UTC client backend[46527] 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-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1b" of jsonpath input at character 8 2025-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1b'::jsonpath; 2025-11-30 18:45:24.041 UTC client backend[46527] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-11-30 18:45:24.041 UTC client backend[46527] 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-11-30 18:45:24.041 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "1.234" 2025-11-30 18:45:24.041 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: select json_value('{"a": "1.234"}', '$.a' returning int error on error); 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: b at character 85 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE( jsonb '[]', '$' COLUMNS ( b int, NESTED PATH '$' AS b COLUMNS ( c int ) ) ) jt; 2025-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0b0x'::jsonpath; 2025-11-30 18:45:24.041 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: a at character 156 2025-11-30 18:45:24.041 UTC client backend[46528] 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-11-30 18:45:24.041 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of bounds 2025-11-30 18:45:24.041 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $[last]'); 2025-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "0o" of jsonpath input at character 8 2025-11-30 18:45:24.041 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0o'::jsonpath; 2025-11-30 18:45:24.042 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1o" of jsonpath input at character 8 2025-11-30 18:45:24.042 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1o'::jsonpath; 2025-11-30 18:45:24.043 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.043 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0o0x'::jsonpath; 2025-11-30 18:45:24.043 UTC client backend[46523] pg_regress/jsonb ERROR: cannot call jsonb_object_keys on a scalar 2025-11-30 18:45:24.043 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object_keys(test_json) FROM test_jsonb WHERE json_type = 'scalar'; 2025-11-30 18:45:24.043 UTC client backend[46523] pg_regress/jsonb ERROR: cannot call jsonb_object_keys on an array 2025-11-30 18:45:24.043 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object_keys(test_json) FROM test_jsonb WHERE json_type = 'array'; 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type json 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Token "aaa" is invalid. 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs CONTEXT: JSON data, line 1: aaa 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"aaa"', '$' OMIT QUOTES ERROR ON ERROR); 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type json 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Token "aaa" is invalid. 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs CONTEXT: JSON data, line 1: aaa 2025-11-30 18:45:24.044 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING json OMIT QUOTES ERROR ON ERROR); 2025-11-30 18:45:24.045 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "0x" of jsonpath input at character 8 2025-11-30 18:45:24.045 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0x'::jsonpath; 2025-11-30 18:45:24.045 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(3) 2025-11-30 18:45:24.045 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING char(3) ERROR ON ERROR); 2025-11-30 18:45:24.045 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1x" of jsonpath input at character 8 2025-11-30 18:45:24.045 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1x'::jsonpath; 2025-11-30 18:45:24.045 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.045 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0x0y'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 8 2025-11-30 18:45:24.046 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1]', '$' WITH WRAPPER OMIT QUOTES); 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '_100'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "100_" of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '100_'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '100__000'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '_1_000.5'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1_000_" of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1_000_.5'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1_000._" of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1_000._5'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 8 2025-11-30 18:45:24.046 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1]', '$' WITH CONDITIONAL WRAPPER OMIT QUOTES); 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1_000.5_" of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1_000.5_'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1_000.5e" of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '1_000.5e_1'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0b_10_0101'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0o_273'::jsonpath; 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath ERROR: syntax error at end of jsonpath input at character 8 2025-11-30 18:45:24.046 UTC client backend[46524] pg_regress/jsonpath STATEMENT: select '0x_42F'::jsonpath; 2025-11-30 18:45:24.047 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is not a single numeric value 2025-11-30 18:45:24.047 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,2,3]', '$[last ? (@.type() == "string")]'); 2025-11-30 18:45:24.047 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: expected JSON array 2025-11-30 18:45:24.047 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb'{"rec": "{1,2,3}"}', '$.rec' returning int[] keep quotes error on error); 2025-11-30 18:45:24.048 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: malformed range literal: ""[1,2]"" 2025-11-30 18:45:24.048 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Missing left parenthesis or bracket. 2025-11-30 18:45:24.048 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb'{"rec": "[1,2]"}', '$.rec' returning int4range keep quotes error on error); 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json ERROR: argument list must have even number of elements 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json HINT: The arguments of json_build_object() must consist of alternating keys and values. 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object('{a,b,c}'::text[]); 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object('{a,b,c}'::text[], '{d,e,f}'::text[]); 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json ERROR: argument list must have even number of elements 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json HINT: The arguments of json_build_object() must consist of alternating keys and values. 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object('a', 'b', 'c'); 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json ERROR: null value not allowed for object key 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object(NULL, 'a'); 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json ERROR: argument list must have even number of elements 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json HINT: The arguments of json_build_object() must consist of alternating keys and values. 2025-11-30 18:45:24.049 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object(VARIADIC '{a,b,c}'::text[]); 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json ERROR: null value not allowed for object key 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object(VARIADIC ARRAY[NULL, 'a']::text[]); 2025-11-30 18:45:24.050 UTC client backend[46524] pg_regress/jsonpath LOG: disconnection: session time: 0:00:00.061 user=postgres database=regression host=[local] 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json ERROR: null value not allowed for object key 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object(null,2); 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object(r,2) FROM (SELECT 1 AS a, 2 AS b) r; 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object(json '{"a":1,"b":2}', 3); 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.050 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_build_object('{1,2,3}'::int[], 3); 2025-11-30 18:45:24.051 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: could not find jsonpath variable "value" 2025-11-30 18:45:24.051 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)'); 2025-11-30 18:45:24.052 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.052 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY); 2025-11-30 18:45:24.052 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.052 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY NULL ON ERROR); 2025-11-30 18:45:24.052 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.052 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY EMPTY ARRAY ON ERROR); 2025-11-30 18:45:24.052 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: "vars" argument is not an object 2025-11-30 18:45:24.052 UTC client backend[46526] pg_regress/jsonb_jsonpath DETAIL: Jsonpath parameters should be encoded as key-value pairs of "vars" object. 2025-11-30 18:45:24.052 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)', '1'); 2025-11-30 18:45:24.053 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: "vars" argument is not an object 2025-11-30 18:45:24.053 UTC client backend[46526] pg_regress/jsonb_jsonpath DETAIL: Jsonpath parameters should be encoded as key-value pairs of "vars" object. 2025-11-30 18:45:24.053 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)', '[{"value" : 13}]'); 2025-11-30 18:45:24.053 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.053 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY EMPTY OBJECT ON ERROR); 2025-11-30 18:45:24.053 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.053 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY ERROR ON ERROR); 2025-11-30 18:45:24.053 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_QUERY must return single item when no wrapper is requested 2025-11-30 18:45:24.053 UTC client backend[46529] pg_regress/sqljson_queryfuncs HINT: Use the WITH WRAPPER clause to wrap SQL/JSON items into an array. 2025-11-30 18:45:24.053 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1,2]', '$[*]' ERROR ON ERROR); 2025-11-30 18:45:24.055 UTC client backend[46522] pg_regress/json ERROR: null value not allowed for object key 2025-11-30 18:45:24.055 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_object_agg(name, type) FROM foo; 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (EMPTY OBJECT) to the RETURNING type 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: expected JSON array 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[3,4]', '$[*]' RETURNING bigint[] EMPTY OBJECT ON ERROR); 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (EMPTY OBJECT) to the RETURNING type 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: expected JSON array 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"[3,4]"', '$[*]' RETURNING bigint[] EMPTY OBJECT ON ERROR); 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type smallint: ""123.1"" 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int2 error on error); 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: ""123.1"" 2025-11-30 18:45:24.056 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int4 error on error); 2025-11-30 18:45:24.057 UTC client backend[46523] pg_regress/jsonb ERROR: cannot get array length of a non-array 2025-11-30 18:45:24.057 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_array_length('{"f1":1,"f2":[5,6]}'); 2025-11-30 18:45:24.057 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type bigint: ""123.1"" 2025-11-30 18:45:24.057 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int8 error on error); 2025-11-30 18:45:24.057 UTC client backend[46523] pg_regress/jsonb ERROR: cannot get array length of a scalar 2025-11-30 18:45:24.057 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_array_length('4'); 2025-11-30 18:45:24.057 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type boolean: ""123.1"" 2025-11-30 18:45:24.057 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING bool error on error); 2025-11-30 18:45:24.057 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type numeric: ""123.1"" 2025-11-30 18:45:24.057 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING numeric error on error); 2025-11-30 18:45:24.058 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type real: ""123.1"" 2025-11-30 18:45:24.058 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING real error on error); 2025-11-30 18:45:24.058 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type double precision: ""123.1"" 2025-11-30 18:45:24.058 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING float8 error on error); 2025-11-30 18:45:24.058 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type smallint: "123.1" 2025-11-30 18:45:24.058 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int2 omit quotes error on error); 2025-11-30 18:45:24.059 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: returning pseudo-types is not supported in SQL/JSON functions 2025-11-30 18:45:24.059 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[3,4]', '$[*]' RETURNING anyarray EMPTY OBJECT ON ERROR); 2025-11-30 18:45:24.059 UTC client backend[46522] pg_regress/json ERROR: array must have even number of elements 2025-11-30 18:45:24.059 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_object('{a,b,c}'); 2025-11-30 18:45:24.059 UTC client backend[46522] pg_regress/json ERROR: array must have two columns 2025-11-30 18:45:24.059 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_object('{{a},{b}}'); 2025-11-30 18:45:24.059 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-11-30 18:45:24.059 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('0', '1 / $'); 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('0', '1 / $ + 2'); 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('0', '-(3 + 1 % $)'); 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: right operand of jsonpath operator + is not a single numeric value 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$ + "2"'); 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: right operand of jsonpath operator * is not a single numeric value 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1, 2]', '3 * $'); 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: operand of unary jsonpath operator - is not a numeric value 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"a"', '-$'); 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: operand of unary jsonpath operator + is not a numeric value 2025-11-30 18:45:24.060 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,"2",3]', '+$'); 2025-11-30 18:45:24.060 UTC client backend[46522] pg_regress/json ERROR: array must have two columns 2025-11-30 18:45:24.060 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_object('{{a,b,c},{b,c,d}}'); 2025-11-30 18:45:24.061 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: left operand of jsonpath operator * is not a single numeric value 2025-11-30 18:45:24.061 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{"a": [1, 2]}', 'lax $.a * 3'); 2025-11-30 18:45:24.061 UTC client backend[46522] pg_regress/json ERROR: wrong number of array subscripts 2025-11-30 18:45:24.061 UTC client backend[46522] pg_regress/json STATEMENT: SELECT json_object('{{{a,b},{c,d}},{{b,c},{d,e}}}'); 2025-11-30 18:45:24.061 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath wildcard member accessor can only be applied to an object 2025-11-30 18:45:24.061 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,2,3,{"b": [3,4,5]}]', 'strict $.*'); 2025-11-30 18:45:24.061 UTC client backend[46522] pg_regress/json ERROR: wrong number of array subscripts 2025-11-30 18:45:24.061 UTC client backend[46522] 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-11-30 18:45:24.061 UTC client backend[46522] pg_regress/json ERROR: mismatched array dimensions 2025-11-30 18:45:24.061 UTC client backend[46522] pg_regress/json STATEMENT: select json_object('{a,b,c,"d e f",g}','{1,2,3,"a b c"}'); 2025-11-30 18:45:24.061 UTC client backend[46522] pg_regress/json ERROR: mismatched array dimensions 2025-11-30 18:45:24.061 UTC client backend[46522] pg_regress/json STATEMENT: select json_object('{a,b,c,"d e f"}','{1,2,3,"a b c",g}'); 2025-11-30 18:45:24.062 UTC client backend[46522] pg_regress/json ERROR: null value not allowed for object key 2025-11-30 18:45:24.062 UTC client backend[46522] pg_regress/json STATEMENT: select json_object('{a,b,NULL,"d e f"}','{1,2,3,"a b c"}'); 2025-11-30 18:45:24.062 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: cannot call populate_composite on a scalar 2025-11-30 18:45:24.062 UTC client backend[46529] 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-11-30 18:45:24.062 UTC client backend[46527] pg_regress/sqljson ERROR: cannot use type integer in IS JSON predicate 2025-11-30 18:45:24.062 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT NULL::int IS JSON; 2025-11-30 18:45:24.062 UTC client backend[46522] pg_regress/json ERROR: duplicate JSON object key value: "0" 2025-11-30 18:45:24.062 UTC client backend[46522] pg_regress/json STATEMENT: select json_object_agg_unique(mod(i,100), i) from generate_series(0, 199) i; 2025-11-30 18:45:24.063 UTC client backend[46527] pg_regress/sqljson ERROR: invalid byte sequence for encoding "UTF8": 0x00 2025-11-30 18:45:24.063 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT bytea '\x00' IS JSON; 2025-11-30 18:45:24.064 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .size() can only be applied to an array 2025-11-30 18:45:24.064 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,null,true,"11",[],[1],[1,2,3],{},{"a":1,"b":2}]', 'strict $[*].size()'); 2025-11-30 18:45:24.065 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .keyvalue() can only be applied to an object 2025-11-30 18:45:24.065 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[{},1]', '$[*].keyvalue()'); 2025-11-30 18:45:24.065 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .keyvalue() can only be applied to an object 2025-11-30 18:45:24.065 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[{"a": 1, "b": [1, 2]}, {"c": {"a": "bbb"}}]', 'strict $.keyvalue()'); 2025-11-30 18:45:24.065 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .keyvalue() can only be applied to an object 2025-11-30 18:45:24.065 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[{"a": 1, "b": [1, 2]}, {"c": {"a": "bbb"}}]', 'strict $.keyvalue().a'); 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.double()'); 2025-11-30 18:45:24.066 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.066 UTC client backend[46522] pg_regress/json HINT: See the value of key "ia". 2025-11-30 18:45:24.066 UTC client backend[46522] pg_regress/json STATEMENT: select * from json_to_record('{"ia": 123}') as x(ia _int4); 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.double()'); 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.double()'); 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.double()'); 2025-11-30 18:45:24.066 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "a" 2025-11-30 18:45:24.066 UTC client backend[46529] 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-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .double() is invalid for type double precision 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.double()'); 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .double() is invalid for type double precision 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.double()'); 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-11-30 18:45:24.066 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.double()'); 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.double()'); 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.double()'); 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.double()'); 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .abs() can only be applied to a numeric value 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.abs()'); 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .floor() can only be applied to a numeric value 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.floor()'); 2025-11-30 18:45:24.067 UTC client backend[46522] pg_regress/json ERROR: expected JSON array 2025-11-30 18:45:24.067 UTC client backend[46522] pg_regress/json HINT: See the array element [1] of key "ia". 2025-11-30 18:45:24.067 UTC client backend[46522] pg_regress/json STATEMENT: select * from json_to_record('{"ia": [[1], 2]}') as x(ia _int4); 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ceiling() can only be applied to a numeric value 2025-11-30 18:45:24.067 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.2"', '$.ceiling()'); 2025-11-30 18:45:24.067 UTC client backend[46522] pg_regress/json ERROR: malformed JSON array 2025-11-30 18:45:24.067 UTC client backend[46522] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.067 UTC client backend[46522] pg_regress/json STATEMENT: select * from json_to_record('{"ia": [[1], [2, 3]]}') as x(ia _int4); 2025-11-30 18:45:24.067 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: syntax error at or near "{" of jsonpath input 2025-11-30 18:45:24.067 UTC client backend[46529] 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-11-30 18:45:24.068 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "a" 2025-11-30 18:45:24.068 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1,2,null,"a"]', '$[*]' RETURNING int[] WITH WRAPPER ERROR ON ERROR); 2025-11-30 18:45:24.069 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON EMPTY expression (NULL) to the RETURNING type 2025-11-30 18:45:24.069 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: domain sqljsonb_int_not_null does not allow null values 2025-11-30 18:45:24.069 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '{"a": 1}', '$.b' RETURNING sqljsonb_int_not_null); 2025-11-30 18:45:24.069 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-11-30 18:45:24.069 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '{"a": 1}', '$.b' RETURNING sqljsonb_int_not_null ERROR ON EMPTY ERROR ON ERROR); 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.datetime()'); 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.datetime()'); 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.datetime()'); 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.datetime()'); 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-11-30 18:45:24.069 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.datetime()'); 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: datetime format is not recognized: "bogus" 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use a datetime template argument to specify the input data format. 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.datetime()'); 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: invalid datetime format separator: "a" 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34"', '$.datetime("aaa")'); 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: invalid value "aa" for "HH24" 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath DETAIL: Value must be an integer. 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"aaaa"', '$.datetime("HH24")'); 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: trailing characters remain in input string after datetime format 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy")'); 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: trailing characters remain in input string after datetime format 2025-11-30 18:45:24.070 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy").type()'); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: unmatched format character "T" 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017t12:34:56"', '$.datetime("dd-mm-yyyy\"T\"HH24:MI:SS")'); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: unmatched format character "T" 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34:56"', '$.datetime("dd-mm-yyyy\"T\"HH24:MI:SS")'); 2025-11-30 18:45:24.071 UTC client backend[46527] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-11-30 18:45:24.071 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('{ "a" : 1 } ' RETURNING varchar(2)); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.bigint()'); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.bigint()'); 2025-11-30 18:45:24.071 UTC client backend[46527] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-11-30 18:45:24.071 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('a': JSON_OBJECT('b': 1 RETURNING varchar(2))); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.bigint()'); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.bigint()'); 2025-11-30 18:45:24.071 UTC client backend[46527] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-11-30 18:45:24.071 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(JSON_ARRAY('{ "a" : 123 }' RETURNING varchar(2))); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23"', '$.bigint()'); 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.071 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.bigint()'); 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.bigint()'); 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "nan" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.bigint()'); 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "NaN" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.bigint()'); 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "inf" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.bigint()'); 2025-11-30 18:45:24.072 UTC client backend[46527] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-11-30 18:45:24.072 UTC client backend[46527] 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-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "-inf" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.072 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.bigint()'); 2025-11-30 18:45:24.072 UTC client backend[46527] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-11-30 18:45:24.072 UTC client backend[46527] 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-11-30 18:45:24.072 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: syntax error at or near "empty" at character 79 2025-11-30 18:45:24.072 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int exists empty object on empty)); 2025-11-30 18:45:24.072 UTC client backend[46452] isolation/eval-plan-qual/s2 LOG: disconnection: session time: 0:00:02.850 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:24.072 UTC client backend[46451] isolation/eval-plan-qual/s1 LOG: disconnection: session time: 0:00:02.853 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:24.072 UTC client backend[46453] isolation/eval-plan-qual/s3 LOG: disconnection: session time: 0:00:02.848 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior at character 57 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause. 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int) NULL ON ERROR); 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid ON EMPTY behavior for column "a" at character 56 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: Only ERROR, NULL, or DEFAULT expression is allowed in ON EMPTY for scalar columns. 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int true on empty)); 2025-11-30 18:45:24.073 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "12345678901234567890" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.073 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345678901234567890', '$.bigint()'); 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior for column "a" at character 68 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: Only ERROR, NULL, EMPTY ARRAY, EMPTY OBJECT, or DEFAULT expression is allowed in ON ERROR for formatted columns. 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int omit quotes true on error)); 2025-11-30 18:45:24.073 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "12345678901234567890" of jsonpath item method .bigint() is invalid for type bigint 2025-11-30 18:45:24.073 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12345678901234567890"', '$.bigint()'); 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior for column "a" at character 63 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable DETAIL: Only ERROR, TRUE, FALSE, or UNKNOWN is allowed in ON ERROR for EXISTS columns. 2025-11-30 18:45:24.073 UTC client backend[46528] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int exists empty object on error)); 2025-11-30 18:45:24.075 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value 2025-11-30 18:45:24.075 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.boolean()'); 2025-11-30 18:45:24.075 UTC client backend[46527] pg_regress/sqljson ERROR: value too long for type character(2) 2025-11-30 18:45:24.075 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('123' RETURNING sqljson_char2); 2025-11-30 18:45:24.075 UTC client backend[46527] pg_regress/sqljson ERROR: value for domain sqljson_char2 violates check constraint "sqljson_char2_check" 2025-11-30 18:45:24.075 UTC client backend[46527] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('12' RETURNING sqljson_char2); 2025-11-30 18:45:24.077 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value 2025-11-30 18:45:24.077 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.boolean()'); 2025-11-30 18:45:24.077 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value 2025-11-30 18:45:24.077 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.boolean()'); 2025-11-30 18:45:24.078 UTC client backend[46450] isolation/eval-plan-qual/control connection LOG: disconnection: session time: 0:00:02.861 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:24.079 UTC unrecognized[46533] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.079 UTC client backend[46533] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.079 UTC client backend[46533] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual-trigger 2025-11-30 18:45:24.080 UTC client backend[46533] isolation/eval-plan-qual-trigger LOG: connection ready: setup total=3.011 ms, fork=1.519 ms, authentication=0.118 ms 2025-11-30 18:45:24.081 UTC client backend[46527] pg_regress/sqljson LOG: disconnection: session time: 0:00:00.090 user=postgres database=regression host=[local] 2025-11-30 18:45:24.081 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.081 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1.23', '$.boolean()'); 2025-11-30 18:45:24.081 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.081 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23"', '$.boolean()'); 2025-11-30 18:45:24.082 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.082 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.boolean()'); 2025-11-30 18:45:24.083 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.083 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.boolean()'); 2025-11-30 18:45:24.083 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "nan" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.083 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.boolean()'); 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb ERROR: argument list must have even number of elements 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb HINT: The arguments of jsonb_build_object() must consist of alternating keys and values. 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('{a,b,c}'::text[]); 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('{a,b,c}'::text[], '{d,e,f}'::text[]); 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb ERROR: argument list must have even number of elements 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb HINT: The arguments of jsonb_build_object() must consist of alternating keys and values. 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('a', 'b', 'c'); 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb ERROR: argument 1: key must not be null 2025-11-30 18:45:24.083 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(NULL, 'a'); 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb ERROR: argument list must have even number of elements 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb HINT: The arguments of jsonb_build_object() must consist of alternating keys and values. 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(VARIADIC '{a,b,c}'::text[]); 2025-11-30 18:45:24.084 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "NaN" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.084 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.boolean()'); 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb ERROR: argument 1: key must not be null 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(VARIADIC ARRAY[NULL, 'a']::text[]); 2025-11-30 18:45:24.084 UTC client backend[46522] pg_regress/json ERROR: wrong flag in flag array: "" 2025-11-30 18:45:24.084 UTC client backend[46522] pg_regress/json HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-11-30 18:45:24.084 UTC client backend[46522] 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-11-30 18:45:24.084 UTC client backend[46522] pg_regress/json ERROR: wrong flag type, only arrays and scalars are allowed 2025-11-30 18:45:24.084 UTC client backend[46522] 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-11-30 18:45:24.084 UTC client backend[46522] pg_regress/json ERROR: flag array element is not a string 2025-11-30 18:45:24.084 UTC client backend[46522] pg_regress/json HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-11-30 18:45:24.084 UTC client backend[46522] 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-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb ERROR: argument 1: key must not be null 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(null,2); 2025-11-30 18:45:24.084 UTC client backend[46522] pg_regress/json ERROR: flag array element is not a string 2025-11-30 18:45:24.084 UTC client backend[46522] pg_regress/json HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-11-30 18:45:24.084 UTC client backend[46522] 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-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(r,2) FROM (SELECT 1 AS a, 2 AS b) r; 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(json '{"a":1,"b":2}', 3); 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-11-30 18:45:24.084 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('{1,2,3}'::int[], 3); 2025-11-30 18:45:24.085 UTC client backend[46523] pg_regress/jsonb ERROR: field name must not be null 2025-11-30 18:45:24.085 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object_agg(NULL, '{"a":1}'); 2025-11-30 18:45:24.086 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "inf" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.086 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.boolean()'); 2025-11-30 18:45:24.086 UTC unrecognized[46534] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.087 UTC client backend[46534] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.087 UTC client backend[46534] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual-trigger 2025-11-30 18:45:24.088 UTC client backend[46534] isolation/eval-plan-qual-trigger LOG: connection ready: setup total=6.256 ms, fork=2.077 ms, authentication=0.138 ms 2025-11-30 18:45:24.088 UTC client backend[46528] pg_regress/sqljson_jsontable LOG: disconnection: session time: 0:00:00.099 user=postgres database=regression host=[local] 2025-11-30 18:45:24.089 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "-inf" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.089 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.boolean()'); 2025-11-30 18:45:24.089 UTC unrecognized[46535] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.090 UTC client backend[46522] pg_regress/json LOG: disconnection: session time: 0:00:00.106 user=postgres database=regression host=[local] 2025-11-30 18:45:24.090 UTC client backend[46535] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.090 UTC client backend[46535] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual-trigger 2025-11-30 18:45:24.090 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "100" of jsonpath item method .boolean() is invalid for type boolean 2025-11-30 18:45:24.090 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"100"', '$.boolean()'); 2025-11-30 18:45:24.091 UTC client backend[46535] isolation/eval-plan-qual-trigger LOG: connection ready: setup total=1.981 ms, fork=0.602 ms, authentication=0.120 ms 2025-11-30 18:45:24.091 UTC client backend[46523] pg_regress/jsonb ERROR: field name must not be null 2025-11-30 18:45:24.091 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object_agg(name, type) FROM foo; 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: array must have even number of elements 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{a,b,c}'); 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: array must have two columns 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{{a},{b}}'); 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: array must have two columns 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{{a,b,c},{b,c,d}}'); 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: wrong number of array subscripts 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{{{a,b},{c,d}},{{b,c},{d,e}}}'); 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: wrong number of array subscripts 2025-11-30 18:45:24.092 UTC client backend[46523] 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-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: mismatched array dimensions 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_object('{a,b,c,"d e f",g}','{1,2,3,"a b c"}'); 2025-11-30 18:45:24.092 UTC unrecognized[46536] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: mismatched array dimensions 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_object('{a,b,c,"d e f"}','{1,2,3,"a b c",g}'); 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb ERROR: null value not allowed for object key 2025-11-30 18:45:24.092 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_object('{a,b,NULL,"d e f"}','{1,2,3,"a b c"}'); 2025-11-30 18:45:24.093 UTC client backend[46536] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.093 UTC client backend[46536] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual-trigger 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.date()'); 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.date()'); 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.date()'); 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.date()'); 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.date()'); 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: date format is not recognized: "bogus" 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.date()'); 2025-11-30 18:45:24.093 UTC client backend[46536] isolation/eval-plan-qual-trigger LOG: connection ready: setup total=2.135 ms, fork=0.573 ms, authentication=0.126 ms 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: date format is not recognized: "12:34:56" 2025-11-30 18:45:24.093 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56"', '$.date()'); 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: date format is not recognized: "12:34:56 +05:30" 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56 +05:30"', '$.date()'); 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to date without time zone usage 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.date()'); 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "2" of jsonpath input at character 41 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15"', '$.date(2)'); 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.decimal()'); 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.decimal()'); 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.decimal()'); 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-11-30 18:45:24.094 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.decimal()'); 2025-11-30 18:45:24.095 UTC unrecognized[46537] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .decimal() is invalid for type numeric 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.decimal()'); 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.decimal()'); 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.decimal()'); 2025-11-30 18:45:24.095 UTC client backend[46537] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.095 UTC client backend[46537] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/eval-plan-qual-trigger 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.decimal()'); 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-11-30 18:45:24.095 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.decimal()'); 2025-11-30 18:45:24.096 UTC client backend[46537] isolation/eval-plan-qual-trigger LOG: connection ready: setup total=1.772 ms, fork=0.450 ms, authentication=0.104 ms 2025-11-30 18:45:24.096 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "12345.678" of jsonpath item method .decimal() is invalid for type numeric 2025-11-30 18:45:24.096 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(6, 2)'); 2025-11-30 18:45:24.096 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "12345.678" of jsonpath item method .decimal() is invalid for type numeric 2025-11-30 18:45:24.096 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(4, 6)'); 2025-11-30 18:45:24.096 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NUMERIC precision 0 must be between 1 and 1000 2025-11-30 18:45:24.096 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(0, 6)'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NUMERIC precision 1001 must be between 1 and 1000 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(1001, 6)'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NUMERIC precision -6 must be between 1 and 1000 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234.5678', '$.decimal(-6, +2)'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NUMERIC scale -1001 must be between -1000 and 1000 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234.5678', '$.decimal(6, -1001)'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NUMERIC scale 1001 must be between -1000 and 1000 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234.5678', '$.decimal(6, 1001)'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: precision of jsonpath item method .decimal() is out of range for type integer 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12.3', '$.decimal(12345678901,1)'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: scale of jsonpath item method .decimal() is out of range for type integer 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12.3', '$.decimal(1,12345678901)'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.integer()'); 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-11-30 18:45:24.097 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23"', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "nan" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "NaN" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "inf" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.integer()'); 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "-inf" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.098 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.integer()'); 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "12345678901" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345678901', '$.integer()'); 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "12345678901" of jsonpath item method .integer() is invalid for type integer 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12345678901"', '$.integer()'); 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.number()'); 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-11-30 18:45:24.099 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.number()'); 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.number()'); 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.number()'); 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .number() is invalid for type numeric 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.number()'); 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.number()'); 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.number()'); 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-11-30 18:45:24.100 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.number()'); 2025-11-30 18:45:24.101 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-11-30 18:45:24.101 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.number()'); 2025-11-30 18:45:24.101 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value 2025-11-30 18:45:24.101 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.string()'); 2025-11-30 18:45:24.102 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value 2025-11-30 18:45:24.102 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.string()'); 2025-11-30 18:45:24.102 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value 2025-11-30 18:45:24.102 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.string()'); 2025-11-30 18:45:24.102 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.102 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.102 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +5:30"', '$.timestamp().string()'); 2025-11-30 18:45:24.103 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.103 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.103 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56"', '$.timestamp_tz().string()'); 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time() can only be applied to a string 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.time()'); 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time() can only be applied to a string 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.time()'); 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time() can only be applied to a string 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.time()'); 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time() can only be applied to a string 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.time()'); 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time() can only be applied to a string 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.time()'); 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time format is not recognized: "bogus" 2025-11-30 18:45:24.104 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.time()'); 2025-11-30 18:45:24.104 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint1" 2025-11-30 18:45:24.104 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains (, 1, [1, 2]). 2025-11-30 18:45:24.104 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('', 1); 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time format is not recognized: "2023-08-15" 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15"', '$.time()'); 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timetz to time without time zone usage 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56 +05:30"', '$.time()'); 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "-" of jsonpath input at character 43 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56.789"', '$.time(-1)'); 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "2.0" of jsonpath input at character 43 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56.789"', '$.time(2.0)'); 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time precision of jsonpath item method .time() is out of range for type integer 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56.789"', '$.time(12345678901)'); 2025-11-30 18:45:24.105 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2" 2025-11-30 18:45:24.105 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains (1, 1, [1, 2]). 2025-11-30 18:45:24.105 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('1', 1); 2025-11-30 18:45:24.105 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type timestamp: "[100, 200, false]" 2025-11-30 18:45:24.105 UTC client backend[46523] 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-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIME(10) precision reduced to maximum allowed, 6 2025-11-30 18:45:24.105 UTC client backend[46523] pg_regress/jsonb ERROR: domain jsb_int_not_null does not allow null values 2025-11-30 18:45:24.105 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT i FROM jsonb_populate_record(NULL::jsbrec_i_not_null, '{"x": 43.2}') q; 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIME(8) precision reduced to maximum allowed, 6 2025-11-30 18:45:24.105 UTC client backend[46523] pg_regress/jsonb ERROR: domain jsb_int_not_null does not allow null values 2025-11-30 18:45:24.105 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT i FROM jsonb_populate_record(NULL::jsbrec_i_not_null, '{"i": null}') q; 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time_tz() can only be applied to a string 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.time_tz()'); 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time_tz() can only be applied to a string 2025-11-30 18:45:24.105 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.time_tz()'); 2025-11-30 18:45:24.106 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2" 2025-11-30 18:45:24.106 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ([], null, [1, 2]). 2025-11-30 18:45:24.106 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('[]'); 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time_tz() can only be applied to a string 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.time_tz()'); 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time_tz() can only be applied to a string 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.time_tz()'); 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .time_tz() can only be applied to a string 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.time_tz()'); 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "ia". 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": 123}') q; 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time_tz format is not recognized: "bogus" 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.time_tz()'); 2025-11-30 18:45:24.106 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2" 2025-11-30 18:45:24.106 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ({"b": 1}, 1, [1, 2]). 2025-11-30 18:45:24.106 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('{"b": 1}', 1); 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb HINT: See the array element [1] of key "ia". 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": [[1], 2]}') q; 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time_tz format is not recognized: "2023-08-15" 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15"', '$.time_tz()'); 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb ERROR: malformed JSON array 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.106 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": [[1], [2, 3]]}') q; 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time_tz format is not recognized: "2023-08-15 12:34:56" 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56"', '$.time_tz()'); 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "-" of jsonpath input at character 50 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56.789 +05:30"', '$.time_tz(-1)'); 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "2.0" of jsonpath input at character 50 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56.789 +05:30"', '$.time_tz(2.0)'); 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time precision of jsonpath item method .time_tz() is out of range for type integer 2025-11-30 18:45:24.106 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56.789 +05:30"', '$.time_tz(12345678901)'); 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "ia1". 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia1 FROM jsonb_populate_record(NULL::jsbrec, '{"ia1": 123}') q; 2025-11-30 18:45:24.107 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint3" 2025-11-30 18:45:24.107 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ({"a": 1}, 1, [1, 2]). 2025-11-30 18:45:24.107 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('{"a": 1}', 1); 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIME(10) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIME(8) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "ia1d". 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia1d FROM jsonb_populate_record(NULL::jsbrec, '{"ia1d": 123}') q; 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp() can only be applied to a string 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.timestamp()'); 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb ERROR: value for domain jsb_int_array_1d violates check constraint "jsb_int_array_1d_check" 2025-11-30 18:45:24.107 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia1d FROM jsonb_populate_record(NULL::jsbrec, '{"ia1d": [1, "2", null, 4]}') q; 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp() can only be applied to a string 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.timestamp()'); 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp() can only be applied to a string 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.timestamp()'); 2025-11-30 18:45:24.107 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint4" 2025-11-30 18:45:24.107 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ({"a": 10}, 1, [1, 2]). 2025-11-30 18:45:24.107 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('{"a": 10}', 1); 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp() can only be applied to a string 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.timestamp()'); 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp() can only be applied to a string 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.timestamp()'); 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: timestamp format is not recognized: "bogus" 2025-11-30 18:45:24.107 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.timestamp()'); 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb ERROR: malformed JSON array 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia2 FROM jsonb_populate_record(NULL::jsbrec, '{"ia2": [[1, 2], [3]]}') q; 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb HINT: See the array element [1] of key "ia2". 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia2 FROM jsonb_populate_record(NULL::jsbrec, '{"ia2": [[1, 2], 3, 4]}') q; 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb ERROR: value for domain jsb_int_array_2d violates check constraint "jsb_int_array_2d_check" 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ia2d FROM jsonb_populate_record(NULL::jsbrec, '{"ia2d": [[1, "2"], [null, 4]]}') q; 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: timestamp format is not recognized: "12:34:56" 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56"', '$.timestamp()'); 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: timestamp format is not recognized: "12:34:56 +05:30" 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56 +05:30"', '$.timestamp()'); 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "-" of jsonpath input at character 54 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56.789"', '$.timestamp(-1)'); 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "2.0" of jsonpath input at character 54 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56.789"', '$.timestamp(2.0)'); 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time precision of jsonpath item method .timestamp() is out of range for type integer 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56.789"', '$.timestamp(12345678901)'); 2025-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIMESTAMP(10) precision reduced to maximum allowed, 6 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb ERROR: malformed JSON array 2025-11-30 18:45:24.108 UTC client backend[46523] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.108 UTC client backend[46523] 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-11-30 18:45:24.108 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIMESTAMP(8) precision reduced to maximum allowed, 6 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp_tz() can only be applied to a string 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.timestamp_tz()'); 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "ta". 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ta FROM jsonb_populate_record(NULL::jsbrec, '{"ta": 123}') q; 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp_tz() can only be applied to a string 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.timestamp_tz()'); 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp_tz() can only be applied to a string 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.timestamp_tz()'); 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb HINT: See the array element [1] of key "ta". 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ta FROM jsonb_populate_record(NULL::jsbrec, '{"ta": [[1, 2, 3], {"k": "v"}]}') q; 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp_tz() can only be applied to a string 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.timestamp_tz()'); 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .timestamp_tz() can only be applied to a string 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.timestamp_tz()'); 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: timestamp_tz format is not recognized: "bogus" 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.timestamp_tz()'); 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb ERROR: value too long for type character(10) 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT c FROM jsonb_populate_record(NULL::jsbrec, '{"c": "aaaaaaaaaaaaa"}') q; 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from date to timestamptz without time zone usage 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15"', '$.timestamp_tz()'); 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "ca". 2025-11-30 18:45:24.109 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": 123}') q; 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: timestamp_tz format is not recognized: "12:34:56" 2025-11-30 18:45:24.109 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56"', '$.timestamp_tz()'); 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: timestamp_tz format is not recognized: "12:34:56 +05:30" 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56 +05:30"', '$.timestamp_tz()'); 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "-" of jsonpath input at character 61 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56.789 +05:30"', '$.timestamp_tz(-1)'); 2025-11-30 18:45:24.110 UTC client backend[46523] pg_regress/jsonb ERROR: value too long for type character(10) 2025-11-30 18:45:24.110 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": ["aaaaaaaaaaaaaaaa"]}') q; 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "2.0" of jsonpath input at character 61 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56.789 +05:30"', '$.timestamp_tz(2.0)'); 2025-11-30 18:45:24.110 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.110 UTC client backend[46523] pg_regress/jsonb HINT: See the array element [1] of key "ca". 2025-11-30 18:45:24.110 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": [[1, 2, 3], {"k": "v"}]}') q; 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: time precision of jsonpath item method .timestamp_tz() is out of range for type integer 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56.789 +05:30"', '$.timestamp_tz(12345678901)'); 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIMESTAMP(10) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath WARNING: TIMESTAMP(8) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to time without time zone usage 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.110 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.time()'); 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56"', '$.time_tz()'); 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.timestamp()'); 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56"', '$.timestamp_tz()'); 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: input string is too short for datetime format 2025-11-30 18:45:24.111 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy HH24:MI TZH")'); 2025-11-30 18:45:24.111 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.111 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "jsa". 2025-11-30 18:45:24.111 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsa FROM jsonb_populate_record(NULL::jsbrec, '{"jsa": 123}') q; 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: input string is too short for datetime format 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34"', '$.datetime("HH24:MI TZH")'); 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb ERROR: cannot call populate_composite on a scalar 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT rec FROM jsonb_populate_record(NULL::jsbrec, '{"rec": 123}') q; 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb ERROR: cannot call populate_composite on an array 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT rec FROM jsonb_populate_record(NULL::jsbrec, '{"rec": [1, 2]}') q; 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "reca". 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT reca FROM jsonb_populate_record(NULL::jsbrec, '{"reca": 123}') q; 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to time without time zone usage 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.time()'); 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb ERROR: cannot call populate_composite on a scalar 2025-11-30 18:45:24.112 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT reca FROM jsonb_populate_record(NULL::jsbrec, '{"reca": [1, 2]}') q; 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.112 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.timestamp()'); 2025-11-30 18:45:24.113 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.113 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.113 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56"', '$.timestamp_tz()'); 2025-11-30 18:45:24.113 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: input string is too short for datetime format 2025-11-30 18:45:24.113 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy HH24:MI TZH")'); 2025-11-30 18:45:24.113 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.113 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.time()')); 2025-11-30 18:45:24.113 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: input string is too short for datetime format 2025-11-30 18:45:24.113 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34"', '$.datetime("HH24:MI TZH")'); 2025-11-30 18:45:24.113 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.113 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date()')); 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.time_tz()')); 2025-11-30 18:45:24.114 UTC client backend[46523] pg_regress/jsonb ERROR: value too long for type character(2) 2025-11-30 18:45:24.114 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_char2, '{"a": "aaa"}') q; 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.timestamp()')); 2025-11-30 18:45:24.114 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to time without time zone usage 2025-11-30 18:45:24.114 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.114 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.time()'); 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.timestamp_tz()')); 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.time_tz())')); 2025-11-30 18:45:24.114 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.114 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.114 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.timestamp()'); 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.time())')); 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.time())')); 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.time_tz())')); 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.114 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.timestamp_tz())')); 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.timestamp_tz())')); 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.datetime("HH:MI TZH"))')); 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.datetime("HH:MI TZH"))')); 2025-11-30 18:45:24.115 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: datetime format is not recognized: "2017-03-10t12:34:56+3:10" 2025-11-30 18:45:24.115 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use a datetime template argument to specify the input data format. 2025-11-30 18:45:24.115 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2017-03-10t12:34:56+3:10"', '$.datetime()'); 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.datetime("HH:MI TZH"))')); 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.datetime("HH:MI"))')); 2025-11-30 18:45:24.115 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.115 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "a". 2025-11-30 18:45:24.115 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_ia, '{"a": 43.2}') q; 2025-11-30 18:45:24.115 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: datetime format is not recognized: "2017-03-10t12:34:56.789+3:10" 2025-11-30 18:45:24.115 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use a datetime template argument to specify the input data format. 2025-11-30 18:45:24.115 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2017-03-10t12:34:56.789+3:10"', '$.datetime()'); 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.datetime("HH:MI TZH"))')); 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.115 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.datetime("HH:MI"))')); 2025-11-30 18:45:24.116 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.116 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date() < $x' PASSING '12:34'::timetz AS x)); 2025-11-30 18:45:24.116 UTC client backend[46523] pg_regress/jsonb ERROR: malformed JSON array 2025-11-30 18:45:24.116 UTC client backend[46523] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.116 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_ia2, '{"a": [[1], [2, 3]]}') q; 2025-11-30 18:45:24.116 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.116 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date() < $x' PASSING '1234'::int AS x)); 2025-11-30 18:45:24.116 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.116 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp(2) < $.timestamp(3))')); 2025-11-30 18:45:24.116 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from date to timestamptz without time zone usage 2025-11-30 18:45:24.116 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.116 UTC client backend[46526] 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-11-30 18:45:24.116 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from date to timestamptz without time zone usage 2025-11-30 18:45:24.116 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.116 UTC client backend[46526] 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-11-30 18:45:24.116 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from date to timestamptz without time zone usage 2025-11-30 18:45:24.116 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.116 UTC client backend[46526] 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-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to date without time zone usage 2025-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.117 UTC client backend[46526] 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-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to date without time zone usage 2025-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.117 UTC client backend[46526] 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-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to date without time zone usage 2025-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.117 UTC client backend[46526] 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-11-30 18:45:24.117 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.117 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.datetime() < $.datetime())')); 2025-11-30 18:45:24.117 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.117 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.datetime() < $.datetime("HH:MI TZH"))')); 2025-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.117 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.117 UTC client backend[46526] 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-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.118 UTC client backend[46526] 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-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.118 UTC client backend[46526] 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-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timetz to time without time zone usage 2025-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.118 UTC client backend[46526] 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-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timetz to time without time zone usage 2025-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.118 UTC client backend[46526] 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-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timetz to time without time zone usage 2025-11-30 18:45:24.118 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.118 UTC client backend[46526] 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-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timetz to time without time zone usage 2025-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.119 UTC client backend[46526] 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-11-30 18:45:24.119 UTC client backend[46523] pg_regress/jsonb ERROR: domain jsb_i_not_null does not allow null values 2025-11-30 18:45:24.119 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_i_not_null_rec, '{"a": null}') q; 2025-11-30 18:45:24.119 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.119 UTC client backend[46529] 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-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.119 UTC client backend[46526] 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-11-30 18:45:24.119 UTC client backend[46523] pg_regress/jsonb ERROR: value for domain jsb_i_gt_1 violates check constraint "jsb_i_gt_1_check" 2025-11-30 18:45:24.119 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_i_gt_1_rec, '{"a": 1}') q; 2025-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.119 UTC client backend[46526] 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-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.119 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.119 UTC client backend[46526] 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-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.120 UTC client backend[46526] 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-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.120 UTC client backend[46526] 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-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.120 UTC client backend[46526] 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-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from time to timetz without time zone usage 2025-11-30 18:45:24.120 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.120 UTC client backend[46526] 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-11-30 18:45:24.120 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.120 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.datetime() < $x' PASSING '12:34'::timetz AS x)); 2025-11-30 18:45:24.121 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.121 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.121 UTC client backend[46526] 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-11-30 18:45:24.121 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.121 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.121 UTC client backend[46526] 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-11-30 18:45:24.121 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.121 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.121 UTC client backend[46526] 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-11-30 18:45:24.121 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.121 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.datetime() ? (@ == $x)' PASSING '12:34'::time AS x)); 2025-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.122 UTC client backend[46526] 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-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.122 UTC client backend[46526] 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-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.122 UTC client backend[46526] 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-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-11-30 18:45:24.122 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.122 UTC client backend[46526] 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-11-30 18:45:24.122 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.122 UTC client backend[46529] 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-11-30 18:45:24.123 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.123 UTC client backend[46529] 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-11-30 18:45:24.123 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.123 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.123 UTC client backend[46526] 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-11-30 18:45:24.123 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.123 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.123 UTC client backend[46526] 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-11-30 18:45:24.123 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.123 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.123 UTC client backend[46526] 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-11-30 18:45:24.123 UTC client backend[46523] pg_regress/jsonb ERROR: could not determine row type for result of jsonb_populate_record 2025-11-30 18:45:24.123 UTC client backend[46523] pg_regress/jsonb HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-11-30 18:45:24.123 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_record(null::record, '{"x": 0, "y": 1}'); 2025-11-30 18:45:24.124 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-11-30 18:45:24.124 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_VALUE(js, '$' DEFAULT random()::int ON ERROR)); 2025-11-30 18:45:24.124 UTC client backend[46523] pg_regress/jsonb ERROR: value for domain jb_ordered_pair violates check constraint "jb_ordered_pair_check" 2025-11-30 18:45:24.124 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_record(row(1,2)::jb_ordered_pair, '{"x": 1, "y": 0}'); 2025-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.124 UTC client backend[46526] 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-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.124 UTC client backend[46526] 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-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.124 UTC client backend[46526] 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-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-11-30 18:45:24.124 UTC client backend[46526] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-11-30 18:45:24.124 UTC client backend[46526] 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-11-30 18:45:24.124 UTC client backend[46523] pg_regress/jsonb ERROR: invalid input syntax for type timestamp: "[100, 200, 300]" 2025-11-30 18:45:24.124 UTC client backend[46523] 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-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: DEFAULT expression must not return a set at character 50 2025-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT ret_setint() ON ERROR) FROM test_jsonb_mutability; 2025-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: DEFAULT expression must not contain column references at character 50 2025-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT b + 1 ON ERROR) FROM test_jsonb_mutability; 2025-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 50 2025-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT sum(1) over() ON ERROR) FROM test_jsonb_mutability; 2025-11-30 18:45:24.125 UTC client backend[46523] pg_regress/jsonb ERROR: could not determine row type for result of jsonb_populate_recordset 2025-11-30 18:45:24.125 UTC client backend[46523] pg_regress/jsonb HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-11-30 18:45:24.125 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_recordset(null::record, '[{"x": 0, "y": 1}]'); 2025-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 50 2025-11-30 18:45:24.125 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT (SELECT 1) ON ERROR) FROM test_jsonb_mutability; 2025-11-30 18:45:24.125 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: could not find jsonpath variable "undefined_var" 2025-11-30 18:45:24.125 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_query('[{"a": 1}]', '$undefined_var'); 2025-11-30 18:45:24.125 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: JSON object does not contain key "a" 2025-11-30 18:45:24.125 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_query_array('[{"a": 1}, {"a": 2}, {}]', 'strict $[*].a'); 2025-11-30 18:45:24.125 UTC client backend[46523] pg_regress/jsonb ERROR: could not determine row type for result of jsonb_populate_recordset 2025-11-30 18:45:24.125 UTC client backend[46523] pg_regress/jsonb HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-11-30 18:45:24.125 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_recordset(null::record, '[]'); 2025-11-30 18:45:24.126 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: JSON object does not contain key "a" 2025-11-30 18:45:24.126 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_query_first('[{"a": 1}, {"a": 2}, {}]', 'strict $[*].a'); 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb ERROR: value for domain jb_ordered_pair violates check constraint "jb_ordered_pair_check" 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_recordset(row(1,2)::jb_ordered_pair, '[{"x": 1, "y": 0}]'); 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb DETAIL: Returned row contains 1 attribute, but query expects 2. 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_populate_recordset(row(0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-11-30 18:45:24.126 UTC client backend[46523] 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-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb DETAIL: Returned row contains 3 attributes, but query expects 2. 2025-11-30 18:45:24.126 UTC client backend[46523] 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-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-11-30 18:45:24.126 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_populate_recordset(row(1000000000::int,50::int),'[{"b":"2"},{"a":"3"}]') q (a text, b text); 2025-11-30 18:45:24.126 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: could not find jsonpath variable "undefined_var" 2025-11-30 18:45:24.126 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_query_first('[{"a": 1}]', '$undefined_var'); 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: could not find jsonpath variable "undefined_var" 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_exists('[{"a": 1}]', '$undefined_var'); 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb HINT: See the value of key "ia". 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_to_record('{"ia": 123}') as x(ia _int4); 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: single boolean result is expected 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('1', '$', silent => false); 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: single boolean result is expected 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('"a"', '$', silent => false); 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb ERROR: expected JSON array 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb HINT: See the array element [1] of key "ia". 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_to_record('{"ia": [[1], 2]}') as x(ia _int4); 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: single boolean result is expected 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('{}', '$', silent => false); 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb ERROR: malformed JSON array 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-11-30 18:45:24.127 UTC client backend[46523] pg_regress/jsonb STATEMENT: select * from jsonb_to_record('{"ia": [[1], [2, 3]]}') as x(ia _int4); 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: single boolean result is expected 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('[true]', '$', silent => false); 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: single boolean result is expected 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('{}', 'lax $.a', silent => false); 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: JSON object does not contain key "a" 2025-11-30 18:45:24.127 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('{}', 'strict $.a', silent => false); 2025-11-30 18:45:24.128 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: single boolean result is expected 2025-11-30 18:45:24.128 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('[true, true]', '$[*]', silent => false); 2025-11-30 18:45:24.128 UTC client backend[46526] pg_regress/jsonb_jsonpath ERROR: could not find jsonpath variable "undefined_var" 2025-11-30 18:45:24.128 UTC client backend[46526] pg_regress/jsonb_jsonpath STATEMENT: SELECT jsonb_path_match('[{"a": 1}]', '$undefined_var'); 2025-11-30 18:45:24.130 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON EMPTY expression (DEFAULT) to the RETURNING type 2025-11-30 18:45:24.130 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: value for domain queryfuncs_test_domain violates check constraint "queryfuncs_test_domain_check" 2025-11-30 18:45:24.130 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '{"d1": "H"}', '$.a2' RETURNING queryfuncs_test_domain DEFAULT 'foo'::queryfuncs_test_domain ON EMPTY); 2025-11-30 18:45:24.130 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 55 2025-11-30 18:45:24.130 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int DEFAULT (SELECT '"1"')::jsonb ON ERROR); 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 73 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING queryfuncs_test_domain DEFAULT (select '"1"')::queryfuncs_test_domain ON ERROR); 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 55 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int DEFAULT (SELECT 1)::oid::int ON ERROR); 2025-11-30 18:45:24.131 UTC client backend[46526] pg_regress/jsonb_jsonpath LOG: disconnection: session time: 0:00:00.145 user=postgres database=regression host=[local] 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 57 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int[] DEFAULT (SELECT '{1}')::oid[]::int[] ON ERROR); 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 57 2025-11-30 18:45:24.131 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int[] DEFAULT (SELECT '{1}')::text COLLATE "C" ON ERROR); 2025-11-30 18:45:24.132 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 62 2025-11-30 18:45:24.132 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING someparent DEFAULT (SELECT '(1)')::somechild::someparent ON ERROR); 2025-11-30 18:45:24.135 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: JSON path expression must be of type jsonpath, not of type date at character 40 2025-11-30 18:45:24.135 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '{"a": 123}', ('$' || '.' || 'a' || NULL)::date WITH WRAPPER); 2025-11-30 18:45:24.135 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: syntax error at or near " " of jsonpath input 2025-11-30 18:45:24.135 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '{"a": 123}', 'error' || ' ' || 'error'); 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: JSON path expression must be of type jsonpath, not of type jsonpaths at character 28 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT json_value('"aaa"', jsonpaths RETURNING json) FROM jsonpaths; 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not find jsonpath variable "xyz" 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb 'null', '$xyz' PASSING 1 AS xy); 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not find jsonpath variable "xy" 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb 'null', '$xy' PASSING 1 AS xyz); 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not find jsonpath variable "Xyz" 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb 'null', '$Xyz' PASSING 1 AS Xyz); 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid ON ERROR behavior at character 35 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Only ERROR, TRUE, FALSE, or UNKNOWN is allowed in ON ERROR for JSON_EXISTS(). 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_EXISTS(jsonb '1', '$' DEFAULT 1 ON ERROR); 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid ON ERROR behavior at character 34 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Only ERROR, NULL, or DEFAULT expression is allowed in ON ERROR for JSON_VALUE(). 2025-11-30 18:45:24.138 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', '$' EMPTY ON ERROR); 2025-11-30 18:45:24.139 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: invalid ON ERROR behavior at character 34 2025-11-30 18:45:24.139 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: Only ERROR, NULL, EMPTY ARRAY, EMPTY OBJECT, or DEFAULT expression is allowed in ON ERROR for JSON_QUERY(). 2025-11-30 18:45:24.139 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '1', '$' TRUE ON ERROR); 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '123', '$' RETURNING queryfuncs_char2 ERROR ON ERROR); 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '123', '$' RETURNING queryfuncs_char2_chk ERROR ON ERROR); 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '123', '$' RETURNING queryfuncs_char2 ERROR ON ERROR); 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-11-30 18:45:24.140 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '123', '$' RETURNING queryfuncs_char2_chk ERROR ON ERROR); 2025-11-30 18:45:24.142 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: bit string too long for type bit varying(3) 2025-11-30 18:45:24.142 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1234', '$' RETURNING queryfuncs_d_varbit3 DEFAULT '111111' ON ERROR); 2025-11-30 18:45:24.142 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (DEFAULT) to the RETURNING type 2025-11-30 18:45:24.142 UTC client backend[46529] pg_regress/sqljson_queryfuncs DETAIL: value for domain queryfuncs_d_varbit3 violates check constraint "queryfuncs_d_varbit3_check" 2025-11-30 18:45:24.142 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1234', '$' RETURNING queryfuncs_d_varbit3 DEFAULT '01' ON ERROR); 2025-11-30 18:45:24.143 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: bit string length 3 does not match type bit(2) 2025-11-30 18:45:24.143 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"111"', '$' RETURNING bit(2) ERROR ON ERROR); 2025-11-30 18:45:24.143 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: cannot cast behavior expression of type integer to bit at character 63 2025-11-30 18:45:24.143 UTC client backend[46529] pg_regress/sqljson_queryfuncs HINT: You will need to explicitly cast the expression to type bit. 2025-11-30 18:45:24.143 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1234', '$' RETURNING bit(3) DEFAULT 1 ON ERROR); 2025-11-30 18:45:24.143 UTC client backend[46529] pg_regress/sqljson_queryfuncs ERROR: bit string length 4 does not match type bit(3) 2025-11-30 18:45:24.143 UTC client backend[46529] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"111"', '$.a' RETURNING bit(3) DEFAULT '1111' ON EMPTY); 2025-11-30 18:45:24.145 UTC client backend[46529] pg_regress/sqljson_queryfuncs LOG: disconnection: session time: 0:00:00.152 user=postgres database=regression host=[local] 2025-11-30 18:45:24.229 UTC client backend[46523] pg_regress/jsonb ERROR: path element at position 2 is null 2025-11-30 18:45:24.229 UTC client backend[46523] 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-11-30 18:45:24.230 UTC client backend[46523] pg_regress/jsonb ERROR: path element at position 2 is null 2025-11-30 18:45:24.230 UTC client backend[46523] 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-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb ERROR: path element at position 2 is not an integer: "-1e" 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '{"n":null, "a":1, "b":[1,2], "c":{"1":2}, "d":{"1":[2,3]}}'::jsonb #- '{b,-1e}'; 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb ERROR: cannot delete from scalar 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '"a"'::jsonb - 'a'; 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb ERROR: cannot delete from scalar 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '"a"'::jsonb - 1; 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb ERROR: cannot delete from object using integer index 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '{}'::jsonb - 1; 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb ERROR: cannot delete path in scalar 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '"a"'::jsonb #- '{a}'; 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb ERROR: cannot set path in scalar 2025-11-30 18:45:24.231 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_set('"a"','{a}','"b"'); 2025-11-30 18:45:24.232 UTC client backend[46523] pg_regress/jsonb ERROR: path element at position 2 is not an integer: "non_integer" 2025-11-30 18:45:24.232 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_set('{"a": [1, 2, 3]}', '{a, non_integer}', '"new_value"'); 2025-11-30 18:45:24.232 UTC client backend[46523] pg_regress/jsonb ERROR: path element at position 3 is not an integer: "non_integer" 2025-11-30 18:45:24.232 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_set('{"a": {"b": [1, 2, 3]}}', '{a, b, non_integer}', '"new_value"'); 2025-11-30 18:45:24.232 UTC client backend[46523] pg_regress/jsonb ERROR: path element at position 3 is null 2025-11-30 18:45:24.232 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_set('{"a": {"b": [1, 2, 3]}}', '{a, b, NULL}', '"new_value"'); 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb ERROR: null_value_treatment must be "delete_key", "return_target", "use_json_null", or "raise_exception" 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, true, null); 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb ERROR: null_value_treatment must be "delete_key", "return_target", "use_json_null", or "raise_exception" 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, true, 'no_such_treatment'); 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb ERROR: JSON value must not be null 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb DETAIL: Exception was raised because null_value_treatment is "raise_exception". 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb HINT: To avoid, either change the null_value_treatment argument or ensure that an SQL NULL is not passed. 2025-11-30 18:45:24.233 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, null_value_treatment => 'raise_exception') as raise_exception; 2025-11-30 18:45:24.235 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.235 UTC client backend[46523] pg_regress/jsonb HINT: Try using the function jsonb_set to replace key value. 2025-11-30 18:45:24.235 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_insert('{"a": {"b": "value"}}', '{a, b}', '"new_value"'); 2025-11-30 18:45:24.235 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.235 UTC client backend[46523] pg_regress/jsonb HINT: Try using the function jsonb_set to replace key value. 2025-11-30 18:45:24.235 UTC client backend[46523] pg_regress/jsonb STATEMENT: select jsonb_insert('{"a": {"b": "value"}}', '{a, b}', '"new_value"', true); 2025-11-30 18:45:24.236 UTC client backend[46523] pg_regress/jsonb ERROR: subscript type numeric is not supported at character 34 2025-11-30 18:45:24.236 UTC client backend[46523] pg_regress/jsonb HINT: jsonb subscript must be coercible to either integer or text. 2025-11-30 18:45:24.236 UTC client backend[46523] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[1.0]; 2025-11-30 18:45:24.236 UTC client backend[46523] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 32 2025-11-30 18:45:24.236 UTC client backend[46523] pg_regress/jsonb STATEMENT: select ('{"a": 1}'::jsonb)['a':'b']; 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 36 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[1:2]; 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 35 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[:2]; 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 34 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[1:]; 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb ERROR: jsonb subscript does not support slices 2025-11-30 18:45:24.237 UTC client backend[46523] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[:]; 2025-11-30 18:45:24.241 UTC client backend[46523] pg_regress/jsonb ERROR: jsonb subscript in assignment must not be null 2025-11-30 18:45:24.241 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[NULL] = '1'; 2025-11-30 18:45:24.244 UTC client backend[46523] pg_regress/jsonb ERROR: path element at position 1 is out of range: -8 2025-11-30 18:45:24.244 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[-8] = '1'; 2025-11-30 18:45:24.253 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.253 UTC client backend[46523] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-11-30 18:45:24.253 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a']['b'] = '1'; 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a']['b']['c'] = '1'; 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a'][0] = '1'; 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a'][0]['c'] = '1'; 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-11-30 18:45:24.254 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a'][0][0] = '1'; 2025-11-30 18:45:24.255 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.255 UTC client backend[46523] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-11-30 18:45:24.255 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[0] = '1'; 2025-11-30 18:45:24.255 UTC client backend[46523] pg_regress/jsonb ERROR: cannot replace existing key 2025-11-30 18:45:24.255 UTC client backend[46523] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-11-30 18:45:24.255 UTC client backend[46523] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[0][0] = '1'; 2025-11-30 18:45:24.262 UTC client backend[46523] pg_regress/jsonb ERROR: wrong flag in flag array: "" 2025-11-30 18:45:24.262 UTC client backend[46523] pg_regress/jsonb HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-11-30 18:45:24.262 UTC client backend[46523] 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-11-30 18:45:24.262 UTC client backend[46523] pg_regress/jsonb ERROR: wrong flag type, only arrays and scalars are allowed 2025-11-30 18:45:24.262 UTC client backend[46523] 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-11-30 18:45:24.262 UTC client backend[46523] pg_regress/jsonb ERROR: flag array element is not a string 2025-11-30 18:45:24.262 UTC client backend[46523] pg_regress/jsonb HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-11-30 18:45:24.262 UTC client backend[46523] 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-11-30 18:45:24.262 UTC client backend[46523] pg_regress/jsonb ERROR: flag array element is not a string 2025-11-30 18:45:24.262 UTC client backend[46523] pg_regress/jsonb HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-11-30 18:45:24.262 UTC client backend[46523] 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-11-30 18:45:24.263 UTC client backend[46523] pg_regress/jsonb ERROR: cannot cast jsonb array to type boolean 2025-11-30 18:45:24.263 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '[]'::jsonb::bool; 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb ERROR: cannot cast jsonb array to type double precision 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '[1.0]'::jsonb::float; 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb ERROR: cannot cast jsonb array to type real 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '[1.0]'::jsonb::float4; 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb ERROR: cannot cast jsonb string to type smallint 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '"hello"'::jsonb::int2; 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb ERROR: cannot cast jsonb string to type integer 2025-11-30 18:45:24.264 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '"hello"'::jsonb::int4; 2025-11-30 18:45:24.265 UTC client backend[46523] pg_regress/jsonb ERROR: cannot cast jsonb string to type bigint 2025-11-30 18:45:24.265 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '"hello"'::jsonb::int8; 2025-11-30 18:45:24.265 UTC client backend[46523] pg_regress/jsonb ERROR: cannot cast jsonb object to type numeric 2025-11-30 18:45:24.265 UTC client backend[46523] pg_regress/jsonb STATEMENT: select '{}'::jsonb::numeric; 2025-11-30 18:45:24.271 UTC client backend[46523] pg_regress/jsonb LOG: disconnection: session time: 0:00:00.286 user=postgres database=regression host=[local] 2025-11-30 18:45:24.286 UTC unrecognized[46565] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.286 UTC unrecognized[46566] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.286 UTC client backend[46565] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.286 UTC client backend[46565] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/limit 2025-11-30 18:45:24.287 UTC client backend[46565] pg_regress/limit LOG: connection ready: setup total=8.342 ms, fork=6.688 ms, authentication=0.149 ms 2025-11-30 18:45:24.288 UTC client backend[46566] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.288 UTC client backend[46566] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/alter_table 2025-11-30 18:45:24.289 UTC client backend[46566] pg_regress/alter_table LOG: connection ready: setup total=8.236 ms, fork=5.191 ms, authentication=0.115 ms 2025-11-30 18:45:24.292 UTC unrecognized[46572] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.292 UTC unrecognized[46569] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.292 UTC client backend[46572] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.292 UTC client backend[46572] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rangefuncs 2025-11-30 18:45:24.292 UTC client backend[46569] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.292 UTC client backend[46569] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/plancache 2025-11-30 18:45:24.293 UTC client backend[46572] pg_regress/rangefuncs LOG: connection ready: setup total=8.723 ms, fork=1.382 ms, authentication=0.107 ms 2025-11-30 18:45:24.293 UTC client backend[46569] pg_regress/plancache LOG: connection ready: setup total=10.823 ms, fork=6.076 ms, authentication=0.113 ms 2025-11-30 18:45:24.293 UTC unrecognized[46573] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.293 UTC unrecognized[46570] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.294 UTC unrecognized[46567] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.294 UTC client backend[46573] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.294 UTC client backend[46573] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/prepare 2025-11-30 18:45:24.294 UTC client backend[46570] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.294 UTC client backend[46570] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/domain 2025-11-30 18:45:24.294 UTC client backend[46567] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.294 UTC client backend[46567] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/temp 2025-11-30 18:45:24.295 UTC client backend[46573] pg_regress/prepare LOG: connection ready: setup total=9.163 ms, fork=7.767 ms, authentication=0.107 ms 2025-11-30 18:45:24.295 UTC client backend[46570] pg_regress/domain LOG: connection ready: setup total=12.074 ms, fork=8.819 ms, authentication=0.111 ms 2025-11-30 18:45:24.295 UTC client backend[46567] pg_regress/temp LOG: connection ready: setup total=13.647 ms, fork=7.197 ms, authentication=0.112 ms 2025-11-30 18:45:24.295 UTC unrecognized[46571] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.295 UTC client backend[46571] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.295 UTC client backend[46571] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sequence 2025-11-30 18:45:24.296 UTC client backend[46571] pg_regress/sequence LOG: connection ready: setup total=12.068 ms, fork=7.485 ms, authentication=0.117 ms 2025-11-30 18:45:24.296 UTC unrecognized[46578] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.297 UTC unrecognized[46568] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.297 UTC client backend[46578] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.297 UTC client backend[46578] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copy2 2025-11-30 18:45:24.297 UTC client backend[46568] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.297 UTC client backend[46568] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/plpgsql 2025-11-30 18:45:24.298 UTC client backend[46578] pg_regress/copy2 LOG: connection ready: setup total=6.541 ms, fork=0.750 ms, authentication=0.107 ms 2025-11-30 18:45:24.298 UTC unrecognized[46575] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.298 UTC client backend[46575] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.298 UTC client backend[46575] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/returning 2025-11-30 18:45:24.298 UTC client backend[46568] pg_regress/plpgsql LOG: connection ready: setup total=16.695 ms, fork=14.227 ms, authentication=0.101 ms 2025-11-30 18:45:24.299 UTC client backend[46575] pg_regress/returning LOG: connection ready: setup total=8.645 ms, fork=4.514 ms, authentication=0.104 ms 2025-11-30 18:45:24.299 UTC unrecognized[46577] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.299 UTC unrecognized[46579] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.300 UTC client backend[46577] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.300 UTC client backend[46577] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/xml 2025-11-30 18:45:24.300 UTC client backend[46579] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.300 UTC client backend[46579] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/with 2025-11-30 18:45:24.301 UTC client backend[46577] pg_regress/xml LOG: connection ready: setup total=9.624 ms, fork=4.117 ms, authentication=0.110 ms 2025-11-30 18:45:24.301 UTC client backend[46579] pg_regress/with LOG: connection ready: setup total=9.293 ms, fork=3.687 ms, authentication=0.117 ms 2025-11-30 18:45:24.301 UTC client backend[46571] pg_regress/sequence ERROR: INCREMENT must not be zero 2025-11-30 18:45:24.301 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx INCREMENT BY 0; 2025-11-30 18:45:24.301 UTC unrecognized[46580] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.301 UTC client backend[46580] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.301 UTC client backend[46580] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/conversion 2025-11-30 18:45:24.302 UTC unrecognized[46581] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.302 UTC client backend[46581] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.302 UTC client backend[46581] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/largeobject 2025-11-30 18:45:24.302 UTC unrecognized[46574] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.302 UTC unrecognized[46582] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.303 UTC client backend[46574] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.303 UTC client backend[46574] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/truncate 2025-11-30 18:45:24.303 UTC client backend[46580] pg_regress/conversion LOG: connection ready: setup total=10.982 ms, fork=4.648 ms, authentication=0.106 ms 2025-11-30 18:45:24.303 UTC client backend[46582] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.303 UTC client backend[46582] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/polymorphism 2025-11-30 18:45:24.303 UTC client backend[46581] pg_regress/largeobject LOG: connection ready: setup total=7.637 ms, fork=2.997 ms, authentication=0.102 ms 2025-11-30 18:45:24.304 UTC client backend[46574] pg_regress/truncate LOG: connection ready: setup total=13.376 ms, fork=5.617 ms, authentication=0.107 ms 2025-11-30 18:45:24.304 UTC unrecognized[46576] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.304 UTC client backend[46582] pg_regress/polymorphism LOG: connection ready: setup total=7.946 ms, fork=4.898 ms, authentication=0.101 ms 2025-11-30 18:45:24.304 UTC client backend[46576] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.304 UTC client backend[46576] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rowtypes 2025-11-30 18:45:24.305 UTC client backend[46571] pg_regress/sequence ERROR: MINVALUE (20) must be less than MAXVALUE (-1) 2025-11-30 18:45:24.305 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx INCREMENT BY -1 MINVALUE 20; 2025-11-30 18:45:24.306 UTC client backend[46566] pg_regress/alter_table ERROR: relation "attmp_wrong" does not exist 2025-11-30 18:45:24.306 UTC client backend[46566] pg_regress/alter_table STATEMENT: COMMENT ON TABLE attmp_wrong IS 'table comment'; 2025-11-30 18:45:24.306 UTC client backend[46573] pg_regress/prepare ERROR: prepared statement "q1" already exists 2025-11-30 18:45:24.306 UTC client backend[46573] pg_regress/prepare STATEMENT: PREPARE q1 AS SELECT 2; 2025-11-30 18:45:24.308 UTC client backend[46582] pg_regress/polymorphism ERROR: operator does not exist: point + integer at character 13 2025-11-30 18:45:24.308 UTC client backend[46582] pg_regress/polymorphism DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:24.308 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.308 UTC client backend[46582] pg_regress/polymorphism QUERY: select x + 1 2025-11-30 18:45:24.308 UTC client backend[46582] pg_regress/polymorphism CONTEXT: SQL function "polyf" during inlining 2025-11-30 18:45:24.308 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(point(3,4)); 2025-11-30 18:45:24.308 UTC client backend[46571] pg_regress/sequence ERROR: MINVALUE (1) must be less than MAXVALUE (-20) 2025-11-30 18:45:24.308 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx INCREMENT BY 1 MAXVALUE -20; 2025-11-30 18:45:24.309 UTC client backend[46571] pg_regress/sequence ERROR: START value (10) cannot be greater than MAXVALUE (-1) 2025-11-30 18:45:24.309 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx INCREMENT BY -1 START 10; 2025-11-30 18:45:24.310 UTC client backend[46571] pg_regress/sequence ERROR: START value (-10) cannot be less than MINVALUE (1) 2025-11-30 18:45:24.310 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx INCREMENT BY 1 START -10; 2025-11-30 18:45:24.311 UTC client backend[46576] pg_regress/rowtypes LOG: connection ready: setup total=19.812 ms, fork=5.149 ms, authentication=0.105 ms 2025-11-30 18:45:24.313 UTC client backend[46566] pg_regress/alter_table ERROR: column name "xmin" conflicts with a system column name 2025-11-30 18:45:24.313 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp ADD COLUMN xmin integer; 2025-11-30 18:45:24.314 UTC client backend[46570] pg_regress/domain ERROR: cannot drop type domaindroptest because other objects depend on it 2025-11-30 18:45:24.314 UTC client backend[46570] pg_regress/domain DETAIL: type dependenttypetest depends on type domaindroptest 2025-11-30 18:45:24.314 UTC client backend[46570] pg_regress/domain HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:24.314 UTC client backend[46570] pg_regress/domain STATEMENT: drop domain domaindroptest; 2025-11-30 18:45:24.315 UTC client backend[46571] pg_regress/sequence ERROR: CACHE (0) must be greater than zero 2025-11-30 18:45:24.315 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx CACHE 0; 2025-11-30 18:45:24.317 UTC client backend[46570] pg_regress/domain ERROR: type "domaindroptest" does not exist 2025-11-30 18:45:24.317 UTC client backend[46570] pg_regress/domain STATEMENT: drop domain domaindroptest cascade; 2025-11-30 18:45:24.318 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine element type of "anyarray" argument 2025-11-30 18:45:24.318 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(stavalues1) from pg_statistic; 2025-11-30 18:45:24.319 UTC client backend[46570] pg_regress/domain ERROR: type "no_such_type" does not exist at character 25 2025-11-30 18:45:24.319 UTC client backend[46570] pg_regress/domain STATEMENT: create domain d_fail as no_such_type; 2025-11-30 18:45:24.319 UTC client backend[46571] pg_regress/sequence ERROR: invalid OWNED BY option 2025-11-30 18:45:24.319 UTC client backend[46571] pg_regress/sequence HINT: Specify OWNED BY table.column or OWNED BY NONE. 2025-11-30 18:45:24.319 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx OWNED BY nobody; 2025-11-30 18:45:24.320 UTC client backend[46570] pg_regress/domain ERROR: foreign key constraints not possible for domains at character 29 2025-11-30 18:45:24.320 UTC client backend[46570] pg_regress/domain STATEMENT: create domain d_fail as int constraint cc REFERENCES this_table_not_exists(i); 2025-11-30 18:45:24.321 UTC client backend[46570] pg_regress/domain ERROR: not-null constraints for domains cannot be marked NO INHERIT at character 30 2025-11-30 18:45:24.321 UTC client backend[46570] pg_regress/domain STATEMENT: create domain d_fail as int4 not null no inherit; 2025-11-30 18:45:24.321 UTC client backend[46571] pg_regress/sequence ERROR: sequence cannot be owned by relation "pg_class_oid_index" 2025-11-30 18:45:24.321 UTC client backend[46571] pg_regress/sequence DETAIL: This operation is not supported for indexes. 2025-11-30 18:45:24.321 UTC client backend[46571] pg_regress/sequence STATEMENT: CREATE SEQUENCE sequence_testx OWNED BY pg_class_oid_index.oid; 2025-11-30 18:45:24.323 UTC client backend[46570] pg_regress/domain ERROR: conflicting NULL/NOT NULL constraints at character 39 2025-11-30 18:45:24.323 UTC client backend[46570] pg_regress/domain STATEMENT: create domain d_fail as int4 not null null; 2025-11-30 18:45:24.324 UTC client backend[46580] pg_regress/conversion ERROR: conversion "myconv" already exists 2025-11-30 18:45:24.324 UTC client backend[46580] pg_regress/conversion STATEMENT: CREATE CONVERSION myconv FOR 'LATIN1' TO 'UTF8' FROM iso8859_1_to_utf8; 2025-11-30 18:45:24.325 UTC client backend[46569] pg_regress/plancache ERROR: relation "pcachetest" does not exist at character 35 2025-11-30 18:45:24.325 UTC client backend[46569] pg_regress/plancache STATEMENT: EXECUTE prepstmt; 2025-11-30 18:45:24.325 UTC client backend[46582] pg_regress/polymorphism ERROR: return type anyarray is not supported for SQL functions 2025-11-30 18:45:24.325 UTC client backend[46582] pg_regress/polymorphism CONTEXT: SQL function "polyf" during inlining 2025-11-30 18:45:24.325 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(stavalues1) from pg_statistic; 2025-11-30 18:45:24.325 UTC client backend[46570] pg_regress/domain ERROR: multiple default expressions at character 49 2025-11-30 18:45:24.325 UTC client backend[46570] pg_regress/domain STATEMENT: create domain d_fail as int4 not null default 3 default 3; 2025-11-30 18:45:24.326 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content at character 32 2025-11-30 18:45:24.326 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Couldn't find end of Start Tag wrong line 1 1) no inherit; 2025-11-30 18:45:24.338 UTC client backend[46576] pg_regress/rowtypes ERROR: malformed record literal: "[]" at character 8 2025-11-30 18:45:24.338 UTC client backend[46576] pg_regress/rowtypes DETAIL: Missing left parenthesis. 2025-11-30 18:45:24.338 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select '[]'::fullname; 2025-11-30 18:45:24.339 UTC client backend[46570] pg_regress/domain ERROR: specifying constraint deferrability not supported for domains at character 63 2025-11-30 18:45:24.339 UTC client backend[46570] pg_regress/domain STATEMENT: create domain d_fail as int4 constraint cc check (values > 1) deferrable; 2025-11-30 18:45:24.341 UTC client backend[46578] pg_regress/copy2 ERROR: column "xyz" of relation "x" does not exist 2025-11-30 18:45:24.341 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x (xyz) from stdin; 2025-11-30 18:45:24.342 UTC client backend[46576] pg_regress/rowtypes ERROR: malformed record literal: "(Joe,Blow) /" at character 8 2025-11-30 18:45:24.342 UTC client backend[46576] pg_regress/rowtypes DETAIL: Junk after right parenthesis. 2025-11-30 18:45:24.342 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select '(Joe,Blow) /'::fullname; 2025-11-30 18:45:24.342 UTC client backend[46573] pg_regress/prepare ERROR: wrong number of parameters for prepared statement "q3" 2025-11-30 18:45:24.342 UTC client backend[46573] pg_regress/prepare DETAIL: Expected 5 parameters but got 1. 2025-11-30 18:45:24.342 UTC client backend[46573] pg_regress/prepare STATEMENT: EXECUTE q3('bool'); 2025-11-30 18:45:24.343 UTC client backend[46573] pg_regress/prepare ERROR: wrong number of parameters for prepared statement "q3" 2025-11-30 18:45:24.343 UTC client backend[46573] pg_regress/prepare DETAIL: Expected 5 parameters but got 6. 2025-11-30 18:45:24.343 UTC client backend[46573] pg_regress/prepare STATEMENT: EXECUTE q3('bytea', 5::smallint, 10.5::float, false, 4::bigint, true); 2025-11-30 18:45:24.343 UTC client backend[46573] pg_regress/prepare ERROR: parameter $3 of type boolean cannot be coerced to the expected type double precision at character 38 2025-11-30 18:45:24.343 UTC client backend[46573] pg_regress/prepare HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:24.343 UTC client backend[46573] pg_regress/prepare STATEMENT: EXECUTE q3(5::smallint, 10.5::float, false, 4::bigint, 'bytea'); 2025-11-30 18:45:24.344 UTC client backend[46582] pg_regress/polymorphism ERROR: function polyf(int4range, integer, numeric) does not exist at character 8 2025-11-30 18:45:24.344 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.344 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.344 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(int4range(42, 49), 11, 4.5) as fail; 2025-11-30 18:45:24.344 UTC client backend[46573] pg_regress/prepare ERROR: type "nonexistenttype" does not exist at character 12 2025-11-30 18:45:24.344 UTC client backend[46573] pg_regress/prepare STATEMENT: PREPARE q4(nonexistenttype) AS SELECT $1; 2025-11-30 18:45:24.347 UTC client backend[46582] pg_regress/polymorphism ERROR: function polyf(int4multirange, integer, numeric) does not exist at character 8 2025-11-30 18:45:24.347 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.347 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.347 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(multirange(int4range(42, 49)), 11, 4.5) as fail; 2025-11-30 18:45:24.352 UTC client backend[46574] pg_regress/truncate ERROR: cannot truncate a table referenced in a foreign key constraint 2025-11-30 18:45:24.352 UTC client backend[46574] pg_regress/truncate DETAIL: Table "trunc_b" references "truncate_a". 2025-11-30 18:45:24.352 UTC client backend[46574] pg_regress/truncate HINT: Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE. 2025-11-30 18:45:24.352 UTC client backend[46574] pg_regress/truncate STATEMENT: TRUNCATE TABLE truncate_a; 2025-11-30 18:45:24.352 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine result data type 2025-11-30 18:45:24.352 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-30 18:45:24.352 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function polyf(x anycompatible) returns anycompatiblerange as $$ select array[x + 1, x + 2] $$ language sql; 2025-11-30 18:45:24.352 UTC client backend[46577] pg_regress/xml ERROR: invalid XML comment 2025-11-30 18:45:24.352 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlcomment('test-'); 2025-11-30 18:45:24.353 UTC client backend[46577] pg_regress/xml ERROR: invalid XML comment 2025-11-30 18:45:24.353 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlcomment('--test'); 2025-11-30 18:45:24.353 UTC client backend[46569] pg_regress/plancache ERROR: cached plan must not change result type 2025-11-30 18:45:24.353 UTC client backend[46569] pg_regress/plancache STATEMENT: EXECUTE prepstmt; 2025-11-30 18:45:24.354 UTC unrecognized[46583] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.354 UTC client backend[46583] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.354 UTC client backend[46583] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/temp 2025-11-30 18:45:24.354 UTC client backend[46574] pg_regress/truncate ERROR: cannot truncate a table referenced in a foreign key constraint 2025-11-30 18:45:24.354 UTC client backend[46574] pg_regress/truncate DETAIL: Table "trunc_e" references "truncate_a". 2025-11-30 18:45:24.354 UTC client backend[46574] pg_regress/truncate HINT: Truncate table "trunc_e" at the same time, or use TRUNCATE ... CASCADE. 2025-11-30 18:45:24.354 UTC client backend[46574] pg_regress/truncate STATEMENT: TRUNCATE TABLE truncate_a,trunc_b; 2025-11-30 18:45:24.355 UTC client backend[46583] pg_regress/temp LOG: connection ready: setup total=7.031 ms, fork=4.416 ms, authentication=0.122 ms 2025-11-30 18:45:24.356 UTC client backend[46567] pg_regress/temp LOG: disconnection: session time: 0:00:00.067 user=postgres database=regression host=[local] 2025-11-30 18:45:24.357 UTC client backend[46578] pg_regress/copy2 ERROR: conflicting or redundant options at character 32 2025-11-30 18:45:24.357 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format CSV, FORMAT CSV); 2025-11-30 18:45:24.357 UTC client backend[46574] pg_regress/truncate ERROR: cannot truncate a table referenced in a foreign key constraint 2025-11-30 18:45:24.357 UTC client backend[46574] pg_regress/truncate DETAIL: Table "trunc_b" references "truncate_a". 2025-11-30 18:45:24.357 UTC client backend[46574] pg_regress/truncate HINT: Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE. 2025-11-30 18:45:24.357 UTC client backend[46574] pg_regress/truncate STATEMENT: TRUNCATE TABLE truncate_a,trunc_e; 2025-11-30 18:45:24.358 UTC client backend[46577] pg_regress/xml ERROR: argument of XMLCONCAT must be type xml, not type integer at character 18 2025-11-30 18:45:24.358 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlconcat(1, 2); 2025-11-30 18:45:24.359 UTC client backend[46569] pg_regress/plancache ERROR: cached plan must not change result type 2025-11-30 18:45:24.359 UTC client backend[46569] pg_regress/plancache STATEMENT: EXECUTE prepstmt2(123); 2025-11-30 18:45:24.359 UTC client backend[46583] pg_regress/temp ERROR: relation "temptest" does not exist at character 15 2025-11-30 18:45:24.359 UTC client backend[46583] pg_regress/temp STATEMENT: SELECT * FROM temptest; 2025-11-30 18:45:24.360 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content at character 25 2025-11-30 18:45:24.360 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Couldn't find end of Start Tag syntax line 1 & ^ 2025-11-30 18:45:24.403 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(content '&'); 2025-11-30 18:45:24.404 UTC client backend[46574] pg_regress/truncate ERROR: cannot truncate a table referenced in a foreign key constraint 2025-11-30 18:45:24.404 UTC client backend[46574] pg_regress/truncate DETAIL: Table "trunc_b" references "truncate_a". 2025-11-30 18:45:24.404 UTC client backend[46574] pg_regress/truncate HINT: Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE. 2025-11-30 18:45:24.404 UTC client backend[46574] pg_regress/truncate STATEMENT: TRUNCATE TABLE trunc_c,truncate_a,trunc_d,trunc_e; 2025-11-30 18:45:24.404 UTC client backend[46578] pg_regress/copy2 ERROR: only ON_ERROR STOP is allowed in BINARY mode 2025-11-30 18:45:24.404 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format BINARY, on_error ignore); 2025-11-30 18:45:24.404 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content 2025-11-30 18:45:24.404 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Entity 'idontexist' not defined &idontexist; ^ 2025-11-30 18:45:24.404 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(content '&idontexist;'); 2025-11-30 18:45:24.407 UTC client backend[46571] pg_regress/sequence ERROR: MAXVALUE (100000) is out of range for sequence data type smallint 2025-11-30 18:45:24.407 UTC client backend[46571] pg_regress/sequence STATEMENT: ALTER SEQUENCE sequence_test8 AS smallint; 2025-11-30 18:45:24.407 UTC client backend[46578] pg_regress/copy2 ERROR: COPY ON_ERROR "unsupported" not recognized at character 20 2025-11-30 18:45:24.407 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (on_error unsupported); 2025-11-30 18:45:24.410 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content 2025-11-30 18:45:24.410 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Entity 'idontexist' not defined &idontexist; ^ line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced &idontexist; ^ 2025-11-30 18:45:24.410 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(content '&idontexist;'); 2025-11-30 18:45:24.410 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_QUOTE requires CSV mode 2025-11-30 18:45:24.410 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format TEXT, force_quote(a)); 2025-11-30 18:45:24.412 UTC client backend[46582] pg_regress/polymorphism ERROR: could not determine polymorphic type anycompatiblerange because input has type unknown 2025-11-30 18:45:24.412 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(null); 2025-11-30 18:45:24.412 UTC client backend[46577] pg_regress/xml ERROR: invalid XML document 2025-11-30 18:45:24.412 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Start tag expected, '<' not found ^ 2025-11-30 18:45:24.412 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(document ' '); 2025-11-30 18:45:24.413 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_QUOTE requires CSV mode 2025-11-30 18:45:24.413 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format TEXT, force_quote *); 2025-11-30 18:45:24.414 UTC client backend[46571] pg_regress/sequence ERROR: MINVALUE (-100000) is out of range for sequence data type smallint 2025-11-30 18:45:24.414 UTC client backend[46571] pg_regress/sequence STATEMENT: ALTER SEQUENCE sequence_test10 AS smallint; 2025-11-30 18:45:24.414 UTC client backend[46577] pg_regress/xml ERROR: invalid XML document 2025-11-30 18:45:24.414 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Start tag expected, '<' not found abc ^ 2025-11-30 18:45:24.414 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(document 'abc'); 2025-11-30 18:45:24.415 UTC client backend[46583] pg_regress/temp ERROR: relation "temptest" does not exist at character 15 2025-11-30 18:45:24.415 UTC client backend[46583] pg_regress/temp STATEMENT: SELECT * FROM temptest; 2025-11-30 18:45:24.417 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_QUOTE cannot be used with COPY FROM 2025-11-30 18:45:24.417 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format CSV, force_quote(a)); 2025-11-30 18:45:24.417 UTC client backend[46576] pg_regress/rowtypes ERROR: subfield "c1" is of type complex but expression is of type integer at character 22 2025-11-30 18:45:24.417 UTC client backend[46576] pg_regress/rowtypes HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:24.417 UTC client backend[46576] pg_regress/rowtypes STATEMENT: update quadtable set q.c1 = 12; 2025-11-30 18:45:24.419 UTC client backend[46577] pg_regress/xml ERROR: invalid XML document 2025-11-30 18:45:24.419 UTC client backend[46577] pg_regress/xml DETAIL: line 1: xmlParseEntityRef: no name & ^ line 1: Opening and ending tag mismatch: invalidentity line 1 and abc & ^ 2025-11-30 18:45:24.419 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(document '&'); 2025-11-30 18:45:24.420 UTC client backend[46566] pg_regress/alter_table ERROR: column number must be in range from 1 to 32767 at character 36 2025-11-30 18:45:24.420 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER INDEX attmp_idx ALTER COLUMN 0 SET STATISTICS 1000; 2025-11-30 18:45:24.420 UTC client backend[46577] pg_regress/xml ERROR: invalid XML document 2025-11-30 18:45:24.420 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Entity 'idontexist' not defined &idontexist; ^ line 1: Opening and ending tag mismatch: undefinedentity line 1 and abc &idontexist; ^ 2025-11-30 18:45:24.420 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(document '&idontexist;'); 2025-11-30 18:45:24.420 UTC client backend[46582] pg_regress/polymorphism ERROR: could not determine polymorphic type because input has type unknown 2025-11-30 18:45:24.420 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(null); 2025-11-30 18:45:24.421 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_QUOTE cannot be used with COPY FROM 2025-11-30 18:45:24.421 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format CSV, force_quote *); 2025-11-30 18:45:24.421 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter statistics on non-expression column "a" of index "attmp_idx" 2025-11-30 18:45:24.421 UTC client backend[46566] pg_regress/alter_table HINT: Alter statistics on table column instead. 2025-11-30 18:45:24.421 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER INDEX attmp_idx ALTER COLUMN 1 SET STATISTICS 1000; 2025-11-30 18:45:24.422 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NOT_NULL requires CSV mode 2025-11-30 18:45:24.422 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format TEXT, force_not_null(a)); 2025-11-30 18:45:24.426 UTC client backend[46577] pg_regress/xml ERROR: invalid XML document 2025-11-30 18:45:24.426 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Entity 'idontexist' not defined &idontexist; ^ line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced &idontexist; ^ 2025-11-30 18:45:24.426 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlparse(document '&idontexist;'); 2025-11-30 18:45:24.429 UTC client backend[46565] pg_regress/limit ERROR: SKIP LOCKED and WITH TIES options cannot be used together at character 87 2025-11-30 18:45:24.429 UTC client backend[46565] 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-11-30 18:45:24.429 UTC client backend[46583] pg_regress/temp ERROR: relation "temptest" does not exist at character 15 2025-11-30 18:45:24.429 UTC client backend[46583] pg_regress/temp STATEMENT: SELECT * FROM temptest; 2025-11-30 18:45:24.429 UTC client backend[46582] pg_regress/polymorphism ERROR: could not determine polymorphic type anycompatiblerange because input has type unknown 2025-11-30 18:45:24.429 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(null); 2025-11-30 18:45:24.430 UTC client backend[46565] pg_regress/limit ERROR: WITH TIES cannot be specified without ORDER BY clause at character 103 2025-11-30 18:45:24.430 UTC client backend[46565] pg_regress/limit STATEMENT: SELECT ''::text AS two, unique1, unique2, stringu1 FROM onek WHERE unique1 > 50 FETCH FIRST 2 ROW WITH TIES; 2025-11-30 18:45:24.430 UTC client backend[46583] pg_regress/temp ERROR: ON COMMIT can only be used on temporary tables 2025-11-30 18:45:24.430 UTC client backend[46583] pg_regress/temp STATEMENT: CREATE TABLE temptest(col int) ON COMMIT DELETE ROWS; 2025-11-30 18:45:24.431 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NOT_NULL requires CSV mode 2025-11-30 18:45:24.431 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format TEXT, force_not_null *); 2025-11-30 18:45:24.437 UTC client backend[46577] pg_regress/xml ERROR: invalid XML processing instruction 2025-11-30 18:45:24.437 UTC client backend[46577] pg_regress/xml DETAIL: XML processing instruction target name cannot be "xml". 2025-11-30 18:45:24.437 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlpi(name xml); 2025-11-30 18:45:24.439 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NOT_NULL cannot be used with COPY TO 2025-11-30 18:45:24.439 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x to stdout (format CSV, force_not_null(a)); 2025-11-30 18:45:24.439 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter statistics on non-expression column "b" of index "attmp_idx" 2025-11-30 18:45:24.439 UTC client backend[46566] pg_regress/alter_table HINT: Alter statistics on table column instead. 2025-11-30 18:45:24.439 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER INDEX attmp_idx ALTER COLUMN 3 SET STATISTICS 1000; 2025-11-30 18:45:24.440 UTC client backend[46570] pg_regress/domain ERROR: division by zero 2025-11-30 18:45:24.440 UTC client backend[46570] pg_regress/domain STATEMENT: select * from pg_input_error_info('0', 'weirdfloat'); 2025-11-30 18:45:24.440 UTC client backend[46566] pg_regress/alter_table ERROR: column number 4 of relation "attmp_idx" does not exist 2025-11-30 18:45:24.440 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER INDEX attmp_idx ALTER COLUMN 4 SET STATISTICS 1000; 2025-11-30 18:45:24.442 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NOT_NULL cannot be used with COPY TO 2025-11-30 18:45:24.442 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x to stdout (format CSV, force_not_null *); 2025-11-30 18:45:24.442 UTC client backend[46577] pg_regress/xml ERROR: invalid XML processing instruction 2025-11-30 18:45:24.442 UTC client backend[46577] pg_regress/xml DETAIL: XML processing instruction cannot contain "?>". 2025-11-30 18:45:24.442 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlpi(name foo, 'in?>valid'); 2025-11-30 18:45:24.443 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NULL requires CSV mode 2025-11-30 18:45:24.443 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format TEXT, force_null(a)); 2025-11-30 18:45:24.443 UTC client backend[46583] pg_regress/temp ERROR: ON COMMIT can only be used on temporary tables 2025-11-30 18:45:24.443 UTC client backend[46583] pg_regress/temp STATEMENT: CREATE TABLE temptest(col) ON COMMIT DELETE ROWS AS SELECT 1; 2025-11-30 18:45:24.444 UTC client backend[46577] pg_regress/xml ERROR: invalid XML processing instruction 2025-11-30 18:45:24.444 UTC client backend[46577] pg_regress/xml DETAIL: XML processing instruction target name cannot be "xml". 2025-11-30 18:45:24.444 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlpi(name xml, null); 2025-11-30 18:45:24.444 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NULL requires CSV mode 2025-11-30 18:45:24.444 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (format TEXT, force_null *); 2025-11-30 18:45:24.444 UTC client backend[46571] pg_regress/sequence ERROR: null value in column "f2" of relation "serialtest1" violates not-null constraint 2025-11-30 18:45:24.444 UTC client backend[46571] pg_regress/sequence DETAIL: Failing row contains (wrong, null). 2025-11-30 18:45:24.444 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest1 VALUES ('wrong', NULL); 2025-11-30 18:45:24.445 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NULL cannot be used with COPY TO 2025-11-30 18:45:24.445 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x to stdout (format CSV, force_null(a)); 2025-11-30 18:45:24.453 UTC client backend[46578] pg_regress/copy2 ERROR: COPY FORCE_NULL cannot be used with COPY TO 2025-11-30 18:45:24.453 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x to stdout (format CSV, force_null *); 2025-11-30 18:45:24.454 UTC client backend[46571] pg_regress/sequence ERROR: smallint out of range 2025-11-30 18:45:24.454 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f3) VALUES ('bogus', -32769); 2025-11-30 18:45:24.454 UTC client backend[46578] pg_regress/copy2 ERROR: COPY ON_ERROR cannot be used with COPY TO at character 34 2025-11-30 18:45:24.454 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x to stdout (format BINARY, on_error unsupported); 2025-11-30 18:45:24.455 UTC client backend[46571] pg_regress/sequence ERROR: smallint out of range 2025-11-30 18:45:24.455 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f4) VALUES ('bogus', -32769); 2025-11-30 18:45:24.456 UTC client backend[46571] pg_regress/sequence ERROR: smallint out of range 2025-11-30 18:45:24.456 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f3) VALUES ('bogus', 32768); 2025-11-30 18:45:24.458 UTC client backend[46578] pg_regress/copy2 ERROR: COPY LOG_VERBOSITY "unsupported" not recognized at character 20 2025-11-30 18:45:24.458 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin (log_verbosity unsupported); 2025-11-30 18:45:24.459 UTC client backend[46571] pg_regress/sequence ERROR: smallint out of range 2025-11-30 18:45:24.459 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f4) VALUES ('bogus', 32768); 2025-11-30 18:45:24.460 UTC client backend[46571] pg_regress/sequence ERROR: bigint out of range 2025-11-30 18:45:24.460 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f5) VALUES ('bogus', -9223372036854775809); 2025-11-30 18:45:24.461 UTC client backend[46578] pg_regress/copy2 ERROR: COPY REJECT_LIMIT requires ON_ERROR to be set to IGNORE 2025-11-30 18:45:24.461 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin with (reject_limit 1); 2025-11-30 18:45:24.462 UTC client backend[46578] pg_regress/copy2 ERROR: REJECT_LIMIT (0) must be greater than zero 2025-11-30 18:45:24.462 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin with (on_error ignore, reject_limit 0); 2025-11-30 18:45:24.463 UTC client backend[46578] pg_regress/copy2 ERROR: a negative integer value cannot be specified for header 2025-11-30 18:45:24.463 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin with (header -1); 2025-11-30 18:45:24.466 UTC client backend[46578] pg_regress/copy2 ERROR: header requires a Boolean value, a non-negative integer, or the string "match" 2025-11-30 18:45:24.466 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin with (header 2.5); 2025-11-30 18:45:24.466 UTC client backend[46582] pg_regress/polymorphism ERROR: could not determine polymorphic type anycompatiblemultirange because input has type unknown 2025-11-30 18:45:24.466 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select polyf(null); 2025-11-30 18:45:24.467 UTC client backend[46578] pg_regress/copy2 ERROR: cannot use multi-line header in COPY TO 2025-11-30 18:45:24.467 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x to stdout with (header 2); 2025-11-30 18:45:24.467 UTC client backend[46577] pg_regress/xml ERROR: not an XML document 2025-11-30 18:45:24.467 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlserialize(document 'bad' as text); 2025-11-30 18:45:24.468 UTC client backend[46578] pg_regress/copy2 ERROR: column "d" specified more than once 2025-11-30 18:45:24.468 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x (a, b, c, d, e, d, c) from stdin; 2025-11-30 18:45:24.470 UTC client backend[46571] pg_regress/sequence ERROR: bigint out of range 2025-11-30 18:45:24.470 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f6) VALUES ('bogus', -9223372036854775809); 2025-11-30 18:45:24.472 UTC client backend[46577] pg_regress/xml ERROR: not an XML document 2025-11-30 18:45:24.472 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlserialize(DOCUMENT '7342' AS text INDENT); 2025-11-30 18:45:24.472 UTC client backend[46578] pg_regress/copy2 ERROR: invalid input syntax for type integer: "" 2025-11-30 18:45:24.472 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY x, line 1, column a: "" 2025-11-30 18:45:24.472 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin; 2025-11-30 18:45:24.475 UTC client backend[46576] pg_regress/rowtypes ERROR: could not determine interpretation of row comparison operator ~~ at character 25 2025-11-30 18:45:24.475 UTC client backend[46576] pg_regress/rowtypes HINT: Row comparison operators must be associated with btree operator families. 2025-11-30 18:45:24.475 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select ROW('ABC','DEF') ~~ ROW('DEF','ABC') as fail; 2025-11-30 18:45:24.475 UTC client backend[46577] pg_regress/xml ERROR: not an XML document 2025-11-30 18:45:24.475 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlserialize(DOCUMENT 'text node73text node42' AS text INDENT); 2025-11-30 18:45:24.475 UTC client backend[46578] pg_regress/copy2 ERROR: missing data for column "e" 2025-11-30 18:45:24.475 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY x, line 1: "2000 230 23 23" 2025-11-30 18:45:24.475 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin; 2025-11-30 18:45:24.476 UTC client backend[46571] pg_regress/sequence ERROR: bigint out of range 2025-11-30 18:45:24.476 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f5) VALUES ('bogus', 9223372036854775808); 2025-11-30 18:45:24.481 UTC client backend[46578] pg_regress/copy2 ERROR: missing data for column "e" 2025-11-30 18:45:24.481 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY x, line 1: "2001 231 \N \N" 2025-11-30 18:45:24.481 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin; 2025-11-30 18:45:24.482 UTC client backend[46571] pg_regress/sequence ERROR: bigint out of range 2025-11-30 18:45:24.482 UTC client backend[46571] pg_regress/sequence STATEMENT: INSERT INTO serialTest2 (f1, f6) VALUES ('bogus', 9223372036854775808); 2025-11-30 18:45:24.482 UTC client backend[46566] pg_regress/alter_table ERROR: relation "attmp" does not exist at character 15 2025-11-30 18:45:24.482 UTC client backend[46566] pg_regress/alter_table STATEMENT: SELECT * FROM attmp; 2025-11-30 18:45:24.484 UTC client backend[46578] pg_regress/copy2 ERROR: extra data after last expected column 2025-11-30 18:45:24.484 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY x, line 1: "2002 232 40 50 60 70 80" 2025-11-30 18:45:24.484 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin; 2025-11-30 18:45:24.487 UTC client backend[46577] pg_regress/xml ERROR: not an XML document 2025-11-30 18:45:24.487 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlserialize(DOCUMENT '' AS text INDENT); 2025-11-30 18:45:24.493 UTC client backend[46577] pg_regress/xml ERROR: not an XML document 2025-11-30 18:45:24.493 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xmlserialize(DOCUMENT ' ' AS text INDENT); 2025-11-30 18:45:24.494 UTC client backend[46580] pg_regress/conversion LOG: disconnection: session time: 0:00:00.198 user=postgres database=regression host=[local] 2025-11-30 18:45:24.496 UTC client backend[46565] pg_regress/limit ERROR: row count cannot be null in FETCH FIRST ... WITH TIES clause 2025-11-30 18:45:24.496 UTC client backend[46565] 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-11-30 18:45:24.497 UTC client backend[46578] pg_regress/copy2 ERROR: WHERE clause not allowed with COPY TO at character 18 2025-11-30 18:45:24.497 UTC client backend[46578] pg_regress/copy2 HINT: Try the COPY (SELECT ... WHERE ...) TO variant. 2025-11-30 18:45:24.497 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x TO stdout WHERE a = 1; 2025-11-30 18:45:24.498 UTC client backend[46570] pg_regress/domain ERROR: value too long for type character varying(4) 2025-11-30 18:45:24.498 UTC client backend[46570] pg_regress/domain STATEMENT: INSERT INTO domarrtest values (NULL, '{{"toolong","b","c"},{"d","e","f"}}'); 2025-11-30 18:45:24.499 UTC client backend[46583] pg_regress/temp ERROR: unsupported ON COMMIT and foreign key combination 2025-11-30 18:45:24.499 UTC client backend[46583] pg_regress/temp DETAIL: Table "temptest4" references "temptest3", but they do not have the same ON COMMIT setting. 2025-11-30 18:45:24.499 UTC client backend[46583] pg_regress/temp STATEMENT: COMMIT; 2025-11-30 18:45:24.501 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.501 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.501 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp02a(*) (SFUNC = stfnp, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.501 UTC client backend[46578] pg_regress/copy2 ERROR: column "f" does not exist at character 25 2025-11-30 18:45:24.501 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin WHERE f > 60003; 2025-11-30 18:45:24.502 UTC client backend[46578] pg_regress/copy2 ERROR: aggregate functions are not allowed in COPY FROM WHERE conditions at character 29 2025-11-30 18:45:24.502 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin WHERE a = max(x.b); 2025-11-30 18:45:24.503 UTC client backend[46578] pg_regress/copy2 ERROR: cannot use subquery in COPY FROM WHERE condition at character 27 2025-11-30 18:45:24.503 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin WHERE a IN (SELECT 1 FROM x); 2025-11-30 18:45:24.505 UTC client backend[46578] pg_regress/copy2 ERROR: set-returning functions are not allowed in COPY FROM WHERE conditions at character 31 2025-11-30 18:45:24.505 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin WHERE a IN (generate_series(1,5)); 2025-11-30 18:45:24.505 UTC client backend[46578] pg_regress/copy2 ERROR: window functions are not allowed in COPY FROM WHERE conditions at character 29 2025-11-30 18:45:24.505 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY x from stdin WHERE a = row_number() over(b); 2025-11-30 18:45:24.505 UTC client backend[46570] pg_regress/domain ERROR: value too long for type character varying(4) 2025-11-30 18:45:24.505 UTC client backend[46570] pg_regress/domain CONTEXT: COPY domarrtest, line 1, column testchar4arr: "{qwerty,w,e}" 2025-11-30 18:45:24.505 UTC client backend[46570] pg_regress/domain STATEMENT: COPY domarrtest FROM stdin; 2025-11-30 18:45:24.509 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.509 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.509 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp04a(*) (SFUNC = stfp, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.511 UTC client backend[46575] pg_regress/returning ERROR: invalid reference to FROM-clause entry for table "foo" at character 49 2025-11-30 18:45:24.511 UTC client backend[46575] pg_regress/returning HINT: Perhaps you meant to reference the table alias "bar". 2025-11-30 18:45:24.511 UTC client backend[46575] pg_regress/returning STATEMENT: INSERT INTO foo AS bar DEFAULT VALUES RETURNING foo.*; 2025-11-30 18:45:24.513 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.513 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.513 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp04b(*) (SFUNC = stfp, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.514 UTC client backend[46566] pg_regress/alter_table ERROR: must be owner of index part_attmp_index 2025-11-30 18:45:24.514 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER INDEX part_attmp_index RENAME TO fail; 2025-11-30 18:45:24.516 UTC client backend[46566] pg_regress/alter_table ERROR: must be owner of index part_attmp1_index 2025-11-30 18:45:24.516 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER INDEX part_attmp1_index RENAME TO fail; 2025-11-30 18:45:24.518 UTC client backend[46566] pg_regress/alter_table ERROR: must be owner of table part_at2tmp 2025-11-30 18:45:24.518 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_at2tmp RENAME TO fail; 2025-11-30 18:45:24.520 UTC client backend[46566] pg_regress/alter_table ERROR: must be owner of table part_at2tmp1 2025-11-30 18:45:24.520 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_at2tmp1 RENAME TO fail; 2025-11-30 18:45:24.521 UTC client backend[46575] pg_regress/returning ERROR: syntax error at or near "nonsuch" at character 48 2025-11-30 18:45:24.521 UTC client backend[46575] pg_regress/returning STATEMENT: INSERT INTO foo DEFAULT VALUES RETURNING WITH (nonsuch AS something) *; 2025-11-30 18:45:24.522 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfnp(integer[], anyelement) does not exist 2025-11-30 18:45:24.522 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp07a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[], FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.527 UTC client backend[46575] pg_regress/returning ERROR: table name "foo" specified more than once at character 48 2025-11-30 18:45:24.527 UTC client backend[46575] pg_regress/returning STATEMENT: INSERT INTO foo DEFAULT VALUES RETURNING WITH (new AS foo) *; 2025-11-30 18:45:24.532 UTC client backend[46575] pg_regress/returning ERROR: OLD cannot be specified multiple times at character 68 2025-11-30 18:45:24.532 UTC client backend[46575] pg_regress/returning STATEMENT: INSERT INTO foo DEFAULT VALUES RETURNING WITH (old AS o, new AS n, old AS o) *; 2025-11-30 18:45:24.532 UTC client backend[46571] pg_regress/sequence ERROR: currval of sequence "sequence_test" is not yet defined in this session 2025-11-30 18:45:24.532 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT currval('sequence_test'::regclass); 2025-11-30 18:45:24.533 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare dissimilar column types bigint and integer at record column 1 2025-11-30 18:45:24.533 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select * from int8_tbl i8 where i8 in (row(123,456)); 2025-11-30 18:45:24.535 UTC client backend[46575] pg_regress/returning ERROR: NEW cannot be specified multiple times at character 68 2025-11-30 18:45:24.535 UTC client backend[46575] pg_regress/returning STATEMENT: INSERT INTO foo DEFAULT VALUES RETURNING WITH (old AS o, new AS n, new AS n) *; 2025-11-30 18:45:24.535 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf1p(integer[], anyelement) does not exist 2025-11-30 18:45:24.535 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp11a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[], FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.537 UTC client backend[46575] pg_regress/returning ERROR: table name "x" specified more than once at character 58 2025-11-30 18:45:24.537 UTC client backend[46575] pg_regress/returning STATEMENT: INSERT INTO foo DEFAULT VALUES RETURNING WITH (old AS x, new AS x) *; 2025-11-30 18:45:24.537 UTC client backend[46565] pg_regress/limit LOG: disconnection: session time: 0:00:00.251 user=postgres database=regression host=[local] 2025-11-30 18:45:24.540 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf1p(integer[], anyelement) does not exist 2025-11-30 18:45:24.540 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp11b(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[], INITCOND = '{}'); 2025-11-30 18:45:24.541 UTC client backend[46570] pg_regress/domain ERROR: duplicate key value violates unique constraint "dcomptable_d1_key" 2025-11-30 18:45:24.541 UTC client backend[46570] pg_regress/domain DETAIL: Key (d1)=((1,2)) already exists. 2025-11-30 18:45:24.541 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dcomptable values (row(1,2)::dcomptype); 2025-11-30 18:45:24.541 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfp(integer[], anyelement) does not exist 2025-11-30 18:45:24.541 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp12a(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[], FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.542 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfp(integer[], anyelement) does not exist 2025-11-30 18:45:24.542 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp12b(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[], INITCOND = '{}'); 2025-11-30 18:45:24.544 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.544 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.544 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp13a(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.545 UTC client backend[46583] pg_regress/temp ERROR: function nonempty(unknown) does not exist at character 8 2025-11-30 18:45:24.545 UTC client backend[46583] pg_regress/temp DETAIL: There is no function of that name. 2025-11-30 18:45:24.545 UTC client backend[46583] pg_regress/temp STATEMENT: select nonempty(''); 2025-11-30 18:45:24.545 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.545 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.545 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp14a(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.547 UTC client backend[46576] pg_regress/rowtypes ERROR: could not identify column "nosuch" in record data type at character 9 2025-11-30 18:45:24.547 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select (row(1, 2.0)).nosuch; 2025-11-30 18:45:24.548 UTC client backend[46570] pg_regress/domain ERROR: column "d1" of table "dcomptable" contains values that violate the new constraint 2025-11-30 18:45:24.548 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain dcomptype add constraint c2 check ((value).r > (value).i); 2025-11-30 18:45:24.549 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfnp(anyarray, anyelement) does not exist 2025-11-30 18:45:24.549 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp15a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.551 UTC client backend[46571] pg_regress/sequence ERROR: cannot drop sequence t1_f1_seq because other objects depend on it 2025-11-30 18:45:24.551 UTC client backend[46571] pg_regress/sequence DETAIL: default value for column f1 of table t1 depends on sequence t1_f1_seq 2025-11-30 18:45:24.551 UTC client backend[46571] pg_regress/sequence HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:24.551 UTC client backend[46571] pg_regress/sequence STATEMENT: DROP SEQUENCE t1_f1_seq; 2025-11-30 18:45:24.552 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptype violates check constraint "c1" 2025-11-30 18:45:24.552 UTC client backend[46570] pg_regress/domain STATEMENT: select row(2,1)::dcomptype; 2025-11-30 18:45:24.552 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf2p(anyarray, anyelement) does not exist 2025-11-30 18:45:24.552 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp16a(BASETYPE = anyelement, SFUNC = tf2p, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.552 UTC client backend[46571] pg_regress/sequence ERROR: cannot drop sequence myseq2 because other objects depend on it 2025-11-30 18:45:24.552 UTC client backend[46571] pg_regress/sequence DETAIL: default value for column f2 of table t1 depends on sequence myseq2 2025-11-30 18:45:24.552 UTC client backend[46571] pg_regress/sequence HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:24.552 UTC client backend[46571] pg_regress/sequence STATEMENT: DROP SEQUENCE myseq2; 2025-11-30 18:45:24.552 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content at character 8 2025-11-30 18:45:24.552 UTC client backend[46577] pg_regress/xml DETAIL: line 1: StartTag: invalid element name <> ^ 2025-11-30 18:45:24.552 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT '<>' IS NOT DOCUMENT; 2025-11-30 18:45:24.553 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.553 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.553 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp17a(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.553 UTC client backend[46583] pg_regress/temp ERROR: value for domain nonempty violates check constraint "nonempty_check" 2025-11-30 18:45:24.553 UTC client backend[46583] pg_regress/temp STATEMENT: select pg_temp.nonempty(''); 2025-11-30 18:45:24.553 UTC client backend[46569] pg_regress/plancache ERROR: new row for relation "pc_list_part_def" violates partition constraint 2025-11-30 18:45:24.553 UTC client backend[46569] pg_regress/plancache DETAIL: Failing row contains (null). 2025-11-30 18:45:24.553 UTC client backend[46569] pg_regress/plancache STATEMENT: execute pstmt_def_insert(null); 2025-11-30 18:45:24.553 UTC client backend[46576] pg_regress/rowtypes ERROR: could not identify column "f3" in record data type at character 9 2025-11-30 18:45:24.553 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select (r).f3 from (select row(1, 2.0) as r) ss; 2025-11-30 18:45:24.554 UTC client backend[46569] pg_regress/plancache ERROR: new row for relation "pc_list_part_def" violates partition constraint 2025-11-30 18:45:24.554 UTC client backend[46569] pg_regress/plancache DETAIL: Failing row contains (1). 2025-11-30 18:45:24.554 UTC client backend[46569] pg_regress/plancache STATEMENT: execute pstmt_def_insert(1); 2025-11-30 18:45:24.555 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptype violates check constraint "c1" 2025-11-30 18:45:24.555 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dcomptable values (row(2,1)::comptype); 2025-11-30 18:45:24.555 UTC client backend[46571] pg_regress/sequence ERROR: sequence "t1_f1_seq" does not exist 2025-11-30 18:45:24.555 UTC client backend[46571] pg_regress/sequence STATEMENT: DROP SEQUENCE t1_f1_seq; 2025-11-30 18:45:24.555 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare rows of zero length at character 14 2025-11-30 18:45:24.555 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select ROW() = ROW(); 2025-11-30 18:45:24.555 UTC client backend[46566] pg_regress/alter_table ERROR: must be owner of index onek_unique1 2025-11-30 18:45:24.555 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER INDEX onek_unique1 RENAME TO fail; 2025-11-30 18:45:24.556 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.556 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.556 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp17b(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.556 UTC client backend[46583] pg_regress/temp ERROR: value for domain nonempty violates check constraint "nonempty_check" 2025-11-30 18:45:24.556 UTC client backend[46583] pg_regress/temp STATEMENT: select ''::nonempty; 2025-11-30 18:45:24.557 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.557 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.557 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp18a(BASETYPE = int, SFUNC = tfp, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.557 UTC client backend[46571] pg_regress/sequence ERROR: cannot open relation "serialtest1" 2025-11-30 18:45:24.557 UTC client backend[46571] pg_regress/sequence DETAIL: This operation is not supported for tables. 2025-11-30 18:45:24.557 UTC client backend[46571] pg_regress/sequence STATEMENT: ALTER SEQUENCE serialTest1 CYCLE; 2025-11-30 18:45:24.557 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptype violates check constraint "c1" 2025-11-30 18:45:24.557 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dcomptable (d1.r, d1.i) values(100, 99); 2025-11-30 18:45:24.558 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.558 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.558 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp18b(BASETYPE = int, SFUNC = tfp, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.558 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptype violates check constraint "c1" 2025-11-30 18:45:24.558 UTC client backend[46570] pg_regress/domain STATEMENT: update dcomptable set d1.r = (d1).r + 1 where (d1).i > 0; 2025-11-30 18:45:24.558 UTC client backend[46579] pg_regress/with ERROR: search column "foo" not in WITH query column list at character 146 2025-11-30 18:45:24.558 UTC client backend[46579] 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-11-30 18:45:24.559 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf1p(anyarray, anyelement) does not exist 2025-11-30 18:45:24.559 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp19a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}'); 2025-11-30 18:45:24.559 UTC client backend[46569] pg_regress/plancache ERROR: new row for relation "pc_list_part_def" violates partition constraint 2025-11-30 18:45:24.559 UTC client backend[46569] pg_regress/plancache DETAIL: Failing row contains (2). 2025-11-30 18:45:24.559 UTC client backend[46569] pg_regress/plancache STATEMENT: execute pstmt_def_insert(2); 2025-11-30 18:45:24.559 UTC client backend[46579] pg_regress/with ERROR: search sequence column name "label" already used in WITH query column list at character 146 2025-11-30 18:45:24.559 UTC client backend[46579] 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-11-30 18:45:24.559 UTC client backend[46579] pg_regress/with ERROR: search column "f" specified more than once at character 146 2025-11-30 18:45:24.559 UTC client backend[46579] 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-11-30 18:45:24.560 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf1p(anyarray, anyelement) does not exist 2025-11-30 18:45:24.560 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggp19b(BASETYPE = anyelement, SFUNC = tf1p, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.561 UTC client backend[46571] pg_regress/sequence ERROR: RESTART value (0) cannot be less than MINVALUE (1) 2025-11-30 18:45:24.561 UTC client backend[46571] pg_regress/sequence STATEMENT: ALTER SEQUENCE sequence_test2 RESTART WITH 0; 2025-11-30 18:45:24.561 UTC client backend[46579] pg_regress/with ERROR: with a SEARCH or CYCLE clause, the left side of the UNION must be a SELECT 2025-11-30 18:45:24.561 UTC client backend[46579] 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-11-30 18:45:24.562 UTC client backend[46579] pg_regress/with ERROR: with a SEARCH or CYCLE clause, the right side of the UNION must be a SELECT 2025-11-30 18:45:24.562 UTC client backend[46579] 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-11-30 18:45:24.562 UTC client backend[46571] pg_regress/sequence ERROR: RESTART value (40) cannot be greater than MAXVALUE (-1) 2025-11-30 18:45:24.562 UTC client backend[46571] pg_regress/sequence STATEMENT: ALTER SEQUENCE sequence_test4 RESTART WITH 40; 2025-11-30 18:45:24.563 UTC client backend[46579] 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-11-30 18:45:24.563 UTC client backend[46579] 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-11-30 18:45:24.563 UTC client backend[46577] pg_regress/xml ERROR: invalid XML document at character 14 2025-11-30 18:45:24.563 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Start tag expected, '<' not found bad ^ 2025-11-30 18:45:24.563 UTC client backend[46577] pg_regress/xml STATEMENT: EXECUTE foo ('bad'); 2025-11-30 18:45:24.567 UTC client backend[46576] pg_regress/rowtypes ERROR: could not identify an ordering operator for type cantcompare at character 27 2025-11-30 18:45:24.567 UTC client backend[46576] pg_regress/rowtypes HINT: Use an explicit ordering operator or modify the query. 2025-11-30 18:45:24.567 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select * from cc order by f1; 2025-11-30 18:45:24.568 UTC client backend[46577] pg_regress/xml ERROR: invalid XML document at character 12 2025-11-30 18:45:24.568 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Extra content at the end of the document ^ 2025-11-30 18:45:24.568 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xml ''; 2025-11-30 18:45:24.576 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.576 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.576 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn02a(*) (SFUNC = stfnp, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.579 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content at character 12 2025-11-30 18:45:24.579 UTC client backend[46577] pg_regress/xml DETAIL: line 1: StartTag: invalid element name oops ^ 2025-11-30 18:45:24.579 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xml ' oops '; 2025-11-30 18:45:24.579 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.579 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.579 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn02b(*) (SFUNC = stfnp, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.581 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content at character 12 2025-11-30 18:45:24.581 UTC client backend[46577] pg_regress/xml DETAIL: line 1: StartTag: invalid element name ^ 2025-11-30 18:45:24.581 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xml ' '; 2025-11-30 18:45:24.581 UTC client backend[46566] pg_regress/alter_table ERROR: must be owner of view attmp_view_new 2025-11-30 18:45:24.581 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER VIEW attmp_view_new RENAME TO fail; 2025-11-30 18:45:24.582 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare dissimilar column types integer and text at record column 2 2025-11-30 18:45:24.582 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 < row(1, 'abc')::testtype3; 2025-11-30 18:45:24.582 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare dissimilar column types integer and text at record column 2 2025-11-30 18:45:24.582 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 <> row(1, 'abc')::testtype3; 2025-11-30 18:45:24.583 UTC client backend[46577] pg_regress/xml ERROR: invalid XML content at character 12 2025-11-30 18:45:24.583 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Extra content at the end of the document ^ 2025-11-30 18:45:24.583 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xml ''; 2025-11-30 18:45:24.584 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare record types with different numbers of columns 2025-11-30 18:45:24.584 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 < row(1)::testtype5; 2025-11-30 18:45:24.584 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare record types with different numbers of columns 2025-11-30 18:45:24.584 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 <> row(1)::testtype5; 2025-11-30 18:45:24.586 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.586 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.586 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn04a(*) (SFUNC = stfp, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.588 UTC client backend[46576] pg_regress/rowtypes ERROR: could not identify a comparison function for type point 2025-11-30 18:45:24.588 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, '(1,2)')::testtype6 < row(1, '(1,3)')::testtype6; 2025-11-30 18:45:24.591 UTC client backend[46576] pg_regress/rowtypes ERROR: could not identify an equality operator for type point 2025-11-30 18:45:24.591 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, '(1,2)')::testtype6 <> row(1, '(1,3)')::testtype6; 2025-11-30 18:45:24.592 UTC client backend[46571] pg_regress/sequence ERROR: nextval: reached maximum value of sequence "sequence_test2" (36) 2025-11-30 18:45:24.592 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT nextval('sequence_test2'); 2025-11-30 18:45:24.596 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfnp(integer[], anyelement) does not exist 2025-11-30 18:45:24.596 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn07a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[], FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.597 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptype violates check constraint "c1" 2025-11-30 18:45:24.597 UTC client backend[46570] pg_regress/domain STATEMENT: select makedcomp(2,1); 2025-11-30 18:45:24.597 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfnp(integer[], anyelement) does not exist 2025-11-30 18:45:24.597 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn07b(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[], INITCOND = '{}'); 2025-11-30 18:45:24.599 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop index onek_unique1_constraint because constraint onek_unique1_constraint on table onek requires it 2025-11-30 18:45:24.599 UTC client backend[46566] pg_regress/alter_table HINT: You can drop constraint onek_unique1_constraint on table onek instead. 2025-11-30 18:45:24.599 UTC client backend[46566] pg_regress/alter_table STATEMENT: DROP INDEX onek_unique1_constraint; 2025-11-30 18:45:24.601 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop index onek_unique1_constraint_foo because constraint onek_unique1_constraint_foo on table onek requires it 2025-11-30 18:45:24.601 UTC client backend[46566] pg_regress/alter_table HINT: You can drop constraint onek_unique1_constraint_foo on table onek instead. 2025-11-30 18:45:24.601 UTC client backend[46566] pg_regress/alter_table STATEMENT: DROP INDEX onek_unique1_constraint_foo; 2025-11-30 18:45:24.603 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf1p(integer[], anyelement) does not exist 2025-11-30 18:45:24.603 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn11a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[], FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.603 UTC client backend[46571] pg_regress/sequence ERROR: nextval: reached minimum value of sequence "sequence_test2" (-36) 2025-11-30 18:45:24.603 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT nextval('sequence_test2'); 2025-11-30 18:45:24.604 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfp(integer[], anyelement) does not exist 2025-11-30 18:45:24.604 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn12a(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[], FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.605 UTC client backend[46571] pg_regress/sequence ERROR: setval: value -100 is out of bounds for sequence "sequence_test2" (5..36) 2025-11-30 18:45:24.605 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT setval('sequence_test2', -100); 2025-11-30 18:45:24.606 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.606 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.606 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn13a(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.606 UTC client backend[46571] pg_regress/sequence ERROR: setval: value 100 is out of bounds for sequence "sequence_test2" (5..36) 2025-11-30 18:45:24.606 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT setval('sequence_test2', 100); 2025-11-30 18:45:24.607 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.607 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.607 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn13b(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.608 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptype violates check constraint "c1" 2025-11-30 18:45:24.608 UTC client backend[46570] pg_regress/domain STATEMENT: select row(0,1)::dcomptype; 2025-11-30 18:45:24.612 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.612 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.612 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn14a(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.617 UTC client backend[46575] pg_regress/returning ERROR: column reference "new.f1" is ambiguous at character 120 2025-11-30 18:45:24.617 UTC client backend[46575] pg_regress/returning DETAIL: It could refer to either a PL/pgSQL variable or a table column. 2025-11-30 18:45:24.617 UTC client backend[46575] 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-11-30 18:45:24.617 UTC client backend[46575] pg_regress/returning CONTEXT: PL/pgSQL function joinview_upd_trig_fn() line 4 at SQL statement 2025-11-30 18:45:24.617 UTC client backend[46575] 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-11-30 18:45:24.617 UTC client backend[46570] pg_regress/domain ERROR: operator does not exist: character varying > double precision 2025-11-30 18:45:24.617 UTC client backend[46570] pg_regress/domain DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:24.617 UTC client backend[46570] pg_regress/domain HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.617 UTC client backend[46570] pg_regress/domain STATEMENT: alter type comptype alter attribute r type varchar; 2025-11-30 18:45:24.618 UTC client backend[46569] pg_regress/plancache LOG: disconnection: session time: 0:00:00.329 user=postgres database=regression host=[local] 2025-11-30 18:45:24.622 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.622 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.622 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn14b(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.622 UTC client backend[46577] pg_regress/xml ERROR: empty XPath expression 2025-11-30 18:45:24.622 UTC client backend[46577] pg_regress/xml CONTEXT: SQL function "xpath" statement 1 2025-11-30 18:45:24.622 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xpath('', ''); 2025-11-30 18:45:24.628 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare dissimilar column types integer and text at record column 2 2025-11-30 18:45:24.628 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 *< row(1, 'abc')::testtype3; 2025-11-30 18:45:24.628 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare dissimilar column types integer and text at record column 2 2025-11-30 18:45:24.628 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 *<> row(1, 'abc')::testtype3; 2025-11-30 18:45:24.629 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare record types with different numbers of columns 2025-11-30 18:45:24.629 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 *< row(1)::testtype5; 2025-11-30 18:45:24.629 UTC client backend[46576] pg_regress/rowtypes ERROR: cannot compare record types with different numbers of columns 2025-11-30 18:45:24.629 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select row(1, 2)::testtype1 *<> row(1)::testtype5; 2025-11-30 18:45:24.632 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfnp(anyarray, anyelement) does not exist 2025-11-30 18:45:24.632 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn15a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.634 UTC client backend[46570] pg_regress/domain ERROR: cannot drop column r of composite type comptype because other objects depend on it 2025-11-30 18:45:24.634 UTC client backend[46570] pg_regress/domain DETAIL: constraint c1 depends on column r of composite type comptype 2025-11-30 18:45:24.634 UTC client backend[46570] pg_regress/domain HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:24.634 UTC client backend[46570] pg_regress/domain STATEMENT: alter type comptype drop attribute r; 2025-11-30 18:45:24.636 UTC client backend[46578] pg_regress/copy2 ERROR: cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction 2025-11-30 18:45:24.636 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY vistest FROM stdin CSV FREEZE; 2025-11-30 18:45:24.637 UTC client backend[46582] pg_regress/polymorphism ERROR: function tfnp(anyarray, anyelement) does not exist 2025-11-30 18:45:24.637 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn15b(BASETYPE = anyelement, SFUNC = tfnp, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.638 UTC client backend[46575] pg_regress/returning ERROR: column old.f3 does not exist at character 38 2025-11-30 18:45:24.638 UTC client backend[46575] pg_regress/returning STATEMENT: UPDATE foo SET f4 = f4 + 1 RETURNING old.f3; 2025-11-30 18:45:24.643 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf2p(anyarray, anyelement) does not exist 2025-11-30 18:45:24.643 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn16a(BASETYPE = anyelement, SFUNC = tf2p, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.644 UTC client backend[46566] pg_regress/alter_table ERROR: cannot rename inherited constraint "con1" 2025-11-30 18:45:24.644 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE constraint_rename_test2 RENAME CONSTRAINT con1 TO con1foo; 2025-11-30 18:45:24.644 UTC client backend[46578] pg_regress/copy2 ERROR: cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction 2025-11-30 18:45:24.644 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY vistest FROM stdin CSV FREEZE; 2025-11-30 18:45:24.644 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf2p(anyarray, anyelement) does not exist 2025-11-30 18:45:24.644 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn16b(BASETYPE = anyelement, SFUNC = tf2p, STYPE = anyarray, INITCOND = '{}'); 2025-11-30 18:45:24.644 UTC client backend[46566] pg_regress/alter_table ERROR: inherited constraint "con1" must be renamed in child tables too 2025-11-30 18:45:24.644 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE ONLY constraint_rename_test RENAME CONSTRAINT con1 TO con1foo; 2025-11-30 18:45:24.647 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.647 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.647 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn17a(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.648 UTC client backend[46571] pg_regress/sequence ERROR: relation "asdf" does not exist 2025-11-30 18:45:24.648 UTC client backend[46571] pg_regress/sequence STATEMENT: COMMENT ON SEQUENCE asdf IS 'won''t work'; 2025-11-30 18:45:24.649 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine transition data type 2025-11-30 18:45:24.649 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.649 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn18a(BASETYPE = int, SFUNC = tfp, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.651 UTC client backend[46582] pg_regress/polymorphism ERROR: function tf1p(anyarray, anyelement) does not exist 2025-11-30 18:45:24.651 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn19a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.652 UTC client backend[46582] pg_regress/polymorphism ERROR: function ffnp(anyarray) does not exist 2025-11-30 18:45:24.652 UTC client backend[46582] pg_regress/polymorphism STATEMENT: CREATE AGGREGATE myaggn20a(BASETYPE = anyelement, SFUNC = tfp, STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}'); 2025-11-30 18:45:24.655 UTC client backend[46578] pg_regress/copy2 ERROR: cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction 2025-11-30 18:45:24.655 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY vistest FROM stdin CSV FREEZE; 2025-11-30 18:45:24.657 UTC client backend[46575] pg_regress/returning ERROR: RETURNING must have at least one column at character 38 2025-11-30 18:45:24.657 UTC client backend[46575] pg_regress/returning STATEMENT: INSERT INTO zerocol SELECT RETURNING old.*, new.*, *; 2025-11-30 18:45:24.659 UTC client backend[46571] pg_regress/sequence ERROR: lastval is not yet defined in this session 2025-11-30 18:45:24.659 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT lastval(); 2025-11-30 18:45:24.661 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.661 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_func'; 2025-11-30 18:45:24.663 UTC client backend[46571] pg_regress/sequence ERROR: lastval is not yet defined in this session 2025-11-30 18:45:24.663 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT lastval(); 2025-11-30 18:45:24.663 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.663 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_func'; 2025-11-30 18:45:24.668 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.668 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_operator'; 2025-11-30 18:45:24.673 UTC client backend[46579] pg_regress/with ERROR: cycle column "foo" not in WITH query column list at character 144 2025-11-30 18:45:24.673 UTC client backend[46579] 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-11-30 18:45:24.674 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.674 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_type'; 2025-11-30 18:45:24.679 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.679 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_view'; 2025-11-30 18:45:24.685 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.685 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_sequence'; 2025-11-30 18:45:24.688 UTC client backend[46579] pg_regress/with ERROR: CYCLE types boolean and integer cannot be matched at character 184 2025-11-30 18:45:24.688 UTC client backend[46579] 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-11-30 18:45:24.691 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.691 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_tab'; 2025-11-30 18:45:24.692 UTC client backend[46578] pg_regress/copy2 ERROR: null value in column "b" of relation "forcetest" violates not-null constraint 2025-11-30 18:45:24.692 UTC client backend[46578] pg_regress/copy2 DETAIL: Failing row contains (3, null, , null, null). 2025-11-30 18:45:24.692 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY forcetest, line 1: "3,,""" 2025-11-30 18:45:24.692 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NULL(b), FORCE_NOT_NULL(c)); 2025-11-30 18:45:24.692 UTC client backend[46571] pg_regress/sequence ERROR: cannot execute nextval() in a read-only transaction 2025-11-30 18:45:24.692 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT nextval('sequence_test2'); 2025-11-30 18:45:24.693 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.693 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_tab'; 2025-11-30 18:45:24.694 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.694 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_tab'; 2025-11-30 18:45:24.695 UTC client backend[46571] pg_regress/sequence ERROR: cannot execute setval() in a read-only transaction 2025-11-30 18:45:24.695 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT setval('sequence_test2', 1); 2025-11-30 18:45:24.698 UTC client backend[46583] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.698 UTC client backend[46583] pg_regress/temp STATEMENT: prepare transaction 'twophase_tab'; 2025-11-30 18:45:24.698 UTC client backend[46578] pg_regress/copy2 ERROR: FORCE_NOT_NULL column "b" not referenced by COPY 2025-11-30 18:45:24.698 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY forcetest (d, e) FROM STDIN WITH (FORMAT csv, FORCE_NOT_NULL(b)); 2025-11-30 18:45:24.700 UTC client backend[46572] pg_regress/rangefuncs ERROR: function result type must be integer because of OUT parameters 2025-11-30 18:45:24.700 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: CREATE OR REPLACE FUNCTION rngfunc(in f1 int, out f2 int) RETURNS float AS 'select $1+1' LANGUAGE sql; 2025-11-30 18:45:24.701 UTC client backend[46572] pg_regress/rangefuncs ERROR: function result type must be record because of OUT parameters 2025-11-30 18:45:24.701 UTC client backend[46572] 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-11-30 18:45:24.701 UTC client backend[46572] pg_regress/rangefuncs ERROR: cannot change return type of existing function 2025-11-30 18:45:24.701 UTC client backend[46572] pg_regress/rangefuncs HINT: Use DROP FUNCTION rngfunc(integer) first. 2025-11-30 18:45:24.701 UTC client backend[46572] 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-11-30 18:45:24.701 UTC client backend[46578] pg_regress/copy2 ERROR: FORCE_NULL column "b" not referenced by COPY 2025-11-30 18:45:24.701 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY forcetest (d, e) FROM STDIN WITH (FORMAT csv, FORCE_NULL(b)); 2025-11-30 18:45:24.703 UTC client backend[46577] pg_regress/xml ERROR: could not parse XML document 2025-11-30 18:45:24.703 UTC client backend[46577] pg_regress/xml DETAIL: line 1: xmlns: '<' is not a valid URI ^ 2025-11-30 18:45:24.703 UTC client backend[46577] pg_regress/xml CONTEXT: SQL function "xpath" statement 1 2025-11-30 18:45:24.703 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xpath('/*', ''); 2025-11-30 18:45:24.704 UTC unrecognized[46584] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.704 UTC client backend[46577] pg_regress/xml ERROR: could not parse XML document 2025-11-30 18:45:24.704 UTC client backend[46577] pg_regress/xml DETAIL: line 1: Namespace prefix nosuchprefix on tag is not defined ^ 2025-11-30 18:45:24.704 UTC client backend[46577] pg_regress/xml CONTEXT: SQL function "xpath" statement 1 2025-11-30 18:45:24.704 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT xpath('/*', ''); 2025-11-30 18:45:24.704 UTC client backend[46584] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.704 UTC client backend[46584] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/temp 2025-11-30 18:45:24.705 UTC client backend[46584] pg_regress/temp LOG: connection ready: setup total=2.960 ms, fork=0.514 ms, authentication=0.122 ms 2025-11-30 18:45:24.707 UTC client backend[46572] pg_regress/rangefuncs ERROR: could not determine polymorphic type because input has type unknown 2025-11-30 18:45:24.707 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: SELECT dup('xyz'); 2025-11-30 18:45:24.707 UTC client backend[46584] pg_regress/temp ERROR: cannot PREPARE a transaction that has operated on temporary objects 2025-11-30 18:45:24.707 UTC client backend[46584] pg_regress/temp STATEMENT: PREPARE TRANSACTION 'twophase_search'; 2025-11-30 18:45:24.708 UTC client backend[46577] pg_regress/xml WARNING: line 1: xmlns: URI relative is not absolute ^ 2025-11-30 18:45:24.708 UTC client backend[46577] pg_regress/xml CONTEXT: SQL function "xpath" statement 1 2025-11-30 18:45:24.708 UTC client backend[46572] pg_regress/rangefuncs ERROR: cannot change name of input parameter "f1" 2025-11-30 18:45:24.708 UTC client backend[46572] pg_regress/rangefuncs HINT: Use DROP FUNCTION dup(anyelement) first. 2025-11-30 18:45:24.708 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: CREATE OR REPLACE FUNCTION dup (inout f2 anyelement, out f3 anyarray) AS 'select $1, array[$1,$1]' LANGUAGE sql; 2025-11-30 18:45:24.708 UTC client backend[46579] pg_regress/with ERROR: could not identify an equality operator for type point 2025-11-30 18:45:24.708 UTC client backend[46579] 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-11-30 18:45:24.709 UTC client backend[46579] pg_regress/with ERROR: cycle mark column name "label" already used in WITH query column list at character 144 2025-11-30 18:45:24.709 UTC client backend[46579] 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-11-30 18:45:24.709 UTC client backend[46579] pg_regress/with ERROR: cycle path column name "label" already used in WITH query column list at character 144 2025-11-30 18:45:24.709 UTC client backend[46579] 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-11-30 18:45:24.709 UTC client backend[46579] pg_regress/with ERROR: cycle mark column name and cycle path column name are the same at character 144 2025-11-30 18:45:24.709 UTC client backend[46579] 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-11-30 18:45:24.709 UTC client backend[46579] pg_regress/with ERROR: cycle column "f" specified more than once at character 144 2025-11-30 18:45:24.709 UTC client backend[46579] 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-11-30 18:45:24.710 UTC client backend[46579] pg_regress/with ERROR: search sequence column name and cycle mark column name are the same at character 144 2025-11-30 18:45:24.710 UTC client backend[46579] 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-11-30 18:45:24.710 UTC client backend[46572] pg_regress/rangefuncs ERROR: cannot determine result data type 2025-11-30 18:45:24.710 UTC client backend[46572] pg_regress/rangefuncs DETAIL: A result of type anyelement requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange. 2025-11-30 18:45:24.710 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: CREATE FUNCTION bad (f1 int, out f2 anyelement, out f3 anyarray) AS 'select $1, array[$1,$1]' LANGUAGE sql; 2025-11-30 18:45:24.710 UTC client backend[46579] pg_regress/with ERROR: search sequence column name and cycle path column name are the same at character 144 2025-11-30 18:45:24.710 UTC client backend[46579] 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-11-30 18:45:24.710 UTC unrecognized[46585] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:24.711 UTC client backend[46571] pg_regress/sequence ERROR: permission denied for sequence seq3 2025-11-30 18:45:24.711 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT nextval('seq3'); 2025-11-30 18:45:24.711 UTC client backend[46585] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:24.711 UTC client backend[46585] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/temp 2025-11-30 18:45:24.712 UTC client backend[46585] pg_regress/temp LOG: connection ready: setup total=4.077 ms, fork=1.636 ms, authentication=0.113 ms 2025-11-30 18:45:24.712 UTC client backend[46584] pg_regress/temp LOG: disconnection: session time: 0:00:00.008 user=postgres database=regression host=[local] 2025-11-30 18:45:24.714 UTC client backend[46583] pg_regress/temp LOG: disconnection: session time: 0:00:00.361 user=postgres database=regression host=[local] 2025-11-30 18:45:24.716 UTC client backend[46574] pg_regress/truncate ERROR: relation "truncate_a_id1" does not exist at character 16 2025-11-30 18:45:24.716 UTC client backend[46574] pg_regress/truncate STATEMENT: SELECT nextval('truncate_a_id1'); 2025-11-30 18:45:24.717 UTC client backend[46574] pg_regress/truncate ERROR: cannot truncate only a partitioned table 2025-11-30 18:45:24.717 UTC client backend[46574] pg_regress/truncate HINT: Do not specify the ONLY keyword, or use TRUNCATE ONLY on the partitions directly. 2025-11-30 18:45:24.717 UTC client backend[46574] pg_regress/truncate STATEMENT: TRUNCATE ONLY truncparted; 2025-11-30 18:45:24.719 UTC client backend[46574] pg_regress/truncate ERROR: cannot truncate only a partitioned table 2025-11-30 18:45:24.719 UTC client backend[46574] pg_regress/truncate HINT: Do not specify the ONLY keyword, or use TRUNCATE ONLY on the partitions directly. 2025-11-30 18:45:24.719 UTC client backend[46574] pg_regress/truncate STATEMENT: TRUNCATE ONLY truncparted; 2025-11-30 18:45:24.725 UTC client backend[46572] pg_regress/rangefuncs ERROR: cannot determine result data type 2025-11-30 18:45:24.725 UTC client backend[46572] pg_regress/rangefuncs DETAIL: A result of type anycompatible requires at least one input of type anycompatible, anycompatiblearray, anycompatiblenonarray, anycompatiblerange, or anycompatiblemultirange. 2025-11-30 18:45:24.725 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: CREATE FUNCTION bad (f1 anyarray, out f2 anycompatible, out f3 anycompatiblearray) AS 'select $1, array[$1,$1]' LANGUAGE sql; 2025-11-30 18:45:24.730 UTC client backend[46582] pg_regress/polymorphism ERROR: function add_group(smallint[], bigint, integer) does not exist 2025-11-30 18:45:24.730 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create aggregate build_group(int8, integer) ( SFUNC = add_group, STYPE = int2[] ); 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: WITH query "x" has 1 columns available but 2 columns specified at character 6 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH x(n, b) AS (SELECT 1) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT 1 INTERSECT SELECT n+1 FROM x) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT 1 INTERSECT ALL SELECT n+1 FROM x) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT 1 EXCEPT SELECT n+1 FROM x) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT 1 EXCEPT ALL SELECT n+1 FROM x) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT n FROM x) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within its non-recursive term at character 39 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT n FROM x UNION ALL SELECT 1) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within a subquery at character 54 2025-11-30 18:45:24.731 UTC client backend[46579] 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-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within its non-recursive term at character 55 2025-11-30 18:45:24.731 UTC client backend[46579] 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-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: ORDER BY in a recursive query is not implemented at character 63 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS ( SELECT 0 UNION SELECT 1 ORDER BY (SELECT n FROM x)) SELECT * FROM x; 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with ERROR: recursive query "x" must not contain data-modifying statements at character 16 2025-11-30 18:45:24.731 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS ( WITH sub_cte AS (SELECT * FROM x) DELETE FROM graph RETURNING f) SELECT * FROM x; 2025-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within an outer join at character 95 2025-11-30 18:45:24.732 UTC client backend[46579] 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-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within an outer join at character 83 2025-11-30 18:45:24.732 UTC client backend[46579] 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-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within an outer join at character 83 2025-11-30 18:45:24.732 UTC client backend[46579] 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-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within a subquery at character 114 2025-11-30 18:45:24.732 UTC client backend[46579] 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-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: aggregate functions are not allowed in a recursive query's recursive term at character 51 2025-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT count(*) FROM x) SELECT * FROM x; 2025-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: aggregate functions are not allowed in a recursive query's recursive term at character 51 2025-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT sum(n) FROM x) SELECT * FROM x; 2025-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: ORDER BY in a recursive query is not implemented at character 71 2025-11-30 18:45:24.732 UTC client backend[46579] 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-11-30 18:45:24.732 UTC client backend[46579] pg_regress/with ERROR: OFFSET in a recursive query is not implemented at character 78 2025-11-30 18:45:24.732 UTC client backend[46579] 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-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: FOR UPDATE/SHARE in a recursive query is not implemented 2025-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x FOR UPDATE) SELECT * FROM x; 2025-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "x" must not appear within a subquery at character 77 2025-11-30 18:45:24.733 UTC client backend[46579] 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-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: mutual recursion between WITH items is not implemented at character 18 2025-11-30 18:45:24.733 UTC client backend[46579] 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-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "foo" must not appear more than once at character 140 2025-11-30 18:45:24.733 UTC client backend[46579] 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-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "foo" must not appear more than once at character 158 2025-11-30 18:45:24.733 UTC client backend[46579] 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-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "foo" must not appear within EXCEPT at character 137 2025-11-30 18:45:24.733 UTC client backend[46579] 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-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "foo" must not appear more than once at character 140 2025-11-30 18:45:24.733 UTC client backend[46579] 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-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with ERROR: recursive query "foo" column 1 has type integer in non-recursive term but type numeric overall at character 37 2025-11-30 18:45:24.733 UTC client backend[46579] pg_regress/with HINT: Cast the output of the non-recursive term to the correct type. 2025-11-30 18:45:24.733 UTC client backend[46579] 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-11-30 18:45:24.734 UTC client backend[46579] 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-11-30 18:45:24.734 UTC client backend[46579] pg_regress/with HINT: Cast the output of the non-recursive term to the correct type. 2025-11-30 18:45:24.734 UTC client backend[46579] 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-11-30 18:45:24.735 UTC client backend[46579] pg_regress/with ERROR: cannot refer to OLD within WITH query 2025-11-30 18:45:24.735 UTC client backend[46579] 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-11-30 18:45:24.735 UTC client backend[46577] pg_regress/xml ERROR: XMLTABLE function has 1 columns available but 2 columns specified 2025-11-30 18:45:24.735 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT * FROM XMLTABLE (ROW () PASSING null COLUMNS v1 timestamp) AS f (v1, v2); 2025-11-30 18:45:24.735 UTC client backend[46578] pg_regress/copy2 ERROR: conflicting or redundant options at character 73 2025-11-30 18:45:24.735 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NOT_NULL *, FORCE_NOT_NULL(b)); 2025-11-30 18:45:24.737 UTC client backend[46570] pg_regress/domain ERROR: duplicate key value violates unique constraint "dcomptable_d1_key" 2025-11-30 18:45:24.737 UTC client backend[46570] pg_regress/domain DETAIL: Key (d1)=({"(1,2)"}) already exists. 2025-11-30 18:45:24.737 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dcomptable values (array[row(1,2)]::dcomptypea); 2025-11-30 18:45:24.737 UTC client backend[46579] pg_regress/with ERROR: outer-level aggregate cannot use a nested CTE at character 63 2025-11-30 18:45:24.737 UTC client backend[46579] pg_regress/with DETAIL: CTE "cte1" is below the aggregate's semantic level. 2025-11-30 18:45:24.737 UTC client backend[46579] pg_regress/with STATEMENT: select f1, (with cte1(x,y) as (select 1,2) select count((select i4.f1 from cte1))) as ss from int4_tbl i4; 2025-11-30 18:45:24.738 UTC client backend[46577] pg_regress/xml ERROR: option name "__pg__is_not_null" cannot be used in XMLTABLE at character 66 2025-11-30 18:45:24.738 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT * FROM XMLTABLE (ROW () PASSING null COLUMNS v1 timestamp __pg__is_not_null 1) AS f (v1); 2025-11-30 18:45:24.738 UTC client backend[46579] pg_regress/with ERROR: relation "outermost" does not exist at character 96 2025-11-30 18:45:24.738 UTC client backend[46579] pg_regress/with DETAIL: There is a WITH item named "outermost", but it cannot be referenced from this part of the query. 2025-11-30 18:45:24.738 UTC client backend[46579] pg_regress/with HINT: Use WITH RECURSIVE, or re-order the WITH items to remove forward references. 2025-11-30 18:45:24.738 UTC client backend[46579] 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-11-30 18:45:24.739 UTC client backend[46579] pg_regress/with ERROR: recursive reference to query "outermost" must not appear within a subquery at character 69 2025-11-30 18:45:24.739 UTC client backend[46579] 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-11-30 18:45:24.740 UTC client backend[46574] pg_regress/truncate ERROR: cannot truncate a table referenced in a foreign key constraint 2025-11-30 18:45:24.740 UTC client backend[46574] pg_regress/truncate DETAIL: Table "truncpart" references "truncprim". 2025-11-30 18:45:24.740 UTC client backend[46574] pg_regress/truncate HINT: Truncate table "truncpart" at the same time, or use TRUNCATE ... CASCADE. 2025-11-30 18:45:24.740 UTC client backend[46574] pg_regress/truncate STATEMENT: TRUNCATE TABLE truncprim; 2025-11-30 18:45:24.741 UTC client backend[46578] pg_regress/copy2 ERROR: conflicting or redundant options at character 69 2025-11-30 18:45:24.741 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NULL *, FORCE_NULL(b)); 2025-11-30 18:45:24.748 UTC client backend[46577] pg_regress/xml ERROR: DEFAULT namespace is not supported 2025-11-30 18:45:24.748 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT * FROM XMLTABLE(XMLNAMESPACES(DEFAULT 'http://x.y'), '/rows/row' PASSING '10' COLUMNS a int PATH 'a'); 2025-11-30 18:45:24.754 UTC client backend[46585] pg_regress/temp ERROR: no empty local buffer available 2025-11-30 18:45:24.754 UTC client backend[46585] pg_regress/temp CONTEXT: SQL statement "DECLARE c_99 CURSOR FOR SELECT ctid FROM test_temp WHERE ctid >= '( 99, 1)'::tid " PL/pgSQL function test_temp_pin(integer,integer) line 9 at EXECUTE 2025-11-30 18:45:24.754 UTC client backend[46585] pg_regress/temp STATEMENT: SELECT test_temp_pin(10, 105); 2025-11-30 18:45:24.769 UTC client backend[46585] pg_regress/temp ERROR: no empty local buffer available 2025-11-30 18:45:24.769 UTC client backend[46585] pg_regress/temp CONTEXT: SQL statement "DECLARE c_99 CURSOR FOR SELECT ctid FROM test_temp WHERE ctid >= '( 99, 1)'::tid " PL/pgSQL function test_temp_pin(integer,integer) line 9 at EXECUTE 2025-11-30 18:45:24.769 UTC client backend[46585] pg_regress/temp STATEMENT: SELECT test_temp_pin(10, 105); 2025-11-30 18:45:24.770 UTC client backend[46576] pg_regress/rowtypes ERROR: column "f1" is of type integer but expression is of type compos at character 82 2025-11-30 18:45:24.770 UTC client backend[46576] pg_regress/rowtypes HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:24.770 UTC client backend[46576] pg_regress/rowtypes STATEMENT: create function fcompos1(v compos) returns void as $$ insert into compos values (v); -- fail $$ language sql; 2025-11-30 18:45:24.771 UTC client backend[46579] pg_regress/with ERROR: INSERT ... SELECT rule actions are not supported for queries having data-modifying statements in WITH 2025-11-30 18:45:24.771 UTC client backend[46579] pg_regress/with STATEMENT: WITH t1 AS ( DELETE FROM bug6051 RETURNING * ) INSERT INTO bug6051 SELECT * FROM t1; 2025-11-30 18:45:24.774 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot compare arrays of different element types 2025-11-30 18:45:24.774 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select max(histogram_bounds) from pg_stats where tablename = 'pg_am'; 2025-11-30 18:45:24.774 UTC client backend[46571] pg_regress/sequence ERROR: permission denied for sequence seq3 2025-11-30 18:45:24.774 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT currval('seq3'); 2025-11-30 18:45:24.780 UTC client backend[46582] pg_regress/polymorphism ERROR: function "array_in" in FROM has unsupported return type anyarray at character 15 2025-11-30 18:45:24.780 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from array_in('{1,2,3}','int4'::regtype,-1); 2025-11-30 18:45:24.780 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot accept a value of type anyrange 2025-11-30 18:45:24.780 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select anyrange_in('[10,20)','int4range'::regtype,-1); 2025-11-30 18:45:24.785 UTC client backend[46585] pg_regress/temp ERROR: cannot DROP TABLE "test_temp" because it is being used by active queries in this session 2025-11-30 18:45:24.785 UTC client backend[46585] pg_regress/temp STATEMENT: DROP TABLE test_temp; 2025-11-30 18:45:24.786 UTC client backend[46582] pg_regress/polymorphism ERROR: function myleast() does not exist at character 8 2025-11-30 18:45:24.786 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given number of arguments. 2025-11-30 18:45:24.786 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select myleast(); 2025-11-30 18:45:24.788 UTC client backend[46578] pg_regress/copy2 ERROR: new row for relation "check_con_tbl" violates check constraint "check_con_tbl_check" 2025-11-30 18:45:24.788 UTC client backend[46578] pg_regress/copy2 DETAIL: Failing row contains (0). 2025-11-30 18:45:24.788 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY check_con_tbl, line 1: "0" 2025-11-30 18:45:24.788 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy check_con_tbl from stdin; 2025-11-30 18:45:24.789 UTC client backend[46585] pg_regress/temp ERROR: cannot TRUNCATE "test_temp" because it is being used by active queries in this session 2025-11-30 18:45:24.789 UTC client backend[46585] pg_regress/temp STATEMENT: TRUNCATE test_temp; 2025-11-30 18:45:24.795 UTC client backend[46577] pg_regress/xml ERROR: more than one value returned by column XPath expression 2025-11-30 18:45:24.795 UTC client backend[46577] pg_regress/xml STATEMENT: SELECT * FROM xmltable('/root' passing 'a1aa2a bbbbxxxcccc' COLUMNS element text PATH 'element/text()'); 2025-11-30 18:45:24.804 UTC client backend[46571] pg_regress/sequence ERROR: permission denied for sequence seq3 2025-11-30 18:45:24.804 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT lastval(); 2025-11-30 18:45:24.810 UTC client backend[46571] pg_regress/sequence ERROR: permission denied for sequence seq3 2025-11-30 18:45:24.810 UTC client backend[46571] pg_regress/sequence STATEMENT: SELECT setval('seq3', 5); 2025-11-30 18:45:24.810 UTC client backend[46571] pg_regress/sequence ERROR: must be owner of sequence sequence_test2 2025-11-30 18:45:24.810 UTC client backend[46571] pg_regress/sequence STATEMENT: ALTER SEQUENCE sequence_test2 START WITH 1; 2025-11-30 18:45:24.816 UTC client backend[46577] pg_regress/xml ERROR: null is not allowed in column "size" 2025-11-30 18:45:24.816 UTC client backend[46577] 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-11-30 18:45:24.826 UTC client backend[46585] pg_regress/temp LOG: disconnection: session time: 0:00:00.116 user=postgres database=regression host=[local] 2025-11-30 18:45:24.828 UTC client backend[46571] pg_regress/sequence LOG: disconnection: session time: 0:00:00.536 user=postgres database=regression host=[local] 2025-11-30 18:45:24.831 UTC client backend[46570] pg_regress/domain ERROR: column "d1" of table "dcomptable" contains values that violate the new constraint 2025-11-30 18:45:24.831 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain dcomptypea add constraint c2 check (value[1].r > value[1].i); 2025-11-30 18:45:24.835 UTC client backend[46575] pg_regress/returning LOG: disconnection: session time: 0:00:00.540 user=postgres database=regression host=[local] 2025-11-30 18:45:24.837 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptypea violates check constraint "c1" 2025-11-30 18:45:24.837 UTC client backend[46570] pg_regress/domain STATEMENT: select array[row(2,1)]::dcomptypea; 2025-11-30 18:45:24.845 UTC client backend[46582] pg_regress/polymorphism ERROR: function formarray(numeric, numeric[]) does not exist at character 8 2025-11-30 18:45:24.845 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.845 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.845 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select formarray(1.1, array[1.2,55.5]); 2025-11-30 18:45:24.849 UTC client backend[46582] pg_regress/polymorphism ERROR: function formarray(integer, text) does not exist at character 8 2025-11-30 18:45:24.849 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.849 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.849 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select formarray(1, 'x'::text); 2025-11-30 18:45:24.853 UTC client backend[46578] pg_regress/copy2 ERROR: permission denied for table rls_t1 2025-11-30 18:45:24.853 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY rls_t1 TO stdout; 2025-11-30 18:45:24.854 UTC client backend[46582] pg_regress/polymorphism ERROR: function formarray(integer, text[]) does not exist at character 8 2025-11-30 18:45:24.854 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.854 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.854 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select formarray(1, variadic array['x'::text]); 2025-11-30 18:45:24.854 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptypea violates check constraint "c1" 2025-11-30 18:45:24.854 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dcomptable values (array[row(2,1)]::comptype[]); 2025-11-30 18:45:24.867 UTC client backend[46566] pg_regress/alter_table ERROR: column "c" referenced in foreign key constraint does not exist 2025-11-30 18:45:24.867 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 add constraint attmpconstr foreign key(c) references attmp2 match full; 2025-11-30 18:45:24.867 UTC client backend[46578] pg_regress/copy2 ERROR: permission denied for table rls_t1 2025-11-30 18:45:24.867 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY rls_t1 (a, b, c) TO stdout; 2025-11-30 18:45:24.868 UTC client backend[46566] pg_regress/alter_table ERROR: column "b" referenced in foreign key constraint does not exist 2025-11-30 18:45:24.868 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 add constraint attmpconstr foreign key(a) references attmp2(b) match full; 2025-11-30 18:45:24.868 UTC client backend[46578] pg_regress/copy2 ERROR: permission denied for table rls_t1 2025-11-30 18:45:24.868 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY rls_t1 (c) TO stdout; 2025-11-30 18:45:24.868 UTC client backend[46572] pg_regress/rangefuncs ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:24.868 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from array_to_set(array['one', 'two']); 2025-11-30 18:45:24.868 UTC client backend[46572] pg_regress/rangefuncs ERROR: return type mismatch in function declared to return record 2025-11-30 18:45:24.868 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Final statement returns integer instead of point at column 1. 2025-11-30 18:45:24.868 UTC client backend[46572] pg_regress/rangefuncs CONTEXT: SQL function "array_to_set" statement 1 2025-11-30 18:45:24.868 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from array_to_set(array['one', 'two']) as t(f1 point,f2 text); 2025-11-30 18:45:24.870 UTC client backend[46566] pg_regress/alter_table ERROR: insert or update on table "attmp3" violates foreign key constraint "attmpconstr" 2025-11-30 18:45:24.870 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (a)=(5) is not present in table "attmp2". 2025-11-30 18:45:24.870 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 add constraint attmpconstr foreign key (a) references attmp2 match full; 2025-11-30 18:45:24.871 UTC client backend[46572] pg_regress/rangefuncs ERROR: return type mismatch in function declared to return record 2025-11-30 18:45:24.871 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Final statement returns integer instead of point at column 1. 2025-11-30 18:45:24.871 UTC client backend[46572] pg_regress/rangefuncs CONTEXT: SQL function "array_to_set" during inlining 2025-11-30 18:45:24.871 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from array_to_set(array['one', 'two']) as t(f1 point,f2 text); 2025-11-30 18:45:24.873 UTC client backend[46572] pg_regress/rangefuncs ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:24.873 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from testrngfunc(); 2025-11-30 18:45:24.875 UTC client backend[46572] pg_regress/rangefuncs ERROR: a column definition list is required for functions returning "record" at character 15 2025-11-30 18:45:24.875 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from testrngfunc(); 2025-11-30 18:45:24.878 UTC client backend[46568] pg_regress/plpgsql ERROR: duplicate key value violates unique constraint "pfield_name" 2025-11-30 18:45:24.878 UTC client backend[46568] pg_regress/plpgsql DETAIL: Key (name)=(PF1_1) already exists. 2025-11-30 18:45:24.878 UTC client backend[46568] pg_regress/plpgsql STATEMENT: insert into PField values ('PF1_1', 'should fail due to unique index'); 2025-11-30 18:45:24.878 UTC client backend[46576] pg_regress/rowtypes ERROR: function text(fullname) does not exist at character 8 2025-11-30 18:45:24.878 UTC client backend[46576] pg_regress/rowtypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.878 UTC client backend[46576] pg_regress/rowtypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.878 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select text(fullname) from fullname; 2025-11-30 18:45:24.880 UTC client backend[46566] pg_regress/alter_table ERROR: insert or update on table "attmp3" violates foreign key constraint "attmpconstr" 2025-11-30 18:45:24.880 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (a)=(5) is not present in table "attmp2". 2025-11-30 18:45:24.880 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 validate constraint attmpconstr; 2025-11-30 18:45:24.882 UTC client backend[46566] pg_regress/alter_table ERROR: check constraint "b_greater_than_ten" of relation "attmp3" is violated by some row 2025-11-30 18:45:24.882 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 ADD CONSTRAINT b_greater_than_ten CHECK (b > 10); 2025-11-30 18:45:24.884 UTC client backend[46574] pg_regress/truncate LOG: disconnection: session time: 0:00:00.587 user=postgres database=regression host=[local] 2025-11-30 18:45:24.884 UTC client backend[46566] pg_regress/alter_table ERROR: check constraint "b_greater_than_ten" of relation "attmp3" is violated by some row 2025-11-30 18:45:24.884 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 VALIDATE CONSTRAINT b_greater_than_ten; 2025-11-30 18:45:24.885 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptypea violates check constraint "c1" 2025-11-30 18:45:24.885 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dcomptable (d1[1].r, d1[1].i) values(100, 99); 2025-11-30 18:45:24.885 UTC client backend[46566] pg_regress/alter_table ERROR: cannot validate NOT ENFORCED constraint 2025-11-30 18:45:24.885 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 VALIDATE CONSTRAINT b_greater_than_ten_not_enforced; 2025-11-30 18:45:24.886 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer, integer, integer) does not exist at character 8 2025-11-30 18:45:24.886 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given number of arguments. 2025-11-30 18:45:24.886 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select dfunc(10, 20, 30); 2025-11-30 18:45:24.886 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc() does not exist 2025-11-30 18:45:24.886 UTC client backend[46582] pg_regress/polymorphism STATEMENT: drop function dfunc(); 2025-11-30 18:45:24.886 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer) does not exist 2025-11-30 18:45:24.886 UTC client backend[46582] pg_regress/polymorphism STATEMENT: drop function dfunc(int); 2025-11-30 18:45:24.887 UTC client backend[46582] pg_regress/polymorphism ERROR: input parameters after one with a default value must also have defaults at character 34 2025-11-30 18:45:24.887 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function dfunc(a int = 1, b int) returns int as $$ select $1 + $2; $$ language sql; 2025-11-30 18:45:24.892 UTC client backend[46566] pg_regress/alter_table ERROR: check constraint "b_le_20" of relation "attmp6" is violated by some row 2025-11-30 18:45:24.892 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp3 VALIDATE CONSTRAINT b_le_20; 2025-11-30 18:45:24.893 UTC client backend[46568] pg_regress/plpgsql ERROR: WS.not.there does not exist 2025-11-30 18:45:24.893 UTC client backend[46568] 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-11-30 18:45:24.893 UTC client backend[46568] pg_regress/plpgsql STATEMENT: update PSlot set backlink = 'WS.not.there' where slotname = 'PS.base.a1'; 2025-11-30 18:45:24.894 UTC client backend[46576] pg_regress/rowtypes ERROR: column fullname.text does not exist at character 8 2025-11-30 18:45:24.894 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select fullname.text from fullname; 2025-11-30 18:45:24.895 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc() is not unique at character 8 2025-11-30 18:45:24.895 UTC client backend[46582] pg_regress/polymorphism DETAIL: Could not choose a best candidate function. 2025-11-30 18:45:24.895 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.895 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select dfunc(); 2025-11-30 18:45:24.896 UTC client backend[46568] pg_regress/plpgsql ERROR: illegal backlink beginning with XX 2025-11-30 18:45:24.896 UTC client backend[46568] 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-11-30 18:45:24.896 UTC client backend[46568] pg_regress/plpgsql STATEMENT: update PSlot set backlink = 'XX.illegal' where slotname = 'PS.base.a1'; 2025-11-30 18:45:24.897 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc() is not unique at character 8 2025-11-30 18:45:24.897 UTC client backend[46582] pg_regress/polymorphism DETAIL: Could not choose a best candidate function. 2025-11-30 18:45:24.897 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.897 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select dfunc(); 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer) is not unique at character 8 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism DETAIL: Could not choose a best candidate function. 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select dfunc(1); 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer, integer) is not unique at character 8 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism DETAIL: Could not choose a best candidate function. 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.898 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select dfunc(1, 2); 2025-11-30 18:45:24.899 UTC client backend[46568] pg_regress/plpgsql ERROR: PS.not.there does not exist 2025-11-30 18:45:24.899 UTC client backend[46568] 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-11-30 18:45:24.899 UTC client backend[46568] pg_regress/plpgsql STATEMENT: update PSlot set slotlink = 'PS.not.there' where slotname = 'PS.base.a1'; 2025-11-30 18:45:24.899 UTC client backend[46582] pg_regress/polymorphism ERROR: only input parameters can have default values at character 23 2025-11-30 18:45:24.899 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function dfunc(out int = 20) returns int as $$ select 1; $$ language sql; 2025-11-30 18:45:24.901 UTC client backend[46568] pg_regress/plpgsql ERROR: illegal slotlink beginning with XX 2025-11-30 18:45:24.901 UTC client backend[46568] 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-11-30 18:45:24.901 UTC client backend[46568] pg_regress/plpgsql STATEMENT: update PSlot set slotlink = 'XX.illegal' where slotname = 'PS.base.a1'; 2025-11-30 18:45:24.902 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc() does not exist at character 8 2025-11-30 18:45:24.902 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given number of arguments. 2025-11-30 18:45:24.902 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select dfunc(); 2025-11-30 18:45:24.903 UTC client backend[46568] pg_regress/plpgsql ERROR: duplicate key value violates unique constraint "hslot_name" 2025-11-30 18:45:24.903 UTC client backend[46568] pg_regress/plpgsql DETAIL: Key (slotname)=(HS.base.hub1.1 ) already exists. 2025-11-30 18:45:24.903 UTC client backend[46568] pg_regress/plpgsql STATEMENT: insert into HSlot values ('HS', 'base.hub1', 1, ''); 2025-11-30 18:45:24.903 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptypea violates check constraint "c1" 2025-11-30 18:45:24.903 UTC client backend[46570] pg_regress/domain STATEMENT: update dcomptable set d1[1].r = d1[1].r + 1 where d1[1].i > 0; 2025-11-30 18:45:24.904 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot remove parameter defaults from existing function 2025-11-30 18:45:24.904 UTC client backend[46582] pg_regress/polymorphism HINT: Use DROP FUNCTION dfunc(integer[]) first. 2025-11-30 18:45:24.904 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create or replace function dfunc(a variadic int[]) returns int as $$ select array_upper($1, 1) $$ language sql; 2025-11-30 18:45:24.904 UTC client backend[46568] pg_regress/plpgsql ERROR: no manual manipulation of HSlot 2025-11-30 18:45:24.904 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function tg_hslot_biu() line 12 at RAISE 2025-11-30 18:45:24.904 UTC client backend[46568] pg_regress/plpgsql STATEMENT: insert into HSlot values ('HS', 'base.hub1', 20, ''); 2025-11-30 18:45:24.906 UTC client backend[46568] pg_regress/plpgsql ERROR: no manual manipulation of HSlot 2025-11-30 18:45:24.906 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function tg_hslot_bd() line 12 at RAISE 2025-11-30 18:45:24.906 UTC client backend[46568] pg_regress/plpgsql STATEMENT: delete from HSlot; 2025-11-30 18:45:24.907 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer) is not unique at character 8 2025-11-30 18:45:24.907 UTC client backend[46582] pg_regress/polymorphism DETAIL: Could not choose a best candidate function. 2025-11-30 18:45:24.907 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.907 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select dfunc(1); 2025-11-30 18:45:24.908 UTC client backend[46568] pg_regress/plpgsql ERROR: system "notthere" does not exist 2025-11-30 18:45:24.908 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function tg_iface_biu() line 8 at RAISE 2025-11-30 18:45:24.908 UTC client backend[46568] pg_regress/plpgsql STATEMENT: insert into IFace values ('IF', 'notthere', 'eth0', ''); 2025-11-30 18:45:24.909 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer) does not exist at character 15 2025-11-30 18:45:24.909 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given number of arguments. 2025-11-30 18:45:24.909 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from dfunc(0); 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism ERROR: argument name "x" used more than once at character 39 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from dfunc(x := 20, b := 10, x := 30); 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism ERROR: positional argument cannot follow named argument at character 34 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from dfunc(10, b := 20, 30); 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(x => integer, b => integer, c => integer) does not exist at character 15 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument names. 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from dfunc(x := 10, b := 20, c := 30); 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer, integer, a => integer) does not exist at character 15 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism DETAIL: In the closest available match, an argument was specified both positionally and by name. 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from dfunc(10, 10, a := 20); 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(integer, c => integer, d => integer) does not exist at character 15 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism DETAIL: In the closest available match, not all required arguments were supplied. 2025-11-30 18:45:24.910 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from dfunc(1,c := 2,d := 3); 2025-11-30 18:45:24.910 UTC client backend[46579] pg_regress/with ERROR: WITH RECURSIVE is not supported for MERGE statement 2025-11-30 18:45:24.910 UTC client backend[46579] 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-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism ERROR: function xleast(integer, arr => integer[]) does not exist at character 8 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism DETAIL: A function of that name exists, but it is not in the search_path. 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select xleast(1, variadic arr => array[2,3]); 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism ERROR: function xleast(foo => integer, arr => integer[]) does not exist at character 8 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument names. 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select xleast(foo => 1, variadic arr => array[2,3]); 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism ERROR: positional argument cannot follow named argument at character 32 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select xleast(x => 1, variadic array[2,3]); 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism ERROR: function xleast(integer, x => integer[]) does not exist at character 8 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism DETAIL: In the closest available match, an argument was specified both positionally and by name. 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select xleast(1, variadic x => array[2,3]); 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism ERROR: function xleast(arr => integer[], x => integer) does not exist at character 8 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism HINT: The VARIADIC parameter must be placed last, even when using argument names. 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select xleast(arr => array[1], variadic x => 3); 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism ERROR: function xleast(arr => integer[], x => integer) does not exist at character 8 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism HINT: This call would be correct if the variadic array were labeled VARIADIC and placed last. 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select xleast(arr => array[1], x => 3); 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism ERROR: function xleast(arr => integer, x => integer[]) does not exist at character 8 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.912 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select xleast(arr => 1, variadic x => array[2,3]); 2025-11-30 18:45:24.912 UTC client backend[46578] pg_regress/copy2 ERROR: cannot copy to view "instead_of_insert_tbl_view" 2025-11-30 18:45:24.912 UTC client backend[46578] pg_regress/copy2 HINT: To enable copying to a view, provide an INSTEAD OF INSERT trigger. 2025-11-30 18:45:24.912 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY instead_of_insert_tbl_view FROM stdin; 2025-11-30 18:45:24.913 UTC client backend[46582] pg_regress/polymorphism ERROR: function dfunc(unknown, c => integer, b => date) does not exist at character 15 2025-11-30 18:45:24.913 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.913 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.913 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select * from dfunc('Hello World', c := 20, b := '2009-07-25'::date); 2025-11-30 18:45:24.915 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot change name of input parameter "c" 2025-11-30 18:45:24.915 UTC client backend[46582] pg_regress/polymorphism HINT: Use DROP FUNCTION dfunc(character varying,numeric) first. 2025-11-30 18:45:24.915 UTC client backend[46582] 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-11-30 18:45:24.915 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot change name of input parameter "c" 2025-11-30 18:45:24.915 UTC client backend[46582] pg_regress/polymorphism HINT: Use DROP FUNCTION dfunc(character varying,numeric) first. 2025-11-30 18:45:24.915 UTC client backend[46582] 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-11-30 18:45:24.916 UTC client backend[46576] pg_regress/rowtypes ERROR: function text(record) does not exist at character 8 2025-11-30 18:45:24.916 UTC client backend[46576] pg_regress/rowtypes DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.916 UTC client backend[46576] pg_regress/rowtypes HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.916 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select text(row('Jim', 'Beam')); 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism ERROR: parameter name "a" used more than once at character 34 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function testpolym(a int, a int) returns int as $$ select 1;$$ language sql; 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism ERROR: parameter name "a" used more than once at character 43 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function testpolym(int, out a int, out a int) returns int as $$ select 1;$$ language sql; 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism ERROR: parameter name "a" used more than once at character 38 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function testpolym(out a int, inout a int) returns int as $$ select 1;$$ language sql; 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism ERROR: parameter name "a" used more than once at character 34 2025-11-30 18:45:24.916 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function testpolym(a int, inout a int) returns int as $$ select 1;$$ language sql; 2025-11-30 18:45:24.929 UTC client backend[46581] pg_regress/largeobject ERROR: large object read request is too large 2025-11-30 18:45:24.929 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_get(66687); 2025-11-30 18:45:24.930 UTC client backend[46568] pg_regress/plpgsql ERROR: IFace slotname "IF.orion.ethernet_interface_name_too_long" too long (20 char max) 2025-11-30 18:45:24.930 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function tg_iface_biu() line 14 at RAISE 2025-11-30 18:45:24.930 UTC client backend[46568] pg_regress/plpgsql STATEMENT: insert into IFace values ('IF', 'orion', 'ethernet_interface_name_too_long', ''); 2025-11-30 18:45:24.932 UTC client backend[46566] pg_regress/alter_table ERROR: check constraint "check_a_is_2" of relation "parent_noinh_convalid" is violated by some row 2025-11-30 18:45:24.932 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table parent_noinh_convalid validate constraint check_a_is_2; 2025-11-30 18:45:24.941 UTC client backend[46576] pg_regress/rowtypes ERROR: could not identify column "text" in record data type at character 9 2025-11-30 18:45:24.941 UTC client backend[46576] pg_regress/rowtypes STATEMENT: select (row('Jim', 'Beam')).text; 2025-11-30 18:45:24.941 UTC client backend[46566] pg_regress/alter_table ERROR: there is no unique constraint matching given keys for referenced table "attmp4" 2025-11-30 18:45:24.941 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE attmp5 add constraint attmpconstr foreign key(a) references attmp4(a) match full; 2025-11-30 18:45:24.941 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_open(INV_WRITE) in a read-only transaction 2025-11-30 18:45:24.941 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_open(2121, x'20000'::int); 2025-11-30 18:45:24.941 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer, point) does not exist at character 29 2025-11-30 18:45:24.941 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.941 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.941 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, point(1,2)) x; 2025-11-30 18:45:24.942 UTC client backend[46570] pg_regress/domain ERROR: value for domain posint violates check constraint "posint_check" 2025-11-30 18:45:24.942 UTC client backend[46570] pg_regress/domain STATEMENT: insert into pitable values(array[-1]); 2025-11-30 18:45:24.942 UTC client backend[46570] pg_regress/domain ERROR: value for domain posint violates check constraint "posint_check" at character 28 2025-11-30 18:45:24.942 UTC client backend[46570] pg_regress/domain STATEMENT: insert into pitable values('{0}'); 2025-11-30 18:45:24.943 UTC client backend[46570] pg_regress/domain ERROR: value for domain posint violates check constraint "posint_check" 2025-11-30 18:45:24.943 UTC client backend[46570] pg_regress/domain STATEMENT: update pitable set f1[1] = 0; 2025-11-30 18:45:24.944 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_create() in a read-only transaction 2025-11-30 18:45:24.944 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_create(42); 2025-11-30 18:45:24.945 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer, integer[]) does not exist at character 29 2025-11-30 18:45:24.945 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.945 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.945 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, array[1,2]) x; 2025-11-30 18:45:24.947 UTC client backend[46570] pg_regress/domain ERROR: value too long for type character varying(4) 2025-11-30 18:45:24.947 UTC client backend[46570] pg_regress/domain STATEMENT: insert into vc4table values(array['too long']); 2025-11-30 18:45:24.947 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_creat() in a read-only transaction 2025-11-30 18:45:24.947 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_creat(42); 2025-11-30 18:45:24.948 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_unlink() in a read-only transaction 2025-11-30 18:45:24.948 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_unlink(42); 2025-11-30 18:45:24.949 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lowrite() in a read-only transaction 2025-11-30 18:45:24.949 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lowrite(42, 'x'); 2025-11-30 18:45:24.951 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_import() in a read-only transaction 2025-11-30 18:45:24.951 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_import('/tmp/cirrus-ci-build/build/testrun/regress-running/regress/results/lotest.txt'); 2025-11-30 18:45:24.952 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_truncate() in a read-only transaction 2025-11-30 18:45:24.952 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_truncate(42, 0); 2025-11-30 18:45:24.952 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer, point[]) does not exist at character 29 2025-11-30 18:45:24.952 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.952 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.952 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, array[point(1,2)]) x; 2025-11-30 18:45:24.953 UTC client backend[46570] pg_regress/domain ERROR: column "f1" is of type dposinta[] but expression is of type integer[] at character 34 2025-11-30 18:45:24.953 UTC client backend[46570] pg_regress/domain HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:24.953 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dposintatable values(array[array[42]]); 2025-11-30 18:45:24.953 UTC client backend[46570] pg_regress/domain ERROR: column "f1" is of type dposinta[] but expression is of type posint[] at character 34 2025-11-30 18:45:24.953 UTC client backend[46570] pg_regress/domain HINT: You will need to rewrite or cast the expression. 2025-11-30 18:45:24.953 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dposintatable values(array[array[42]::posint[]]); 2025-11-30 18:45:24.953 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer, integer) does not exist at character 29 2025-11-30 18:45:24.953 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.953 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.953 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, 12) x; 2025-11-30 18:45:24.956 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_truncate64() in a read-only transaction 2025-11-30 18:45:24.956 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_truncate64(42, 0); 2025-11-30 18:45:24.956 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer, integer) does not exist at character 29 2025-11-30 18:45:24.956 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.956 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.956 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, 12) x; 2025-11-30 18:45:24.957 UTC client backend[46570] pg_regress/domain ERROR: wrong number of array subscripts 2025-11-30 18:45:24.957 UTC client backend[46570] pg_regress/domain STATEMENT: update dposintatable set f1[2][1] = array[97]; 2025-11-30 18:45:24.957 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(numeric, int4range) does not exist at character 29 2025-11-30 18:45:24.957 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.957 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.957 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11.2, int4range(4,7)) x; 2025-11-30 18:45:24.957 UTC client backend[46570] pg_regress/domain ERROR: syntax error at or near "[" at character 33 2025-11-30 18:45:24.957 UTC client backend[46570] pg_regress/domain STATEMENT: update dposintatable set (f1[2])[1] = array[98]; 2025-11-30 18:45:24.958 UTC client backend[46582] pg_regress/polymorphism ERROR: could not determine polymorphic type anycompatiblerange because input has type unknown 2025-11-30 18:45:24.958 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11.2, '[4,7)') x; 2025-11-30 18:45:24.958 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_from_bytea() in a read-only transaction 2025-11-30 18:45:24.958 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_from_bytea(0, 'x'); 2025-11-30 18:45:24.961 UTC client backend[46581] pg_regress/largeobject ERROR: cannot execute lo_put() in a read-only transaction 2025-11-30 18:45:24.961 UTC client backend[46581] pg_regress/largeobject STATEMENT: SELECT lo_put(42, 0, 'x'); 2025-11-30 18:45:24.961 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(int4range, numrange) does not exist at character 29 2025-11-30 18:45:24.961 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.961 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.961 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(int4range(11,12), numrange(4,7)) x; 2025-11-30 18:45:24.961 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine result data type 2025-11-30 18:45:24.961 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-30 18:45:24.961 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function anyctest(anycompatible) returns anycompatiblerange as $$ select $1 $$ language sql; 2025-11-30 18:45:24.963 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer, integer) does not exist at character 29 2025-11-30 18:45:24.963 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.963 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.963 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, 12) x; 2025-11-30 18:45:24.964 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(numeric, int4multirange) does not exist at character 29 2025-11-30 18:45:24.964 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.964 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.964 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11.2, multirange(int4range(4,7))) x; 2025-11-30 18:45:24.964 UTC client backend[46582] pg_regress/polymorphism ERROR: could not determine polymorphic type anycompatiblemultirange because input has type unknown 2025-11-30 18:45:24.964 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11.2, '{[4,7)}') x; 2025-11-30 18:45:24.965 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(int4multirange, nummultirange) does not exist at character 29 2025-11-30 18:45:24.965 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.965 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.965 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(multirange(int4range(11,12)), multirange(numrange(4,7))) x; 2025-11-30 18:45:24.965 UTC client backend[46582] pg_regress/polymorphism ERROR: cannot determine result data type 2025-11-30 18:45:24.965 UTC client backend[46582] pg_regress/polymorphism DETAIL: A result of type anycompatiblemultirange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-30 18:45:24.965 UTC client backend[46582] pg_regress/polymorphism STATEMENT: create function anyctest(anycompatible) returns anycompatiblemultirange as $$ select $1 $$ language sql; 2025-11-30 18:45:24.966 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer[], integer[]) does not exist at character 29 2025-11-30 18:45:24.966 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.966 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.966 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(array[11], array[1,2]) x; 2025-11-30 18:45:24.966 UTC client backend[46578] pg_regress/copy2 ERROR: invalid input syntax for type integer: "a" 2025-11-30 18:45:24.966 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY check_ign_err, line 2, column n: "a" 2025-11-30 18:45:24.966 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY check_ign_err FROM STDIN WITH (on_error stop); 2025-11-30 18:45:24.967 UTC client backend[46568] pg_regress/plpgsql ERROR: operator does not exist: point + integer at character 3 2025-11-30 18:45:24.967 UTC client backend[46568] pg_regress/plpgsql DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:24.967 UTC client backend[46568] pg_regress/plpgsql HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.967 UTC client backend[46568] pg_regress/plpgsql QUERY: x + 1 2025-11-30 18:45:24.967 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function f1(anyelement) line 3 at RETURN 2025-11-30 18:45:24.967 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select f1(point(3,4)); 2025-11-30 18:45:24.967 UTC client backend[46582] pg_regress/polymorphism ERROR: function anyctest(integer, numeric[], integer, numeric) does not exist at character 29 2025-11-30 18:45:24.967 UTC client backend[46582] pg_regress/polymorphism DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.967 UTC client backend[46582] pg_regress/polymorphism HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.967 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, array[1, 2.2], 42, 34.5) x; 2025-11-30 18:45:24.967 UTC client backend[46581] pg_regress/largeobject LOG: disconnection: session time: 0:00:00.668 user=postgres database=regression host=[local] 2025-11-30 18:45:24.968 UTC client backend[46582] pg_regress/polymorphism ERROR: invalid input syntax for type integer: "12.2" at character 42 2025-11-30 18:45:24.968 UTC client backend[46582] pg_regress/polymorphism STATEMENT: select x, pg_typeof(x) from anyctest(11, '12.2') x; 2025-11-30 18:45:24.970 UTC client backend[46582] pg_regress/polymorphism LOG: disconnection: session time: 0:00:00.669 user=postgres database=regression host=[local] 2025-11-30 18:45:24.972 UTC client backend[46579] pg_regress/with ERROR: recursive query "t" must not contain data-modifying statements at character 16 2025-11-30 18:45:24.972 UTC client backend[46579] pg_regress/with STATEMENT: WITH RECURSIVE t AS ( INSERT INTO y SELECT * FROM t ) VALUES(FALSE); 2025-11-30 18:45:24.973 UTC client backend[46570] pg_regress/domain ERROR: value for domain dcomptype violates check constraint "dcomptype_check" 2025-11-30 18:45:24.973 UTC client backend[46570] pg_regress/domain STATEMENT: update dcomptable set f1[1].cf1 = -1; 2025-11-30 18:45:24.975 UTC client backend[46579] pg_regress/with ERROR: WITH query "t" does not have a RETURNING clause at character 54 2025-11-30 18:45:24.975 UTC client backend[46579] pg_regress/with STATEMENT: WITH t AS ( INSERT INTO y VALUES(0) ) SELECT * FROM t; 2025-11-30 18:45:24.975 UTC client backend[46579] pg_regress/with ERROR: recursive query "t" must not contain data-modifying statements at character 16 2025-11-30 18:45:24.975 UTC client backend[46579] 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-11-30 18:45:24.975 UTC client backend[46579] pg_regress/with ERROR: WITH clause containing a data-modifying statement must be at the top level at character 23 2025-11-30 18:45:24.975 UTC client backend[46579] pg_regress/with STATEMENT: SELECT * FROM ( WITH t AS (UPDATE y SET a=a+1 RETURNING *) SELECT * FROM t ) ss; 2025-11-30 18:45:24.976 UTC client backend[46568] pg_regress/plpgsql ERROR: cannot determine element type of "anyarray" argument 2025-11-30 18:45:24.976 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select f1(stavalues1) from pg_statistic; 2025-11-30 18:45:24.982 UTC client backend[46568] pg_regress/plpgsql ERROR: PL/pgSQL functions cannot accept type anyarray 2025-11-30 18:45:24.982 UTC client backend[46568] pg_regress/plpgsql CONTEXT: compilation of PL/pgSQL function "f1" near line 1 2025-11-30 18:45:24.982 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select f1(stavalues1) from pg_statistic; 2025-11-30 18:45:24.983 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnull does not allow null values 2025-11-30 18:45:24.983 UTC client backend[46570] pg_regress/domain STATEMENT: INSERT INTO nulltest DEFAULT VALUES; 2025-11-30 18:45:24.983 UTC client backend[46570] pg_regress/domain ERROR: domain dcheck does not allow null values 2025-11-30 18:45:24.983 UTC client backend[46570] pg_regress/domain STATEMENT: insert into nulltest values ('a', 'b', 'c', 'd', NULL); 2025-11-30 18:45:24.984 UTC client backend[46568] pg_regress/plpgsql ERROR: cannot determine result data type 2025-11-30 18:45:24.984 UTC client backend[46568] pg_regress/plpgsql DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-30 18:45:24.984 UTC client backend[46568] pg_regress/plpgsql STATEMENT: create function f1(x anyelement) returns anyrange as $$ begin return array[x + 1, x + 2]; end$$ language plpgsql; 2025-11-30 18:45:24.984 UTC client backend[46570] pg_regress/domain ERROR: new row for relation "nulltest" violates check constraint "nulltest_col5_check" 2025-11-30 18:45:24.984 UTC client backend[46570] pg_regress/domain DETAIL: Failing row contains (a, b, c, d, a). 2025-11-30 18:45:24.984 UTC client backend[46570] pg_regress/domain STATEMENT: insert into nulltest values ('a', 'b', 'c', 'd', 'a'); 2025-11-30 18:45:24.984 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnull does not allow null values 2025-11-30 18:45:24.984 UTC client backend[46570] pg_regress/domain STATEMENT: INSERT INTO nulltest values (NULL, 'b', 'c', 'd', 'd'); 2025-11-30 18:45:24.984 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnull does not allow null values 2025-11-30 18:45:24.984 UTC client backend[46570] pg_regress/domain STATEMENT: INSERT INTO nulltest values ('a', NULL, 'c', 'd', 'c'); 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain ERROR: null value in column "col3" of relation "nulltest" violates not-null constraint 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain DETAIL: Failing row contains (a, b, null, d, c). 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain STATEMENT: INSERT INTO nulltest values ('a', 'b', NULL, 'd', 'c'); 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain ERROR: null value in column "col3" of relation "nulltest" violates not-null constraint 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain DETAIL: Failing row contains (a, b, null, d, d). 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain CONTEXT: COPY nulltest, line 1: "a b \N d d" 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain STATEMENT: COPY nulltest FROM stdin; 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain ERROR: domain dcheck does not allow null values 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain CONTEXT: COPY nulltest, line 1, column col5: null input 2025-11-30 18:45:24.985 UTC client backend[46570] pg_regress/domain STATEMENT: COPY nulltest FROM stdin; 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain ERROR: new row for relation "nulltest" violates check constraint "nulltest_col5_check" 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain DETAIL: Failing row contains (a, b, c, null, a). 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain CONTEXT: COPY nulltest, line 3: "a b c \N a" 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain STATEMENT: COPY nulltest FROM stdin; 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnull does not allow null values 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain STATEMENT: SELECT cast(NULL as dnotnull); 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnull does not allow null values 2025-11-30 18:45:24.986 UTC client backend[46570] pg_regress/domain STATEMENT: SELECT cast(cast(NULL as dnull) as dnotnull); 2025-11-30 18:45:24.987 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnull does not allow null values 2025-11-30 18:45:24.987 UTC client backend[46570] pg_regress/domain STATEMENT: SELECT cast(col4 as dnotnull) from nulltest; 2025-11-30 18:45:24.989 UTC client backend[46568] pg_regress/plpgsql ERROR: function f1(int4range, integer, numeric) does not exist at character 8 2025-11-30 18:45:24.989 UTC client backend[46568] pg_regress/plpgsql DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.989 UTC client backend[46568] pg_regress/plpgsql HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.989 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select f1(int4range(42, 49), 11, 4.5) as fail; 2025-11-30 18:45:24.990 UTC client backend[46568] pg_regress/plpgsql ERROR: cannot determine result data type 2025-11-30 18:45:24.990 UTC client backend[46568] pg_regress/plpgsql DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-30 18:45:24.990 UTC client backend[46568] pg_regress/plpgsql STATEMENT: create function f1(x anycompatible) returns anycompatiblerange as $$ begin return array[x + 1, x + 2]; end$$ language plpgsql; 2025-11-30 18:45:24.995 UTC client backend[46572] pg_regress/rangefuncs ERROR: a column definition list is redundant for a function returning a named composite type at character 34 2025-11-30 18:45:24.995 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from testrngfunc() as t(f1 int8,f2 int8); 2025-11-30 18:45:24.995 UTC client backend[46568] pg_regress/plpgsql ERROR: function f1(integer, numeric[], integer, numeric) does not exist at character 48 2025-11-30 18:45:24.995 UTC client backend[46568] pg_regress/plpgsql DETAIL: No function of that name accepts the given argument types. 2025-11-30 18:45:24.995 UTC client backend[46568] pg_regress/plpgsql HINT: You might need to add explicit type casts. 2025-11-30 18:45:24.995 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select x, pg_typeof(x), y, pg_typeof(y) from f1(11, array[1, 2.2], 42, 34.5); 2025-11-30 18:45:24.995 UTC client backend[46572] pg_regress/rangefuncs ERROR: a column definition list is redundant for a function with OUT parameters at character 38 2025-11-30 18:45:24.995 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from pg_get_keywords() as t(f1 int8,f2 int8); 2025-11-30 18:45:24.996 UTC client backend[46568] pg_regress/plpgsql ERROR: RETURN cannot have a parameter in function with OUT parameters at character 74 2025-11-30 18:45:24.996 UTC client backend[46568] pg_regress/plpgsql STATEMENT: create function f1(in i int, out j int) returns int as $$ begin return i+1; end$$ language plpgsql; 2025-11-30 18:45:24.996 UTC client backend[46572] pg_regress/rangefuncs ERROR: a column definition list is only allowed for functions returning "record" at character 27 2025-11-30 18:45:24.996 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from sin(3) as t(f1 int8,f2 int8); 2025-11-30 18:45:24.999 UTC client backend[46570] pg_regress/domain ERROR: null value in column "col5" of relation "defaulttest" violates not-null constraint 2025-11-30 18:45:24.999 UTC client backend[46570] pg_regress/domain DETAIL: Failing row contains (3, 12, 5, 0, null, 88, 8000, 12.12). 2025-11-30 18:45:24.999 UTC client backend[46570] pg_regress/domain STATEMENT: insert into defaulttest(col4) values(0); 2025-11-30 18:45:24.999 UTC client backend[46579] pg_regress/with ERROR: conditional DO INSTEAD rules are not supported for data-modifying statements in WITH 2025-11-30 18:45:24.999 UTC client backend[46579] pg_regress/with STATEMENT: WITH t AS ( INSERT INTO y VALUES(0) ) VALUES(FALSE); 2025-11-30 18:45:25.001 UTC client backend[46570] pg_regress/domain ERROR: null value in column "col5" of relation "defaulttest" violates not-null constraint 2025-11-30 18:45:25.001 UTC client backend[46570] pg_regress/domain DETAIL: Failing row contains (3, 12, 5, 0, null, 88, 8000, 12.12). 2025-11-30 18:45:25.001 UTC client backend[46570] pg_regress/domain STATEMENT: insert into defaulttest(col4) values(0); 2025-11-30 18:45:25.003 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-11-30 18:45:25.003 UTC client backend[46566] 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-11-30 18:45:25.003 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable; 2025-11-30 18:45:25.004 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-11-30 18:45:25.004 UTC client backend[46566] 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-11-30 18:45:25.004 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable(ptest1); 2025-11-30 18:45:25.008 UTC client backend[46570] pg_regress/domain ERROR: column "col1" of table "domnotnull" contains null values 2025-11-30 18:45:25.008 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain dnotnulltest set not null; 2025-11-30 18:45:25.009 UTC client backend[46566] pg_regress/alter_table ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:25.009 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-11-30 18:45:25.009 UTC client backend[46566] pg_regress/alter_table STATEMENT: INSERT INTO FKTABLE VALUES(43); 2025-11-30 18:45:25.009 UTC client backend[46579] pg_regress/with ERROR: DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH 2025-11-30 18:45:25.009 UTC client backend[46579] pg_regress/with STATEMENT: WITH t AS ( INSERT INTO y VALUES(0) ) VALUES(FALSE); 2025-11-30 18:45:25.010 UTC client backend[46570] pg_regress/domain ERROR: column "col2" of table "domnotnull" contains null values 2025-11-30 18:45:25.010 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain dnotnulltest set not null; 2025-11-30 18:45:25.011 UTC client backend[46579] pg_regress/with ERROR: DO INSTEAD NOTIFY rules are not supported for data-modifying statements in WITH 2025-11-30 18:45:25.011 UTC client backend[46579] pg_regress/with STATEMENT: WITH t AS ( INSERT INTO y VALUES(0) ) VALUES(FALSE); 2025-11-30 18:45:25.011 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnulltest does not allow null values 2025-11-30 18:45:25.011 UTC client backend[46570] pg_regress/domain STATEMENT: update domnotnull set col1 = null; 2025-11-30 18:45:25.012 UTC client backend[46579] pg_regress/with ERROR: DO ALSO rules are not supported for data-modifying statements in WITH 2025-11-30 18:45:25.012 UTC client backend[46579] pg_regress/with STATEMENT: WITH t AS ( INSERT INTO y VALUES(0) ) VALUES(FALSE); 2025-11-30 18:45:25.013 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-11-30 18:45:25.013 UTC client backend[46566] 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-11-30 18:45:25.013 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable; 2025-11-30 18:45:25.013 UTC client backend[46579] pg_regress/with ERROR: multi-statement DO INSTEAD rules are not supported for data-modifying statements in WITH 2025-11-30 18:45:25.013 UTC client backend[46579] pg_regress/with STATEMENT: WITH t AS ( INSERT INTO y VALUES(0) ) VALUES(FALSE); 2025-11-30 18:45:25.014 UTC client backend[46570] pg_regress/domain ERROR: domain dnotnulltest does not allow null values 2025-11-30 18:45:25.014 UTC client backend[46570] pg_regress/domain STATEMENT: update domnotnull set col1 = null; 2025-11-30 18:45:25.014 UTC client backend[46579] pg_regress/with ERROR: syntax error at or near "with" at character 19 2025-11-30 18:45:25.014 UTC client backend[46579] pg_regress/with STATEMENT: create table foo (with baz); 2025-11-30 18:45:25.015 UTC client backend[46579] pg_regress/with ERROR: syntax error at or near "with" at character 19 2025-11-30 18:45:25.015 UTC client backend[46579] pg_regress/with STATEMENT: create table foo (with ordinality); 2025-11-30 18:45:25.016 UTC client backend[46572] pg_regress/rangefuncs ERROR: cannot drop column moredrop of table users because other objects depend on it 2025-11-30 18:45:25.016 UTC client backend[46572] pg_regress/rangefuncs DETAIL: view usersview depends on column moredrop of table users 2025-11-30 18:45:25.016 UTC client backend[46572] pg_regress/rangefuncs HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:25.016 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: alter table users drop column moredrop; 2025-11-30 18:45:25.016 UTC client backend[46579] pg_regress/with ERROR: relation "with_test" does not exist at character 43 2025-11-30 18:45:25.016 UTC client backend[46579] pg_regress/with STATEMENT: WITH with_test AS (SELECT 42) INSERT INTO with_test VALUES (1); 2025-11-30 18:45:25.019 UTC client backend[46578] pg_regress/copy2 ERROR: invalid input syntax for type widget: "1" 2025-11-30 18:45:25.019 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY hard_err, line 1, column foo: "1" 2025-11-30 18:45:25.019 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY hard_err FROM STDIN WITH (on_error ignore); 2025-11-30 18:45:25.022 UTC client backend[46572] pg_regress/rangefuncs ERROR: attribute 5 of type record has been dropped 2025-11-30 18:45:25.022 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from usersview; 2025-11-30 18:45:25.023 UTC client backend[46566] pg_regress/alter_table ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-11-30 18:45:25.023 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-11-30 18:45:25.023 UTC client backend[46566] pg_regress/alter_table STATEMENT: INSERT INTO FKTABLE VALUES(43); 2025-11-30 18:45:25.024 UTC client backend[46572] pg_regress/rangefuncs ERROR: cannot alter type of a column used by a view or rule 2025-11-30 18:45:25.024 UTC client backend[46572] pg_regress/rangefuncs DETAIL: rule _RETURN on view usersview depends on column "seq" 2025-11-30 18:45:25.024 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: alter table users alter column seq type numeric; 2025-11-30 18:45:25.034 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:25.034 UTC client backend[46566] 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-11-30 18:45:25.034 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable; 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes ERROR: missing FROM-clause entry for table "d" at character 8 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes STATEMENT: SELECT d.a FROM (SELECT compositetable AS d FROM compositetable) s; 2025-11-30 18:45:25.035 UTC client backend[46572] pg_regress/rangefuncs ERROR: attribute 2 of type record has wrong type 2025-11-30 18:45:25.035 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Table has type numeric, but query expects integer. 2025-11-30 18:45:25.035 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from usersview; 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes ERROR: column "ctid" not found in data type compositetable at character 9 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes STATEMENT: SELECT (d).ctid FROM (SELECT compositetable AS d FROM compositetable) s; 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes ERROR: column "nonexistent" not found in data type compositetable at character 9 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes STATEMENT: SELECT (NULL::compositetable).nonexistent; 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes ERROR: column "oid" not found in data type compositetable at character 9 2025-11-30 18:45:25.035 UTC client backend[46576] pg_regress/rowtypes STATEMENT: SELECT (NULL::compositetable).oid; 2025-11-30 18:45:25.039 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:25.039 UTC client backend[46566] 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-11-30 18:45:25.039 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable(ptest1, ptest2); 2025-11-30 18:45:25.042 UTC client backend[46579] pg_regress/with LOG: disconnection: session time: 0:00:00.746 user=postgres database=regression host=[local] 2025-11-30 18:45:25.048 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-11-30 18:45:25.048 UTC client backend[46566] 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-11-30 18:45:25.048 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable(ptest2, ptest1); 2025-11-30 18:45:25.049 UTC client backend[46570] pg_regress/domain ERROR: column "col1" of table "domcontest" contains values that violate the new constraint 2025-11-30 18:45:25.049 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain con add constraint t check (VALUE < 1); 2025-11-30 18:45:25.049 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-11-30 18:45:25.049 UTC client backend[46566] 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-11-30 18:45:25.049 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest2, ftest1) references pktable(ptest1, ptest2); 2025-11-30 18:45:25.050 UTC client backend[46576] pg_regress/rowtypes LOG: disconnection: session time: 0:00:00.754 user=postgres database=regression host=[local] 2025-11-30 18:45:25.055 UTC client backend[46570] pg_regress/domain ERROR: value for domain con violates check constraint "con_check" 2025-11-30 18:45:25.055 UTC client backend[46570] pg_regress/domain STATEMENT: insert into domcontest values (-5); 2025-11-30 18:45:25.055 UTC client backend[46570] pg_regress/domain ERROR: value for domain con violates check constraint "t" 2025-11-30 18:45:25.055 UTC client backend[46570] pg_regress/domain STATEMENT: insert into domcontest values (42); 2025-11-30 18:45:25.055 UTC client backend[46570] pg_regress/domain ERROR: value for domain con violates check constraint "con_check" 2025-11-30 18:45:25.055 UTC client backend[46570] pg_regress/domain STATEMENT: insert into domcontest values (-5); 2025-11-30 18:45:25.056 UTC client backend[46570] pg_regress/domain ERROR: constraint "nonexistent" of domain "con" does not exist 2025-11-30 18:45:25.056 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain con drop constraint nonexistent; 2025-11-30 18:45:25.056 UTC client backend[46572] pg_regress/rangefuncs ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:25.056 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Returned type integer at ordinal position 2, but query expects numeric. 2025-11-30 18:45:25.056 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from rngfuncbar(); 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 ERROR: missing data for column "k" 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY check_ign_err, line 1: "1 {1}" 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY check_ign_err FROM STDIN WITH (on_error ignore); 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 ERROR: extra data after last expected column 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY check_ign_err, line 1: "1 {1} 3 abc" 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY check_ign_err FROM STDIN WITH (on_error ignore); 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 ERROR: skipped more than REJECT_LIMIT (3) rows due to data type incompatibility 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY check_ign_err, line 5, column n: "" 2025-11-30 18:45:25.057 UTC client backend[46578] pg_regress/copy2 STATEMENT: COPY check_ign_err FROM STDIN WITH (on_error ignore, reject_limit 3); 2025-11-30 18:45:25.058 UTC client backend[46570] pg_regress/domain ERROR: column "col1" of table "domconnotnulltest" contains null values 2025-11-30 18:45:25.058 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain connotnull add not null; 2025-11-30 18:45:25.058 UTC client backend[46572] pg_regress/rangefuncs ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:25.058 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Returned row contains 3 attributes, but query expects 2. 2025-11-30 18:45:25.058 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from rngfuncbar(); 2025-11-30 18:45:25.059 UTC client backend[46570] pg_regress/domain ERROR: column "col2" of table "domconnotnulltest" contains null values 2025-11-30 18:45:25.059 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain connotnull add not null; 2025-11-30 18:45:25.063 UTC client backend[46568] pg_regress/plpgsql ERROR: cursor "test1" does not exist 2025-11-30 18:45:25.063 UTC client backend[46568] pg_regress/plpgsql STATEMENT: fetch next from test1; 2025-11-30 18:45:25.065 UTC client backend[46568] pg_regress/plpgsql ERROR: variable "rc" is declared CONSTANT 2025-11-30 18:45:25.065 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function constant_refcursor() line 5 at OPEN 2025-11-30 18:45:25.065 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select constant_refcursor(); 2025-11-30 18:45:25.069 UTC client backend[46570] pg_regress/domain ERROR: domain connotnull does not allow null values 2025-11-30 18:45:25.069 UTC client backend[46570] pg_regress/domain STATEMENT: update domconnotnulltest set col1 = null; 2025-11-30 18:45:25.071 UTC client backend[46568] pg_regress/plpgsql ERROR: value for parameter "param2" of cursor "c1" specified more than once at character 198 2025-11-30 18:45:25.071 UTC client backend[46568] 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-11-30 18:45:25.071 UTC client backend[46568] pg_regress/plpgsql ERROR: value for parameter "param1" of cursor "c1" specified more than once at character 188 2025-11-30 18:45:25.071 UTC client backend[46568] 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-11-30 18:45:25.071 UTC client backend[46568] pg_regress/plpgsql ERROR: value for parameter "p2" of cursor "c1" specified more than once at character 191 2025-11-30 18:45:25.071 UTC client backend[46568] 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-11-30 18:45:25.072 UTC client backend[46568] pg_regress/plpgsql ERROR: not enough arguments for cursor "c1" at character 189 2025-11-30 18:45:25.072 UTC client backend[46568] 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-11-30 18:45:25.073 UTC client backend[46568] pg_regress/plpgsql ERROR: division by zero 2025-11-30 18:45:25.073 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL expression "42/0 AS p1, 77 AS p2" PL/pgSQL function namedparmcursor_test7() line 6 at OPEN 2025-11-30 18:45:25.073 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select namedparmcursor_test7(); 2025-11-30 18:45:25.076 UTC client backend[46568] pg_regress/plpgsql ERROR: too many parameters specified for RAISE 2025-11-30 18:45:25.076 UTC client backend[46568] pg_regress/plpgsql CONTEXT: compilation of PL/pgSQL function "raise_test1" near line 3 2025-11-30 18:45:25.076 UTC client backend[46568] 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-11-30 18:45:25.076 UTC client backend[46572] pg_regress/rangefuncs ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:25.076 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Returned row contains 3 attributes, but query expects 2. 2025-11-30 18:45:25.076 UTC client backend[46572] 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-11-30 18:45:25.076 UTC client backend[46568] pg_regress/plpgsql ERROR: too few parameters specified for RAISE 2025-11-30 18:45:25.076 UTC client backend[46568] pg_regress/plpgsql CONTEXT: compilation of PL/pgSQL function "raise_test2" near line 3 2025-11-30 18:45:25.076 UTC client backend[46568] 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-11-30 18:45:25.076 UTC client backend[46570] pg_regress/domain ERROR: column "stuff" of table "thethings" contains values that violate the new constraint 2025-11-30 18:45:25.076 UTC client backend[46570] pg_regress/domain STATEMENT: ALTER DOMAIN things ADD CONSTRAINT meow CHECK (VALUE < 11); 2025-11-30 18:45:25.077 UTC client backend[46572] pg_regress/rangefuncs ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:25.077 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Returned row contains 3 attributes, but query expects 4. 2025-11-30 18:45:25.077 UTC client backend[46572] 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-11-30 18:45:25.077 UTC client backend[46570] pg_regress/domain ERROR: column "stuff" of table "thethings" contains values that violate the new constraint 2025-11-30 18:45:25.077 UTC client backend[46570] pg_regress/domain STATEMENT: ALTER DOMAIN things VALIDATE CONSTRAINT meow; 2025-11-30 18:45:25.077 UTC client backend[46572] pg_regress/rangefuncs ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:25.077 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Returned type integer at ordinal position 3, but query expects double precision. 2025-11-30 18:45:25.077 UTC client backend[46572] 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-11-30 18:45:25.078 UTC client backend[46572] pg_regress/rangefuncs ERROR: function return row and query-specified return row do not match 2025-11-30 18:45:25.078 UTC client backend[46572] pg_regress/rangefuncs DETAIL: Returned row contains 1 attribute, but query expects 2. 2025-11-30 18:45:25.078 UTC client backend[46572] pg_regress/rangefuncs STATEMENT: select * from int8_tbl, coalesce(row(1)) as (a int, b int); 2025-11-30 18:45:25.079 UTC client backend[46568] pg_regress/plpgsql ERROR: syntax error at or near "Johnny" at character 83 2025-11-30 18:45:25.079 UTC client backend[46568] 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-11-30 18:45:25.080 UTC client backend[46568] pg_regress/plpgsql ERROR: syntax error at or near "the" at character 99 2025-11-30 18:45:25.080 UTC client backend[46568] 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-11-30 18:45:25.080 UTC client backend[46568] pg_regress/plpgsql ERROR: missing expression at or near ";" at character 74 2025-11-30 18:45:25.080 UTC client backend[46568] pg_regress/plpgsql STATEMENT: create function missing_return_expr() returns int as $$ begin return ; end;$$ language plpgsql; 2025-11-30 18:45:25.080 UTC client backend[46568] pg_regress/plpgsql ERROR: RETURN cannot have a parameter in function returning void at character 72 2025-11-30 18:45:25.080 UTC client backend[46568] pg_regress/plpgsql STATEMENT: create function void_return_expr() returns void as $$ begin return 5; end;$$ language plpgsql; 2025-11-30 18:45:25.082 UTC client backend[46568] pg_regress/plpgsql ERROR: control reached end of function without RETURN 2025-11-30 18:45:25.082 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function missing_return_expr() 2025-11-30 18:45:25.082 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select missing_return_expr(); 2025-11-30 18:45:25.083 UTC client backend[46572] pg_regress/rangefuncs LOG: disconnection: session time: 0:00:00.797 user=postgres database=regression host=[local] 2025-11-30 18:45:25.083 UTC client backend[46570] pg_regress/domain ERROR: domain dom does not allow null values 2025-11-30 18:45:25.083 UTC client backend[46570] pg_regress/domain STATEMENT: select * from domview; 2025-11-30 18:45:25.084 UTC client backend[46570] pg_regress/domain ERROR: value for domain dom violates check constraint "domchkgt6" 2025-11-30 18:45:25.084 UTC client backend[46570] pg_regress/domain STATEMENT: select * from domview; 2025-11-30 18:45:25.088 UTC client backend[46578] pg_regress/copy2 ERROR: cannot specify DEFAULT in BINARY mode 2025-11-30 18:45:25.088 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (format binary, default '\D'); 2025-11-30 18:45:25.089 UTC client backend[46578] pg_regress/copy2 ERROR: COPY default representation cannot use newline or carriage return 2025-11-30 18:45:25.089 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (default E'\n'); 2025-11-30 18:45:25.089 UTC client backend[46578] pg_regress/copy2 ERROR: COPY default representation cannot use newline or carriage return 2025-11-30 18:45:25.089 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (default E'\r'); 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain ERROR: value for domain dtop violates check constraint "dinter_check" 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain STATEMENT: select 'y1234'::dtop; 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain ERROR: value for domain dtop violates check constraint "dinter_check" 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain STATEMENT: select 'y123'::dtop; 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain ERROR: value for domain dtop violates check constraint "dinter_check" 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain STATEMENT: select 'yz23'::dtop; 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql ERROR: column "sqlstate" does not exist at character 1 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql QUERY: sqlstate 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function excpt_test1() line 3 at RAISE 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select excpt_test1(); 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain ERROR: value for domain dtop violates check constraint "dtop_check" 2025-11-30 18:45:25.090 UTC client backend[46570] pg_regress/domain STATEMENT: select 'xz23'::dtop; 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql ERROR: column "sqlstate" does not exist at character 1 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql QUERY: sqlstate 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function excpt_test2() line 5 at RAISE 2025-11-30 18:45:25.090 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select excpt_test2(); 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 ERROR: COPY delimiter character must not appear in the DEFAULT specification 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (delimiter ';', default 'test;test'); 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 ERROR: CSV quote character must not appear in the DEFAULT specification 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (format csv, quote '"', default 'test"test'); 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 ERROR: NULL specification and DEFAULT specification cannot be the same 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (default '\N'); 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 ERROR: unexpected default marker in COPY data 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 DETAIL: Column "id" has no default value. 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY copy_default, line 1: "\D value '2022-07-04'" 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (default '\D'); 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 ERROR: unexpected default marker in COPY data 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 DETAIL: Column "id" has no default value. 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 CONTEXT: COPY copy_default, line 1: "\D,value,2022-07-04" 2025-11-30 18:45:25.091 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy copy_default from stdin with (format csv, default '\D'); 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain ERROR: value too long for type character varying(4) 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dtest values('x1234'); 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain ERROR: value too long for type character varying(4) 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dtest values('y1234'); 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain ERROR: value for domain dtop violates check constraint "dinter_check" 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dtest values('y123'); 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain ERROR: value for domain dtop violates check constraint "dinter_check" 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dtest values('yz23'); 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain ERROR: value for domain dtop violates check constraint "dtop_check" 2025-11-30 18:45:25.092 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dtest values('xz23'); 2025-11-30 18:45:25.098 UTC client backend[46578] pg_regress/copy2 ERROR: COPY DEFAULT cannot be used with COPY TO 2025-11-30 18:45:25.098 UTC client backend[46578] pg_regress/copy2 STATEMENT: copy (select 1 as test) TO stdout with (default '\D'); 2025-11-30 18:45:25.099 UTC client backend[46570] pg_regress/domain ERROR: domain str_domain does not allow null values 2025-11-30 18:45:25.099 UTC client backend[46570] pg_regress/domain STATEMENT: alter table domain_test add column c str_domain; 2025-11-30 18:45:25.099 UTC client backend[46570] pg_regress/domain ERROR: redundant NOT NULL constraint definition at character 58 2025-11-30 18:45:25.099 UTC client backend[46570] pg_regress/domain STATEMENT: create domain int_domain1 as int constraint nn1 not null constraint nn2 not null; 2025-11-30 18:45:25.102 UTC client backend[46570] pg_regress/domain ERROR: value for domain str_domain2 violates check constraint "str_domain2_check" 2025-11-30 18:45:25.102 UTC client backend[46570] pg_regress/domain STATEMENT: alter table domain_test add column d str_domain2; 2025-11-30 18:45:25.103 UTC client backend[46578] pg_regress/copy2 LOG: disconnection: session time: 0:00:00.811 user=postgres database=regression host=[local] 2025-11-30 18:45:25.104 UTC client backend[46577] pg_regress/xml LOG: disconnection: session time: 0:00:00.808 user=postgres database=regression host=[local] 2025-11-30 18:45:25.104 UTC client backend[46570] pg_regress/domain ERROR: value for domain pos_int violates check constraint "pos_int_check" 2025-11-30 18:45:25.104 UTC client backend[46570] pg_regress/domain STATEMENT: execute s1(0); 2025-11-30 18:45:25.104 UTC client backend[46570] pg_regress/domain ERROR: domain pos_int does not allow null values 2025-11-30 18:45:25.104 UTC client backend[46570] pg_regress/domain STATEMENT: execute s1(NULL); 2025-11-30 18:45:25.105 UTC client backend[46570] pg_regress/domain ERROR: domain pos_int does not allow null values 2025-11-30 18:45:25.105 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function doubledecrement(pos_int) line 2 during statement block local variable initialization 2025-11-30 18:45:25.105 UTC client backend[46570] pg_regress/domain STATEMENT: select doubledecrement(3); 2025-11-30 18:45:25.106 UTC client backend[46570] pg_regress/domain ERROR: value for domain pos_int violates check constraint "pos_int_check" 2025-11-30 18:45:25.106 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function doubledecrement(pos_int) line 2 during statement block local variable initialization 2025-11-30 18:45:25.106 UTC client backend[46570] pg_regress/domain STATEMENT: select doubledecrement(3); 2025-11-30 18:45:25.106 UTC client backend[46570] pg_regress/domain ERROR: domain pos_int does not allow null values 2025-11-30 18:45:25.106 UTC client backend[46570] pg_regress/domain STATEMENT: select doubledecrement(null); 2025-11-30 18:45:25.106 UTC client backend[46570] pg_regress/domain ERROR: value for domain pos_int violates check constraint "pos_int_check" 2025-11-30 18:45:25.106 UTC client backend[46570] pg_regress/domain STATEMENT: select doubledecrement(0); 2025-11-30 18:45:25.107 UTC client backend[46570] pg_regress/domain ERROR: value for domain pos_int violates check constraint "pos_int_check" 2025-11-30 18:45:25.107 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function doubledecrement(pos_int) line 4 at assignment 2025-11-30 18:45:25.107 UTC client backend[46570] pg_regress/domain STATEMENT: select doubledecrement(1); 2025-11-30 18:45:25.107 UTC client backend[46570] pg_regress/domain ERROR: value for domain pos_int violates check constraint "pos_int_check" 2025-11-30 18:45:25.107 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function doubledecrement(pos_int) while casting return value to function's return type 2025-11-30 18:45:25.107 UTC client backend[46570] pg_regress/domain STATEMENT: select doubledecrement(2); 2025-11-30 18:45:25.107 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.107 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.107 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at SQL statement 2025-11-30 18:45:25.107 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.110 UTC client backend[46570] pg_regress/domain ERROR: cannot alter type "posint" because column "ddtest2.f1" uses it 2025-11-30 18:45:25.110 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain posint add constraint c1 check(value >= 0); 2025-11-30 18:45:25.111 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned no rows 2025-11-30 18:45:25.111 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at SQL statement 2025-11-30 18:45:25.111 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.112 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.112 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.112 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at SQL statement 2025-11-30 18:45:25.112 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.113 UTC client backend[46570] pg_regress/domain ERROR: cannot alter type "posint" because column "ddtest2.f1" uses it 2025-11-30 18:45:25.113 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain posint add constraint c1 check(value >= 0); 2025-11-30 18:45:25.114 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc1" violates check constraint "atacc_test1" 2025-11-30 18:45:25.114 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (2). 2025-11-30 18:45:25.114 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test) values (2); 2025-11-30 18:45:25.114 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned no rows 2025-11-30 18:45:25.114 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at EXECUTE 2025-11-30 18:45:25.114 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.115 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.115 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at EXECUTE 2025-11-30 18:45:25.115 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.117 UTC client backend[46566] pg_regress/alter_table ERROR: check constraint "atacc_test1" of relation "atacc1" is violated by some row 2025-11-30 18:45:25.117 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test1 check (test>3); 2025-11-30 18:45:25.117 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned no rows 2025-11-30 18:45:25.117 UTC client backend[46568] pg_regress/plpgsql DETAIL: parameters: p1 = '2', p3 = 'foo' 2025-11-30 18:45:25.117 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 8 at SQL statement 2025-11-30 18:45:25.117 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.117 UTC client backend[46570] pg_regress/domain ERROR: cannot alter type "posint" because column "ddtest2.f1" uses it 2025-11-30 18:45:25.117 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain posint add constraint c1 check(value >= 0); 2025-11-30 18:45:25.118 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned no rows 2025-11-30 18:45:25.118 UTC client backend[46568] 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-11-30 18:45:25.118 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 8 at SQL statement 2025-11-30 18:45:25.118 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.118 UTC client backend[46566] pg_regress/alter_table ERROR: column "test1" does not exist 2025-11-30 18:45:25.118 UTC client backend[46566] pg_regress/alter_table HINT: Perhaps you meant to reference the column "atacc1.test". 2025-11-30 18:45:25.118 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test1 check (test1>3); 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql DETAIL: parameters: p1 = '2', p3 = 'foo' 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 8 at SQL statement 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at SQL statement 2025-11-30 18:45:25.119 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.120 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned no rows 2025-11-30 18:45:25.120 UTC client backend[46568] pg_regress/plpgsql DETAIL: parameters: $1 = '0', $2 = 'foo' 2025-11-30 18:45:25.120 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at EXECUTE 2025-11-30 18:45:25.120 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.121 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc1" violates check constraint "atacc_test1" 2025-11-30 18:45:25.121 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (4, 4, 2). 2025-11-30 18:45:25.121 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test,test2,test3) values (4,4,2); 2025-11-30 18:45:25.121 UTC client backend[46570] pg_regress/domain ERROR: cannot alter type "posint" because column "ddtest2.f1" uses it 2025-11-30 18:45:25.121 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain posint add constraint c1 check(value >= 0); 2025-11-30 18:45:25.121 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.121 UTC client backend[46568] pg_regress/plpgsql DETAIL: parameters: $1 = '1' 2025-11-30 18:45:25.121 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at EXECUTE 2025-11-30 18:45:25.121 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.122 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.122 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 5 at EXECUTE 2025-11-30 18:45:25.122 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.123 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.123 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.123 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 10 at SQL statement 2025-11-30 18:45:25.123 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.124 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.124 UTC client backend[46568] pg_regress/plpgsql DETAIL: parameters: p1 = '2', p3 = 'foo' 2025-11-30 18:45:25.124 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.124 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stricttest() line 10 at SQL statement 2025-11-30 18:45:25.124 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stricttest(); 2025-11-30 18:45:25.124 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc1" violates check constraint "atacc1_check" 2025-11-30 18:45:25.124 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (4, 3). 2025-11-30 18:45:25.124 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test2, test) values (3, 4); 2025-11-30 18:45:25.126 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "in1" shadows a previously defined variable at character 88 2025-11-30 18:45:25.126 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "out1" shadows a previously defined variable at character 97 2025-11-30 18:45:25.127 UTC client backend[46570] pg_regress/domain ERROR: cannot alter type "posint" because column "ddtest2.f1" uses it 2025-11-30 18:45:25.127 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain posint add constraint c1 check(value >= 0); 2025-11-30 18:45:25.127 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "in1" shadows a previously defined variable at character 88 2025-11-30 18:45:25.127 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "out1" shadows a previously defined variable at character 97 2025-11-30 18:45:25.129 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "f1" shadows a previously defined variable at character 93 2025-11-30 18:45:25.129 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc2" violates check constraint "foo" 2025-11-30 18:45:25.129 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (-3). 2025-11-30 18:45:25.129 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc2 (test2) values (-3); 2025-11-30 18:45:25.130 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "in1" shadows a previously defined variable at character 76 2025-11-30 18:45:25.130 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc3" violates check constraint "foo" 2025-11-30 18:45:25.130 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null, -3, null). 2025-11-30 18:45:25.130 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc3 (test2) values (-3); 2025-11-30 18:45:25.130 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "in1" shadows a previously defined variable at character 101 2025-11-30 18:45:25.131 UTC client backend[46568] pg_regress/plpgsql WARNING: variable "f1" shadows a previously defined variable at character 88 2025-11-30 18:45:25.132 UTC client backend[46570] pg_regress/domain ERROR: value for domain posint2 violates check constraint "posint2_check" 2025-11-30 18:45:25.132 UTC client backend[46570] pg_regress/domain STATEMENT: insert into ddtest2 values(11); 2025-11-30 18:45:25.132 UTC client backend[46570] pg_regress/domain ERROR: value for domain posint2 violates check constraint "c1" 2025-11-30 18:45:25.132 UTC client backend[46570] pg_regress/domain STATEMENT: insert into ddtest2 values(-2); 2025-11-30 18:45:25.132 UTC client backend[46568] pg_regress/plpgsql ERROR: variable "f1" shadows a previously defined variable at character 78 2025-11-30 18:45:25.132 UTC client backend[46568] pg_regress/plpgsql STATEMENT: create or replace function shadowtest(f1 int) returns boolean as $$ declare f1 int; begin return 1; end $$ language plpgsql; 2025-11-30 18:45:25.133 UTC client backend[46568] pg_regress/plpgsql ERROR: function shadowtest(integer) does not exist at character 8 2025-11-30 18:45:25.133 UTC client backend[46568] pg_regress/plpgsql DETAIL: There is no function of that name. 2025-11-30 18:45:25.133 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select shadowtest(1); 2025-11-30 18:45:25.133 UTC client backend[46570] pg_regress/domain ERROR: column "f1" of table "ddtest2" contains values that violate the new constraint 2025-11-30 18:45:25.133 UTC client backend[46570] pg_regress/domain STATEMENT: alter domain posint add constraint c2 check(value >= 10); 2025-11-30 18:45:25.135 UTC client backend[46568] pg_regress/plpgsql WARNING: query returned more than one row 2025-11-30 18:45:25.135 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.135 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 4 at SQL statement 2025-11-30 18:45:25.135 UTC client backend[46566] pg_regress/alter_table ERROR: relation "atacc2" is not a parent of relation "atacc3" 2025-11-30 18:45:25.135 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc3 no inherit atacc2; 2025-11-30 18:45:25.135 UTC client backend[46568] pg_regress/plpgsql ERROR: query returned more than one row 2025-11-30 18:45:25.135 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns a single row, or use LIMIT 1. 2025-11-30 18:45:25.135 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 4 at SQL statement 2025-11-30 18:45:25.135 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ declare x int; begin select v from generate_series(1,2) g(v) into x; end; $$; 2025-11-30 18:45:25.136 UTC client backend[46570] pg_regress/domain ERROR: numeric field overflow 2025-11-30 18:45:25.136 UTC client backend[46570] pg_regress/domain DETAIL: A field with precision 4, scale 2 must round to an absolute value less than 10^2. 2025-11-30 18:45:25.136 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function array_elem_check(numeric) line 5 at assignment 2025-11-30 18:45:25.136 UTC client backend[46570] pg_regress/domain STATEMENT: select array_elem_check(121.00); 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql WARNING: number of source and target fields in assignment does not match 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql DETAIL: strict_multi_assignment check of extra_warnings is active. 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns the exact list of columns. 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 6 at SQL statement 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql WARNING: number of source and target fields in assignment does not match 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql DETAIL: strict_multi_assignment check of extra_warnings is active. 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns the exact list of columns. 2025-11-30 18:45:25.136 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 8 at SQL statement 2025-11-30 18:45:25.137 UTC client backend[46566] pg_regress/alter_table ERROR: child table is missing constraint "foo" 2025-11-30 18:45:25.137 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc3 inherit atacc2; 2025-11-30 18:45:25.137 UTC client backend[46566] pg_regress/alter_table ERROR: child table is missing column "test2" 2025-11-30 18:45:25.137 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc3 inherit atacc2; 2025-11-30 18:45:25.137 UTC client backend[46568] pg_regress/plpgsql ERROR: number of source and target fields in assignment does not match 2025-11-30 18:45:25.137 UTC client backend[46568] pg_regress/plpgsql DETAIL: strict_multi_assignment check of extra_errors is active. 2025-11-30 18:45:25.137 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns the exact list of columns. 2025-11-30 18:45:25.137 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 6 at SQL statement 2025-11-30 18:45:25.137 UTC client backend[46568] 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-11-30 18:45:25.137 UTC client backend[46566] pg_regress/alter_table ERROR: child table "atacc3" has different type for column "test2" 2025-11-30 18:45:25.137 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc3 inherit atacc2; 2025-11-30 18:45:25.137 UTC client backend[46570] pg_regress/domain ERROR: numeric field overflow 2025-11-30 18:45:25.137 UTC client backend[46570] pg_regress/domain DETAIL: A field with precision 4, scale 2 must round to an absolute value less than 10^2. 2025-11-30 18:45:25.137 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function array_elem_check(numeric) line 5 at assignment 2025-11-30 18:45:25.137 UTC client backend[46570] pg_regress/domain STATEMENT: select array_elem_check(121.00); 2025-11-30 18:45:25.139 UTC client backend[46570] pg_regress/domain ERROR: numeric field overflow 2025-11-30 18:45:25.139 UTC client backend[46570] pg_regress/domain DETAIL: A field with precision 4, scale 2 must round to an absolute value less than 10^2. 2025-11-30 18:45:25.139 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function array_elem_check(numeric) line 5 at assignment 2025-11-30 18:45:25.139 UTC client backend[46570] pg_regress/domain STATEMENT: select array_elem_check(121.00); 2025-11-30 18:45:25.139 UTC client backend[46568] pg_regress/plpgsql ERROR: number of source and target fields in assignment does not match 2025-11-30 18:45:25.139 UTC client backend[46568] pg_regress/plpgsql DETAIL: strict_multi_assignment check of extra_errors is active. 2025-11-30 18:45:25.139 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns the exact list of columns. 2025-11-30 18:45:25.139 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 8 at SQL statement 2025-11-30 18:45:25.139 UTC client backend[46568] 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-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql ERROR: number of source and target fields in assignment does not match 2025-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql DETAIL: strict_multi_assignment check of extra_errors is active. 2025-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns the exact list of columns. 2025-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 7 at SQL statement 2025-11-30 18:45:25.140 UTC client backend[46568] 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-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql ERROR: number of source and target fields in assignment does not match 2025-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql DETAIL: strict_multi_assignment check of extra_errors is active. 2025-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql HINT: Make sure the query returns the exact list of columns. 2025-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 5 at SQL statement 2025-11-30 18:45:25.140 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ declare t test_01; begin select 1 into t; -- should fail; end; $$; 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table ERROR: relation "atacc2" would be inherited from more than once 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc3 inherit atacc2; 2025-11-30 18:45:25.140 UTC client backend[46570] pg_regress/domain ERROR: value for domain orderedpair violates check constraint "orderedpair_check" 2025-11-30 18:45:25.140 UTC client backend[46570] pg_regress/domain STATEMENT: select array[2,1]::orderedpair; 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table ERROR: circular inheritance not allowed 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table DETAIL: "atacc3" is already a child of "atacc2". 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc2 inherit atacc3; 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table ERROR: circular inheritance not allowed 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table DETAIL: "atacc2" is already a child of "atacc2". 2025-11-30 18:45:25.140 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc2 inherit atacc2; 2025-11-30 18:45:25.142 UTC client backend[46570] pg_regress/domain ERROR: value for domain orderedpair violates check constraint "orderedpair_check" 2025-11-30 18:45:25.142 UTC client backend[46570] pg_regress/domain STATEMENT: insert into op values (array[2,1]); 2025-11-30 18:45:25.142 UTC client backend[46570] pg_regress/domain ERROR: value for domain orderedpair violates check constraint "orderedpair_check" 2025-11-30 18:45:25.142 UTC client backend[46570] pg_regress/domain STATEMENT: update op set f1[2] = 0; 2025-11-30 18:45:25.143 UTC client backend[46570] pg_regress/domain ERROR: value for domain orderedpair violates check constraint "orderedpair_check" 2025-11-30 18:45:25.143 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function array_elem_check(integer) line 5 at assignment 2025-11-30 18:45:25.143 UTC client backend[46570] pg_regress/domain STATEMENT: select array_elem_check(-1); 2025-11-30 18:45:25.143 UTC client backend[46568] pg_regress/plpgsql ERROR: cursor can only scan forward 2025-11-30 18:45:25.143 UTC client backend[46568] pg_regress/plpgsql HINT: Declare it with SCROLL option to enable backward scan. 2025-11-30 18:45:25.143 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function sc_test() line 7 at FETCH 2025-11-30 18:45:25.143 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select * from sc_test(); 2025-11-30 18:45:25.145 UTC client backend[46570] pg_regress/domain ERROR: value for domain di violates check constraint "pos" 2025-11-30 18:45:25.145 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function dom_check(integer) line 4 at assignment 2025-11-30 18:45:25.145 UTC client backend[46570] pg_regress/domain STATEMENT: select dom_check(0); 2025-11-30 18:45:25.146 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc1" violates check constraint "foo" 2025-11-30 18:45:25.146 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (-3). 2025-11-30 18:45:25.146 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test) values (-3); 2025-11-30 18:45:25.146 UTC client backend[46570] pg_regress/domain ERROR: value for domain di violates check constraint "pos" 2025-11-30 18:45:25.146 UTC client backend[46570] pg_regress/domain CONTEXT: PL/pgSQL function dom_check(integer) line 4 at assignment 2025-11-30 18:45:25.146 UTC client backend[46570] pg_regress/domain STATEMENT: select dom_check(0); 2025-11-30 18:45:25.147 UTC client backend[46566] pg_regress/alter_table ERROR: check constraint "foo" of relation "atacc2" is violated by some row 2025-11-30 18:45:25.147 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc2 add constraint foo check (test>0) no inherit; 2025-11-30 18:45:25.149 UTC client backend[46570] pg_regress/domain ERROR: value for domain inotnull violates check constraint "inotnull_check" 2025-11-30 18:45:25.149 UTC client backend[46570] pg_regress/domain STATEMENT: select null::inotnull; 2025-11-30 18:45:25.150 UTC client backend[46570] pg_regress/domain ERROR: value for domain inotnull violates check constraint "inotnull_check" 2025-11-30 18:45:25.150 UTC client backend[46570] pg_regress/domain STATEMENT: insert into dom_table values (null); 2025-11-30 18:45:25.150 UTC client backend[46566] pg_regress/alter_table ERROR: duplicate key value violates unique constraint "atacc_test1" 2025-11-30 18:45:25.150 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test)=(2) already exists. 2025-11-30 18:45:25.150 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test) values (2); 2025-11-30 18:45:25.152 UTC client backend[46566] pg_regress/alter_table ERROR: could not create unique index "atacc_test1" 2025-11-30 18:45:25.152 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test)=(0) is duplicated. 2025-11-30 18:45:25.152 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter column test type integer using 0; 2025-11-30 18:45:25.155 UTC client backend[46566] pg_regress/alter_table ERROR: could not create unique index "atacc_test1" 2025-11-30 18:45:25.155 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test)=(2) is duplicated. 2025-11-30 18:45:25.155 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test1 unique (test); 2025-11-30 18:45:25.156 UTC client backend[46570] pg_regress/domain ERROR: specifying constraint enforceability not supported for domains at character 90 2025-11-30 18:45:25.156 UTC client backend[46570] pg_regress/domain STATEMENT: CREATE DOMAIN constraint_enforced_dom AS int CONSTRAINT the_constraint CHECK (value > 0) ENFORCED; 2025-11-30 18:45:25.157 UTC client backend[46570] pg_regress/domain ERROR: specifying constraint enforceability not supported for domains at character 94 2025-11-30 18:45:25.157 UTC client backend[46570] pg_regress/domain STATEMENT: CREATE DOMAIN constraint_not_enforced_dom AS int CONSTRAINT the_constraint CHECK (value > 0) NOT ENFORCED; 2025-11-30 18:45:25.157 UTC client backend[46570] pg_regress/domain ERROR: CHECK constraints cannot be marked ENFORCED at character 86 2025-11-30 18:45:25.157 UTC client backend[46570] pg_regress/domain STATEMENT: ALTER DOMAIN constraint_enforced_dom ADD CONSTRAINT the_constraint CHECK (value > 0) ENFORCED; 2025-11-30 18:45:25.157 UTC client backend[46570] pg_regress/domain ERROR: CHECK constraints cannot be marked NOT ENFORCED at character 86 2025-11-30 18:45:25.157 UTC client backend[46570] pg_regress/domain STATEMENT: ALTER DOMAIN constraint_enforced_dom ADD CONSTRAINT the_constraint CHECK (value > 0) NOT ENFORCED; 2025-11-30 18:45:25.157 UTC client backend[46566] pg_regress/alter_table ERROR: column "test1" named in key does not exist 2025-11-30 18:45:25.157 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test1 unique (test1); 2025-11-30 18:45:25.160 UTC client backend[46566] pg_regress/alter_table ERROR: duplicate key value violates unique constraint "atacc_test1" 2025-11-30 18:45:25.160 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test, test2)=(4, 4) already exists. 2025-11-30 18:45:25.160 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test,test2) values (4,4); 2025-11-30 18:45:25.164 UTC client backend[46566] pg_regress/alter_table ERROR: duplicate key value violates unique constraint "atacc1_test_key" 2025-11-30 18:45:25.164 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test)=(3) already exists. 2025-11-30 18:45:25.164 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test2, test) values (2, 3); 2025-11-30 18:45:25.166 UTC client backend[46568] pg_regress/plpgsql ERROR: cursor FOR loop must use a bound cursor variable at character 98 2025-11-30 18:45:25.166 UTC client backend[46568] 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-11-30 18:45:25.171 UTC client backend[46566] pg_regress/alter_table ERROR: duplicate key value violates unique constraint "atacc_test1" 2025-11-30 18:45:25.171 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test)=(2) already exists. 2025-11-30 18:45:25.171 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test) values (2); 2025-11-30 18:45:25.172 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "test" of relation "atacc1" violates not-null constraint 2025-11-30 18:45:25.172 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (4, null). 2025-11-30 18:45:25.172 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test) values(NULL); 2025-11-30 18:45:25.172 UTC client backend[46566] pg_regress/alter_table ERROR: multiple primary keys for table "atacc1" are not allowed 2025-11-30 18:45:25.172 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_oid1 primary key(id); 2025-11-30 18:45:25.178 UTC client backend[46566] pg_regress/alter_table ERROR: could not create unique index "atacc_test1" 2025-11-30 18:45:25.178 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test)=(2) is duplicated. 2025-11-30 18:45:25.178 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test1 primary key (test); 2025-11-30 18:45:25.180 UTC client backend[46568] pg_regress/plpgsql ERROR: returned record type does not match expected record type 2025-11-30 18:45:25.180 UTC client backend[46568] pg_regress/plpgsql DETAIL: Returned type unknown does not match expected type character varying in column "y" (position 2). 2025-11-30 18:45:25.180 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function compos() while casting return value to function's return type 2025-11-30 18:45:25.180 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select compos(); 2025-11-30 18:45:25.181 UTC client backend[46566] pg_regress/alter_table ERROR: column "test" of relation "atacc1" contains null values 2025-11-30 18:45:25.181 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test1 primary key (test); 2025-11-30 18:45:25.183 UTC client backend[46566] pg_regress/alter_table ERROR: column "test1" of relation "atacc1" does not exist 2025-11-30 18:45:25.183 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test1 primary key (test1); 2025-11-30 18:45:25.184 UTC client backend[46570] pg_regress/domain LOG: disconnection: session time: 0:00:00.892 user=postgres database=regression host=[local] 2025-11-30 18:45:25.186 UTC client backend[46568] pg_regress/plpgsql ERROR: cannot return non-composite value from function returning composite type 2025-11-30 18:45:25.186 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function compos() line 3 at RETURN 2025-11-30 18:45:25.186 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select compos(); 2025-11-30 18:45:25.186 UTC client backend[46566] pg_regress/alter_table ERROR: column "test2" of relation "atacc1" contains null values 2025-11-30 18:45:25.186 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add column test2 int primary key; 2025-11-30 18:45:25.186 UTC client backend[46568] pg_regress/plpgsql ERROR: cannot return non-composite value from function returning composite type 2025-11-30 18:45:25.186 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function compos() line 4 at RETURN 2025-11-30 18:45:25.186 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select * from compos(); 2025-11-30 18:45:25.188 UTC client backend[46568] pg_regress/plpgsql ERROR: invalid input syntax for type integer: "(1,hello)" 2025-11-30 18:45:25.188 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function compos() while casting return value to function's return type 2025-11-30 18:45:25.188 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select compos(); 2025-11-30 18:45:25.188 UTC client backend[46568] pg_regress/plpgsql ERROR: invalid input syntax for type integer: "(1,hello)" 2025-11-30 18:45:25.188 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function compos() while casting return value to function's return type 2025-11-30 18:45:25.188 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select compos(); 2025-11-30 18:45:25.190 UTC client backend[46568] pg_regress/plpgsql ERROR: 1 2 3 2025-11-30 18:45:25.190 UTC client backend[46568] pg_regress/plpgsql DETAIL: some detail info 2025-11-30 18:45:25.190 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 5 at RAISE 2025-11-30 18:45:25.190 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.191 UTC client backend[46568] pg_regress/plpgsql ERROR: check me 2025-11-30 18:45:25.191 UTC client backend[46568] pg_regress/plpgsql DETAIL: some detail info 2025-11-30 18:45:25.191 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.191 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.192 UTC client backend[46568] pg_regress/plpgsql ERROR: check me 2025-11-30 18:45:25.192 UTC client backend[46568] pg_regress/plpgsql DETAIL: some detail info 2025-11-30 18:45:25.192 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.192 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql ERROR: check me 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql DETAIL: some detail info 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql ERROR: division_by_zero 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql DETAIL: some detail info 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.193 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.194 UTC client backend[46568] pg_regress/plpgsql ERROR: division_by_zero 2025-11-30 18:45:25.194 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.194 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.195 UTC client backend[46568] pg_regress/plpgsql ERROR: 1234F 2025-11-30 18:45:25.195 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.195 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.195 UTC client backend[46568] pg_regress/plpgsql ERROR: custom message 2025-11-30 18:45:25.195 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.195 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.196 UTC client backend[46568] pg_regress/plpgsql ERROR: custom message 2025-11-30 18:45:25.196 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.196 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.197 UTC client backend[46568] pg_regress/plpgsql ERROR: RAISE option already specified: MESSAGE 2025-11-30 18:45:25.197 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.197 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.197 UTC client backend[46568] pg_regress/plpgsql ERROR: RAISE option already specified: ERRCODE 2025-11-30 18:45:25.197 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.197 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.198 UTC client backend[46568] pg_regress/plpgsql ERROR: RAISE without parameters cannot be used outside an exception handler 2025-11-30 18:45:25.198 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 3 at RAISE 2025-11-30 18:45:25.198 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.202 UTC client backend[46568] pg_regress/plpgsql ERROR: GET STACKED DIAGNOSTICS cannot be used outside an exception handler 2025-11-30 18:45:25.202 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function stacked_diagnostics_test() line 6 at GET STACKED DIAGNOSTICS 2025-11-30 18:45:25.202 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select stacked_diagnostics_test(); 2025-11-30 18:45:25.211 UTC client backend[46568] pg_regress/plpgsql ERROR: substitute message 2025-11-30 18:45:25.211 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function raise_test() line 7 at RAISE 2025-11-30 18:45:25.211 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select raise_test(); 2025-11-30 18:45:25.216 UTC client backend[46566] pg_regress/alter_table ERROR: check constraint "atacc1_chk" of relation "atacc1" is violated by some row 2025-11-30 18:45:25.216 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 validate constraint atacc1_chk, alter a type int; 2025-11-30 18:45:25.220 UTC client backend[46566] pg_regress/alter_table ERROR: multiple primary keys for table "atacc1" are not allowed 2025-11-30 18:45:25.220 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add constraint atacc_test2 primary key (test); 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table ERROR: duplicate key value violates unique constraint "atacc_test1" 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test, test2)=(4, 4) already exists. 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test,test2) values (4,4); 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "test" of relation "atacc1" violates not-null constraint 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null, 3). 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test,test2) values (NULL,3); 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "test2" of relation "atacc1" violates not-null constraint 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (3, null). 2025-11-30 18:45:25.221 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test,test2) values (3, NULL); 2025-11-30 18:45:25.222 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "test" of relation "atacc1" violates not-null constraint 2025-11-30 18:45:25.222 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null, null). 2025-11-30 18:45:25.222 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test,test2) values (NULL,NULL); 2025-11-30 18:45:25.224 UTC client backend[46568] pg_regress/plpgsql ERROR: SELECT INTO query does not return tuples 2025-11-30 18:45:25.224 UTC client backend[46568] pg_regress/plpgsql CONTEXT: SQL statement "select 10 into no_such_table" PL/pgSQL function rttest() line 3 at RETURN QUERY 2025-11-30 18:45:25.224 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select * from rttest(); 2025-11-30 18:45:25.225 UTC client backend[46568] pg_regress/plpgsql ERROR: SELECT INTO query does not return tuples 2025-11-30 18:45:25.225 UTC client backend[46568] pg_regress/plpgsql CONTEXT: SQL statement "select 10 into no_such_table" PL/pgSQL function rttest() line 3 at RETURN QUERY 2025-11-30 18:45:25.225 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select * from rttest(); 2025-11-30 18:45:25.225 UTC client backend[46568] pg_regress/plpgsql ERROR: relation "no_such_table" does not exist at character 15 2025-11-30 18:45:25.225 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select * from no_such_table; 2025-11-30 18:45:25.227 UTC client backend[46566] pg_regress/alter_table ERROR: duplicate key value violates unique constraint "atacc1_pkey" 2025-11-30 18:45:25.227 UTC client backend[46566] pg_regress/alter_table DETAIL: Key (test)=(3) already exists. 2025-11-30 18:45:25.227 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test2, test) values (2, 3); 2025-11-30 18:45:25.227 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "test" of relation "atacc1" violates not-null constraint 2025-11-30 18:45:25.227 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null, 1). 2025-11-30 18:45:25.227 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (test2, test) values (1, NULL); 2025-11-30 18:45:25.228 UTC client backend[46566] pg_regress/alter_table ERROR: permission denied: "pg_class" is a system catalog 2025-11-30 18:45:25.228 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table pg_class alter column relname drop not null; 2025-11-30 18:45:25.229 UTC client backend[46566] pg_regress/alter_table ERROR: permission denied: "pg_class" is a system catalog 2025-11-30 18:45:25.229 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table pg_class alter relname set not null; 2025-11-30 18:45:25.229 UTC client backend[46566] pg_regress/alter_table ERROR: relation "non_existent" does not exist 2025-11-30 18:45:25.229 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table non_existent alter column bar set not null; 2025-11-30 18:45:25.229 UTC client backend[46566] pg_regress/alter_table ERROR: relation "non_existent" does not exist 2025-11-30 18:45:25.229 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table non_existent alter column bar drop not null; 2025-11-30 18:45:25.240 UTC client backend[46568] pg_regress/plpgsql ERROR: schema "nonexistent" does not exist 2025-11-30 18:45:25.240 UTC client backend[46568] pg_regress/plpgsql CONTEXT: SQL function "error1" statement 1 PL/pgSQL function error2(text) line 3 at RETURN 2025-11-30 18:45:25.240 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select error2('nonexistent.stuffs'); 2025-11-30 18:45:25.240 UTC client backend[46566] pg_regress/alter_table ERROR: column "test" is in a primary key 2025-11-30 18:45:25.240 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter column test drop not null; 2025-11-30 18:45:25.246 UTC client backend[46568] pg_regress/plpgsql ERROR: invalid input syntax for type date: "-1" 2025-11-30 18:45:25.246 UTC client backend[46568] 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-11-30 18:45:25.246 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select cast_invoker(-1); 2025-11-30 18:45:25.250 UTC client backend[46568] pg_regress/plpgsql ERROR: division by zero 2025-11-30 18:45:25.250 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL expression "1/0" PL/pgSQL function fail() line 3 at RETURN 2025-11-30 18:45:25.250 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select fail(); 2025-11-30 18:45:25.251 UTC client backend[46568] pg_regress/plpgsql ERROR: division by zero 2025-11-30 18:45:25.251 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL expression "1/0" PL/pgSQL function fail() line 3 at RETURN 2025-11-30 18:45:25.251 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select fail(); 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql WARNING: nonstandard use of \\ in a string literal at character 78 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql WARNING: nonstandard use of \\ in a string literal at character 106 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql WARNING: nonstandard use of \\ in a string literal at character 106 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql WARNING: nonstandard use of \\ in a string literal at character 23 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql CONTEXT: compilation of PL/pgSQL function "strtest" near line 3 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql WARNING: nonstandard use of \\ in a string literal at character 51 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql CONTEXT: compilation of PL/pgSQL function "strtest" near line 3 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql WARNING: nonstandard use of \\ in a string literal at character 1 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql QUERY: 'foo\\bar\041baz' 2025-11-30 18:45:25.252 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function strtest() line 4 at RETURN 2025-11-30 18:45:25.257 UTC client backend[46568] pg_regress/plpgsql ERROR: RETURN cannot have a parameter in function returning void at character 36 2025-11-30 18:45:25.257 UTC client backend[46568] pg_regress/plpgsql STATEMENT: DO LANGUAGE plpgsql $$begin return 1; end$$; 2025-11-30 18:45:25.258 UTC client backend[46568] pg_regress/plpgsql ERROR: column "foo" does not exist at character 33 2025-11-30 18:45:25.258 UTC client backend[46568] pg_regress/plpgsql QUERY: SELECT rtrim(roomno) AS roomno, foo FROM Room ORDER BY roomno 2025-11-30 18:45:25.258 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 4 at FOR over SELECT rows 2025-11-30 18:45:25.258 UTC client backend[46568] 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-11-30 18:45:25.258 UTC client backend[46568] pg_regress/plpgsql ERROR: column "x" does not exist at character 1 2025-11-30 18:45:25.258 UTC client backend[46568] pg_regress/plpgsql QUERY: x + 1 2025-11-30 18:45:25.258 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:25.258 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ declare x int := x + 1; -- error begin raise notice 'x = %', x; end; $$; 2025-11-30 18:45:25.259 UTC client backend[46568] pg_regress/plpgsql ERROR: column "x" does not exist at character 1 2025-11-30 18:45:25.259 UTC client backend[46568] pg_regress/plpgsql QUERY: x + 1 2025-11-30 18:45:25.259 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 2 during statement block local variable initialization 2025-11-30 18:45:25.259 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ declare y int := x + 1; -- error x int := 42; begin raise notice 'x = %, y = %', x, y; end; $$; 2025-11-30 18:45:25.259 UTC client backend[46566] pg_regress/alter_table ERROR: column "test" of relation "atacc1" contains null values 2025-11-30 18:45:25.259 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter test set not null; 2025-11-30 18:45:25.260 UTC client backend[46566] pg_regress/alter_table ERROR: column "bar" of relation "atacc1" does not exist 2025-11-30 18:45:25.260 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter bar set not null; 2025-11-30 18:45:25.260 UTC client backend[46566] pg_regress/alter_table ERROR: column "bar" of relation "atacc1" does not exist 2025-11-30 18:45:25.260 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter bar drop not null; 2025-11-30 18:45:25.260 UTC client backend[46568] pg_regress/plpgsql ERROR: column reference "q1" is ambiguous at character 8 2025-11-30 18:45:25.260 UTC client backend[46568] pg_regress/plpgsql DETAIL: It could refer to either a PL/pgSQL variable or a table column. 2025-11-30 18:45:25.260 UTC client backend[46568] pg_regress/plpgsql QUERY: select q1,q2 from int8_tbl 2025-11-30 18:45:25.260 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function conflict_test() line 5 at FOR over SELECT rows 2025-11-30 18:45:25.260 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select * from conflict_test(); 2025-11-30 18:45:25.261 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER action ALTER COLUMN ... DROP NOT NULL cannot be performed on relation "myview" 2025-11-30 18:45:25.261 UTC client backend[46566] pg_regress/alter_table DETAIL: This operation is not supported for views. 2025-11-30 18:45:25.261 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table myview alter column test drop not null; 2025-11-30 18:45:25.261 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER action ALTER COLUMN ... SET NOT NULL cannot be performed on relation "myview" 2025-11-30 18:45:25.261 UTC client backend[46566] pg_regress/alter_table DETAIL: This operation is not supported for views. 2025-11-30 18:45:25.261 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table myview alter column test set not null; 2025-11-30 18:45:25.265 UTC client backend[46566] pg_regress/alter_table ERROR: column "test_a" of relation "atacc1" contains null values 2025-11-30 18:45:25.265 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter test_a set not null; 2025-11-30 18:45:25.267 UTC client backend[46566] pg_regress/alter_table ERROR: column "test_a" of relation "atacc1" contains null values 2025-11-30 18:45:25.267 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter test_a set not null; 2025-11-30 18:45:25.270 UTC client backend[46568] pg_regress/plpgsql ERROR: FOREACH ... SLICE loop variable must be of an array type 2025-11-30 18:45:25.270 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array 2025-11-30 18:45:25.270 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select foreach_test(ARRAY[1,2,3,4]); 2025-11-30 18:45:25.270 UTC client backend[46568] pg_regress/plpgsql ERROR: FOREACH ... SLICE loop variable must be of an array type 2025-11-30 18:45:25.270 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array 2025-11-30 18:45:25.270 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select foreach_test(ARRAY[[1,2],[3,4]]); 2025-11-30 18:45:25.271 UTC client backend[46566] pg_regress/alter_table ERROR: column "test_b" of relation "atacc1" contains null values 2025-11-30 18:45:25.271 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter test_a set not null, alter test_b set not null; 2025-11-30 18:45:25.272 UTC client backend[46566] pg_regress/alter_table ERROR: column "test_b" of relation "atacc1" contains null values 2025-11-30 18:45:25.272 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter test_b set not null, alter test_a set not null; 2025-11-30 18:45:25.273 UTC client backend[46568] pg_regress/plpgsql ERROR: slice dimension (2) is out of the valid range 0..1 2025-11-30 18:45:25.273 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array 2025-11-30 18:45:25.273 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select foreach_test(ARRAY[1,2,3,4]); 2025-11-30 18:45:25.284 UTC client backend[46568] pg_regress/plpgsql ERROR: value for domain orderedarray violates check constraint "sorted" 2025-11-30 18:45:25.284 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select '{2,1}'::orderedarray; 2025-11-30 18:45:25.286 UTC client backend[46568] pg_regress/plpgsql ERROR: value for domain orderedarray violates check constraint "sorted" 2025-11-30 18:45:25.286 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function testoa(integer,integer,integer) line 4 at assignment 2025-11-30 18:45:25.286 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select testoa(2,1,3); 2025-11-30 18:45:25.286 UTC client backend[46568] pg_regress/plpgsql ERROR: value for domain orderedarray violates check constraint "sorted" 2025-11-30 18:45:25.286 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function testoa(integer,integer,integer) line 5 at assignment 2025-11-30 18:45:25.286 UTC client backend[46568] pg_regress/plpgsql STATEMENT: select testoa(1,2,1); 2025-11-30 18:45:25.302 UTC client backend[46568] pg_regress/plpgsql ERROR: assertion failed 2025-11-30 18:45:25.302 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 3 at ASSERT 2025-11-30 18:45:25.302 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ begin assert 1=0; -- should fail end; $$; 2025-11-30 18:45:25.302 UTC client backend[46568] pg_regress/plpgsql ERROR: assertion failed 2025-11-30 18:45:25.302 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 3 at ASSERT 2025-11-30 18:45:25.302 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ begin assert NULL; -- should fail end; $$; 2025-11-30 18:45:25.303 UTC client backend[46568] pg_regress/plpgsql ERROR: assertion failed, var = "some value" 2025-11-30 18:45:25.303 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 4 at ASSERT 2025-11-30 18:45:25.303 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ declare var text := 'some value'; begin assert 1=0, format('assertion failed, var = "%s"', var); end; $$; 2025-11-30 18:45:25.303 UTC client backend[46568] pg_regress/plpgsql ERROR: unhandled assertion 2025-11-30 18:45:25.303 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 3 at ASSERT 2025-11-30 18:45:25.303 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ begin assert 1=0, 'unhandled assertion'; exception when others then null; -- do nothing end; $$; 2025-11-30 18:45:25.306 UTC client backend[46568] pg_regress/plpgsql ERROR: value for domain plpgsql_domain violates check constraint "plpgsql_domain_check" 2025-11-30 18:45:25.306 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 4 at assignment 2025-11-30 18:45:25.306 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ declare v_test plpgsql_domain := 1; begin v_test := 0; -- fail end; $$; 2025-11-30 18:45:25.308 UTC client backend[46568] pg_regress/plpgsql ERROR: value for domain plpgsql_arr_domain violates check constraint "plpgsql_arr_domain_check" 2025-11-30 18:45:25.308 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function inline_code_block line 4 at assignment 2025-11-30 18:45:25.308 UTC client backend[46568] pg_regress/plpgsql STATEMENT: do $$ declare v_test plpgsql_arr_domain := array[1]; begin v_test := 0 || v_test; -- fail end; $$; 2025-11-30 18:45:25.312 UTC client backend[46568] pg_regress/plpgsql ERROR: OLD TABLE can only be specified for a DELETE or UPDATE trigger 2025-11-30 18:45:25.312 UTC client backend[46568] 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-11-30 18:45:25.330 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "a" of relation "parent" violates not-null constraint 2025-11-30 18:45:25.330 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null). 2025-11-30 18:45:25.330 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into parent values (NULL); 2025-11-30 18:45:25.330 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "a" of relation "child" violates not-null constraint 2025-11-30 18:45:25.330 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null, foo). 2025-11-30 18:45:25.330 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into child (a, b) values (NULL, 'foo'); 2025-11-30 18:45:25.332 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "parent" contains null values 2025-11-30 18:45:25.332 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table only parent alter a set not null; 2025-11-30 18:45:25.333 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "child" contains null values 2025-11-30 18:45:25.333 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table child alter a set not null; 2025-11-30 18:45:25.340 UTC client backend[46566] pg_regress/alter_table ERROR: invalid input syntax for type integer: "wrong_datatype" 2025-11-30 18:45:25.340 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table def_test alter column c1 set default 'wrong_datatype'; 2025-11-30 18:45:25.341 UTC client backend[46566] pg_regress/alter_table ERROR: column "c3" of relation "def_test" does not exist 2025-11-30 18:45:25.341 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table def_test alter column c3 set default 30; 2025-11-30 18:45:25.349 UTC client backend[46566] pg_regress/alter_table ERROR: permission denied: "pg_class" is a system catalog 2025-11-30 18:45:25.349 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table pg_class drop column relname; 2025-11-30 18:45:25.349 UTC client backend[46566] pg_regress/alter_table ERROR: relation "nosuchtable" does not exist 2025-11-30 18:45:25.349 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table nosuchtable drop column bar; 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 drop a; 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist at character 31 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table STATEMENT: select * from atacc1 order by a; 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist at character 31 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table STATEMENT: select * from atacc1 order by "........pg.dropped.1........"; 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist at character 31 2025-11-30 18:45:25.352 UTC client backend[46566] pg_regress/alter_table STATEMENT: select * from atacc1 group by a; 2025-11-30 18:45:25.353 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist at character 31 2025-11-30 18:45:25.353 UTC client backend[46566] pg_regress/alter_table STATEMENT: select * from atacc1 group by "........pg.dropped.1........"; 2025-11-30 18:45:25.353 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist at character 8 2025-11-30 18:45:25.353 UTC client backend[46566] pg_regress/alter_table STATEMENT: select a from atacc1; 2025-11-30 18:45:25.353 UTC client backend[46566] pg_regress/alter_table ERROR: column atacc1.a does not exist at character 8 2025-11-30 18:45:25.353 UTC client backend[46566] pg_regress/alter_table STATEMENT: select atacc1.a from atacc1; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist at character 8 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: select a,b,c,d from atacc1; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist at character 28 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: select * from atacc1 where a = 1; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist at character 8 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: select "........pg.dropped.1........" from atacc1; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column atacc1.........pg.dropped.1........ does not exist at character 8 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: select atacc1."........pg.dropped.1........" from atacc1; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist at character 8 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: select "........pg.dropped.1........",b,c,d from atacc1; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist at character 28 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: select * from atacc1 where "........pg.dropped.1........" = 1; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist at character 19 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: update atacc1 set a = 3; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist at character 31 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: update atacc1 set b = 2 where a = 3; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist at character 19 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: update atacc1 set "........pg.dropped.1........" = 3; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist at character 31 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: update atacc1 set b = 2 where "........pg.dropped.1........" = 3; 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: INSERT has more expressions than target columns at character 40 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 values (10, 11, 12, 13); 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table ERROR: INSERT has more expressions than target columns at character 45 2025-11-30 18:45:25.354 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 values (default, 11, 12, 13); 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (a) values (10); 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (a) values (default); 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (a,b,c,d) values (10,11,12,13); 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.355 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 (a,b,c,d) values (default,11,12,13); 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 ("........pg.dropped.1........") values (10); 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 ("........pg.dropped.1........") values (default); 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 ("........pg.dropped.1........",b,c,d) values (10,11,12,13); 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1 ("........pg.dropped.1........",b,c,d) values (default,11,12,13); 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist at character 26 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table STATEMENT: delete from atacc1 where a = 3; 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist at character 26 2025-11-30 18:45:25.356 UTC client backend[46566] pg_regress/alter_table STATEMENT: delete from atacc1 where "........pg.dropped.1........" = 3; 2025-11-30 18:45:25.357 UTC client backend[46566] pg_regress/alter_table ERROR: column "bar" of relation "atacc1" does not exist 2025-11-30 18:45:25.357 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 drop bar; 2025-11-30 18:45:25.357 UTC client backend[46566] pg_regress/alter_table ERROR: syntax error at or near "WITH" at character 24 2025-11-30 18:45:25.357 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 SET WITH OIDS; 2025-11-30 18:45:25.357 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop system column "xmin" 2025-11-30 18:45:25.357 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 drop xmin; 2025-11-30 18:45:25.359 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER action DROP COLUMN cannot be performed on relation "myview" 2025-11-30 18:45:25.359 UTC client backend[46566] pg_regress/alter_table DETAIL: This operation is not supported for views. 2025-11-30 18:45:25.359 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table myview drop d; 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table STATEMENT: analyze atacc1(a); 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table STATEMENT: analyze atacc1("........pg.dropped.1........"); 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table STATEMENT: vacuum analyze atacc1(a); 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.360 UTC client backend[46566] pg_regress/alter_table STATEMENT: vacuum analyze atacc1("........pg.dropped.1........"); 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: comment on column atacc1.a is 'testing'; 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: comment on column atacc1."........pg.dropped.1........" is 'testing'; 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter a set storage plain; 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter "........pg.dropped.1........" set storage plain; 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter a set statistics 0; 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter "........pg.dropped.1........" set statistics 0; 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter a set default 3; 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.361 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter "........pg.dropped.1........" set default 3; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter a drop default; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter "........pg.dropped.1........" drop default; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter a set not null; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter "........pg.dropped.1........" set not null; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter a drop not null; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 alter "........pg.dropped.1........" drop not null; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 rename a to x; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 rename "........pg.dropped.1........" to x; 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "atacc1" does not exist 2025-11-30 18:45:25.362 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add primary key(a); 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "atacc1" does not exist 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add primary key("........pg.dropped.1........"); 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" named in key does not exist 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add unique(a); 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" named in key does not exist 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add unique("........pg.dropped.1........"); 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add check (a > 3); 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist 2025-11-30 18:45:25.363 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add check ("........pg.dropped.1........" > 3); 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" referenced in foreign key constraint does not exist 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add foreign key (a) references atacc2(id); 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" referenced in foreign key constraint does not exist 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc1 add foreign key ("........pg.dropped.1........") references atacc2(id); 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" referenced in foreign key constraint does not exist 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc2 add foreign key (id) references atacc1(a); 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" referenced in foreign key constraint does not exist 2025-11-30 18:45:25.365 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table atacc2 add foreign key (id) references atacc1("........pg.dropped.1........"); 2025-11-30 18:45:25.367 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist 2025-11-30 18:45:25.367 UTC client backend[46566] pg_regress/alter_table STATEMENT: create index "testing_idx" on atacc1(a); 2025-11-30 18:45:25.367 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" does not exist 2025-11-30 18:45:25.367 UTC client backend[46566] pg_regress/alter_table STATEMENT: create index "testing_idx" on atacc1("........pg.dropped.1........"); 2025-11-30 18:45:25.377 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc1" violates check constraint "atacc1_value_check" 2025-11-30 18:45:25.377 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (1, 100). 2025-11-30 18:45:25.377 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1(value) values (100); 2025-11-30 18:45:25.379 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "atacc1" violates check constraint "atacc1_value_check" 2025-11-30 18:45:25.379 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (2, 100). 2025-11-30 18:45:25.379 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1(value) values (100); 2025-11-30 18:45:25.380 UTC client backend[46566] pg_regress/alter_table ERROR: null value in column "id" of relation "atacc1" violates not-null constraint 2025-11-30 18:45:25.380 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null, 0). 2025-11-30 18:45:25.380 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into atacc1(id, value) values (null, 0); 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" has a type conflict 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table DETAIL: double precision versus real 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table STATEMENT: create table child (a float4) inherits (parent); 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table ERROR: column "b" has a type conflict 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table DETAIL: numeric(10,4) versus numeric(10,7) 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table STATEMENT: create table child (b decimal(10,7)) inherits (parent); 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table ERROR: column "c" has a collation conflict 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table DETAIL: "C" versus "POSIX" 2025-11-30 18:45:25.389 UTC client backend[46566] pg_regress/alter_table STATEMENT: create table child (c text collate "POSIX") inherits (parent); 2025-11-30 18:45:25.395 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "attest" does not exist 2025-11-30 18:45:25.395 UTC client backend[46566] pg_regress/alter_table STATEMENT: copy attest(a) to stdout; 2025-11-30 18:45:25.395 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "attest" does not exist 2025-11-30 18:45:25.395 UTC client backend[46566] pg_regress/alter_table STATEMENT: copy attest("........pg.dropped.1........") to stdout; 2025-11-30 18:45:25.395 UTC client backend[46566] pg_regress/alter_table ERROR: extra data after last expected column 2025-11-30 18:45:25.395 UTC client backend[46566] pg_regress/alter_table CONTEXT: COPY attest, line 1: "10 11 12" 2025-11-30 18:45:25.395 UTC client backend[46566] pg_regress/alter_table STATEMENT: copy attest from stdin; 2025-11-30 18:45:25.396 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" of relation "attest" does not exist 2025-11-30 18:45:25.396 UTC client backend[46566] pg_regress/alter_table STATEMENT: copy attest(a) from stdin; 2025-11-30 18:45:25.396 UTC client backend[46566] pg_regress/alter_table ERROR: column "........pg.dropped.1........" of relation "attest" does not exist 2025-11-30 18:45:25.396 UTC client backend[46566] pg_regress/alter_table STATEMENT: copy attest("........pg.dropped.1........") from stdin; 2025-11-30 18:45:25.398 UTC client backend[46568] pg_regress/plpgsql ERROR: relation "dx" cannot be the target of a modifying statement 2025-11-30 18:45:25.398 UTC client backend[46568] 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-11-30 18:45:25.398 UTC client backend[46568] pg_regress/plpgsql STATEMENT: DELETE FROM transition_table_level2 WHERE level2_no BETWEEN 301 AND 305; 2025-11-30 18:45:25.399 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "a" 2025-11-30 18:45:25.399 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table dropColumnchild drop column a; 2025-11-30 18:45:25.399 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "b" 2025-11-30 18:45:25.399 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table only dropColumnChild drop column b; 2025-11-30 18:45:25.401 UTC client backend[46568] pg_regress/plpgsql ERROR: RI error 2025-11-30 18:45:25.401 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function transition_table_level1_ri_parent_del_func() line 6 at RAISE 2025-11-30 18:45:25.401 UTC client backend[46568] pg_regress/plpgsql STATEMENT: DELETE FROM transition_table_level1 WHERE level1_no = 25; 2025-11-30 18:45:25.404 UTC client backend[46568] pg_regress/plpgsql ERROR: RI error 2025-11-30 18:45:25.404 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function transition_table_level1_ri_parent_upd_func() line 15 at RAISE 2025-11-30 18:45:25.404 UTC client backend[46568] pg_regress/plpgsql STATEMENT: UPDATE transition_table_level1 SET level1_no = -1 WHERE level1_no = 30; 2025-11-30 18:45:25.404 UTC client backend[46566] pg_regress/alter_table ERROR: cannot rename inherited column "a" 2025-11-30 18:45:25.404 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table renameColumnChild rename column a to d; 2025-11-30 18:45:25.404 UTC client backend[46566] pg_regress/alter_table ERROR: inherited column "a" must be renamed in child tables too 2025-11-30 18:45:25.404 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table only renameColumnChild rename column a to d; 2025-11-30 18:45:25.404 UTC client backend[46566] pg_regress/alter_table ERROR: inherited column "a" must be renamed in child tables too 2025-11-30 18:45:25.404 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table only renameColumn rename column a to d; 2025-11-30 18:45:25.405 UTC client backend[46568] pg_regress/plpgsql ERROR: RI error 2025-11-30 18:45:25.405 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function transition_table_level2_ri_child_insupd_func() line 8 at RAISE 2025-11-30 18:45:25.405 UTC client backend[46568] pg_regress/plpgsql STATEMENT: INSERT INTO transition_table_level2 (level2_no, parent_no) VALUES (10000, 10000); 2025-11-30 18:45:25.405 UTC client backend[46566] pg_regress/alter_table ERROR: column must be added to child tables too 2025-11-30 18:45:25.405 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table only renameColumn add column x int; 2025-11-30 18:45:25.406 UTC client backend[46568] pg_regress/plpgsql ERROR: RI error 2025-11-30 18:45:25.406 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function transition_table_level2_ri_child_insupd_func() line 8 at RAISE 2025-11-30 18:45:25.406 UTC client backend[46568] pg_regress/plpgsql STATEMENT: UPDATE transition_table_level2 SET parent_no = 2000 WHERE level2_no = 40; 2025-11-30 18:45:25.407 UTC client backend[46566] pg_regress/alter_table ERROR: multiple ENFORCED/NOT ENFORCED clauses not allowed at character 70 2025-11-30 18:45:25.407 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table renameColumn add column y int check (x > 0) not enforced enforced; 2025-11-30 18:45:25.409 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "f1" 2025-11-30 18:45:25.409 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table c1 drop column f1; 2025-11-30 18:45:25.411 UTC client backend[46566] pg_regress/alter_table ERROR: column "f1" does not exist at character 8 2025-11-30 18:45:25.411 UTC client backend[46566] pg_regress/alter_table HINT: Perhaps you meant to reference the column "c1.f2". 2025-11-30 18:45:25.411 UTC client backend[46566] pg_regress/alter_table STATEMENT: select f1 from c1; 2025-11-30 18:45:25.414 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "f1" 2025-11-30 18:45:25.414 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table c1 drop column f1; 2025-11-30 18:45:25.414 UTC client backend[46566] pg_regress/alter_table ERROR: column "f1" does not exist at character 8 2025-11-30 18:45:25.414 UTC client backend[46566] pg_regress/alter_table HINT: Perhaps you meant to reference the column "c1.f2". 2025-11-30 18:45:25.414 UTC client backend[46566] pg_regress/alter_table STATEMENT: select f1 from c1; 2025-11-30 18:45:25.417 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "f1" 2025-11-30 18:45:25.417 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table c1 drop column f1; 2025-11-30 18:45:25.418 UTC client backend[46568] pg_regress/plpgsql ERROR: TRUNCATE triggers with transition tables are not supported 2025-11-30 18:45:25.418 UTC client backend[46568] 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-11-30 18:45:25.421 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "f1" 2025-11-30 18:45:25.421 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table c1 drop column f1; 2025-11-30 18:45:25.421 UTC client backend[46568] pg_regress/plpgsql WARNING: old table = 1=1,2=2,3=3, new table = 1=11,2=22,3=33 2025-11-30 18:45:25.421 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE 2025-11-30 18:45:25.426 UTC client backend[46568] pg_regress/plpgsql WARNING: old table = 1=11,2=22,3=33, new table = 1=1111,2=2222,3=3333 2025-11-30 18:45:25.426 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE 2025-11-30 18:45:25.428 UTC client backend[46568] pg_regress/plpgsql ERROR: column "name" does not exist at character 33 2025-11-30 18:45:25.428 UTC client backend[46568] pg_regress/plpgsql QUERY: (SELECT string_agg(id || '=' || name, ',') FROM d) 2025-11-30 18:45:25.428 UTC client backend[46568] pg_regress/plpgsql CONTEXT: PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE 2025-11-30 18:45:25.428 UTC client backend[46568] pg_regress/plpgsql STATEMENT: UPDATE alter_table_under_transition_tables SET id = id; 2025-11-30 18:45:25.431 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "name" 2025-11-30 18:45:25.431 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table gc1 drop column name; 2025-11-30 18:45:25.432 UTC client backend[46566] pg_regress/alter_table ERROR: column "name" of relation "gc1" does not exist 2025-11-30 18:45:25.432 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table gc1 drop column name; 2025-11-30 18:45:25.434 UTC client backend[46566] pg_regress/alter_table ERROR: column "non_existing" of relation "dropcolumnexists" does not exist 2025-11-30 18:45:25.434 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table dropColumnExists drop column non_existing; 2025-11-30 18:45:25.444 UTC client backend[46568] pg_regress/plpgsql ERROR: "x" is not a scalar variable at character 72 2025-11-30 18:45:25.444 UTC client backend[46568] pg_regress/plpgsql STATEMENT: CREATE FUNCTION fx(x WSlot) RETURNS void AS $$ BEGIN GET DIAGNOSTICS x = ROW_COUNT; RETURN; END; $$ LANGUAGE plpgsql; 2025-11-30 18:45:25.448 UTC client backend[46568] pg_regress/plpgsql LOG: disconnection: session time: 0:00:01.152 user=postgres database=regression host=[local] 2025-11-30 18:45:25.450 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "c1" violates check constraint "p1_a1_check" 2025-11-30 18:45:25.450 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (11, xyz, 33, 0). 2025-11-30 18:45:25.450 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into c1 values(11,'xyz',33,0); 2025-11-30 18:45:25.460 UTC client backend[46566] pg_regress/alter_table ERROR: column "f1" cannot be cast automatically to type integer 2025-11-30 18:45:25.460 UTC client backend[46566] pg_regress/alter_table HINT: You might need to specify "USING f1::integer". 2025-11-30 18:45:25.460 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table foo alter f1 TYPE integer; 2025-11-30 18:45:25.467 UTC client backend[46566] pg_regress/alter_table ERROR: column "atcol1" cannot be cast automatically to type boolean 2025-11-30 18:45:25.467 UTC client backend[46566] pg_regress/alter_table HINT: You might need to specify "USING atcol1::boolean". 2025-11-30 18:45:25.467 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table anothertab alter column atcol1 type boolean; 2025-11-30 18:45:25.467 UTC client backend[46566] pg_regress/alter_table ERROR: result of USING clause for column "atcol1" cannot be cast automatically to type boolean 2025-11-30 18:45:25.467 UTC client backend[46566] pg_regress/alter_table HINT: You might need to add an explicit cast. 2025-11-30 18:45:25.467 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table anothertab alter column atcol1 type boolean using atcol1::int; 2025-11-30 18:45:25.472 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "anothertab" violates check constraint "anothertab_chk" 2025-11-30 18:45:25.472 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (45, null). 2025-11-30 18:45:25.472 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into anothertab (atcol1, atcol2) values (45, null); 2025-11-30 18:45:25.478 UTC client backend[46566] pg_regress/alter_table ERROR: default for column "atcol1" cannot be cast automatically to type boolean 2025-11-30 18:45:25.478 UTC client backend[46566] 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-11-30 18:45:25.480 UTC client backend[46566] pg_regress/alter_table ERROR: operator does not exist: boolean <= integer 2025-11-30 18:45:25.480 UTC client backend[46566] pg_regress/alter_table DETAIL: No operator of that name accepts the given argument types. 2025-11-30 18:45:25.480 UTC client backend[46566] pg_regress/alter_table HINT: You might need to add explicit type casts. 2025-11-30 18:45:25.480 UTC client backend[46566] 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-11-30 18:45:25.481 UTC client backend[46566] pg_regress/alter_table ERROR: constraint "anothertab_chk" of relation "anothertab" does not exist 2025-11-30 18:45:25.481 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table anothertab drop constraint anothertab_chk; 2025-11-30 18:45:25.533 UTC client backend[46536] isolation/eval-plan-qual-trigger/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:25.533 UTC client backend[46536] isolation/eval-plan-qual-trigger/s2 STATEMENT: UPDATE trigtest SET data = data || '-ups2' WHERE noisy_oper('upd', key, '=', 'key-a') AND noisy_oper('upk', data, '<>', 'mismatch') RETURNING *; 2025-11-30 18:45:25.557 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter table "at_tab1" because column "at_tab2.y" uses its row type 2025-11-30 18:45:25.557 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table at_tab1 alter column b type varchar; 2025-11-30 18:45:25.562 UTC client backend[46566] pg_regress/alter_table ERROR: ROW() column has type text instead of type character varying 2025-11-30 18:45:25.562 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into at_tab2 values(1,'42'); 2025-11-30 18:45:25.567 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter table "at_tab1" because column "at_tab2.y" uses its row type 2025-11-30 18:45:25.567 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table at_tab1 alter column b type varchar; 2025-11-30 18:45:25.584 UTC client backend[46536] isolation/eval-plan-qual-trigger/s2 ERROR: could not serialize access due to concurrent delete 2025-11-30 18:45:25.584 UTC client backend[46536] isolation/eval-plan-qual-trigger/s2 STATEMENT: UPDATE trigtest SET data = data || '-ups2' WHERE noisy_oper('upd', key, '=', 'key-a') AND noisy_oper('upk', data, '<>', 'mismatch') RETURNING *; 2025-11-30 18:45:25.615 UTC client backend[46533] isolation/eval-plan-qual-trigger/control connection LOG: disconnection: session time: 0:00:01.536 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.615 UTC client backend[46534] isolation/eval-plan-qual-trigger/s0 LOG: disconnection: session time: 0:00:01.531 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.615 UTC client backend[46537] isolation/eval-plan-qual-trigger/s3 LOG: disconnection: session time: 0:00:01.520 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.615 UTC client backend[46536] isolation/eval-plan-qual-trigger/s2 LOG: disconnection: session time: 0:00:01.523 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.616 UTC client backend[46535] isolation/eval-plan-qual-trigger/s1 LOG: disconnection: session time: 0:00:01.527 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.620 UTC unrecognized[46589] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.621 UTC client backend[46589] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.621 UTC client backend[46589] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/inplace-inval 2025-11-30 18:45:25.622 UTC client backend[46589] isolation/inplace-inval LOG: connection ready: setup total=1.779 ms, fork=0.354 ms, authentication=0.109 ms 2025-11-30 18:45:25.623 UTC unrecognized[46590] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.623 UTC client backend[46590] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.623 UTC client backend[46590] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/inplace-inval 2025-11-30 18:45:25.624 UTC client backend[46590] isolation/inplace-inval LOG: connection ready: setup total=1.549 ms, fork=0.301 ms, authentication=0.104 ms 2025-11-30 18:45:25.625 UTC unrecognized[46591] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.626 UTC client backend[46591] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.626 UTC client backend[46591] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/inplace-inval 2025-11-30 18:45:25.626 UTC client backend[46591] isolation/inplace-inval LOG: connection ready: setup total=1.510 ms, fork=0.284 ms, authentication=0.093 ms 2025-11-30 18:45:25.627 UTC unrecognized[46592] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.628 UTC client backend[46592] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.628 UTC client backend[46592] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/inplace-inval 2025-11-30 18:45:25.629 UTC client backend[46592] isolation/inplace-inval LOG: connection ready: setup total=1.585 ms, fork=0.284 ms, authentication=0.101 ms 2025-11-30 18:45:25.642 UTC client backend[46589] isolation/inplace-inval/control connection LOG: disconnection: session time: 0:00:00.021 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.642 UTC client backend[46591] isolation/inplace-inval/s2 LOG: disconnection: session time: 0:00:00.016 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.642 UTC client backend[46590] isolation/inplace-inval/s1 LOG: disconnection: session time: 0:00:00.018 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.642 UTC client backend[46592] isolation/inplace-inval/s3 LOG: disconnection: session time: 0:00:00.014 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.647 UTC unrecognized[46595] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.648 UTC client backend[46595] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.648 UTC client backend[46595] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace 2025-11-30 18:45:25.649 UTC client backend[46595] isolation/intra-grant-inplace LOG: connection ready: setup total=1.863 ms, fork=0.332 ms, authentication=0.123 ms 2025-11-30 18:45:25.650 UTC unrecognized[46596] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.650 UTC client backend[46596] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.650 UTC client backend[46596] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace 2025-11-30 18:45:25.651 UTC client backend[46596] isolation/intra-grant-inplace LOG: connection ready: setup total=1.597 ms, fork=0.306 ms, authentication=0.101 ms 2025-11-30 18:45:25.652 UTC unrecognized[46597] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.653 UTC client backend[46597] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.653 UTC client backend[46597] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace 2025-11-30 18:45:25.653 UTC client backend[46597] isolation/intra-grant-inplace LOG: connection ready: setup total=1.566 ms, fork=0.303 ms, authentication=0.098 ms 2025-11-30 18:45:25.655 UTC unrecognized[46598] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.655 UTC client backend[46598] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.655 UTC client backend[46598] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace 2025-11-30 18:45:25.656 UTC client backend[46598] isolation/intra-grant-inplace LOG: connection ready: setup total=1.555 ms, fork=0.319 ms, authentication=0.094 ms 2025-11-30 18:45:25.657 UTC unrecognized[46599] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.657 UTC client backend[46599] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.657 UTC client backend[46599] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace 2025-11-30 18:45:25.658 UTC client backend[46599] isolation/intra-grant-inplace LOG: connection ready: setup total=1.622 ms, fork=0.320 ms, authentication=0.111 ms 2025-11-30 18:45:25.659 UTC unrecognized[46600] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.660 UTC client backend[46600] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.660 UTC client backend[46600] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace 2025-11-30 18:45:25.660 UTC client backend[46600] isolation/intra-grant-inplace LOG: connection ready: setup total=1.547 ms, fork=0.292 ms, authentication=0.096 ms 2025-11-30 18:45:25.669 UTC client backend[46566] pg_regress/alter_table ERROR: composite type recur1 cannot be made a member of itself 2025-11-30 18:45:25.669 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table recur1 add column f2 recur1; 2025-11-30 18:45:25.669 UTC client backend[46566] pg_regress/alter_table ERROR: composite type recur1 cannot be made a member of itself 2025-11-30 18:45:25.669 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table recur1 add column f2 recur1[]; 2025-11-30 18:45:25.670 UTC client backend[46566] pg_regress/alter_table ERROR: composite type recur1 cannot be made a member of itself 2025-11-30 18:45:25.670 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table recur1 add column f2 array_of_recur1; 2025-11-30 18:45:25.671 UTC client backend[46566] pg_regress/alter_table ERROR: composite type recur1 cannot be made a member of itself 2025-11-30 18:45:25.671 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table recur1 add column f2 recur2; 2025-11-30 18:45:25.672 UTC client backend[46566] pg_regress/alter_table ERROR: composite type recur1 cannot be made a member of itself 2025-11-30 18:45:25.672 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table recur1 alter column f2 type recur2; 2025-11-30 18:45:25.676 UTC client backend[46597] isolation/intra-grant-inplace/s2 LOG: process 46597 still waiting for AccessExclusiveLock on relation 68489 of database 16387 after 10.178 ms 2025-11-30 18:45:25.676 UTC client backend[46597] isolation/intra-grant-inplace/s2 DETAIL: Process holding the lock: 46596. Wait queue: 46597. 2025-11-30 18:45:25.676 UTC client backend[46597] isolation/intra-grant-inplace/s2 CONTEXT: waiting for AccessExclusiveLock on relation 68489 of database 16387 2025-11-30 18:45:25.676 UTC client backend[46597] isolation/intra-grant-inplace/s2 STATEMENT: ALTER TABLE intra_grant_inplace ADD PRIMARY KEY (c); 2025-11-30 18:45:25.676 UTC client backend[46597] isolation/intra-grant-inplace/s2 LOG: process 46597 acquired AccessExclusiveLock on relation 68489 of database 16387 after 10.391 ms 2025-11-30 18:45:25.676 UTC client backend[46597] isolation/intra-grant-inplace/s2 CONTEXT: waiting for AccessExclusiveLock on relation 68489 of database 16387 2025-11-30 18:45:25.676 UTC client backend[46597] isolation/intra-grant-inplace/s2 STATEMENT: ALTER TABLE intra_grant_inplace ADD PRIMARY KEY (c); 2025-11-30 18:45:25.678 UTC client backend[46566] pg_regress/alter_table ERROR: column data type integer can only have storage PLAIN 2025-11-30 18:45:25.678 UTC client backend[46566] pg_regress/alter_table STATEMENT: create table test_storage_failed (a text, b int storage extended); 2025-11-30 18:45:25.758 UTC client backend[46597] isolation/intra-grant-inplace/s2 LOG: process 46597 still waiting for AccessExclusiveLock on relation 68573 of database 16387 after 10.663 ms 2025-11-30 18:45:25.758 UTC client backend[46597] isolation/intra-grant-inplace/s2 DETAIL: Process holding the lock: 46596. Wait queue: 46597. 2025-11-30 18:45:25.758 UTC client backend[46597] isolation/intra-grant-inplace/s2 CONTEXT: waiting for AccessExclusiveLock on relation 68573 of database 16387 2025-11-30 18:45:25.758 UTC client backend[46597] isolation/intra-grant-inplace/s2 STATEMENT: ALTER TABLE intra_grant_inplace ADD PRIMARY KEY (c); 2025-11-30 18:45:25.791 UTC client backend[46597] isolation/intra-grant-inplace/s2 LOG: process 46597 acquired AccessExclusiveLock on relation 68573 of database 16387 after 42.962 ms 2025-11-30 18:45:25.791 UTC client backend[46597] isolation/intra-grant-inplace/s2 CONTEXT: waiting for AccessExclusiveLock on relation 68573 of database 16387 2025-11-30 18:45:25.791 UTC client backend[46597] isolation/intra-grant-inplace/s2 STATEMENT: ALTER TABLE intra_grant_inplace ADD PRIMARY KEY (c); 2025-11-30 18:45:25.811 UTC client backend[46566] pg_regress/alter_table ERROR: cannot convert whole-row table reference 2025-11-30 18:45:25.811 UTC client backend[46566] pg_regress/alter_table DETAIL: USING expression contains a whole-row table reference. 2025-11-30 18:45:25.811 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE test_type_diff2 ALTER COLUMN int_four TYPE int4 USING (pg_column_size(test_type_diff2)); 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 LOG: process 46597 detected deadlock while waiting for AccessExclusiveLock on relation 68597 of database 16387 after 10.681 ms 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 DETAIL: Process holding the lock: 46596. Wait queue: . 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 CONTEXT: waiting for AccessExclusiveLock on relation 68597 of database 16387 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 STATEMENT: ALTER TABLE intra_grant_inplace ADD PRIMARY KEY (c); 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 ERROR: deadlock detected 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 DETAIL: Process 46597 waits for AccessExclusiveLock on relation 68597 of database 16387; blocked by process 46596. Process 46596 waits for ShareLock on transaction 28953; blocked by process 46597. Process 46597: ALTER TABLE intra_grant_inplace ADD PRIMARY KEY (c); Process 46596: GRANT SELECT ON intra_grant_inplace TO PUBLIC; 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 HINT: See server log for query details. 2025-11-30 18:45:25.816 UTC client backend[46597] isolation/intra-grant-inplace/s2 STATEMENT: ALTER TABLE intra_grant_inplace ADD PRIMARY KEY (c); 2025-11-30 18:45:25.896 UTC client backend[46566] pg_regress/alter_table ERROR: type "lockmodes" does not exist 2025-11-30 18:45:25.896 UTC client backend[46566] pg_regress/alter_table STATEMENT: drop type lockmodes; 2025-11-30 18:45:25.897 UTC client backend[46566] pg_regress/alter_table ERROR: view "my_locks" does not exist 2025-11-30 18:45:25.897 UTC client backend[46566] pg_regress/alter_table STATEMENT: drop view my_locks; 2025-11-30 18:45:25.908 UTC client backend[46599] isolation/intra-grant-inplace/s4 WARNING: got: cache lookup failed for relation REDACTED 2025-11-30 18:45:25.908 UTC client backend[46599] isolation/intra-grant-inplace/s4 CONTEXT: PL/pgSQL function inline_code_block line 5 at RAISE 2025-11-30 18:45:25.908 UTC client backend[46595] isolation/intra-grant-inplace/control connection LOG: disconnection: session time: 0:00:00.261 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.908 UTC client backend[46597] isolation/intra-grant-inplace/s2 LOG: disconnection: session time: 0:00:00.256 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.908 UTC client backend[46596] isolation/intra-grant-inplace/s1 LOG: disconnection: session time: 0:00:00.258 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.908 UTC client backend[46598] isolation/intra-grant-inplace/s3 LOG: disconnection: session time: 0:00:00.253 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.910 UTC client backend[46599] isolation/intra-grant-inplace/s4 LOG: disconnection: session time: 0:00:00.252 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.910 UTC client backend[46600] isolation/intra-grant-inplace/s5 LOG: disconnection: session time: 0:00:00.250 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.916 UTC unrecognized[46603] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.917 UTC client backend[46603] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.917 UTC client backend[46603] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace-db 2025-11-30 18:45:25.918 UTC client backend[46603] isolation/intra-grant-inplace-db LOG: connection ready: setup total=2.283 ms, fork=0.468 ms, authentication=0.166 ms 2025-11-30 18:45:25.919 UTC unrecognized[46604] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.920 UTC client backend[46604] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.920 UTC client backend[46604] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace-db 2025-11-30 18:45:25.921 UTC client backend[46604] isolation/intra-grant-inplace-db LOG: connection ready: setup total=1.973 ms, fork=0.401 ms, authentication=0.127 ms 2025-11-30 18:45:25.922 UTC unrecognized[46605] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.922 UTC client backend[46605] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.922 UTC client backend[46605] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace-db 2025-11-30 18:45:25.923 UTC client backend[46605] isolation/intra-grant-inplace-db LOG: connection ready: setup total=1.611 ms, fork=0.301 ms, authentication=0.109 ms 2025-11-30 18:45:25.924 UTC unrecognized[46606] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:25.925 UTC client backend[46606] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:25.925 UTC client backend[46606] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/intra-grant-inplace-db 2025-11-30 18:45:25.926 UTC client backend[46606] isolation/intra-grant-inplace-db LOG: connection ready: setup total=1.564 ms, fork=0.304 ms, authentication=0.102 ms 2025-11-30 18:45:25.942 UTC client backend[46566] pg_regress/alter_table ERROR: unrecognized parameter "autovacuum_enabled" 2025-11-30 18:45:25.942 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table my_locks set (autovacuum_enabled = false); 2025-11-30 18:45:25.943 UTC client backend[46566] pg_regress/alter_table ERROR: unrecognized parameter "autovacuum_enabled" 2025-11-30 18:45:25.943 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter view my_locks set (autovacuum_enabled = false); 2025-11-30 18:45:25.989 UTC client backend[46566] pg_regress/alter_table ERROR: relation "nosuchtype" does not exist 2025-11-30 18:45:25.989 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE nosuchtype ADD ATTRIBUTE b text; 2025-11-30 18:45:25.993 UTC client backend[46566] pg_regress/alter_table ERROR: column "b" of relation "test_type" already exists 2025-11-30 18:45:25.993 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type ADD ATTRIBUTE b text; 2025-11-30 18:45:25.996 UTC client backend[46603] isolation/intra-grant-inplace-db/control connection LOG: disconnection: session time: 0:00:00.079 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.996 UTC client backend[46604] isolation/intra-grant-inplace-db/s1 LOG: disconnection: session time: 0:00:00.076 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.996 UTC client backend[46605] isolation/intra-grant-inplace-db/s2 LOG: disconnection: session time: 0:00:00.073 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:25.998 UTC client backend[46606] isolation/intra-grant-inplace-db/s3 LOG: disconnection: session time: 0:00:00.073 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.002 UTC unrecognized[46611] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.002 UTC client backend[46611] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.002 UTC client backend[46611] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/lock-update-delete 2025-11-30 18:45:26.006 UTC client backend[46566] pg_regress/alter_table ERROR: column "c" of relation "test_type" does not exist 2025-11-30 18:45:26.006 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type DROP ATTRIBUTE c; 2025-11-30 18:45:26.007 UTC client backend[46611] isolation/lock-update-delete LOG: connection ready: setup total=5.655 ms, fork=0.375 ms, authentication=0.108 ms 2025-11-30 18:45:26.008 UTC unrecognized[46612] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.009 UTC client backend[46612] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.009 UTC client backend[46612] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/lock-update-delete 2025-11-30 18:45:26.009 UTC client backend[46612] isolation/lock-update-delete LOG: connection ready: setup total=1.631 ms, fork=0.328 ms, authentication=0.103 ms 2025-11-30 18:45:26.011 UTC unrecognized[46613] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.011 UTC client backend[46613] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.011 UTC client backend[46613] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/lock-update-delete 2025-11-30 18:45:26.011 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" does not exist 2025-11-30 18:45:26.011 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type RENAME ATTRIBUTE a TO aa; 2025-11-30 18:45:26.012 UTC client backend[46613] isolation/lock-update-delete LOG: connection ready: setup total=1.601 ms, fork=0.295 ms, authentication=0.099 ms 2025-11-30 18:45:26.018 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter type "test_type1" because column "test_tbl1.y" uses it 2025-11-30 18:45:26.018 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type1 ALTER ATTRIBUTE b TYPE varchar; 2025-11-30 18:45:26.023 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter type "test_type1" because column "test_tbl1_idx.row" uses it 2025-11-30 18:45:26.023 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type1 ALTER ATTRIBUTE b TYPE varchar; 2025-11-30 18:45:26.042 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter type "test_type2" because it is the type of a typed table 2025-11-30 18:45:26.042 UTC client backend[46566] pg_regress/alter_table HINT: Use ALTER ... CASCADE to alter the typed tables too. 2025-11-30 18:45:26.042 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type2 ADD ATTRIBUTE c text; 2025-11-30 18:45:26.056 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter type "test_type2" because it is the type of a typed table 2025-11-30 18:45:26.056 UTC client backend[46566] pg_regress/alter_table HINT: Use ALTER ... CASCADE to alter the typed tables too. 2025-11-30 18:45:26.056 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type2 ALTER ATTRIBUTE b TYPE varchar; 2025-11-30 18:45:26.069 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter type "test_type2" because it is the type of a typed table 2025-11-30 18:45:26.069 UTC client backend[46566] pg_regress/alter_table HINT: Use ALTER ... CASCADE to alter the typed tables too. 2025-11-30 18:45:26.069 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type2 DROP ATTRIBUTE b; 2025-11-30 18:45:26.082 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter type "test_type2" because it is the type of a typed table 2025-11-30 18:45:26.082 UTC client backend[46566] pg_regress/alter_table HINT: Use ALTER ... CASCADE to alter the typed tables too. 2025-11-30 18:45:26.082 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_type2 RENAME ATTRIBUTE a TO aa; 2025-11-30 18:45:26.109 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop column a of composite type test_typex because other objects depend on it 2025-11-30 18:45:26.109 UTC client backend[46566] pg_regress/alter_table DETAIL: constraint test_tblx_y_check on table test_tblx depends on column a of composite type test_typex 2025-11-30 18:45:26.109 UTC client backend[46566] pg_regress/alter_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-30 18:45:26.109 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TYPE test_typex DROP ATTRIBUTE a; 2025-11-30 18:45:26.133 UTC client backend[46566] pg_regress/alter_table ERROR: table "tt1" has different type for column "y" 2025-11-30 18:45:26.133 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt1 OF tt_t0; 2025-11-30 18:45:26.133 UTC client backend[46566] pg_regress/alter_table ERROR: table "tt2" has different type for column "y" 2025-11-30 18:45:26.133 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt2 OF tt_t0; 2025-11-30 18:45:26.133 UTC client backend[46566] pg_regress/alter_table ERROR: table has column "y" where type requires "x" 2025-11-30 18:45:26.133 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt3 OF tt_t0; 2025-11-30 18:45:26.134 UTC client backend[46566] pg_regress/alter_table ERROR: table is missing column "y" 2025-11-30 18:45:26.134 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt4 OF tt_t0; 2025-11-30 18:45:26.134 UTC client backend[46566] pg_regress/alter_table ERROR: table has extra column "z" 2025-11-30 18:45:26.134 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt5 OF tt_t0; 2025-11-30 18:45:26.134 UTC client backend[46566] pg_regress/alter_table ERROR: typed tables cannot inherit 2025-11-30 18:45:26.134 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt6 OF tt_t0; 2025-11-30 18:45:26.148 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "test_drop_constr_child" violates check constraint "test_drop_constr_parent_c_check" 2025-11-30 18:45:26.148 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (null). 2025-11-30 18:45:26.148 UTC client backend[46566] pg_regress/alter_table STATEMENT: INSERT INTO test_drop_constr_child (c) VALUES (NULL); 2025-11-30 18:45:26.170 UTC client backend[46566] pg_regress/alter_table ERROR: constraint "foo" for relation "tt9" already exists 2025-11-30 18:45:26.170 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt9 ADD CONSTRAINT foo CHECK(c > 4); 2025-11-30 18:45:26.173 UTC client backend[46566] pg_regress/alter_table ERROR: relation "tt9_c_key" already exists 2025-11-30 18:45:26.173 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt9 ADD CONSTRAINT tt9_c_key UNIQUE(c); 2025-11-30 18:45:26.173 UTC client backend[46566] pg_regress/alter_table ERROR: constraint "foo" for relation "tt9" already exists 2025-11-30 18:45:26.173 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt9 ADD CONSTRAINT foo UNIQUE(c); 2025-11-30 18:45:26.173 UTC client backend[46566] pg_regress/alter_table ERROR: constraint "tt9_c_key" for relation "tt9" already exists 2025-11-30 18:45:26.173 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE tt9 ADD CONSTRAINT tt9_c_key CHECK(c > 5); 2025-11-30 18:45:26.215 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter system column "xmin" at character 39 2025-11-30 18:45:26.215 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE comment_test ALTER COLUMN xmin SET DATA TYPE x; 2025-11-30 18:45:26.215 UTC client backend[46566] pg_regress/alter_table ERROR: type "x" does not exist at character 56 2025-11-30 18:45:26.215 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE comment_test ALTER COLUMN id SET DATA TYPE x; 2025-11-30 18:45:26.216 UTC client backend[46566] pg_regress/alter_table ERROR: collations are not supported by type integer at character 60 2025-11-30 18:45:26.216 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE comment_test ALTER COLUMN id SET DATA TYPE int COLLATE "C"; 2025-11-30 18:45:26.230 UTC client backend[46566] pg_regress/alter_table ERROR: foreign key constraint "comment_test_child_fk" cannot be implemented 2025-11-30 18:45:26.230 UTC client backend[46566] 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-11-30 18:45:26.230 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE comment_test ALTER COLUMN id SET DATA TYPE int USING id::integer; 2025-11-30 18:45:26.257 UTC client backend[46566] pg_regress/alter_table ERROR: permission denied to create "pg_catalog.new_system_table" 2025-11-30 18:45:26.257 UTC client backend[46566] pg_regress/alter_table DETAIL: System catalog modifications are currently disallowed. 2025-11-30 18:45:26.257 UTC client backend[46566] pg_regress/alter_table STATEMENT: CREATE TABLE pg_catalog.new_system_table(); 2025-11-30 18:45:26.291 UTC client backend[46566] pg_regress/alter_table ERROR: could not change table "unlogged2" to logged because it references unlogged table "unlogged1" 2025-11-30 18:45:26.291 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE unlogged2 SET LOGGED; 2025-11-30 18:45:26.322 UTC client backend[46566] pg_regress/alter_table ERROR: could not change table "logged1" to unlogged because it references logged table "logged2" 2025-11-30 18:45:26.322 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE logged1 SET UNLOGGED; 2025-11-30 18:45:26.363 UTC client backend[46566] pg_regress/alter_table ERROR: column "c2" of relation "test_add_column" already exists 2025-11-30 18:45:26.363 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE test_add_column ADD COLUMN c2 integer; 2025-11-30 18:45:26.363 UTC client backend[46566] pg_regress/alter_table ERROR: column "c2" of relation "test_add_column" already exists 2025-11-30 18:45:26.363 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE ONLY test_add_column ADD COLUMN c2 integer; 2025-11-30 18:45:26.380 UTC client backend[46566] pg_regress/alter_table ERROR: column "c2" of relation "test_add_column" already exists 2025-11-30 18:45:26.380 UTC client backend[46566] 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-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop column "a" because it is part of the partition key of relation "partitioned" 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE partitioned DROP COLUMN a; 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter column "a" because it is part of the partition key of relation "partitioned" at character 38 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE partitioned ALTER COLUMN a TYPE char(5); 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop column "b" because it is part of the partition key of relation "partitioned" 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE partitioned DROP COLUMN b; 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter column "b" because it is part of the partition key of relation "partitioned" at character 38 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE partitioned ALTER COLUMN b TYPE char(5); 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table ERROR: cannot specify storage parameters for a partitioned table 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table HINT: Specify storage parameters for its leaf partitions instead. 2025-11-30 18:45:26.552 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE partitioned SET (fillfactor=100); 2025-11-30 18:45:26.553 UTC client backend[46566] pg_regress/alter_table ERROR: cannot change inheritance of partitioned table 2025-11-30 18:45:26.553 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE partitioned INHERIT nonpartitioned; 2025-11-30 18:45:26.553 UTC client backend[46566] pg_regress/alter_table ERROR: cannot inherit from partitioned table "partitioned" 2025-11-30 18:45:26.553 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE nonpartitioned INHERIT partitioned; 2025-11-30 18:45:26.553 UTC client backend[46566] pg_regress/alter_table ERROR: cannot add NO INHERIT constraint to partitioned table "partitioned" 2025-11-30 18:45:26.553 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE partitioned ADD CONSTRAINT chk_a CHECK (a > 0) NO INHERIT; 2025-11-30 18:45:26.556 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER action ATTACH PARTITION cannot be performed on relation "unparted" 2025-11-30 18:45:26.556 UTC client backend[46566] pg_regress/alter_table DETAIL: This operation is not supported for tables. 2025-11-30 18:45:26.556 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE unparted ATTACH PARTITION fail_part FOR VALUES IN ('a'); 2025-11-30 18:45:26.560 UTC client backend[46566] pg_regress/alter_table ERROR: invalid bound specification for a list partition at character 63 2025-11-30 18:45:26.560 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES FROM (1) TO (10); 2025-11-30 18:45:26.562 UTC client backend[46566] pg_regress/alter_table ERROR: relation "nonexistent" does not exist 2025-11-30 18:45:26.562 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION nonexistent FOR VALUES IN (1); 2025-11-30 18:45:26.562 UTC client backend[46611] isolation/lock-update-delete/control connection LOG: disconnection: session time: 0:00:00.560 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.562 UTC client backend[46612] isolation/lock-update-delete/s1 LOG: disconnection: session time: 0:00:00.554 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.562 UTC client backend[46613] isolation/lock-update-delete/s2 LOG: disconnection: session time: 0:00:00.551 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.565 UTC client backend[46566] pg_regress/alter_table ERROR: must be owner of table not_owned_by_me 2025-11-30 18:45:26.565 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE owned_by_me ATTACH PARTITION not_owned_by_me FOR VALUES IN (1); 2025-11-30 18:45:26.567 UTC unrecognized[46616] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.568 UTC client backend[46616] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.568 UTC client backend[46616] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/lock-update-traversal 2025-11-30 18:45:26.568 UTC client backend[46616] isolation/lock-update-traversal LOG: connection ready: setup total=1.799 ms, fork=0.313 ms, authentication=0.110 ms 2025-11-30 18:45:26.570 UTC unrecognized[46617] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.570 UTC client backend[46566] pg_regress/alter_table ERROR: cannot attach inheritance child as partition 2025-11-30 18:45:26.570 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION child FOR VALUES IN (1); 2025-11-30 18:45:26.570 UTC client backend[46617] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.570 UTC client backend[46617] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/lock-update-traversal 2025-11-30 18:45:26.570 UTC client backend[46566] pg_regress/alter_table ERROR: cannot attach inheritance parent as partition 2025-11-30 18:45:26.570 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION parent FOR VALUES IN (1); 2025-11-30 18:45:26.571 UTC client backend[46617] isolation/lock-update-traversal LOG: connection ready: setup total=1.586 ms, fork=0.298 ms, authentication=0.102 ms 2025-11-30 18:45:26.572 UTC unrecognized[46618] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.573 UTC client backend[46618] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.573 UTC client backend[46618] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/lock-update-traversal 2025-11-30 18:45:26.573 UTC client backend[46618] isolation/lock-update-traversal LOG: connection ready: setup total=1.584 ms, fork=0.284 ms, authentication=0.100 ms 2025-11-30 18:45:26.575 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "parent" violates partition constraint 2025-11-30 18:45:26.575 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (2, null). 2025-11-30 18:45:26.575 UTC client backend[46566] pg_regress/alter_table STATEMENT: UPDATE parent SET a = 2 WHERE a = 1; 2025-11-30 18:45:26.578 UTC client backend[46566] pg_regress/alter_table ERROR: cannot attach a permanent relation as partition of temporary relation "temp_parted" 2025-11-30 18:45:26.578 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE temp_parted ATTACH PARTITION perm_part FOR VALUES IN (1); 2025-11-30 18:45:26.580 UTC client backend[46566] pg_regress/alter_table ERROR: cannot attach a typed table as partition 2025-11-30 18:45:26.580 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.583 UTC client backend[46566] pg_regress/alter_table ERROR: table "fail_part" contains column "c" not found in parent "list_parted" 2025-11-30 18:45:26.583 UTC client backend[46566] pg_regress/alter_table DETAIL: The new partition may contain only the columns present in parent. 2025-11-30 18:45:26.583 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.585 UTC client backend[46566] pg_regress/alter_table ERROR: child table is missing column "b" 2025-11-30 18:45:26.585 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.587 UTC client backend[46566] pg_regress/alter_table ERROR: child table "fail_part" has different type for column "b" 2025-11-30 18:45:26.587 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.590 UTC client backend[46566] pg_regress/alter_table ERROR: child table "fail_part" has different collation for column "b" 2025-11-30 18:45:26.590 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.592 UTC client backend[46566] pg_regress/alter_table ERROR: child table is missing constraint "check_a" 2025-11-30 18:45:26.592 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.593 UTC client backend[46566] pg_regress/alter_table ERROR: child table "fail_part" has different definition for check constraint "check_a" 2025-11-30 18:45:26.593 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.600 UTC client backend[46566] pg_regress/alter_table ERROR: constraint "part_fail_a_not_null" conflicts with non-inherited constraint on child table "part_fail" 2025-11-30 18:45:26.600 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION part_fail FOR VALUES IN (2); 2025-11-30 18:45:26.603 UTC client backend[46566] pg_regress/alter_table ERROR: partition "fail_part" would overlap partition "part_1" at character 67 2025-11-30 18:45:26.603 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1); 2025-11-30 18:45:26.608 UTC client backend[46566] pg_regress/alter_table ERROR: partition "fail_def_part" conflicts with existing default partition "def_part" at character 56 2025-11-30 18:45:26.608 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted ATTACH PARTITION fail_def_part DEFAULT; 2025-11-30 18:45:26.612 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "part_2" is violated by some row 2025-11-30 18:45:26.612 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 ATTACH PARTITION part_2 FOR VALUES IN (2); 2025-11-30 18:45:26.614 UTC client backend[46616] isolation/lock-update-traversal/control connection LOG: disconnection: session time: 0:00:00.047 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.614 UTC client backend[46618] isolation/lock-update-traversal/s2 LOG: disconnection: session time: 0:00:00.042 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.614 UTC client backend[46617] isolation/lock-update-traversal/s1 LOG: disconnection: session time: 0:00:00.044 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.617 UTC client backend[46566] pg_regress/alter_table ERROR: updated partition constraint for default partition "list_parted2_def" would be violated by some row 2025-11-30 18:45:26.617 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 ATTACH PARTITION part_3 FOR VALUES IN (11); 2025-11-30 18:45:26.619 UTC unrecognized[46621] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.619 UTC client backend[46621] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.619 UTC client backend[46621] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/inherit-temp 2025-11-30 18:45:26.620 UTC client backend[46621] isolation/inherit-temp LOG: connection ready: setup total=1.705 ms, fork=0.280 ms, authentication=0.110 ms 2025-11-30 18:45:26.622 UTC unrecognized[46622] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.622 UTC client backend[46622] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.622 UTC client backend[46622] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/inherit-temp 2025-11-30 18:45:26.623 UTC client backend[46622] isolation/inherit-temp LOG: connection ready: setup total=1.955 ms, fork=0.537 ms, authentication=0.119 ms 2025-11-30 18:45:26.625 UTC unrecognized[46623] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.625 UTC client backend[46623] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.625 UTC client backend[46623] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/inherit-temp 2025-11-30 18:45:26.626 UTC client backend[46623] isolation/inherit-temp LOG: connection ready: setup total=1.681 ms, fork=0.427 ms, authentication=0.097 ms 2025-11-30 18:45:26.629 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "part1" is violated by some row 2025-11-30 18:45:26.629 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE range_parted ATTACH PARTITION part1 FOR VALUES FROM (1, 1) TO (1, 10); 2025-11-30 18:45:26.637 UTC client backend[46566] pg_regress/alter_table ERROR: partition "partr_def2" conflicts with existing default partition "partr_def1" at character 54 2025-11-30 18:45:26.637 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE range_parted ATTACH PARTITION partr_def2 DEFAULT; 2025-11-30 18:45:26.639 UTC client backend[46566] pg_regress/alter_table ERROR: updated partition constraint for default partition "partr_def1" would be violated by some row 2025-11-30 18:45:26.639 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE range_parted ATTACH partition part3 FOR VALUES FROM (2, 10) TO (2, 20); 2025-11-30 18:45:26.643 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "part_5_a" is violated by some row 2025-11-30 18:45:26.643 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 ATTACH PARTITION part_5 FOR VALUES IN (5); 2025-11-30 18:45:26.662 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "part_7_a_null" is violated by some row 2025-11-30 18:45:26.662 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 ATTACH PARTITION part_7 FOR VALUES IN (7); 2025-11-30 18:45:26.670 UTC client backend[46566] pg_regress/alter_table ERROR: updated partition constraint for default partition "part5_def_p1" would be violated by some row 2025-11-30 18:45:26.670 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_5 ATTACH PARTITION part5_p1 FOR VALUES IN ('y'); 2025-11-30 18:45:26.672 UTC client backend[46566] pg_regress/alter_table ERROR: "part_2" is already a partition 2025-11-30 18:45:26.672 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 ATTACH PARTITION part_2 FOR VALUES IN (2); 2025-11-30 18:45:26.672 UTC client backend[46566] pg_regress/alter_table ERROR: circular inheritance not allowed 2025-11-30 18:45:26.672 UTC client backend[46566] pg_regress/alter_table DETAIL: "part_5" is already a child of "list_parted2". 2025-11-30 18:45:26.672 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_5 ATTACH PARTITION list_parted2 FOR VALUES IN ('b'); 2025-11-30 18:45:26.673 UTC client backend[46566] pg_regress/alter_table ERROR: circular inheritance not allowed 2025-11-30 18:45:26.673 UTC client backend[46566] pg_regress/alter_table DETAIL: "list_parted2" is already a child of "list_parted2". 2025-11-30 18:45:26.673 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 ATTACH PARTITION list_parted2 FOR VALUES IN (0); 2025-11-30 18:45:26.696 UTC client backend[46621] isolation/inherit-temp/control connection LOG: disconnection: session time: 0:00:00.076 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.696 UTC client backend[46622] isolation/inherit-temp/s1 LOG: disconnection: session time: 0:00:00.074 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.696 UTC client backend[46623] isolation/inherit-temp/s2 LOG: disconnection: session time: 0:00:00.071 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.698 UTC client backend[46566] pg_regress/alter_table ERROR: partition "fail_part" would overlap partition "hpart_1" at character 63 2025-11-30 18:45:26.698 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 4); 2025-11-30 18:45:26.698 UTC client backend[46566] pg_regress/alter_table ERROR: partition "fail_part" would overlap partition "hpart_1" at character 63 2025-11-30 18:45:26.698 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 0); 2025-11-30 18:45:26.701 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "hpart_2" is violated by some row 2025-11-30 18:45:26.701 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted ATTACH PARTITION hpart_2 FOR VALUES WITH (MODULUS 4, REMAINDER 1); 2025-11-30 18:45:26.701 UTC unrecognized[46626] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.702 UTC client backend[46626] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.702 UTC client backend[46626] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/temp-schema-cleanup 2025-11-30 18:45:26.703 UTC client backend[46626] isolation/temp-schema-cleanup LOG: connection ready: setup total=1.764 ms, fork=0.313 ms, authentication=0.111 ms 2025-11-30 18:45:26.704 UTC unrecognized[46627] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.704 UTC client backend[46627] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.704 UTC client backend[46627] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/temp-schema-cleanup 2025-11-30 18:45:26.705 UTC client backend[46627] isolation/temp-schema-cleanup LOG: connection ready: setup total=1.631 ms, fork=0.290 ms, authentication=0.103 ms 2025-11-30 18:45:26.705 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "hpart_5_a" is violated by some row 2025-11-30 18:45:26.705 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted ATTACH PARTITION hpart_5 FOR VALUES WITH (MODULUS 4, REMAINDER 2); 2025-11-30 18:45:26.706 UTC unrecognized[46628] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.707 UTC client backend[46628] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.707 UTC client backend[46628] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/temp-schema-cleanup 2025-11-30 18:45:26.707 UTC client backend[46628] isolation/temp-schema-cleanup LOG: connection ready: setup total=1.585 ms, fork=0.289 ms, authentication=0.099 ms 2025-11-30 18:45:26.708 UTC client backend[46566] pg_regress/alter_table ERROR: modulus for hash partition must be an integer value greater than zero 2025-11-30 18:45:26.708 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 0, REMAINDER 1); 2025-11-30 18:45:26.708 UTC client backend[46566] pg_regress/alter_table ERROR: remainder for hash partition must be less than modulus 2025-11-30 18:45:26.708 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 8); 2025-11-30 18:45:26.708 UTC client backend[46566] pg_regress/alter_table ERROR: every hash partition modulus must be a factor of the next larger modulus 2025-11-30 18:45:26.708 UTC client backend[46566] pg_regress/alter_table DETAIL: The new modulus 3 is not a factor of 4, the modulus of existing partition "hpart_1". 2025-11-30 18:45:26.708 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 3, REMAINDER 2); 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER action DETACH PARTITION cannot be performed on relation "regular_table" 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table DETAIL: This operation is not supported for tables. 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE regular_table DETACH PARTITION any_name; 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER action DETACH PARTITION cannot be performed on relation "regular_table" 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table DETAIL: This operation is not supported for tables. 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE regular_table DETACH PARTITION any_name CONCURRENTLY; 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER action DETACH PARTITION ... FINALIZE cannot be performed on relation "regular_table" 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table DETAIL: This operation is not supported for tables. 2025-11-30 18:45:26.710 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE regular_table DETACH PARTITION any_name FINALIZE; 2025-11-30 18:45:26.711 UTC client backend[46566] pg_regress/alter_table ERROR: relation "part_4" does not exist 2025-11-30 18:45:26.711 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 DETACH PARTITION part_4; 2025-11-30 18:45:26.711 UTC client backend[46566] pg_regress/alter_table ERROR: relation "hpart_4" does not exist 2025-11-30 18:45:26.711 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted DETACH PARTITION hpart_4; 2025-11-30 18:45:26.712 UTC client backend[46566] pg_regress/alter_table ERROR: relation "not_a_part" is not a partition of relation "list_parted2" 2025-11-30 18:45:26.712 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 DETACH PARTITION not_a_part; 2025-11-30 18:45:26.712 UTC client backend[46566] pg_regress/alter_table ERROR: relation "part_1" is not a partition of relation "list_parted2" 2025-11-30 18:45:26.712 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 DETACH PARTITION part_1; 2025-11-30 18:45:26.712 UTC client backend[46566] pg_regress/alter_table ERROR: relation "not_a_part" is not a partition of relation "hash_parted" 2025-11-30 18:45:26.712 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE hash_parted DETACH PARTITION not_a_part; 2025-11-30 18:45:26.723 UTC client backend[46566] pg_regress/alter_table ERROR: ALTER TABLE ... DETACH CONCURRENTLY cannot run inside a transaction block 2025-11-30 18:45:26.723 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE range_parted2 DETACH PARTITION part_rp CONCURRENTLY; 2025-11-30 18:45:26.725 UTC client backend[46566] pg_regress/alter_table ERROR: cannot detach partitions concurrently when a default partition exists 2025-11-30 18:45:26.725 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE range_parted2 DETACH PARTITION part_rp CONCURRENTLY; 2025-11-30 18:45:26.725 UTC client backend[46566] pg_regress/alter_table ERROR: cannot detach partitions concurrently when a default partition exists 2025-11-30 18:45:26.725 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE range_parted2 DETACH PARTITION part_rpd CONCURRENTLY; 2025-11-30 18:45:26.743 UTC client backend[46566] pg_regress/alter_table ERROR: column must be added to child tables too 2025-11-30 18:45:26.743 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE ONLY list_parted2 ADD COLUMN c int; 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop column from only the partitioned table when partitions exist 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table HINT: Do not specify the ONLY keyword. 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE ONLY list_parted2 DROP COLUMN b; 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table ERROR: cannot add column to a partition 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_2 ADD COLUMN c text; 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited column "b" 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_2 DROP COLUMN b; 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table ERROR: cannot rename inherited column "b" 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_2 RENAME COLUMN b to c; 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter inherited column "b" at character 33 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_2 ALTER COLUMN b TYPE text; 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table ERROR: constraint must be added to child tables too 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table HINT: Do not specify the ONLY keyword. 2025-11-30 18:45:26.744 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE ONLY list_parted2 ALTER b SET NOT NULL; 2025-11-30 18:45:26.745 UTC client backend[46566] pg_regress/alter_table ERROR: constraint must be added to child tables too 2025-11-30 18:45:26.745 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE ONLY list_parted2 ADD CONSTRAINT check_b CHECK (b <> 'zz'); 2025-11-30 18:45:26.755 UTC client backend[46627] isolation/temp-schema-cleanup/s1 FATAL: terminating connection due to administrator command 2025-11-30 18:45:26.755 UTC client backend[46627] isolation/temp-schema-cleanup/s1 STATEMENT: SELECT pg_terminate_backend(pg_backend_pid()); 2025-11-30 18:45:26.757 UTC client backend[46627] isolation/temp-schema-cleanup/s1 LOG: disconnection: session time: 0:00:00.053 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.761 UTC client backend[46626] isolation/temp-schema-cleanup/control connection LOG: disconnection: session time: 0:00:00.059 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.761 UTC client backend[46628] isolation/temp-schema-cleanup/s2 LOG: disconnection: session time: 0:00:00.054 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.765 UTC unrecognized[46631] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.766 UTC client backend[46631] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.766 UTC client backend[46631] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-nothing 2025-11-30 18:45:26.767 UTC client backend[46631] isolation/insert-conflict-do-nothing LOG: connection ready: setup total=1.749 ms, fork=0.296 ms, authentication=0.113 ms 2025-11-30 18:45:26.768 UTC unrecognized[46632] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.768 UTC client backend[46632] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.768 UTC client backend[46632] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-nothing 2025-11-30 18:45:26.769 UTC client backend[46632] isolation/insert-conflict-do-nothing LOG: connection ready: setup total=1.529 ms, fork=0.290 ms, authentication=0.095 ms 2025-11-30 18:45:26.770 UTC unrecognized[46633] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.770 UTC client backend[46633] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.770 UTC client backend[46633] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-nothing 2025-11-30 18:45:26.771 UTC client backend[46633] isolation/insert-conflict-do-nothing LOG: connection ready: setup total=1.589 ms, fork=0.308 ms, authentication=0.097 ms 2025-11-30 18:45:26.780 UTC client backend[46566] pg_regress/alter_table ERROR: column "b" is marked NOT NULL in parent table 2025-11-30 18:45:26.780 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_2 ALTER b DROP NOT NULL; 2025-11-30 18:45:26.780 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop inherited constraint "check_a2" of relation "part_2" 2025-11-30 18:45:26.780 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_2 DROP CONSTRAINT check_a2; 2025-11-30 18:45:26.784 UTC client backend[46566] pg_regress/alter_table ERROR: column "a" is in a primary key 2025-11-30 18:45:26.784 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE ONLY list_parted3 DROP CONSTRAINT list_parted3_a_not_null; 2025-11-30 18:45:26.785 UTC client backend[46566] pg_regress/alter_table ERROR: cannot add NO INHERIT constraint to partitioned table "list_parted2" 2025-11-30 18:45:26.785 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 add constraint check_b2 check (b <> 'zz') NO INHERIT; 2025-11-30 18:45:26.785 UTC client backend[46566] pg_regress/alter_table ERROR: cannot inherit from partition "part_2" 2025-11-30 18:45:26.785 UTC client backend[46566] pg_regress/alter_table STATEMENT: CREATE TABLE inh_test () INHERITS (part_2); 2025-11-30 18:45:26.786 UTC client backend[46566] pg_regress/alter_table ERROR: cannot inherit from a partition 2025-11-30 18:45:26.786 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE inh_test INHERIT part_2; 2025-11-30 18:45:26.786 UTC client backend[46566] pg_regress/alter_table ERROR: cannot change inheritance of a partition 2025-11-30 18:45:26.786 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE part_2 INHERIT inh_test; 2025-11-30 18:45:26.787 UTC client backend[46566] pg_regress/alter_table ERROR: cannot drop column "b" because it is part of the partition key of relation "part_5" 2025-11-30 18:45:26.787 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 DROP COLUMN b; 2025-11-30 18:45:26.787 UTC client backend[46566] 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-11-30 18:45:26.787 UTC client backend[46566] pg_regress/alter_table STATEMENT: ALTER TABLE list_parted2 ALTER COLUMN b TYPE text; 2025-11-30 18:45:26.807 UTC client backend[46631] isolation/insert-conflict-do-nothing/control connection LOG: disconnection: session time: 0:00:00.042 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.807 UTC client backend[46632] isolation/insert-conflict-do-nothing/s1 LOG: disconnection: session time: 0:00:00.039 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.807 UTC client backend[46633] isolation/insert-conflict-do-nothing/s2 LOG: disconnection: session time: 0:00:00.037 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.813 UTC unrecognized[46636] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.813 UTC client backend[46636] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.813 UTC client backend[46636] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-nothing-2 2025-11-30 18:45:26.814 UTC client backend[46636] isolation/insert-conflict-do-nothing-2 LOG: connection ready: setup total=1.727 ms, fork=0.305 ms, authentication=0.110 ms 2025-11-30 18:45:26.815 UTC unrecognized[46637] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.815 UTC client backend[46637] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.815 UTC client backend[46637] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-nothing-2 2025-11-30 18:45:26.816 UTC client backend[46637] isolation/insert-conflict-do-nothing-2 LOG: connection ready: setup total=1.563 ms, fork=0.297 ms, authentication=0.099 ms 2025-11-30 18:45:26.817 UTC unrecognized[46638] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.818 UTC client backend[46638] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.818 UTC client backend[46638] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-nothing-2 2025-11-30 18:45:26.819 UTC client backend[46638] isolation/insert-conflict-do-nothing-2 LOG: connection ready: setup total=1.560 ms, fork=0.302 ms, authentication=0.106 ms 2025-11-30 18:45:26.827 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "p11" is violated by some row 2025-11-30 18:45:26.827 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table p attach partition p1 for values from (1, 2) to (1, 10); 2025-11-30 18:45:26.843 UTC client backend[46566] pg_regress/alter_table ERROR: partition constraint of relation "defpart_attach_test_d" is violated by some row 2025-11-30 18:45:26.843 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table defpart_attach_test attach partition defpart_attach_test_d default; 2025-11-30 18:45:26.847 UTC client backend[46566] pg_regress/alter_table ERROR: updated partition constraint for default partition "defpart_attach_test_d" would be violated by some row 2025-11-30 18:45:26.847 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table defpart_attach_test attach partition defpart_attach_test_2 for values in (2); 2025-11-30 18:45:26.848 UTC client backend[46638] isolation/insert-conflict-do-nothing-2/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:26.848 UTC client backend[46638] isolation/insert-conflict-do-nothing-2/s2 STATEMENT: INSERT INTO ints(key, val) VALUES(1, 'donothing2'), (1, 'donothing3') ON CONFLICT DO NOTHING; 2025-11-30 18:45:26.852 UTC client backend[46566] pg_regress/alter_table ERROR: cannot attach a permanent relation as partition of temporary relation "temp_part_parent" 2025-11-30 18:45:26.852 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table temp_part_parent attach partition perm_part_child default; 2025-11-30 18:45:26.853 UTC client backend[46566] pg_regress/alter_table ERROR: cannot attach a temporary relation as partition of permanent relation "perm_part_parent" 2025-11-30 18:45:26.853 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table perm_part_parent attach partition temp_part_child default; 2025-11-30 18:45:26.859 UTC client backend[46566] pg_regress/alter_table ERROR: cannot ALTER TABLE "tab_part_attach" because it is being used by active queries in this session 2025-11-30 18:45:26.859 UTC client backend[46566] 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-11-30 18:45:26.859 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into tab_part_attach values (1); 2025-11-30 18:45:26.864 UTC client backend[46637] isolation/insert-conflict-do-nothing-2/s1 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:26.864 UTC client backend[46637] isolation/insert-conflict-do-nothing-2/s1 STATEMENT: INSERT INTO ints(key, val) VALUES(1, 'donothing1') ON CONFLICT DO NOTHING; 2025-11-30 18:45:26.892 UTC client backend[46638] isolation/insert-conflict-do-nothing-2/s2 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:26.892 UTC client backend[46638] isolation/insert-conflict-do-nothing-2/s2 STATEMENT: INSERT INTO ints(key, val) VALUES(1, 'donothing2'), (1, 'donothing3') ON CONFLICT DO NOTHING; 2025-11-30 18:45:26.908 UTC client backend[46637] isolation/insert-conflict-do-nothing-2/s1 ERROR: could not serialize access due to concurrent update 2025-11-30 18:45:26.908 UTC client backend[46637] isolation/insert-conflict-do-nothing-2/s1 STATEMENT: INSERT INTO ints(key, val) VALUES(1, 'donothing1') ON CONFLICT DO NOTHING; 2025-11-30 18:45:26.911 UTC client backend[46636] isolation/insert-conflict-do-nothing-2/control connection LOG: disconnection: session time: 0:00:00.098 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.911 UTC client backend[46637] isolation/insert-conflict-do-nothing-2/s1 LOG: disconnection: session time: 0:00:00.095 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.911 UTC client backend[46638] isolation/insert-conflict-do-nothing-2/s2 LOG: disconnection: session time: 0:00:00.093 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.916 UTC unrecognized[46641] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.916 UTC client backend[46641] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.917 UTC client backend[46641] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update 2025-11-30 18:45:26.918 UTC client backend[46641] isolation/insert-conflict-do-update LOG: connection ready: setup total=2.178 ms, fork=0.454 ms, authentication=0.153 ms 2025-11-30 18:45:26.919 UTC unrecognized[46642] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.919 UTC client backend[46642] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.919 UTC client backend[46642] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update 2025-11-30 18:45:26.920 UTC client backend[46642] isolation/insert-conflict-do-update LOG: connection ready: setup total=1.839 ms, fork=0.353 ms, authentication=0.121 ms 2025-11-30 18:45:26.922 UTC unrecognized[46643] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.922 UTC client backend[46643] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.922 UTC client backend[46643] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update 2025-11-30 18:45:26.923 UTC client backend[46643] isolation/insert-conflict-do-update LOG: connection ready: setup total=1.601 ms, fork=0.318 ms, authentication=0.104 ms 2025-11-30 18:45:26.924 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter table "attbl" because column "atref.b" uses its row type 2025-11-30 18:45:26.924 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table attbl alter column a type numeric; 2025-11-30 18:45:26.927 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter table "attbl" because column "atref.b" uses its row type 2025-11-30 18:45:26.927 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table attbl alter column a type numeric; 2025-11-30 18:45:26.930 UTC client backend[46566] pg_regress/alter_table ERROR: cannot alter table "attbl" because column "atref.b" uses its row type 2025-11-30 18:45:26.930 UTC client backend[46566] pg_regress/alter_table STATEMENT: alter table attbl alter column a type numeric; 2025-11-30 18:45:26.955 UTC client backend[46566] pg_regress/alter_table ERROR: new row for relation "attach_parted_part1" violates partition constraint 2025-11-30 18:45:26.955 UTC client backend[46566] pg_regress/alter_table DETAIL: Failing row contains (2, 1). 2025-11-30 18:45:26.955 UTC client backend[46566] pg_regress/alter_table STATEMENT: insert into attach_parted_part1 values (2, 1); 2025-11-30 18:45:26.959 UTC client backend[46566] pg_regress/alter_table WARNING: "wal_level" is insufficient to publish logical changes 2025-11-30 18:45:26.959 UTC client backend[46566] pg_regress/alter_table HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-11-30 18:45:26.960 UTC client backend[46641] isolation/insert-conflict-do-update/control connection LOG: disconnection: session time: 0:00:00.044 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.960 UTC client backend[46642] isolation/insert-conflict-do-update/s1 LOG: disconnection: session time: 0:00:00.040 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.960 UTC client backend[46643] isolation/insert-conflict-do-update/s2 LOG: disconnection: session time: 0:00:00.038 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:26.966 UTC unrecognized[46646] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.967 UTC client backend[46646] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.967 UTC client backend[46646] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update-2 2025-11-30 18:45:26.968 UTC client backend[46646] isolation/insert-conflict-do-update-2 LOG: connection ready: setup total=2.123 ms, fork=0.507 ms, authentication=0.155 ms 2025-11-30 18:45:26.969 UTC unrecognized[46647] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.969 UTC client backend[46647] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.969 UTC client backend[46647] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update-2 2025-11-30 18:45:26.970 UTC client backend[46647] isolation/insert-conflict-do-update-2 LOG: connection ready: setup total=1.584 ms, fork=0.323 ms, authentication=0.104 ms 2025-11-30 18:45:26.972 UTC unrecognized[46648] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:26.972 UTC client backend[46648] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:26.972 UTC client backend[46648] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update-2 2025-11-30 18:45:26.973 UTC client backend[46648] isolation/insert-conflict-do-update-2 LOG: connection ready: setup total=2.067 ms, fork=0.340 ms, authentication=0.157 ms 2025-11-30 18:45:26.982 UTC client backend[46566] pg_regress/alter_table LOG: disconnection: session time: 0:00:02.696 user=postgres database=regression host=[local] 2025-11-30 18:45:27.002 UTC unrecognized[46683] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.003 UTC client backend[46683] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.003 UTC client backend[46683] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/partition_prune 2025-11-30 18:45:27.004 UTC client backend[46683] pg_regress/partition_prune LOG: connection ready: setup total=9.635 ms, fork=7.215 ms, authentication=0.135 ms 2025-11-30 18:45:27.006 UTC unrecognized[46685] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.006 UTC unrecognized[46684] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.006 UTC client backend[46685] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.006 UTC client backend[46685] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/partition_aggregate 2025-11-30 18:45:27.006 UTC client backend[46684] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.006 UTC client backend[46684] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/partition_join 2025-11-30 18:45:27.007 UTC client backend[46685] pg_regress/partition_aggregate LOG: connection ready: setup total=10.499 ms, fork=8.321 ms, authentication=0.164 ms 2025-11-30 18:45:27.007 UTC client backend[46684] pg_regress/partition_join LOG: connection ready: setup total=11.284 ms, fork=8.292 ms, authentication=0.113 ms 2025-11-30 18:45:27.008 UTC unrecognized[46688] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.008 UTC unrecognized[46689] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.008 UTC unrecognized[46694] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.008 UTC unrecognized[46696] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.008 UTC unrecognized[46687] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.008 UTC client backend[46689] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.008 UTC client backend[46689] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/compression 2025-11-30 18:45:27.009 UTC client backend[46687] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.009 UTC client backend[46687] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/partition_info 2025-11-30 18:45:27.009 UTC client backend[46689] pg_regress/compression LOG: connection ready: setup total=9.290 ms, fork=5.239 ms, authentication=0.112 ms 2025-11-30 18:45:27.009 UTC unrecognized[46695] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.009 UTC client backend[46687] pg_regress/partition_info LOG: connection ready: setup total=10.293 ms, fork=5.564 ms, authentication=0.110 ms 2025-11-30 18:45:27.010 UTC client backend[46695] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.010 UTC client backend[46695] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/memoize 2025-11-30 18:45:27.010 UTC unrecognized[46686] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.010 UTC client backend[46688] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.010 UTC client backend[46688] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/compression_lz4 2025-11-30 18:45:27.010 UTC client backend[46686] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.010 UTC client backend[46686] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tuplesort 2025-11-30 18:45:27.011 UTC unrecognized[46693] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.011 UTC client backend[46695] pg_regress/memoize LOG: connection ready: setup total=5.254 ms, fork=3.488 ms, authentication=0.147 ms 2025-11-30 18:45:27.011 UTC client backend[46688] pg_regress/compression_lz4 LOG: connection ready: setup total=11.174 ms, fork=2.309 ms, authentication=0.148 ms 2025-11-30 18:45:27.011 UTC client backend[46693] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.011 UTC client backend[46693] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/hash_part 2025-11-30 18:45:27.011 UTC client backend[46686] pg_regress/tuplesort LOG: connection ready: setup total=14.098 ms, fork=10.887 ms, authentication=0.123 ms 2025-11-30 18:45:27.012 UTC client backend[46694] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.012 UTC client backend[46694] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/numa 2025-11-30 18:45:27.012 UTC client backend[46693] pg_regress/hash_part LOG: connection ready: setup total=7.256 ms, fork=4.949 ms, authentication=0.109 ms 2025-11-30 18:45:27.013 UTC client backend[46696] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.013 UTC client backend[46696] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats 2025-11-30 18:45:27.013 UTC client backend[46694] pg_regress/numa LOG: connection ready: setup total=7.142 ms, fork=2.512 ms, authentication=0.113 ms 2025-11-30 18:45:27.013 UTC unrecognized[46690] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.013 UTC client backend[46690] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.013 UTC client backend[46690] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/explain 2025-11-30 18:45:27.014 UTC client backend[46696] pg_regress/stats LOG: connection ready: setup total=6.649 ms, fork=1.131 ms, authentication=0.135 ms 2025-11-30 18:45:27.014 UTC client backend[46690] pg_regress/explain LOG: connection ready: setup total=13.262 ms, fork=7.464 ms, authentication=0.119 ms 2025-11-30 18:45:27.014 UTC unrecognized[46692] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.015 UTC client backend[46692] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.015 UTC client backend[46692] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/reloptions 2025-11-30 18:45:27.015 UTC unrecognized[46697] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.016 UTC client backend[46692] pg_regress/reloptions LOG: connection ready: setup total=11.283 ms, fork=5.571 ms, authentication=0.114 ms 2025-11-30 18:45:27.016 UTC client backend[46697] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.016 UTC client backend[46697] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/eager_aggregate 2025-11-30 18:45:27.016 UTC unrecognized[46691] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.017 UTC client backend[46691] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.017 UTC client backend[46691] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/indexing 2025-11-30 18:45:27.017 UTC client backend[46697] pg_regress/eager_aggregate LOG: connection ready: setup total=9.159 ms, fork=3.678 ms, authentication=0.110 ms 2025-11-30 18:45:27.017 UTC unrecognized[46698] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.017 UTC client backend[46698] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.017 UTC client backend[46698] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/predicate 2025-11-30 18:45:27.018 UTC client backend[46691] pg_regress/indexing LOG: connection ready: setup total=13.545 ms, fork=8.058 ms, authentication=0.132 ms 2025-11-30 18:45:27.018 UTC client backend[46694] pg_regress/numa ERROR: libnuma initialization failed or NUMA is not supported on this platform 2025-11-30 18:45:27.018 UTC client backend[46694] pg_regress/numa STATEMENT: SELECT COUNT(*) = 0 AS ok FROM pg_shmem_allocations_numa; 2025-11-30 18:45:27.018 UTC client backend[46698] pg_regress/predicate LOG: connection ready: setup total=8.998 ms, fork=2.497 ms, authentication=0.123 ms 2025-11-30 18:45:27.029 UTC client backend[46694] pg_regress/numa LOG: disconnection: session time: 0:00:00.021 user=postgres database=regression host=[local] 2025-11-30 18:45:27.030 UTC client backend[46693] pg_regress/hash_part ERROR: could not open relation with OID 0 2025-11-30 18:45:27.030 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition(0, 4, 0, NULL); 2025-11-30 18:45:27.030 UTC client backend[46692] pg_regress/reloptions ERROR: value 2 out of bounds for option "fillfactor" 2025-11-30 18:45:27.030 UTC client backend[46692] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:27.030 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=2); 2025-11-30 18:45:27.034 UTC client backend[46693] pg_regress/hash_part ERROR: "tenk1" is not a hash partitioned table 2025-11-30 18:45:27.034 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('tenk1'::regclass, 4, 0, NULL); 2025-11-30 18:45:27.034 UTC client backend[46692] pg_regress/reloptions ERROR: value 110 out of bounds for option "fillfactor" 2025-11-30 18:45:27.034 UTC client backend[46692] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:27.034 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=110); 2025-11-30 18:45:27.042 UTC client backend[46693] pg_regress/hash_part ERROR: "mchash1" is not a hash partitioned table 2025-11-30 18:45:27.042 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash1'::regclass, 4, 0, NULL); 2025-11-30 18:45:27.042 UTC client backend[46692] pg_regress/reloptions ERROR: value -10.0 out of bounds for option "autovacuum_analyze_scale_factor" 2025-11-30 18:45:27.042 UTC client backend[46692] pg_regress/reloptions DETAIL: Valid values are between "0.000000" and "100.000000". 2025-11-30 18:45:27.042 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = -10.0); 2025-11-30 18:45:27.047 UTC client backend[46646] isolation/insert-conflict-do-update-2/control connection LOG: disconnection: session time: 0:00:00.081 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:27.052 UTC client backend[46647] isolation/insert-conflict-do-update-2/s1 LOG: disconnection: session time: 0:00:00.082 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:27.055 UTC client backend[46693] pg_regress/hash_part ERROR: modulus for hash partition must be an integer value greater than zero 2025-11-30 18:45:27.055 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 0, 0, NULL); 2025-11-30 18:45:27.055 UTC client backend[46692] pg_regress/reloptions ERROR: value 110.0 out of bounds for option "autovacuum_analyze_scale_factor" 2025-11-30 18:45:27.055 UTC client backend[46692] pg_regress/reloptions DETAIL: Valid values are between "0.000000" and "100.000000". 2025-11-30 18:45:27.055 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = 110.0); 2025-11-30 18:45:27.056 UTC client backend[46648] isolation/insert-conflict-do-update-2/s2 LOG: disconnection: session time: 0:00:00.084 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:27.070 UTC client backend[46693] pg_regress/hash_part ERROR: remainder for hash partition must be an integer value greater than or equal to zero 2025-11-30 18:45:27.070 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 1, -1, NULL); 2025-11-30 18:45:27.070 UTC client backend[46692] pg_regress/reloptions ERROR: unrecognized parameter "not_existing_option" 2025-11-30 18:45:27.070 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (not_existing_option=2); 2025-11-30 18:45:27.078 UTC client backend[46693] pg_regress/hash_part ERROR: remainder for hash partition must be less than modulus 2025-11-30 18:45:27.078 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 1, 1, NULL); 2025-11-30 18:45:27.078 UTC client backend[46692] pg_regress/reloptions ERROR: unrecognized parameter namespace "not_existing_namespace" 2025-11-30 18:45:27.078 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (not_existing_namespace.fillfactor=2); 2025-11-30 18:45:27.081 UTC client backend[46692] pg_regress/reloptions ERROR: value -30.1 out of bounds for option "fillfactor" 2025-11-30 18:45:27.081 UTC client backend[46692] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:27.081 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=-30.1); 2025-11-30 18:45:27.083 UTC client backend[46693] pg_regress/hash_part ERROR: number of partitioning columns (2) does not match number of partition keys provided (3) 2025-11-30 18:45:27.083 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 4, 0, NULL::int, NULL::text, NULL::json); 2025-11-30 18:45:27.083 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for integer option "fillfactor": string 2025-11-30 18:45:27.083 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor='string'); 2025-11-30 18:45:27.085 UTC client backend[46693] pg_regress/hash_part ERROR: number of partitioning columns (2) does not match number of partition keys provided (1) 2025-11-30 18:45:27.085 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 3, 1, NULL::int); 2025-11-30 18:45:27.085 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for integer option "fillfactor": true 2025-11-30 18:45:27.085 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=true); 2025-11-30 18:45:27.087 UTC client backend[46693] pg_regress/hash_part ERROR: column 2 of the partition key has type text, but supplied value is of type integer 2025-11-30 18:45:27.087 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, NULL::int, NULL::int); 2025-11-30 18:45:27.087 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for boolean option "autovacuum_enabled": 12 2025-11-30 18:45:27.087 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=12); 2025-11-30 18:45:27.089 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for boolean option "autovacuum_enabled": 30.5 2025-11-30 18:45:27.089 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=30.5); 2025-11-30 18:45:27.094 UTC client backend[46693] pg_regress/hash_part ERROR: column 2 of the partition key has type "text", but supplied value is of type "integer" 2025-11-30 18:45:27.094 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, variadic array[1,2]::int[]); 2025-11-30 18:45:27.094 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for boolean option "autovacuum_enabled": string 2025-11-30 18:45:27.094 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled='string'); 2025-11-30 18:45:27.098 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for floating point option "autovacuum_analyze_scale_factor": string 2025-11-30 18:45:27.098 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor='string'); 2025-11-30 18:45:27.102 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for floating point option "autovacuum_analyze_scale_factor": true 2025-11-30 18:45:27.102 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor=true); 2025-11-30 18:45:27.106 UTC client backend[46692] pg_regress/reloptions ERROR: parameter "fillfactor" specified more than once 2025-11-30 18:45:27.106 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=30, fillfactor=40); 2025-11-30 18:45:27.108 UTC client backend[46690] pg_regress/explain ERROR: EXPLAIN options ANALYZE and GENERIC_PLAN cannot be used together 2025-11-30 18:45:27.108 UTC client backend[46690] pg_regress/explain CONTEXT: PL/pgSQL function explain_filter(text) line 5 at FOR over EXECUTE statement 2025-11-30 18:45:27.108 UTC client backend[46690] pg_regress/explain STATEMENT: select explain_filter('explain (analyze, generic_plan) select unique1 from tenk1 where thousand = $1'); 2025-11-30 18:45:27.114 UTC client backend[46692] pg_regress/reloptions ERROR: invalid value for integer option "fillfactor": true 2025-11-30 18:45:27.114 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor); 2025-11-30 18:45:27.126 UTC client backend[46693] pg_regress/hash_part ERROR: number of partitioning columns (2) does not match number of partition keys provided (0) 2025-11-30 18:45:27.126 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0, variadic array[]::int[]); 2025-11-30 18:45:27.131 UTC client backend[46693] 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-11-30 18:45:27.131 UTC client backend[46693] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0, variadic array[now(), now()]); 2025-11-30 18:45:27.153 UTC client backend[46692] pg_regress/reloptions ERROR: RESET must not include values for parameters 2025-11-30 18:45:27.153 UTC client backend[46692] pg_regress/reloptions STATEMENT: ALTER TABLE reloptions_test RESET (fillfactor=12); 2025-11-30 18:45:27.156 UTC unrecognized[46703] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.156 UTC client backend[46703] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.156 UTC client backend[46703] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update-3 2025-11-30 18:45:27.159 UTC client backend[46703] isolation/insert-conflict-do-update-3 LOG: connection ready: setup total=6.661 ms, fork=2.064 ms, authentication=0.133 ms 2025-11-30 18:45:27.168 UTC unrecognized[46704] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.168 UTC client backend[46704] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.168 UTC client backend[46704] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update-3 2025-11-30 18:45:27.169 UTC client backend[46704] isolation/insert-conflict-do-update-3 LOG: connection ready: setup total=9.039 ms, fork=2.298 ms, authentication=0.143 ms 2025-11-30 18:45:27.169 UTC client backend[46693] pg_regress/hash_part LOG: disconnection: session time: 0:00:00.159 user=postgres database=regression host=[local] 2025-11-30 18:45:27.178 UTC client backend[46692] pg_regress/reloptions ERROR: null value in column "i" of relation "reloptions_test" violates not-null constraint 2025-11-30 18:45:27.178 UTC client backend[46692] pg_regress/reloptions DETAIL: Failing row contains (null, null). 2025-11-30 18:45:27.178 UTC client backend[46692] pg_regress/reloptions STATEMENT: INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL); 2025-11-30 18:45:27.184 UTC unrecognized[46705] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.184 UTC client backend[46705] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.184 UTC client backend[46705] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-do-update-3 2025-11-30 18:45:27.185 UTC client backend[46705] isolation/insert-conflict-do-update-3 LOG: connection ready: setup total=11.314 ms, fork=6.881 ms, authentication=0.114 ms 2025-11-30 18:45:27.191 UTC client backend[46691] pg_regress/indexing ERROR: cannot create index on partitioned table "idxpart" concurrently 2025-11-30 18:45:27.191 UTC client backend[46691] pg_regress/indexing STATEMENT: create index concurrently on idxpart (a); 2025-11-30 18:45:27.194 UTC client backend[46692] pg_regress/reloptions ERROR: null value in column "i" of relation "reloptions_test" violates not-null constraint 2025-11-30 18:45:27.194 UTC client backend[46692] pg_regress/reloptions DETAIL: Failing row contains (null, null). 2025-11-30 18:45:27.194 UTC client backend[46692] pg_regress/reloptions STATEMENT: INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL); 2025-11-30 18:45:27.225 UTC client backend[46698] pg_regress/predicate LOG: disconnection: session time: 0:00:00.213 user=postgres database=regression host=[local] 2025-11-30 18:45:27.236 UTC client backend[46689] pg_regress/compression ERROR: column data type integer does not support compression 2025-11-30 18:45:27.236 UTC client backend[46689] pg_regress/compression STATEMENT: CREATE TABLE cmdata2 (f1 int COMPRESSION pglz); 2025-11-30 18:45:27.238 UTC client backend[46703] isolation/insert-conflict-do-update-3/control connection LOG: disconnection: session time: 0:00:00.083 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:27.240 UTC client backend[46704] isolation/insert-conflict-do-update-3/s1 LOG: disconnection: session time: 0:00:00.077 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:27.242 UTC client backend[46705] isolation/insert-conflict-do-update-3/s2 LOG: disconnection: session time: 0:00:00.061 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:27.263 UTC client backend[46692] pg_regress/reloptions ERROR: unrecognized parameter "not_existing_option" 2025-11-30 18:45:27.263 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2 (i int) WITH (toast.not_existing_option = 42); 2025-11-30 18:45:27.270 UTC client backend[46687] pg_regress/partition_info LOG: disconnection: session time: 0:00:00.265 user=postgres database=regression host=[local] 2025-11-30 18:45:27.280 UTC client backend[46692] pg_regress/reloptions ERROR: unrecognized parameter "not_existing_option" 2025-11-30 18:45:27.280 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx ON reloptions_test (s) WITH (not_existing_option=2); 2025-11-30 18:45:27.281 UTC unrecognized[46712] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.281 UTC client backend[46692] pg_regress/reloptions ERROR: unrecognized parameter namespace "not_existing_ns" 2025-11-30 18:45:27.281 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx ON reloptions_test (s) WITH (not_existing_ns.fillfactor=2); 2025-11-30 18:45:27.282 UTC client backend[46712] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.282 UTC client backend[46712] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-specconflict 2025-11-30 18:45:27.282 UTC client backend[46692] pg_regress/reloptions ERROR: value 1 out of bounds for option "fillfactor" 2025-11-30 18:45:27.282 UTC client backend[46692] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:27.282 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=1); 2025-11-30 18:45:27.283 UTC client backend[46712] isolation/insert-conflict-specconflict LOG: connection ready: setup total=4.642 ms, fork=2.006 ms, authentication=0.130 ms 2025-11-30 18:45:27.283 UTC client backend[46692] pg_regress/reloptions ERROR: value 130 out of bounds for option "fillfactor" 2025-11-30 18:45:27.283 UTC client backend[46692] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2025-11-30 18:45:27.283 UTC client backend[46692] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=130); 2025-11-30 18:45:27.295 UTC unrecognized[46713] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.295 UTC client backend[46713] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.295 UTC client backend[46713] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-specconflict 2025-11-30 18:45:27.296 UTC client backend[46713] isolation/insert-conflict-specconflict LOG: connection ready: setup total=5.933 ms, fork=3.069 ms, authentication=0.131 ms 2025-11-30 18:45:27.299 UTC client backend[46692] pg_regress/reloptions LOG: disconnection: session time: 0:00:00.289 user=postgres database=regression host=[local] 2025-11-30 18:45:27.302 UTC unrecognized[46714] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.303 UTC client backend[46714] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.303 UTC client backend[46714] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-specconflict 2025-11-30 18:45:27.304 UTC client backend[46714] isolation/insert-conflict-specconflict LOG: connection ready: setup total=5.748 ms, fork=2.507 ms, authentication=0.129 ms 2025-11-30 18:45:27.313 UTC unrecognized[46715] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.314 UTC client backend[46715] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.314 UTC client backend[46715] [unknown] LOG: connection authorized: user=postgres database=isolation_regression application_name=isolation/insert-conflict-specconflict 2025-11-30 18:45:27.315 UTC client backend[46715] isolation/insert-conflict-specconflict LOG: connection ready: setup total=8.812 ms, fork=5.618 ms, authentication=0.122 ms 2025-11-30 18:45:27.347 UTC client backend[46688] pg_regress/compression_lz4 ERROR: column "f1" has a compression method conflict 2025-11-30 18:45:27.347 UTC client backend[46688] pg_regress/compression_lz4 DETAIL: pglz versus lz4 2025-11-30 18:45:27.347 UTC client backend[46688] pg_regress/compression_lz4 STATEMENT: CREATE TABLE cminh() INHERITS(cmdata_pglz, cmdata_lz4); 2025-11-30 18:45:27.357 UTC client backend[46688] pg_regress/compression_lz4 ERROR: column "f1" has a compression method conflict 2025-11-30 18:45:27.357 UTC client backend[46688] pg_regress/compression_lz4 DETAIL: pglz versus lz4 2025-11-30 18:45:27.357 UTC client backend[46688] pg_regress/compression_lz4 STATEMENT: CREATE TABLE cminh(f1 TEXT COMPRESSION lz4) INHERITS(cmdata_pglz); 2025-11-30 18:45:27.394 UTC client backend[46688] pg_regress/compression_lz4 LOG: disconnection: session time: 0:00:00.391 user=postgres database=regression host=[local] 2025-11-30 18:45:27.402 UTC client backend[46695] pg_regress/memoize LOG: disconnection: session time: 0:00:00.393 user=postgres database=regression host=[local] 2025-11-30 18:45:27.436 UTC client backend[46691] pg_regress/indexing ERROR: "idxpart_c" is not a partitioned table 2025-11-30 18:45:27.436 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart_c attach partition idxpart1_c for values from (10) to (20); 2025-11-30 18:45:27.441 UTC client backend[46691] pg_regress/indexing ERROR: ALTER action DETACH PARTITION cannot be performed on relation "idxpart_c" 2025-11-30 18:45:27.441 UTC client backend[46691] pg_regress/indexing DETAIL: This operation is not supported for partitioned indexes. 2025-11-30 18:45:27.441 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart_c detach partition idxpart1_c; 2025-11-30 18:45:27.447 UTC client backend[46690] pg_regress/explain LOG: disconnection: session time: 0:00:00.438 user=postgres database=regression host=[local] 2025-11-30 18:45:27.534 UTC client backend[46689] pg_regress/compression ERROR: invalid value for parameter "default_toast_compression": "" 2025-11-30 18:45:27.534 UTC client backend[46689] pg_regress/compression HINT: Available values: pglz, lz4. 2025-11-30 18:45:27.534 UTC client backend[46689] pg_regress/compression STATEMENT: SET default_toast_compression = ''; 2025-11-30 18:45:27.534 UTC client backend[46689] pg_regress/compression ERROR: invalid value for parameter "default_toast_compression": "I do not exist compression" 2025-11-30 18:45:27.534 UTC client backend[46689] pg_regress/compression HINT: Available values: pglz, lz4. 2025-11-30 18:45:27.534 UTC client backend[46689] pg_regress/compression STATEMENT: SET default_toast_compression = 'I do not exist compression'; 2025-11-30 18:45:27.552 UTC client backend[46689] pg_regress/compression ERROR: invalid compression method "i_do_not_exist_compression" 2025-11-30 18:45:27.552 UTC client backend[46689] pg_regress/compression STATEMENT: CREATE TABLE badcompresstbl (a text COMPRESSION I_Do_Not_Exist_Compression); 2025-11-30 18:45:27.555 UTC client backend[46689] pg_regress/compression ERROR: invalid compression method "i_do_not_exist_compression" 2025-11-30 18:45:27.555 UTC client backend[46689] pg_regress/compression STATEMENT: ALTER TABLE badcompresstbl ALTER a SET COMPRESSION I_Do_Not_Exist_Compression; 2025-11-30 18:45:27.557 UTC client backend[46689] pg_regress/compression LOG: disconnection: session time: 0:00:00.551 user=postgres database=regression host=[local] 2025-11-30 18:45:27.564 UTC client backend[46697] pg_regress/eager_aggregate LOG: disconnection: session time: 0:00:00.552 user=postgres database=regression host=[local] 2025-11-30 18:45:27.582 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop index idxpart1_a_idx because index idxpart_a_idx requires it 2025-11-30 18:45:27.582 UTC client backend[46691] pg_regress/indexing HINT: You can drop index idxpart_a_idx instead. 2025-11-30 18:45:27.582 UTC client backend[46691] pg_regress/indexing STATEMENT: drop index idxpart1_a_idx; 2025-11-30 18:45:27.583 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop partitioned index "idxpart_a_idx" concurrently 2025-11-30 18:45:27.583 UTC client backend[46691] pg_regress/indexing STATEMENT: drop index concurrently idxpart_a_idx; 2025-11-30 18:45:27.591 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop index idxpart1_temp_a_idx because index idxpart_temp_a_idx requires it 2025-11-30 18:45:27.591 UTC client backend[46691] pg_regress/indexing HINT: You can drop index idxpart_temp_a_idx instead. 2025-11-30 18:45:27.591 UTC client backend[46691] pg_regress/indexing STATEMENT: drop index idxpart1_temp_a_idx; 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing ERROR: "idxpart" is not an index 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart attach partition idxpart1; 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing ERROR: "idxpart1" is not an index 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1; 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart_a_b_idx" as a partition of index "idxpart_a_b_idx" 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing DETAIL: Index "idxpart_a_b_idx" is not an index on any partition of table "idxpart". 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart_a_b_idx; 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing ERROR: relation "idxpart1_b_idx" does not exist 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_b_idx; 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_tst1" as a partition of index "idxpart_a_b_idx" 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing DETAIL: The index definitions do not match. 2025-11-30 18:45:27.604 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_tst1; 2025-11-30 18:45:27.605 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_tst2" as a partition of index "idxpart_a_b_idx" 2025-11-30 18:45:27.605 UTC client backend[46691] pg_regress/indexing DETAIL: The index definitions do not match. 2025-11-30 18:45:27.605 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_tst2; 2025-11-30 18:45:27.605 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_tst3" as a partition of index "idxpart_a_b_idx" 2025-11-30 18:45:27.605 UTC client backend[46691] pg_regress/indexing DETAIL: The index definitions do not match. 2025-11-30 18:45:27.605 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_tst3; 2025-11-30 18:45:27.607 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_2_a_b" as a partition of index "idxpart_a_b_idx" 2025-11-30 18:45:27.607 UTC client backend[46691] pg_regress/indexing DETAIL: Another index "idxpart1_a_b_idx" is already attached for partition "idxpart1". 2025-11-30 18:45:27.607 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_2_a_b; 2025-11-30 18:45:27.671 UTC client backend[46683] pg_regress/partition_prune ERROR: table "part_rev" contains column "c" not found in parent "part" 2025-11-30 18:45:27.671 UTC client backend[46683] pg_regress/partition_prune DETAIL: The new partition may contain only the columns present in parent. 2025-11-30 18:45:27.671 UTC client backend[46683] pg_regress/partition_prune STATEMENT: ALTER TABLE part ATTACH PARTITION part_rev FOR VALUES IN (3); 2025-11-30 18:45:27.802 UTC unrecognized[46736] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.803 UTC client backend[46736] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.803 UTC client backend[46736] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats 2025-11-30 18:45:27.804 UTC client backend[46736] pg_regress/stats LOG: connection ready: setup total=2.046 ms, fork=0.501 ms, authentication=0.123 ms 2025-11-30 18:45:27.811 UTC client backend[46736] pg_regress/stats ERROR: unrecognized CHECKPOINT option "wrong" at character 13 2025-11-30 18:45:27.811 UTC client backend[46736] pg_regress/stats STATEMENT: CHECKPOINT (WRONG); 2025-11-30 18:45:27.812 UTC client backend[46736] pg_regress/stats ERROR: unrecognized MODE option "wrong" at character 13 2025-11-30 18:45:27.812 UTC client backend[46736] pg_regress/stats STATEMENT: CHECKPOINT (MODE WRONG); 2025-11-30 18:45:27.812 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:27.825 UTC client backend[46696] pg_regress/stats LOG: disconnection: session time: 0:00:00.817 user=postgres database=regression host=[local] 2025-11-30 18:45:27.849 UTC checkpointer[43405] LOG: checkpoint complete: wrote 7892 buffers (48.2%), wrote 11 SLRU buffers; 0 WAL file(s) added, 0 removed, 18 recycled; write=0.023 s, sync=0.001 s, total=0.037 s; sync files=0, longest=0.000 s, average=0.000 s; distance=294874 kB, estimate=294874 kB; lsn=0/3E2889B8, redo lsn=0/3E22BCE0 2025-11-30 18:45:27.852 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait flush-unlogged 2025-11-30 18:45:27.853 UTC checkpointer[43405] LOG: checkpoint complete: wrote 149 buffers (0.9%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.001 s; sync files=0, longest=0.000 s, average=0.000 s; distance=676 kB, estimate=265454 kB; lsn=0/3E2E9570, redo lsn=0/3E2D4F90 2025-11-30 18:45:27.857 UTC client backend[46685] pg_regress/partition_aggregate LOG: disconnection: session time: 0:00:00.851 user=postgres database=regression host=[local] 2025-11-30 18:45:27.863 UTC client backend[46736] pg_regress/stats ERROR: unrecognized reset target: "unknown" 2025-11-30 18:45:27.863 UTC client backend[46736] pg_regress/stats HINT: Target must be "archiver", "bgwriter", "checkpointer", "io", "recovery_prefetch", "slru", or "wal". 2025-11-30 18:45:27.863 UTC client backend[46736] pg_regress/stats STATEMENT: SELECT pg_stat_reset_shared('unknown'); 2025-11-30 18:45:27.868 UTC client backend[46736] pg_regress/stats ERROR: invalid statistics kind: "zaphod" 2025-11-30 18:45:27.868 UTC client backend[46736] pg_regress/stats STATEMENT: SELECT pg_stat_have_stats('zaphod', 0, 0); 2025-11-30 18:45:27.887 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:27.889 UTC checkpointer[43405] LOG: checkpoint complete: wrote 104 buffers (0.6%), 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=723 kB, estimate=238981 kB; lsn=0/3E3ABF88, redo lsn=0/3E389F70 2025-11-30 18:45:27.889 UTC checkpointer[43405] LOG: checkpoint starting: fast force wait 2025-11-30 18:45:27.889 UTC checkpointer[43405] LOG: checkpoint complete: wrote 15 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.001 s; sync files=0, longest=0.000 s, average=0.000 s; distance=136 kB, estimate=215097 kB; lsn=0/3E3B13A8, redo lsn=0/3E3AC208 2025-11-30 18:45:27.902 UTC unrecognized[46739] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.902 UTC client backend[46739] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.902 UTC client backend[46739] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats 2025-11-30 18:45:27.903 UTC client backend[46739] pg_regress/stats LOG: connection ready: setup total=2.421 ms, fork=0.763 ms, authentication=0.133 ms 2025-11-30 18:45:27.905 UTC client backend[46736] pg_regress/stats LOG: disconnection: session time: 0:00:00.102 user=postgres database=regression host=[local] 2025-11-30 18:45:27.943 UTC unrecognized[46740] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:27.944 UTC client backend[46740] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:27.944 UTC client backend[46740] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats 2025-11-30 18:45:27.945 UTC client backend[46740] pg_regress/stats LOG: connection ready: setup total=2.847 ms, fork=1.158 ms, authentication=0.123 ms 2025-11-30 18:45:27.946 UTC client backend[46739] pg_regress/stats LOG: disconnection: session time: 0:00:00.044 user=postgres database=regression host=[local] 2025-11-30 18:45:27.947 UTC client backend[46740] pg_regress/stats LOG: wait_for_hot_stats delayed 0.000928 seconds 2025-11-30 18:45:27.947 UTC client backend[46740] pg_regress/stats CONTEXT: PL/pgSQL function wait_for_hot_stats() line 17 at RAISE 2025-11-30 18:45:27.947 UTC client backend[46740] pg_regress/stats STATEMENT: SELECT wait_for_hot_stats(); TRAP: failed Assert("ws_next == workspace + func->copiable_size"), File: "../src/pl/plpgsql/src/pl_exec.c", Line: 1375, PID: 46714 0xadfca2 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x84074bb00 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/lib/plpgsql.so 0x84074af11 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/lib/plpgsql.so 0x84075bd75 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/lib/plpgsql.so 0x79054b at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x6c2896 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x79796c at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x7d15b0 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x7cf0b8 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x7997ab at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x99315a at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x992710 <$dtrace798193200.PortalRunMulti+0x1b0> at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x991fdb at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x990e57 <$dtrace647993547.exec_simple_query+0x507> at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x98e79b at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x988c19 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x8d1f4b at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x8d69d0 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x8d4727 at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x8031fd at /tmp/cirrus-ci-build/build/tmp_install/usr/local/pgsql/bin/postgres 0x82deb7e34 <__libc_start1+0x124> at /lib/libc.so.7 2025-11-30 18:45:27.973 UTC client backend[46740] pg_regress/stats LOG: disconnection: session time: 0:00:00.029 user=postgres database=regression host=[local] 2025-11-30 18:45:28.067 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart2_a_idx" as a partition of index "idxpart_a_idx" 2025-11-30 18:45:28.067 UTC client backend[46691] pg_regress/indexing DETAIL: The index definitions do not match. 2025-11-30 18:45:28.067 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_a_idx attach partition idxpart2_a_idx; 2025-11-30 18:45:28.081 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_1b_idx" as a partition of index "idxpart_1_idx" 2025-11-30 18:45:28.081 UTC client backend[46691] pg_regress/indexing DETAIL: The index definitions do not match. 2025-11-30 18:45:28.081 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_1_idx attach partition idxpart1_1b_idx; 2025-11-30 18:45:28.082 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_2b_idx" as a partition of index "idxpart_2_idx" 2025-11-30 18:45:28.082 UTC client backend[46691] pg_regress/indexing DETAIL: The index definitions do not match. 2025-11-30 18:45:28.082 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_2_idx attach partition idxpart1_2b_idx; 2025-11-30 18:45:28.083 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_2c_idx" as a partition of index "idxpart_2_idx" 2025-11-30 18:45:28.083 UTC client backend[46691] pg_regress/indexing DETAIL: The index definitions do not match. 2025-11-30 18:45:28.083 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_2_idx attach partition idxpart1_2c_idx; 2025-11-30 18:45:28.243 UTC client backend[46691] pg_regress/indexing ERROR: multiple primary keys for table "failpart" are not allowed 2025-11-30 18:45:28.243 UTC client backend[46691] pg_regress/indexing STATEMENT: create table failpart partition of idxpart (b primary key) for values from (0) to (100); 2025-11-30 18:45:28.263 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.263 UTC client backend[46691] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.263 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int unique, b int) partition by range (a, b); 2025-11-30 18:45:28.264 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.264 UTC client backend[46691] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart" lacks column "a" which is part of the partition key. 2025-11-30 18:45:28.264 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int, b int unique) partition by range (a, b); 2025-11-30 18:45:28.265 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.265 UTC client backend[46691] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.265 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int primary key, b int) partition by range (b, a); 2025-11-30 18:45:28.267 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.267 UTC client backend[46691] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart" lacks column "a" which is part of the partition key. 2025-11-30 18:45:28.267 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int, b int primary key) partition by range (b, a); 2025-11-30 18:45:28.281 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.281 UTC client backend[46691] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.281 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int4range, b int4range, exclude USING GIST (a with = )) partition by range (a, b); 2025-11-30 18:45:28.282 UTC client backend[46691] pg_regress/indexing ERROR: cannot match partition key to index on column "a" using non-equal operator "-|-" 2025-11-30 18:45:28.282 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int4range, exclude USING GIST (a with -|- )) partition by range (a); 2025-11-30 18:45:28.286 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.286 UTC client backend[46691] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key. 2025-11-30 18:45:28.286 UTC client backend[46691] 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-11-30 18:45:28.290 UTC client backend[46691] pg_regress/indexing ERROR: unsupported PRIMARY KEY constraint with partition key definition 2025-11-30 18:45:28.290 UTC client backend[46691] pg_regress/indexing DETAIL: PRIMARY KEY constraints cannot be used when partition keys include expressions. 2025-11-30 18:45:28.290 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int primary key, b int) partition by range ((b + a)); 2025-11-30 18:45:28.291 UTC client backend[46691] pg_regress/indexing ERROR: unsupported UNIQUE constraint with partition key definition 2025-11-30 18:45:28.291 UTC client backend[46691] pg_regress/indexing DETAIL: UNIQUE constraints cannot be used when partition keys include expressions. 2025-11-30 18:45:28.291 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart (a int unique, b int) partition by range ((b + a)); 2025-11-30 18:45:28.293 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.293 UTC client backend[46691] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.293 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart add primary key (a); 2025-11-30 18:45:28.325 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.325 UTC client backend[46691] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.325 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart add unique (a); 2025-11-30 18:45:28.347 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.347 UTC client backend[46691] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.347 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart add exclude USING GIST (a with =); 2025-11-30 18:45:28.349 UTC client backend[46691] pg_regress/indexing ERROR: cannot match partition key to index on column "a" using non-equal operator "-|-" 2025-11-30 18:45:28.349 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart add exclude USING GIST (a with -|-); 2025-11-30 18:45:28.354 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.354 UTC client backend[46691] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key. 2025-11-30 18:45:28.354 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart add exclude USING GIST (b with =, c with &&); 2025-11-30 18:45:28.389 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.389 UTC client backend[46691] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart2" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.389 UTC client backend[46691] pg_regress/indexing STATEMENT: create table idxpart2 partition of idxpart for values from (0) to (1000) partition by range (b); 2025-11-30 18:45:28.396 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.396 UTC client backend[46691] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart1" lacks column "b" which is part of the partition key. 2025-11-30 18:45:28.396 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart attach partition idxpart1 for values from (1) to (1000); 2025-11-30 18:45:28.424 UTC client backend[46684] pg_regress/partition_join LOG: disconnection: session time: 0:00:01.419 user=postgres database=regression host=[local] 2025-11-30 18:45:28.434 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop index idxpart0_pkey because index idxpart_pkey requires it 2025-11-30 18:45:28.434 UTC client backend[46691] pg_regress/indexing HINT: You can drop index idxpart_pkey instead. 2025-11-30 18:45:28.434 UTC client backend[46691] pg_regress/indexing STATEMENT: drop index idxpart0_pkey; 2025-11-30 18:45:28.435 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop index idxpart1_pkey because index idxpart_pkey requires it 2025-11-30 18:45:28.435 UTC client backend[46691] pg_regress/indexing HINT: You can drop index idxpart_pkey instead. 2025-11-30 18:45:28.435 UTC client backend[46691] pg_regress/indexing STATEMENT: drop index idxpart1_pkey; 2025-11-30 18:45:28.435 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop inherited constraint "idxpart0_pkey" of relation "idxpart0" 2025-11-30 18:45:28.435 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart0 drop constraint idxpart0_pkey; 2025-11-30 18:45:28.435 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop inherited constraint "idxpart1_pkey" of relation "idxpart1" 2025-11-30 18:45:28.435 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart1 drop constraint idxpart1_pkey; 2025-11-30 18:45:28.447 UTC client backend[46691] pg_regress/indexing ERROR: multiple primary keys for table "idxpart1" are not allowed 2025-11-30 18:45:28.447 UTC client backend[46691] pg_regress/indexing STATEMENT: ALTER TABLE idxpart ATTACH PARTITION idxpart1 FOR VALUES FROM (100) TO (200); 2025-11-30 18:45:28.459 UTC client backend[46691] pg_regress/indexing ERROR: multiple primary keys for table "idxpart11" are not allowed 2025-11-30 18:45:28.459 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table idxpart attach partition idxpart1 for values from (0) to (10000); 2025-11-30 18:45:28.481 UTC client backend[46691] pg_regress/indexing ERROR: column "a" of table "idxpart0" is not marked NOT NULL 2025-11-30 18:45:28.481 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table only idxpart add primary key (a); 2025-11-30 18:45:28.492 UTC client backend[46686] pg_regress/tuplesort LOG: disconnection: session time: 0:00:01.483 user=postgres database=regression host=[local] 2025-11-30 18:45:28.505 UTC client backend[46691] pg_regress/indexing ERROR: cannot attach index "idxpart1_a_idx" as a partition of index "idxpart_pkey" 2025-11-30 18:45:28.505 UTC client backend[46691] 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-11-30 18:45:28.505 UTC client backend[46691] pg_regress/indexing STATEMENT: alter index idxpart_pkey attach partition idxpart1_a_idx; 2025-11-30 18:45:28.523 UTC client backend[46691] pg_regress/indexing ERROR: duplicate key value violates unique constraint "idxpart1_a_idx" 2025-11-30 18:45:28.523 UTC client backend[46691] pg_regress/indexing DETAIL: Key (a)=(65536) already exists. 2025-11-30 18:45:28.523 UTC client backend[46691] pg_regress/indexing STATEMENT: insert into idxpart select 2^g, format('two to power of %s', g) from generate_series(15, 17) g; 2025-11-30 18:45:28.527 UTC client backend[46691] pg_regress/indexing ERROR: duplicate key value violates unique constraint "idxpart2_a_idx" 2025-11-30 18:45:28.527 UTC client backend[46691] pg_regress/indexing DETAIL: Key (a)=(285714) already exists. 2025-11-30 18:45:28.527 UTC client backend[46691] pg_regress/indexing STATEMENT: insert into idxpart select a * 2, b || b from idxpart where a between 2^16 and 2^19; 2025-11-30 18:45:28.527 UTC client backend[46691] pg_regress/indexing ERROR: duplicate key value violates unique constraint "idxpart2_a_idx" 2025-11-30 18:45:28.527 UTC client backend[46691] pg_regress/indexing DETAIL: Key (a)=(572814) already exists. 2025-11-30 18:45:28.527 UTC client backend[46691] pg_regress/indexing STATEMENT: insert into idxpart values (572814, 'five'); 2025-11-30 18:45:28.601 UTC client backend[46691] pg_regress/indexing ERROR: duplicate key value violates unique constraint "covidxpart1_a_b_idx" 2025-11-30 18:45:28.601 UTC client backend[46691] pg_regress/indexing DETAIL: Key (a)=(1) already exists. 2025-11-30 18:45:28.601 UTC client backend[46691] pg_regress/indexing STATEMENT: insert into covidxpart values (1, 1); 2025-11-30 18:45:28.605 UTC client backend[46691] pg_regress/indexing ERROR: duplicate key value violates unique constraint "covidxpart3_a_b_idx" 2025-11-30 18:45:28.605 UTC client backend[46691] pg_regress/indexing DETAIL: Key (a)=(3) already exists. 2025-11-30 18:45:28.605 UTC client backend[46691] pg_regress/indexing STATEMENT: insert into covidxpart values (3, 1); 2025-11-30 18:45:28.609 UTC client backend[46691] pg_regress/indexing ERROR: duplicate key value violates unique constraint "covidxpart4_a_b_idx" 2025-11-30 18:45:28.609 UTC client backend[46691] pg_regress/indexing DETAIL: Key (a)=(4) already exists. 2025-11-30 18:45:28.609 UTC client backend[46691] pg_regress/indexing STATEMENT: insert into covidxpart values (4, 1); 2025-11-30 18:45:28.610 UTC client backend[46691] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2025-11-30 18:45:28.610 UTC client backend[46691] pg_regress/indexing DETAIL: UNIQUE constraint on table "covidxpart" lacks column "a" which is part of the partition key. 2025-11-30 18:45:28.610 UTC client backend[46691] pg_regress/indexing STATEMENT: create unique index on covidxpart (b) include (a); 2025-11-30 18:45:28.615 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop inherited constraint "parted_pk_detach_test1_pkey" of relation "parted_pk_detach_test1" 2025-11-30 18:45:28.615 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table parted_pk_detach_test1 drop constraint parted_pk_detach_test1_pkey; 2025-11-30 18:45:28.624 UTC client backend[46691] pg_regress/indexing ERROR: cannot drop inherited constraint "parted_uniq_detach_test1_a_key" of relation "parted_uniq_detach_test1" 2025-11-30 18:45:28.624 UTC client backend[46691] pg_regress/indexing STATEMENT: alter table parted_uniq_detach_test1 drop constraint parted_uniq_detach_test1_a_key; 2025-11-30 18:45:28.682 UTC client backend[46683] pg_regress/partition_prune ERROR: new row violates check option for view "part_abc_view" 2025-11-30 18:45:28.682 UTC client backend[46683] pg_regress/partition_prune DETAIL: Failing row contains (2, a, t). 2025-11-30 18:45:28.682 UTC client backend[46683] pg_regress/partition_prune STATEMENT: execute update_part_abc_view (2, 'a'); 2025-11-30 18:45:28.720 UTC client backend[46683] pg_regress/partition_prune LOG: disconnection: session time: 0:00:01.718 user=postgres database=regression host=[local] 2025-11-30 18:45:28.727 UTC client backend[46691] pg_regress/indexing ERROR: division by zero 2025-11-30 18:45:28.727 UTC client backend[46691] pg_regress/indexing STATEMENT: create index concurrently parted_isvalid_idx_11 on parted_isvalid_tab_11 ((a/b)); 2025-11-30 18:45:28.787 UTC client backend[46691] pg_regress/indexing LOG: disconnection: session time: 0:00:01.775 user=postgres database=regression host=[local] 2025-11-30 18:45:28.810 UTC unrecognized[46788] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:28.810 UTC unrecognized[46789] [unknown] LOG: connection received: host=[local] 2025-11-30 18:45:28.811 UTC client backend[46788] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:28.811 UTC client backend[46788] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/oidjoins 2025-11-30 18:45:28.811 UTC client backend[46789] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/build/runningcheck/pg_hba.conf:117) 2025-11-30 18:45:28.811 UTC client backend[46789] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/event_trigger 2025-11-30 18:45:28.812 UTC client backend[46788] pg_regress/oidjoins LOG: connection ready: setup total=2.282 ms, fork=0.445 ms, authentication=0.150 ms 2025-11-30 18:45:28.812 UTC client backend[46789] pg_regress/event_trigger LOG: connection ready: setup total=2.168 ms, fork=0.358 ms, authentication=0.154 ms 2025-11-30 18:45:28.813 UTC client backend[46789] pg_regress/event_trigger ERROR: function pg_backend_pid must return type event_trigger 2025-11-30 18:45:28.813 UTC client backend[46789] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger on ddl_command_start execute procedure pg_backend_pid(); 2025-11-30 18:45:28.814 UTC client backend[46789] pg_regress/event_trigger ERROR: trigger functions can only be called as triggers 2025-11-30 18:45:28.814 UTC client backend[46789] pg_regress/event_trigger CONTEXT: compilation of PL/pgSQL function "test_event_trigger" near line 1 2025-11-30 18:45:28.814 UTC client backend[46789] pg_regress/event_trigger STATEMENT: SELECT test_event_trigger(); 2025-11-30 18:45:28.814 UTC client backend[46789] pg_regress/event_trigger ERROR: event trigger functions cannot have declared arguments 2025-11-30 18:45:28.814 UTC client backend[46789] pg_regress/event_trigger CONTEXT: compilation of PL/pgSQL function "test_event_trigger_arg" near line 1 2025-11-30 18:45:28.814 UTC client backend[46789] pg_regress/event_trigger STATEMENT: create function test_event_trigger_arg(name text) returns event_trigger as $$ BEGIN RETURN 1; END $$ language plpgsql; 2025-11-30 18:45:28.815 UTC client backend[46789] pg_regress/event_trigger ERROR: SQL functions cannot return type event_trigger 2025-11-30 18:45:28.815 UTC client backend[46789] pg_regress/event_trigger STATEMENT: create function test_event_trigger_sql() returns event_trigger as $$ SELECT 1 $$ language sql; 2025-11-30 18:45:28.815 UTC client backend[46789] pg_regress/event_trigger ERROR: unrecognized event name "elephant_bootstrap" 2025-11-30 18:45:28.815 UTC client backend[46789] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger on elephant_bootstrap execute procedure test_event_trigger(); 2025-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: unrecognized filter variable "food" 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: filter value "sandwich" not recognized for filter variable "tag" 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: filter value "create skunkcabbage" not recognized for filter variable "tag" 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: event triggers are not supported for DROP EVENT TRIGGER 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: event triggers are not supported for CREATE ROLE 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: event triggers are not supported for CREATE DATABASE 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: event triggers are not supported for CREATE TABLESPACE 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: filter variable "tag" specified more than once 2025-11-30 18:45:28.816 UTC client backend[46789] 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-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger ERROR: syntax error at or near "'argument not allowed'" at character 106 2025-11-30 18:45:28.816 UTC client backend[46789] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger2 on ddl_command_start execute procedure test_event_trigger('argument not allowed'); 2025-11-30 18:45:28.817 UTC client backend[46789] pg_regress/event_trigger ERROR: permission denied to create event trigger "regress_event_trigger_noperms" 2025-11-30 18:45:28.817 UTC client backend[46789] pg_regress/event_trigger HINT: Must be superuser to create an event trigger. 2025-11-30 18:45:28.817 UTC client backend[46789] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger_noperms on ddl_command_start execute procedure test_event_trigger(); 2025-11-30 18:45:28.831 UTC client backend[46789] pg_regress/event_trigger ERROR: permission denied to change owner of event trigger "regress_event_trigger" 2025-11-30 18:45:28.831 UTC client backend[46789] pg_regress/event_trigger HINT: The owner of an event trigger must be a superuser. 2025-11-30 18:45:28.831 UTC client backend[46789] pg_regress/event_trigger STATEMENT: alter event trigger regress_event_trigger owner to regress_evt_user; 2025-11-30 18:45:28.831 UTC client backend[46789] pg_regress/event_trigger ERROR: event trigger "regress_event_trigger2" already exists 2025-11-30 18:45:28.831 UTC client backend[46789] pg_regress/event_trigger STATEMENT: alter event trigger regress_event_trigger rename to regress_event_trigger2; 2025-11-30 18:45:28.832 UTC client backend[46789] pg_regress/event_trigger ERROR: event trigger "regress_event_trigger" does not exist 2025-11-30 18:45:28.832 UTC client backend[46789] pg_regress/event_trigger STATEMENT: drop event trigger regress_event_trigger; 2025-11-30 18:45:28.832 UTC client backend[46789] pg_regress/event_trigger ERROR: role "regress_evt_user" cannot be dropped because some objects depend on it 2025-11-30 18:45:28.832 UTC client backend[46789] 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-11-30 18:45:28.832 UTC client backend[46789] pg_regress/event_trigger STATEMENT: drop role regress_evt_user; 2025-11-30 18:45:28.845 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 LOG: process 46715 still waiting for ExclusiveLock on advisory lock [16387,2,3,2] after 1000.717 ms 2025-11-30 18:45:28.845 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 DETAIL: Process holding the lock: 46713. Wait queue: 46715. 2025-11-30 18:45:28.845 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 CONTEXT: waiting for ExclusiveLock on advisory lock [16387,2,3,2] SQL statement "SELECT pg_advisory_xact_lock(current_setting('spec.session')::int, 3)" PL/pgSQL function blurt_and_lock_123(text) line 11 at PERFORM 2025-11-30 18:45:28.845 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 STATEMENT: INSERT INTO upserttest VALUES('k2', ctoast_large_val()) ON CONFLICT DO NOTHING; 2025-11-30 18:45:28.860 UTC client backend[46789] pg_regress/event_trigger ERROR: object audit_tbls.schema_two_table_three of type table cannot be dropped 2025-11-30 18:45:28.860 UTC client backend[46789] 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-11-30 18:45:28.860 UTC client backend[46789] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2025-11-30 18:45:28.868 UTC client backend[46789] pg_regress/event_trigger ERROR: object schema_one.table_three of type table cannot be dropped 2025-11-30 18:45:28.868 UTC client backend[46789] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE 2025-11-30 18:45:28.868 UTC client backend[46789] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2025-11-30 18:45:28.947 UTC client backend[46789] pg_regress/event_trigger ERROR: pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function 2025-11-30 18:45:28.947 UTC client backend[46789] pg_regress/event_trigger STATEMENT: select pg_event_trigger_table_rewrite_oid(); 2025-11-30 18:45:28.954 UTC client backend[46789] pg_regress/event_trigger ERROR: rewrites not allowed 2025-11-30 18:45:28.954 UTC client backend[46789] pg_regress/event_trigger CONTEXT: PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE 2025-11-30 18:45:28.954 UTC client backend[46789] pg_regress/event_trigger STATEMENT: alter table rewriteme alter column foo type numeric; 2025-11-30 18:45:28.971 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 LOG: process 46715 acquired ExclusiveLock on advisory lock [16387,2,3,2] after 1125.993 ms 2025-11-30 18:45:28.971 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 CONTEXT: waiting for ExclusiveLock on advisory lock [16387,2,3,2] SQL statement "SELECT pg_advisory_xact_lock(current_setting('spec.session')::int, 3)" PL/pgSQL function blurt_and_lock_123(text) line 11 at PERFORM 2025-11-30 18:45:28.971 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 STATEMENT: INSERT INTO upserttest VALUES('k2', ctoast_large_val()) ON CONFLICT DO NOTHING; 2025-11-30 18:45:28.971 UTC client backend[46713] isolation/insert-conflict-specconflict/controller LOG: disconnection: session time: 0:00:01.677 user=postgres database=isolation_regression host=[local] 2025-11-30 18:45:28.971 UTC client backend[46712] isolation/insert-conflict-specconflict/control connection LOG: disconnection: session time: 0:00:01.690 user=postgres database=isolation_regression host=[local] TRAP: failed Assert("ws_next == workspace + func->copiable_size"), File: "../src/pl/plpgsql/src/pl_exec.c", Line: 1375, PID: 46715 2025-11-30 18:45:28.973 UTC postmaster[43401] LOG: client backend (PID 46714) was terminated by signal 6: Abort trap 2025-11-30 18:45:28.973 UTC postmaster[43401] DETAIL: Failed process was running: INSERT INTO upserttest VALUES('k2', ctoast_large_val()) ON CONFLICT DO NOTHING; 2025-11-30 18:45:28.973 UTC postmaster[43401] LOG: terminating any other active server processes 2025-11-30 18:45:28.973 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 LOG: could not send data to client: Broken pipe 2025-11-30 18:45:28.973 UTC client backend[46715] isolation/insert-conflict-specconflict/s2 STATEMENT: INSERT INTO upserttest VALUES('k2', ctoast_large_val()) ON CONFLICT DO NOTHING; 2025-11-30 18:45:28.976 UTC postmaster[43401] LOG: shutting down because "restart_after_crash" is off 2025-11-30 18:45:28.978 UTC postmaster[43401] LOG: database system is shut down