2025-01-31 07:57:06.571 UTC postmaster[20167] LOG: starting PostgreSQL 18devel on x86_64-freebsd, compiled by clang-17.0.6, 64-bit 2025-01-31 07:57:06.571 UTC postmaster[20167] LOG: listening on Unix socket "/tmp/pg_regress-2s8NIU/.s.PGSQL.40041" 2025-01-31 07:57:06.573 UTC startup[20170] LOG: database system was shut down at 2025-01-31 07:57:06 UTC 2025-01-31 07:57:06.575 UTC postmaster[20167] LOG: database system is ready to accept connections 2025-01-31 07:57:06.708 UTC client backend[20178] pg_regress/postgres_fdw ERROR: parameter "extensions" must be a list of extension names 2025-01-31 07:57:06.708 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: ALTER SERVER testserver1 OPTIONS (ADD extensions 'foo; bar'); 2025-01-31 07:57:06.708 UTC client backend[20178] pg_regress/postgres_fdw WARNING: extension "foo" is not installed 2025-01-31 07:57:06.708 UTC client backend[20178] pg_regress/postgres_fdw WARNING: extension "bar" is not installed 2025-01-31 07:57:06.708 UTC client backend[20178] pg_regress/postgres_fdw ERROR: invalid option "sslmode" 2025-01-31 07:57:06.708 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR public SERVER testserver1 OPTIONS (ADD sslmode 'require'); 2025-01-31 07:57:06.726 UTC client backend[20180] [unknown] FATAL: database "no such database" does not exist 2025-01-31 07:57:06.726 UTC client backend[20178] pg_regress/postgres_fdw ERROR: could not connect to server "loopback" 2025-01-31 07:57:06.726 UTC client backend[20178] pg_regress/postgres_fdw DETAIL: connection to server on socket "/tmp/pg_regress-2s8NIU/.s.PGSQL.40041" failed: FATAL: database "no such database" does not exist 2025-01-31 07:57:06.726 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: SELECT c3, c4 FROM ft1 ORDER BY c3, c1 LIMIT 1; 2025-01-31 07:57:06.735 UTC client backend[20182] [unknown] FATAL: role "no such user" does not exist 2025-01-31 07:57:06.736 UTC client backend[20178] pg_regress/postgres_fdw ERROR: could not connect to server "loopback" 2025-01-31 07:57:06.736 UTC client backend[20178] pg_regress/postgres_fdw DETAIL: connection to server on socket "/tmp/pg_regress-2s8NIU/.s.PGSQL.40041" failed: FATAL: role "no such user" does not exist 2025-01-31 07:57:06.736 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: SELECT c3, c4 FROM ft1 ORDER BY c3, c1 LIMIT 1; 2025-01-31 07:57:06.753 UTC client backend[20178] pg_regress/postgres_fdw ERROR: cannot add relation "ft1" to publication 2025-01-31 07:57:06.753 UTC client backend[20178] pg_regress/postgres_fdw DETAIL: This operation is not supported for foreign tables. 2025-01-31 07:57:06.753 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: CREATE PUBLICATION testpub_ftbl FOR TABLE ft1; 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: SELECT * from ft1 where c1 < 1; 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1 (c1) VALUES (1); 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: DELETE FROM ft1 WHERE c1 = 1; 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw ERROR: access to non-system foreign table is restricted 2025-01-31 07:57:06.839 UTC client backend[20178] pg_regress/postgres_fdw STATEMENT: TRUNCATE ft1; 2025-01-31 07:57:07.722 UTC client backend[20185] pg_regress/postgres_fdw ERROR: user mapping not found for user "regress_view_owner_another", server "loopback" 2025-01-31 07:57:07.722 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: EXPLAIN (VERBOSE, COSTS OFF) SELECT * FROM v4; 2025-01-31 07:57:07.723 UTC client backend[20185] pg_regress/postgres_fdw ERROR: user mapping not found for user "regress_view_owner_another", server "loopback" 2025-01-31 07:57:07.723 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: EXPLAIN (VERBOSE, COSTS OFF) SELECT * FROM (SELECT * FROM v4 UNION ALL SELECT * FROM v4); 2025-01-31 07:57:08.165 UTC client backend[20185] pg_regress/postgres_fdw ERROR: "reindex_foreign" is not a table or materialized view 2025-01-31 07:57:08.165 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: REINDEX TABLE reindex_foreign; 2025-01-31 07:57:08.165 UTC client backend[20185] pg_regress/postgres_fdw ERROR: "reindex_foreign" is not a table or materialized view 2025-01-31 07:57:08.165 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: REINDEX TABLE CONCURRENTLY reindex_foreign; 2025-01-31 07:57:08.173 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-01-31 07:57:08.173 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: column "x8" of foreign table "ftx" 2025-01-31 07:57:08.173 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 ftx(x1,x2,x3,x4,x5,x6,x7,x8) WHERE x1 = 1; 2025-01-31 07:57:08.176 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-01-31 07:57:08.176 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: column "x8" of foreign table "ftx" 2025-01-31 07:57:08.176 UTC client backend[20185] 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-01-31 07:57:08.179 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-01-31 07:57:08.179 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: whole-row reference to foreign table "ftx" 2025-01-31 07:57:08.179 UTC client backend[20185] 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-01-31 07:57:08.182 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-01-31 07:57:08.182 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: processing expression at position 2 in select list 2025-01-31 07:57:08.182 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT sum(c2), array_agg(c8) FROM ft1 GROUP BY c8; 2025-01-31 07:57:08.185 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid input syntax for type integer: "foo" 2025-01-31 07:57:08.185 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: column "c8" of foreign table "ft1" 2025-01-31 07:57:08.185 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ANALYZE ft1; 2025-01-31 07:57:08.191 UTC client backend[20200] pg_regress ERROR: operator does not exist: public.user_enum ~~ unknown at character 92 2025-01-31 07:57:08.191 UTC client backend[20200] pg_regress HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-01-31 07:57:08.191 UTC client backend[20200] pg_regress 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-01-31 07:57:08.191 UTC client backend[20185] pg_regress/postgres_fdw ERROR: operator does not exist: public.user_enum ~~ unknown 2025-01-31 07:57:08.191 UTC client backend[20185] pg_regress/postgres_fdw HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-01-31 07:57:08.191 UTC client backend[20185] 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-01-31 07:57:08.191 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 WHERE c8 LIKE 'foo' LIMIT 1; 2025-01-31 07:57:08.192 UTC client backend[20200] pg_regress ERROR: operator does not exist: public.user_enum ~~ unknown at character 92 2025-01-31 07:57:08.192 UTC client backend[20200] pg_regress HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-01-31 07:57:08.192 UTC client backend[20200] pg_regress 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-01-31 07:57:08.192 UTC client backend[20185] pg_regress/postgres_fdw ERROR: operator does not exist: public.user_enum ~~ unknown 2025-01-31 07:57:08.192 UTC client backend[20185] pg_regress/postgres_fdw HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-01-31 07:57:08.192 UTC client backend[20185] 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-01-31 07:57:08.192 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 WHERE c8::text LIKE 'foo' LIMIT 1; 2025-01-31 07:57:08.195 UTC client backend[20185] pg_regress/postgres_fdw ERROR: syntax error at or near "ERROR" at character 1 2025-01-31 07:57:08.195 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ERROR OUT; 2025-01-31 07:57:08.196 UTC client backend[20200] pg_regress ERROR: division by zero 2025-01-31 07:57:08.196 UTC client backend[20200] pg_regress STATEMENT: FETCH 100 FROM c2 2025-01-31 07:57:08.196 UTC client backend[20185] pg_regress/postgres_fdw ERROR: division by zero 2025-01-31 07:57:08.196 UTC client backend[20185] 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-01-31 07:57:08.196 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT * FROM ft1 WHERE 1 / (c1 - 1) > 0; 2025-01-31 07:57:08.709 UTC client backend[20202] pg_regress ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-01-31 07:57:08.709 UTC client backend[20202] pg_regress DETAIL: Key ("C 1")=(11) already exists. 2025-01-31 07:57:08.709 UTC client backend[20202] pg_regress 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-01-31 07:57:08.709 UTC client backend[20185] pg_regress/postgres_fdw ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-01-31 07:57:08.709 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Key ("C 1")=(11) already exists. 2025-01-31 07:57:08.709 UTC client backend[20185] 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-01-31 07:57:08.709 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(11, 12); 2025-01-31 07:57:08.711 UTC client backend[20185] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-01-31 07:57:08.711 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(11, 12) ON CONFLICT (c1, c2) DO NOTHING; 2025-01-31 07:57:08.712 UTC client backend[20185] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-01-31 07:57:08.712 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(11, 12) ON CONFLICT (c1, c2) DO UPDATE SET c3 = 'ffg'; 2025-01-31 07:57:08.713 UTC client backend[20202] pg_regress ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.713 UTC client backend[20202] pg_regress DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-01-31 07:57:08.713 UTC client backend[20202] pg_regress 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-01-31 07:57:08.713 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.713 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-01-31 07:57:08.713 UTC client backend[20185] 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-01-31 07:57:08.713 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(1111, -2); 2025-01-31 07:57:08.715 UTC client backend[20202] pg_regress ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.715 UTC client backend[20202] pg_regress 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-01-31 07:57:08.715 UTC client backend[20202] pg_regress STATEMENT: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-01-31 07:57:08.715 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.715 UTC client backend[20185] 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-01-31 07:57:08.715 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-01-31 07:57:08.715 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: UPDATE ft1 SET c2 = -c2 WHERE c1 = 1; 2025-01-31 07:57:08.758 UTC client backend[20202] pg_regress ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.758 UTC client backend[20202] pg_regress 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-01-31 07:57:08.758 UTC client backend[20202] pg_regress STATEMENT: UPDATE "S 1"."T 1" SET c2 = (-2) WHERE ((c2 = 42)) AND (("C 1" = 10)) 2025-01-31 07:57:08.758 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.758 UTC client backend[20185] 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-01-31 07:57:08.758 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE "S 1"."T 1" SET c2 = (-2) WHERE ((c2 = 42)) AND (("C 1" = 10)) 2025-01-31 07:57:08.758 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update ft2 set c2 = -2 where c2 = 42 and c1 = 10; 2025-01-31 07:57:08.819 UTC client backend[20202] pg_regress ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.819 UTC client backend[20202] pg_regress DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-01-31 07:57:08.819 UTC client backend[20202] pg_regress 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-01-31 07:57:08.819 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.819 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (1111, -2, null, null, null, null, ft1 , null). 2025-01-31 07:57:08.819 UTC client backend[20185] 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-01-31 07:57:08.819 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO ft1(c1, c2) VALUES(1111, -2); 2025-01-31 07:57:08.822 UTC client backend[20202] pg_regress ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.822 UTC client backend[20202] pg_regress 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-01-31 07:57:08.822 UTC client backend[20202] pg_regress STATEMENT: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-01-31 07:57:08.822 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "T 1" violates check constraint "c2positive" 2025-01-31 07:57:08.822 UTC client backend[20185] 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-01-31 07:57:08.822 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1)) 2025-01-31 07:57:08.822 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: UPDATE ft1 SET c2 = -c2 WHERE c1 = 1; 2025-01-31 07:57:08.846 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-01-31 07:57:08.846 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-01-31 07:57:08.846 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 5); 2025-01-31 07:57:08.851 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-01-31 07:57:08.851 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (20, 20). 2025-01-31 07:57:08.851 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: UPDATE rw_view SET b = b + 5; 2025-01-31 07:57:08.861 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-01-31 07:57:08.861 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-01-31 07:57:08.861 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 15), (0, 5); 2025-01-31 07:57:08.882 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-01-31 07:57:08.882 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-01-31 07:57:08.882 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 5); 2025-01-31 07:57:08.888 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-01-31 07:57:08.888 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (20, 20). 2025-01-31 07:57:08.888 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: UPDATE rw_view SET b = b + 5; 2025-01-31 07:57:08.898 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row violates check option for view "rw_view" 2025-01-31 07:57:08.898 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (10, 5). 2025-01-31 07:57:08.898 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: INSERT INTO rw_view VALUES (0, 15), (0, 5); 2025-01-31 07:57:09.210 UTC client backend[20185] pg_regress/postgres_fdw ERROR: WHERE CURRENT OF is not supported for this table type 2025-01-31 07:57:09.210 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update bar set f2 = null where current of c; 2025-01-31 07:57:09.286 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot execute MERGE on relation "remp1" 2025-01-31 07:57:09.286 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: This operation is not supported for foreign tables. 2025-01-31 07:57:09.286 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: merge into itrtest using (select 1, 'foo') as source on (true) when matched then do nothing; 2025-01-31 07:57:09.290 UTC client backend[20185] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-01-31 07:57:09.290 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: insert into itrtest values (1, 'bar') on conflict (a) do nothing; 2025-01-31 07:57:09.290 UTC client backend[20185] pg_regress/postgres_fdw ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-01-31 07:57:09.290 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: insert into itrtest values (1, 'bar') on conflict (a) do update set b = excluded.b; 2025-01-31 07:57:09.328 UTC client backend[20208] pg_regress ERROR: new row for relation "loct" violates check constraint "loct_a_check" 2025-01-31 07:57:09.328 UTC client backend[20208] pg_regress DETAIL: Failing row contains (2, foo). 2025-01-31 07:57:09.328 UTC client backend[20208] pg_regress STATEMENT: UPDATE public.loct SET a = 2 WHERE ((b = 'foo')) RETURNING a, b 2025-01-31 07:57:09.328 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "loct" violates check constraint "loct_a_check" 2025-01-31 07:57:09.328 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (2, foo). 2025-01-31 07:57:09.328 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: UPDATE public.loct SET a = 2 WHERE ((b = 'foo')) RETURNING a, b 2025-01-31 07:57:09.328 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 2 where b = 'foo' returning *; 2025-01-31 07:57:09.330 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-01-31 07:57:09.330 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 where b = 'qux' returning *; 2025-01-31 07:57:09.341 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-01-31 07:57:09.341 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 where a = 1 or a = 2 returning *; 2025-01-31 07:57:09.353 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-01-31 07:57:09.353 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 returning *; 2025-01-31 07:57:09.360 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-01-31 07:57:09.360 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 1 from (values (1), (2)) s(x) where a = s.x returning *; 2025-01-31 07:57:09.371 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-01-31 07:57:09.371 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 3 returning *; 2025-01-31 07:57:09.374 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot route tuples into foreign table to be updated "remp" 2025-01-31 07:57:09.374 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: update utrtest set a = 3 from (values (2), (3)) s(x) where a = s.x returning *; 2025-01-31 07:57:09.435 UTC client backend[20210] pg_regress ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-01-31 07:57:09.435 UTC client backend[20210] pg_regress DETAIL: Failing row contains (-1, xyzzy). 2025-01-31 07:57:09.435 UTC client backend[20210] pg_regress STATEMENT: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) 2025-01-31 07:57:09.435 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-01-31 07:57:09.435 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (-1, xyzzy). 2025-01-31 07:57:09.435 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) COPY rem2, line 1: "-1 xyzzy" 2025-01-31 07:57:09.435 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: copy rem2 from stdin; 2025-01-31 07:57:09.496 UTC client backend[20211] pg_regress ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-01-31 07:57:09.496 UTC client backend[20211] pg_regress DETAIL: Failing row contains (-1, xyzzy). 2025-01-31 07:57:09.496 UTC client backend[20211] pg_regress STATEMENT: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) 2025-01-31 07:57:09.496 UTC client backend[20185] pg_regress/postgres_fdw ERROR: new row for relation "loc2" violates check constraint "loc2_f1positive" 2025-01-31 07:57:09.496 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Failing row contains (-1, xyzzy). 2025-01-31 07:57:09.496 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2) COPY rem2 2025-01-31 07:57:09.496 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: copy rem2 from stdin; 2025-01-31 07:57:09.551 UTC client backend[20185] pg_regress/postgres_fdw ERROR: foreign table "tru_ftable" does not allow truncates 2025-01-31 07:57:09.551 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_ftable; 2025-01-31 07:57:09.556 UTC client backend[20185] pg_regress/postgres_fdw ERROR: foreign table "tru_ftable" does not allow truncates 2025-01-31 07:57:09.556 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_ftable; 2025-01-31 07:57:09.557 UTC client backend[20185] pg_regress/postgres_fdw ERROR: foreign table "tru_ftable" does not allow truncates 2025-01-31 07:57:09.557 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_ftable; 2025-01-31 07:57:09.570 UTC client backend[20214] pg_regress ERROR: cannot truncate a table referenced in a foreign key constraint 2025-01-31 07:57:09.570 UTC client backend[20214] pg_regress DETAIL: Table "tru_fk_table" references "tru_pk_table". 2025-01-31 07:57:09.570 UTC client backend[20214] pg_regress HINT: Truncate table "tru_fk_table" at the same time, or use TRUNCATE ... CASCADE. 2025-01-31 07:57:09.570 UTC client backend[20214] pg_regress STATEMENT: TRUNCATE public.tru_pk_table CONTINUE IDENTITY RESTRICT 2025-01-31 07:57:09.570 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot truncate a table referenced in a foreign key constraint 2025-01-31 07:57:09.570 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Table "tru_fk_table" references "tru_pk_table". 2025-01-31 07:57:09.570 UTC client backend[20185] pg_regress/postgres_fdw HINT: Truncate table "tru_fk_table" at the same time, or use TRUNCATE ... CASCADE. 2025-01-31 07:57:09.570 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: TRUNCATE public.tru_pk_table CONTINUE IDENTITY RESTRICT 2025-01-31 07:57:09.570 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: TRUNCATE tru_pk_ftable; NOTICE: truncate cascades to table "tru_fk_table" NOTICE: truncate cascades to table "tru_fk_table" 2025-01-31 07:57:09.907 UTC client backend[20185] pg_regress/postgres_fdw ERROR: relation "t1" already exists 2025-01-31 07:57:09.907 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: importing foreign table "t1" 2025-01-31 07:57:09.907 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA import_source FROM SERVER loopback INTO import_dest4; 2025-01-31 07:57:09.908 UTC client backend[20185] pg_regress/postgres_fdw ERROR: schema "nonesuch" is not present on foreign server "loopback" 2025-01-31 07:57:09.908 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA nonesuch FROM SERVER loopback INTO import_dest4; 2025-01-31 07:57:09.908 UTC client backend[20185] pg_regress/postgres_fdw ERROR: schema "notthere" does not exist 2025-01-31 07:57:09.908 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA nonesuch FROM SERVER loopback INTO notthere; 2025-01-31 07:57:09.908 UTC client backend[20185] pg_regress/postgres_fdw ERROR: server "nowhere" does not exist 2025-01-31 07:57:09.908 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA nonesuch FROM SERVER nowhere INTO notthere; 2025-01-31 07:57:09.916 UTC client backend[20185] pg_regress/postgres_fdw ERROR: type "public.Colors" does not exist at character 137 2025-01-31 07:57:09.916 UTC client backend[20185] 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-01-31 07:57:09.916 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: importing foreign table "t5" 2025-01-31 07:57:09.916 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: IMPORT FOREIGN SCHEMA import_source LIMIT TO (t5) FROM SERVER loopback INTO import_dest5; 2025-01-31 07:57:10.138 UTC client backend[20185] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-01-31 07:57:10.138 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Non-superusers must delegate GSSAPI credentials, provide a password, or enable SCRAM pass-through in user mapping. 2025-01-31 07:57:10.138 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-01-31 07:57:10.138 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid option "password" 2025-01-31 07:57:10.138 UTC client backend[20185] pg_regress/postgres_fdw HINT: Perhaps you meant the option "passfile". 2025-01-31 07:57:10.138 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ALTER SERVER loopback_nopw OPTIONS (ADD password 'dummypw'); 2025-01-31 07:57:10.142 UTC client backend[20185] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-01-31 07:57:10.142 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Non-superuser cannot connect if the server does not request a password or use GSSAPI with delegated credentials. 2025-01-31 07:57:10.142 UTC client backend[20185] pg_regress/postgres_fdw HINT: Target server's authentication method must be changed or password_required=false set in the user mapping attributes. 2025-01-31 07:57:10.142 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-01-31 07:57:10.142 UTC client backend[20185] pg_regress/postgres_fdw ERROR: password_required=false is superuser-only 2025-01-31 07:57:10.142 UTC client backend[20185] 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-01-31 07:57:10.142 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD password_required 'false'); 2025-01-31 07:57:10.144 UTC client backend[20185] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-01-31 07:57:10.144 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Non-superuser cannot connect if the server does not request a password or use GSSAPI with delegated credentials. 2025-01-31 07:57:10.144 UTC client backend[20185] pg_regress/postgres_fdw HINT: Target server's authentication method must be changed or password_required=false set in the user mapping attributes. 2025-01-31 07:57:10.144 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-01-31 07:57:10.155 UTC client backend[20185] pg_regress/postgres_fdw ERROR: sslcert and sslkey are superuser-only 2025-01-31 07:57:10.155 UTC client backend[20185] pg_regress/postgres_fdw HINT: User mappings with the sslcert or sslkey options set may only be created or modified by the superuser. 2025-01-31 07:57:10.155 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD sslcert 'foo.crt'); 2025-01-31 07:57:10.155 UTC client backend[20185] pg_regress/postgres_fdw ERROR: sslcert and sslkey are superuser-only 2025-01-31 07:57:10.155 UTC client backend[20185] pg_regress/postgres_fdw HINT: User mappings with the sslcert or sslkey options set may only be created or modified by the superuser. 2025-01-31 07:57:10.155 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD sslkey 'foo.key'); 2025-01-31 07:57:10.156 UTC client backend[20185] pg_regress/postgres_fdw ERROR: password or GSSAPI delegated credentials required 2025-01-31 07:57:10.156 UTC client backend[20185] pg_regress/postgres_fdw DETAIL: Non-superusers must delegate GSSAPI credentials, provide a password, or enable SCRAM pass-through in user mapping. 2025-01-31 07:57:10.156 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1_nopw LIMIT 1; 2025-01-31 07:57:10.173 UTC client backend[20185] pg_regress/postgres_fdw ERROR: cannot PREPARE a transaction that has operated on postgres_fdw foreign tables 2025-01-31 07:57:10.173 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: PREPARE TRANSACTION 'fdw_tpc'; 2025-01-31 07:57:10.173 UTC client backend[20185] pg_regress/postgres_fdw WARNING: there is no transaction in progress 2025-01-31 07:57:10.181 UTC client backend[20221] fdw_retry_check FATAL: terminating connection due to administrator command 2025-01-31 07:57:10.295 UTC client backend[20222] fdw_retry_check FATAL: terminating connection due to administrator command 2025-01-31 07:57:10.403 UTC client backend[20185] 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-01-31 07:57:10.403 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: SAVEPOINT s2 2025-01-31 07:57:10.403 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT 1 FROM ft1 LIMIT 1; 2025-01-31 07:57:10.430 UTC client backend[20185] pg_regress/postgres_fdw WARNING: cannot close connection for server "loopback" because it is still in use 2025-01-31 07:57:10.431 UTC client backend[20185] pg_regress/postgres_fdw WARNING: cannot close connection for server "loopback" because it is still in use 2025-01-31 07:57:10.431 UTC client backend[20185] pg_regress/postgres_fdw WARNING: cannot close connection for server "loopback2" because it is still in use 2025-01-31 07:57:10.433 UTC client backend[20185] pg_regress/postgres_fdw ERROR: server "unknownserver" does not exist 2025-01-31 07:57:10.433 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT postgres_fdw_disconnect('unknownserver'); 2025-01-31 07:57:10.675 UTC client backend[20233] fdw_retry_check ERROR: relation "public.non_existent_table" does not exist at character 43 2025-01-31 07:57:10.675 UTC client backend[20233] fdw_retry_check STATEMENT: DECLARE c3 CURSOR FOR SELECT a, b, c FROM public.non_existent_table 2025-01-31 07:57:10.675 UTC client backend[20185] pg_regress/postgres_fdw ERROR: relation "public.non_existent_table" does not exist 2025-01-31 07:57:10.675 UTC client backend[20185] pg_regress/postgres_fdw CONTEXT: remote SQL command: SELECT a, b, c FROM public.non_existent_table 2025-01-31 07:57:10.675 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: SELECT * FROM async_pt; 2025-01-31 07:57:10.895 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid value for floating point option "fdw_startup_cost": 100$%$#$# 2025-01-31 07:57:10.895 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: CREATE SERVER inv_scst FOREIGN DATA WRAPPER postgres_fdw OPTIONS(fdw_startup_cost '100$%$#$#'); 2025-01-31 07:57:10.895 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid value for floating point option "fdw_tuple_cost": 100$%$#$# 2025-01-31 07:57:10.895 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: CREATE SERVER inv_scst FOREIGN DATA WRAPPER postgres_fdw OPTIONS(fdw_tuple_cost '100$%$#$#'); 2025-01-31 07:57:10.896 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid value for integer option "fetch_size": 100$%$#$# 2025-01-31 07:57:10.896 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: CREATE FOREIGN TABLE inv_fsz (c1 int ) SERVER loopback OPTIONS (fetch_size '100$%$#$#'); 2025-01-31 07:57:10.897 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid value for integer option "batch_size": 100$%$#$# 2025-01-31 07:57:10.897 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: CREATE FOREIGN TABLE inv_bsz (c1 int ) SERVER loopback OPTIONS (batch_size '100$%$#$#'); 2025-01-31 07:57:10.897 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid option "nonexistent" 2025-01-31 07:57:10.897 UTC client backend[20185] pg_regress/postgres_fdw HINT: There are no valid options in this context. 2025-01-31 07:57:10.897 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ALTER FOREIGN DATA WRAPPER postgres_fdw OPTIONS (nonexistent 'fdw'); 2025-01-31 07:57:10.982 UTC client backend[20185] pg_regress/postgres_fdw ERROR: invalid value for string option "analyze_sampling": invalid 2025-01-31 07:57:10.982 UTC client backend[20185] pg_regress/postgres_fdw STATEMENT: ALTER SERVER loopback OPTIONS (analyze_sampling 'invalid'); 2025-01-31 07:57:10.998 UTC client backend[20244] fdw_conn_check FATAL: terminating connection due to administrator command 2025-01-31 07:57:11.136 UTC client backend[20247] pg_regress/query_cancel ERROR: canceling statement due to statement timeout 2025-01-31 07:57:11.136 UTC client backend[20247] pg_regress/query_cancel STATEMENT: SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d; 2025-01-31 07:57:11.138 UTC client backend[20248] fdw_conn_check ERROR: canceling statement due to user request 2025-01-31 07:57:11.138 UTC client backend[20248] fdw_conn_check STATEMENT: FETCH 100 FROM c2 2025-01-31 07:57:11.141 UTC postmaster[20167] LOG: received fast shutdown request 2025-01-31 07:57:11.141 UTC postmaster[20167] LOG: aborting any active transactions TRAP: failed Assert("(remainMask.mask | targetMask.mask) == BTYPE_MASK_ALL.mask"), File: "../src/backend/postmaster/postmaster.c", Line: 2951, PID: 20167 0xaa7bb2 at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres 0x8a0234 at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres 0x89e215 at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres 0x89d524 at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres