2025-01-28 23:43:56.520 UTC postmaster[20104] LOG:  starting PostgreSQL 18devel on x86_64-freebsd, compiled by clang-17.0.6, 64-bit
2025-01-28 23:43:56.520 UTC postmaster[20104] LOG:  listening on Unix socket "/tmp/pg_regress-MqR5mL/.s.PGSQL.40041"
2025-01-28 23:43:56.522 UTC startup[20107] LOG:  database system was shut down at 2025-01-28 23:43:56 UTC
2025-01-28 23:43:56.524 UTC postmaster[20104] LOG:  database system is ready to accept connections
2025-01-28 23:43:56.656 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  parameter "extensions" must be a list of extension names
2025-01-28 23:43:56.656 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  ALTER SERVER testserver1 OPTIONS (ADD extensions 'foo; bar');
2025-01-28 23:43:56.656 UTC client backend[20115] pg_regress/postgres_fdw WARNING:  extension "foo" is not installed
2025-01-28 23:43:56.656 UTC client backend[20115] pg_regress/postgres_fdw WARNING:  extension "bar" is not installed
2025-01-28 23:43:56.657 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  invalid option "sslmode"
2025-01-28 23:43:56.657 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  ALTER USER MAPPING FOR public SERVER testserver1
		OPTIONS (ADD sslmode 'require');
2025-01-28 23:43:56.674 UTC client backend[20117] [unknown] FATAL:  database "no such database" does not exist
2025-01-28 23:43:56.674 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  could not connect to server "loopback"
2025-01-28 23:43:56.674 UTC client backend[20115] pg_regress/postgres_fdw DETAIL:  connection to server on socket "/tmp/pg_regress-MqR5mL/.s.PGSQL.40041" failed: FATAL:  database "no such database" does not exist
2025-01-28 23:43:56.674 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  SELECT c3, c4 FROM ft1 ORDER BY c3, c1 LIMIT 1;
2025-01-28 23:43:56.683 UTC client backend[20119] [unknown] FATAL:  role "no such user" does not exist
2025-01-28 23:43:56.683 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  could not connect to server "loopback"
2025-01-28 23:43:56.683 UTC client backend[20115] pg_regress/postgres_fdw DETAIL:  connection to server on socket "/tmp/pg_regress-MqR5mL/.s.PGSQL.40041" failed: FATAL:  role "no such user" does not exist
2025-01-28 23:43:56.683 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  SELECT c3, c4 FROM ft1 ORDER BY c3, c1 LIMIT 1;
2025-01-28 23:43:56.700 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  cannot add relation "ft1" to publication
2025-01-28 23:43:56.700 UTC client backend[20115] pg_regress/postgres_fdw DETAIL:  This operation is not supported for foreign tables.
2025-01-28 23:43:56.700 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  CREATE PUBLICATION testpub_ftbl FOR TABLE ft1;
2025-01-28 23:43:56.781 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  access to non-system foreign table is restricted
2025-01-28 23:43:56.781 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  SELECT * from ft1 where c1 < 1;
2025-01-28 23:43:56.781 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  access to non-system foreign table is restricted
2025-01-28 23:43:56.781 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  INSERT INTO ft1 (c1) VALUES (1);
2025-01-28 23:43:56.782 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  access to non-system foreign table is restricted
2025-01-28 23:43:56.782 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  DELETE FROM ft1 WHERE c1 = 1;
2025-01-28 23:43:56.782 UTC client backend[20115] pg_regress/postgres_fdw ERROR:  access to non-system foreign table is restricted
2025-01-28 23:43:56.782 UTC client backend[20115] pg_regress/postgres_fdw STATEMENT:  TRUNCATE ft1;
2025-01-28 23:43:57.657 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  user mapping not found for user "regress_view_owner_another", server "loopback"
2025-01-28 23:43:57.657 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  EXPLAIN (VERBOSE, COSTS OFF) SELECT * FROM v4;
2025-01-28 23:43:57.657 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  user mapping not found for user "regress_view_owner_another", server "loopback"
2025-01-28 23:43:57.657 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  EXPLAIN (VERBOSE, COSTS OFF) SELECT * FROM (SELECT * FROM v4 UNION ALL SELECT * FROM v4);
2025-01-28 23:43:58.087 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  "reindex_foreign" is not a table or materialized view
2025-01-28 23:43:58.087 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  REINDEX TABLE reindex_foreign;
2025-01-28 23:43:58.087 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  "reindex_foreign" is not a table or materialized view
2025-01-28 23:43:58.087 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  REINDEX TABLE CONCURRENTLY reindex_foreign;
2025-01-28 23:43:58.095 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid input syntax for type integer: "foo"
2025-01-28 23:43:58.095 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  column "x8" of foreign table "ftx"
2025-01-28 23:43:58.095 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT * FROM ft1 ftx(x1,x2,x3,x4,x5,x6,x7,x8) WHERE x1 = 1;
2025-01-28 23:43:58.097 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid input syntax for type integer: "foo"
2025-01-28 23:43:58.097 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  column "x8" of foreign table "ftx"
2025-01-28 23:43:58.097 UTC client backend[20122] 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-28 23:43:58.101 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid input syntax for type integer: "foo"
2025-01-28 23:43:58.101 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  whole-row reference to foreign table "ftx"
2025-01-28 23:43:58.101 UTC client backend[20122] 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-28 23:43:58.104 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid input syntax for type integer: "foo"
2025-01-28 23:43:58.104 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  processing expression at position 2 in select list
2025-01-28 23:43:58.104 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT sum(c2), array_agg(c8) FROM ft1 GROUP BY c8;
2025-01-28 23:43:58.108 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid input syntax for type integer: "foo"
2025-01-28 23:43:58.108 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  column "c8" of foreign table "ft1"
2025-01-28 23:43:58.108 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ANALYZE ft1;
2025-01-28 23:43:58.114 UTC client backend[20137] pg_regress ERROR:  operator does not exist: public.user_enum ~~ unknown at character 92
2025-01-28 23:43:58.114 UTC client backend[20137] pg_regress HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-01-28 23:43:58.114 UTC client backend[20137] 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-28 23:43:58.114 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  operator does not exist: public.user_enum ~~ unknown
2025-01-28 23:43:58.114 UTC client backend[20122] pg_regress/postgres_fdw HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-01-28 23:43:58.114 UTC client backend[20122] 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-28 23:43:58.114 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT * FROM ft1 WHERE c8 LIKE 'foo' LIMIT 1;
2025-01-28 23:43:58.115 UTC client backend[20137] pg_regress ERROR:  operator does not exist: public.user_enum ~~ unknown at character 92
2025-01-28 23:43:58.115 UTC client backend[20137] pg_regress HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-01-28 23:43:58.115 UTC client backend[20137] 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-28 23:43:58.115 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  operator does not exist: public.user_enum ~~ unknown
2025-01-28 23:43:58.115 UTC client backend[20122] pg_regress/postgres_fdw HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-01-28 23:43:58.115 UTC client backend[20122] 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-28 23:43:58.115 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT * FROM ft1 WHERE c8::text LIKE 'foo' LIMIT 1;
2025-01-28 23:43:58.117 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  syntax error at or near "ERROR" at character 1
2025-01-28 23:43:58.117 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ERROR OUT;
2025-01-28 23:43:58.119 UTC client backend[20137] pg_regress ERROR:  division by zero
2025-01-28 23:43:58.119 UTC client backend[20137] pg_regress STATEMENT:  FETCH 100 FROM c2
2025-01-28 23:43:58.119 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  division by zero
2025-01-28 23:43:58.119 UTC client backend[20122] 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-28 23:43:58.119 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT * FROM ft1 WHERE 1 / (c1 - 1) > 0;
2025-01-28 23:43:58.644 UTC client backend[20139] pg_regress ERROR:  duplicate key value violates unique constraint "t1_pkey"
2025-01-28 23:43:58.644 UTC client backend[20139] pg_regress DETAIL:  Key ("C 1")=(11) already exists.
2025-01-28 23:43:58.644 UTC client backend[20139] 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-28 23:43:58.644 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  duplicate key value violates unique constraint "t1_pkey"
2025-01-28 23:43:58.644 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Key ("C 1")=(11) already exists.
2025-01-28 23:43:58.644 UTC client backend[20122] 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-28 23:43:58.644 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO ft1(c1, c2) VALUES(11, 12);
2025-01-28 23:43:58.646 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-01-28 23:43:58.646 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO ft1(c1, c2) VALUES(11, 12) ON CONFLICT (c1, c2) DO NOTHING;
2025-01-28 23:43:58.647 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-01-28 23:43:58.647 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO ft1(c1, c2) VALUES(11, 12) ON CONFLICT (c1, c2) DO UPDATE SET c3 = 'ffg';
2025-01-28 23:43:58.648 UTC client backend[20139] pg_regress ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.648 UTC client backend[20139] pg_regress DETAIL:  Failing row contains (1111, -2, null, null, null, null, ft1       , null).
2025-01-28 23:43:58.648 UTC client backend[20139] 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-28 23:43:58.648 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.648 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (1111, -2, null, null, null, null, ft1       , null).
2025-01-28 23:43:58.648 UTC client backend[20122] 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-28 23:43:58.648 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO ft1(c1, c2) VALUES(1111, -2);
2025-01-28 23:43:58.650 UTC client backend[20139] pg_regress ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.650 UTC client backend[20139] 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-28 23:43:58.650 UTC client backend[20139] pg_regress STATEMENT:  UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1))
2025-01-28 23:43:58.650 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.650 UTC client backend[20122] 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-28 23:43:58.650 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  remote SQL command: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1))
2025-01-28 23:43:58.650 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  UPDATE ft1 SET c2 = -c2 WHERE c1 = 1;
2025-01-28 23:43:58.694 UTC client backend[20139] pg_regress ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.694 UTC client backend[20139] 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-28 23:43:58.694 UTC client backend[20139] pg_regress STATEMENT:  UPDATE "S 1"."T 1" SET c2 = (-2) WHERE ((c2 = 42)) AND (("C 1" = 10))
2025-01-28 23:43:58.694 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.694 UTC client backend[20122] 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-28 23:43:58.694 UTC client backend[20122] 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-28 23:43:58.694 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update ft2 set c2 = -2 where c2 = 42 and c1 = 10;
2025-01-28 23:43:58.752 UTC client backend[20139] pg_regress ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.752 UTC client backend[20139] pg_regress DETAIL:  Failing row contains (1111, -2, null, null, null, null, ft1       , null).
2025-01-28 23:43:58.752 UTC client backend[20139] 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-28 23:43:58.752 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.752 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (1111, -2, null, null, null, null, ft1       , null).
2025-01-28 23:43:58.752 UTC client backend[20122] 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-28 23:43:58.752 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO ft1(c1, c2) VALUES(1111, -2);
2025-01-28 23:43:58.754 UTC client backend[20139] pg_regress ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.754 UTC client backend[20139] 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-28 23:43:58.754 UTC client backend[20139] pg_regress STATEMENT:  UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1))
2025-01-28 23:43:58.754 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "T 1" violates check constraint "c2positive"
2025-01-28 23:43:58.754 UTC client backend[20122] 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-28 23:43:58.754 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  remote SQL command: UPDATE "S 1"."T 1" SET c2 = (- c2) WHERE (("C 1" = 1))
2025-01-28 23:43:58.754 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  UPDATE ft1 SET c2 = -c2 WHERE c1 = 1;
2025-01-28 23:43:58.777 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row violates check option for view "rw_view"
2025-01-28 23:43:58.777 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (10, 5).
2025-01-28 23:43:58.777 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO rw_view VALUES (0, 5);
2025-01-28 23:43:58.782 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row violates check option for view "rw_view"
2025-01-28 23:43:58.782 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (20, 20).
2025-01-28 23:43:58.782 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  UPDATE rw_view SET b = b + 5;
2025-01-28 23:43:58.791 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row violates check option for view "rw_view"
2025-01-28 23:43:58.791 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (10, 5).
2025-01-28 23:43:58.791 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO rw_view VALUES (0, 15), (0, 5);
2025-01-28 23:43:58.816 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row violates check option for view "rw_view"
2025-01-28 23:43:58.816 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (10, 5).
2025-01-28 23:43:58.816 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO rw_view VALUES (0, 5);
2025-01-28 23:43:58.823 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row violates check option for view "rw_view"
2025-01-28 23:43:58.823 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (20, 20).
2025-01-28 23:43:58.823 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  UPDATE rw_view SET b = b + 5;
2025-01-28 23:43:58.834 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row violates check option for view "rw_view"
2025-01-28 23:43:58.834 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (10, 5).
2025-01-28 23:43:58.834 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  INSERT INTO rw_view VALUES (0, 15), (0, 5);
2025-01-28 23:43:59.166 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  WHERE CURRENT OF is not supported for this table type
2025-01-28 23:43:59.166 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update bar set f2 = null where current of c;
2025-01-28 23:43:59.240 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot execute MERGE on relation "remp1"
2025-01-28 23:43:59.240 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  This operation is not supported for foreign tables.
2025-01-28 23:43:59.240 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  merge into itrtest using (select 1, 'foo') as source on (true)
	  when matched then do nothing;
2025-01-28 23:43:59.244 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-01-28 23:43:59.244 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  insert into itrtest values (1, 'bar') on conflict (a) do nothing;
2025-01-28 23:43:59.244 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-01-28 23:43:59.244 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  insert into itrtest values (1, 'bar') on conflict (a) do update set b = excluded.b;
2025-01-28 23:43:59.280 UTC client backend[20145] pg_regress ERROR:  new row for relation "loct" violates check constraint "loct_a_check"
2025-01-28 23:43:59.280 UTC client backend[20145] pg_regress DETAIL:  Failing row contains (2, foo).
2025-01-28 23:43:59.280 UTC client backend[20145] pg_regress STATEMENT:  UPDATE public.loct SET a = 2 WHERE ((b = 'foo')) RETURNING a, b
2025-01-28 23:43:59.280 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "loct" violates check constraint "loct_a_check"
2025-01-28 23:43:59.280 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (2, foo).
2025-01-28 23:43:59.280 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  remote SQL command: UPDATE public.loct SET a = 2 WHERE ((b = 'foo')) RETURNING a, b
2025-01-28 23:43:59.280 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update utrtest set a = 2 where b = 'foo' returning *;
2025-01-28 23:43:59.282 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot route tuples into foreign table to be updated "remp"
2025-01-28 23:43:59.282 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update utrtest set a = 1 where b = 'qux' returning *;
2025-01-28 23:43:59.294 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot route tuples into foreign table to be updated "remp"
2025-01-28 23:43:59.294 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update utrtest set a = 1 where a = 1 or a = 2 returning *;
2025-01-28 23:43:59.307 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot route tuples into foreign table to be updated "remp"
2025-01-28 23:43:59.307 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update utrtest set a = 1 returning *;
2025-01-28 23:43:59.315 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot route tuples into foreign table to be updated "remp"
2025-01-28 23:43:59.315 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update utrtest set a = 1 from (values (1), (2)) s(x) where a = s.x returning *;
2025-01-28 23:43:59.326 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot route tuples into foreign table to be updated "remp"
2025-01-28 23:43:59.326 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update utrtest set a = 3 returning *;
2025-01-28 23:43:59.329 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot route tuples into foreign table to be updated "remp"
2025-01-28 23:43:59.329 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  update utrtest set a = 3 from (values (2), (3)) s(x) where a = s.x returning *;
2025-01-28 23:43:59.387 UTC client backend[20147] pg_regress ERROR:  new row for relation "loc2" violates check constraint "loc2_f1positive"
2025-01-28 23:43:59.387 UTC client backend[20147] pg_regress DETAIL:  Failing row contains (-1, xyzzy).
2025-01-28 23:43:59.387 UTC client backend[20147] pg_regress STATEMENT:  INSERT INTO public.loc2(f1, f2) VALUES ($1, $2)
2025-01-28 23:43:59.387 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "loc2" violates check constraint "loc2_f1positive"
2025-01-28 23:43:59.387 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (-1, xyzzy).
2025-01-28 23:43:59.387 UTC client backend[20122] 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-28 23:43:59.387 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  copy rem2 from stdin;
2025-01-28 23:43:59.450 UTC client backend[20148] pg_regress ERROR:  new row for relation "loc2" violates check constraint "loc2_f1positive"
2025-01-28 23:43:59.450 UTC client backend[20148] pg_regress DETAIL:  Failing row contains (-1, xyzzy).
2025-01-28 23:43:59.450 UTC client backend[20148] pg_regress STATEMENT:  INSERT INTO public.loc2(f1, f2) VALUES ($1, $2)
2025-01-28 23:43:59.450 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  new row for relation "loc2" violates check constraint "loc2_f1positive"
2025-01-28 23:43:59.450 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Failing row contains (-1, xyzzy).
2025-01-28 23:43:59.450 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  remote SQL command: INSERT INTO public.loc2(f1, f2) VALUES ($1, $2)
	COPY rem2
2025-01-28 23:43:59.450 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  copy rem2 from stdin;
2025-01-28 23:43:59.504 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  foreign table "tru_ftable" does not allow truncates
2025-01-28 23:43:59.504 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  TRUNCATE tru_ftable;
2025-01-28 23:43:59.509 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  foreign table "tru_ftable" does not allow truncates
2025-01-28 23:43:59.509 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  TRUNCATE tru_ftable;
2025-01-28 23:43:59.510 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  foreign table "tru_ftable" does not allow truncates
2025-01-28 23:43:59.510 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  TRUNCATE tru_ftable;
2025-01-28 23:43:59.524 UTC client backend[20151] pg_regress ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-01-28 23:43:59.524 UTC client backend[20151] pg_regress DETAIL:  Table "tru_fk_table" references "tru_pk_table".
2025-01-28 23:43:59.524 UTC client backend[20151] pg_regress HINT:  Truncate table "tru_fk_table" at the same time, or use TRUNCATE ... CASCADE.
2025-01-28 23:43:59.524 UTC client backend[20151] pg_regress STATEMENT:  TRUNCATE public.tru_pk_table CONTINUE IDENTITY RESTRICT
2025-01-28 23:43:59.524 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-01-28 23:43:59.524 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Table "tru_fk_table" references "tru_pk_table".
2025-01-28 23:43:59.524 UTC client backend[20122] pg_regress/postgres_fdw HINT:  Truncate table "tru_fk_table" at the same time, or use TRUNCATE ... CASCADE.
2025-01-28 23:43:59.524 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  remote SQL command: TRUNCATE public.tru_pk_table CONTINUE IDENTITY RESTRICT
2025-01-28 23:43:59.524 UTC client backend[20122] 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-28 23:43:59.870 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  relation "t1" already exists
2025-01-28 23:43:59.870 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  importing foreign table "t1"
2025-01-28 23:43:59.870 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  IMPORT FOREIGN SCHEMA import_source FROM SERVER loopback INTO import_dest4;
2025-01-28 23:43:59.871 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  schema "nonesuch" is not present on foreign server "loopback"
2025-01-28 23:43:59.871 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  IMPORT FOREIGN SCHEMA nonesuch FROM SERVER loopback INTO import_dest4;
2025-01-28 23:43:59.871 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  schema "notthere" does not exist
2025-01-28 23:43:59.871 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  IMPORT FOREIGN SCHEMA nonesuch FROM SERVER loopback INTO notthere;
2025-01-28 23:43:59.871 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  server "nowhere" does not exist
2025-01-28 23:43:59.871 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  IMPORT FOREIGN SCHEMA nonesuch FROM SERVER nowhere INTO notthere;
2025-01-28 23:43:59.880 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  type "public.Colors" does not exist at character 137
2025-01-28 23:43:59.880 UTC client backend[20122] 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-28 23:43:59.880 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  importing foreign table "t5"
2025-01-28 23:43:59.880 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  IMPORT FOREIGN SCHEMA import_source LIMIT TO (t5)
	  FROM SERVER loopback INTO import_dest5;
2025-01-28 23:44:00.103 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  password or GSSAPI delegated credentials required
2025-01-28 23:44:00.103 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Non-superusers must delegate GSSAPI credentials, provide a password, or enable SCRAM pass-through in user mapping.
2025-01-28 23:44:00.103 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT 1 FROM ft1_nopw LIMIT 1;
2025-01-28 23:44:00.103 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid option "password"
2025-01-28 23:44:00.103 UTC client backend[20122] pg_regress/postgres_fdw HINT:  Perhaps you meant the option "passfile".
2025-01-28 23:44:00.103 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ALTER SERVER loopback_nopw OPTIONS (ADD password 'dummypw');
2025-01-28 23:44:00.107 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  password or GSSAPI delegated credentials required
2025-01-28 23:44:00.107 UTC client backend[20122] 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-28 23:44:00.107 UTC client backend[20122] 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-28 23:44:00.107 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT 1 FROM ft1_nopw LIMIT 1;
2025-01-28 23:44:00.107 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  password_required=false is superuser-only
2025-01-28 23:44:00.107 UTC client backend[20122] 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-28 23:44:00.107 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD password_required 'false');
2025-01-28 23:44:00.110 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  password or GSSAPI delegated credentials required
2025-01-28 23:44:00.110 UTC client backend[20122] 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-28 23:44:00.110 UTC client backend[20122] 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-28 23:44:00.110 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT 1 FROM ft1_nopw LIMIT 1;
2025-01-28 23:44:00.124 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  sslcert and sslkey are superuser-only
2025-01-28 23:44:00.124 UTC client backend[20122] 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-28 23:44:00.124 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD sslcert 'foo.crt');
2025-01-28 23:44:00.125 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  sslcert and sslkey are superuser-only
2025-01-28 23:44:00.125 UTC client backend[20122] 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-28 23:44:00.125 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ALTER USER MAPPING FOR CURRENT_USER SERVER loopback_nopw OPTIONS (ADD sslkey 'foo.key');
2025-01-28 23:44:00.126 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  password or GSSAPI delegated credentials required
2025-01-28 23:44:00.126 UTC client backend[20122] pg_regress/postgres_fdw DETAIL:  Non-superusers must delegate GSSAPI credentials, provide a password, or enable SCRAM pass-through in user mapping.
2025-01-28 23:44:00.126 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT 1 FROM ft1_nopw LIMIT 1;
2025-01-28 23:44:00.142 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  cannot PREPARE a transaction that has operated on postgres_fdw foreign tables
2025-01-28 23:44:00.142 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  PREPARE TRANSACTION 'fdw_tpc';
2025-01-28 23:44:00.142 UTC client backend[20122] pg_regress/postgres_fdw WARNING:  there is no transaction in progress
2025-01-28 23:44:00.149 UTC client backend[20158] fdw_retry_check FATAL:  terminating connection due to administrator command
2025-01-28 23:44:00.264 UTC client backend[20159] fdw_retry_check FATAL:  terminating connection due to administrator command
2025-01-28 23:44:00.372 UTC client backend[20122] 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-28 23:44:00.372 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  remote SQL command: SAVEPOINT s2
2025-01-28 23:44:00.372 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT 1 FROM ft1 LIMIT 1;
2025-01-28 23:44:00.403 UTC client backend[20122] pg_regress/postgres_fdw WARNING:  cannot close connection for server "loopback" because it is still in use
2025-01-28 23:44:00.404 UTC client backend[20122] pg_regress/postgres_fdw WARNING:  cannot close connection for server "loopback" because it is still in use
2025-01-28 23:44:00.404 UTC client backend[20122] pg_regress/postgres_fdw WARNING:  cannot close connection for server "loopback2" because it is still in use
2025-01-28 23:44:00.407 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  server "unknownserver" does not exist
2025-01-28 23:44:00.407 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT postgres_fdw_disconnect('unknownserver');
2025-01-28 23:44:00.671 UTC client backend[20170] fdw_retry_check ERROR:  relation "public.non_existent_table" does not exist at character 43
2025-01-28 23:44:00.671 UTC client backend[20170] fdw_retry_check STATEMENT:  DECLARE c3 CURSOR FOR
	SELECT a, b, c FROM public.non_existent_table
2025-01-28 23:44:00.671 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  relation "public.non_existent_table" does not exist
2025-01-28 23:44:00.671 UTC client backend[20122] pg_regress/postgres_fdw CONTEXT:  remote SQL command: SELECT a, b, c FROM public.non_existent_table
2025-01-28 23:44:00.671 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  SELECT * FROM async_pt;
2025-01-28 23:44:00.903 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid value for floating point option "fdw_startup_cost": 100$%$#$#
2025-01-28 23:44:00.903 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  CREATE SERVER inv_scst FOREIGN DATA WRAPPER postgres_fdw
		OPTIONS(fdw_startup_cost '100$%$#$#');
2025-01-28 23:44:00.903 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid value for floating point option "fdw_tuple_cost": 100$%$#$#
2025-01-28 23:44:00.903 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  CREATE SERVER inv_scst FOREIGN DATA WRAPPER postgres_fdw
		OPTIONS(fdw_tuple_cost '100$%$#$#');
2025-01-28 23:44:00.903 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid value for integer option "fetch_size": 100$%$#$#
2025-01-28 23:44:00.903 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  CREATE FOREIGN TABLE inv_fsz (c1 int )
		SERVER loopback OPTIONS (fetch_size '100$%$#$#');
2025-01-28 23:44:00.904 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid value for integer option "batch_size": 100$%$#$#
2025-01-28 23:44:00.904 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  CREATE FOREIGN TABLE inv_bsz (c1 int )
		SERVER loopback OPTIONS (batch_size '100$%$#$#');
2025-01-28 23:44:00.904 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid option "nonexistent"
2025-01-28 23:44:00.904 UTC client backend[20122] pg_regress/postgres_fdw HINT:  There are no valid options in this context.
2025-01-28 23:44:00.904 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ALTER FOREIGN DATA WRAPPER postgres_fdw OPTIONS (nonexistent 'fdw');
2025-01-28 23:44:00.995 UTC client backend[20122] pg_regress/postgres_fdw ERROR:  invalid value for string option "analyze_sampling": invalid
2025-01-28 23:44:00.995 UTC client backend[20122] pg_regress/postgres_fdw STATEMENT:  ALTER SERVER loopback OPTIONS (analyze_sampling 'invalid');
2025-01-28 23:44:01.011 UTC client backend[20181] fdw_conn_check FATAL:  terminating connection due to administrator command
2025-01-28 23:44:01.146 UTC client backend[20184] pg_regress/query_cancel ERROR:  canceling statement due to statement timeout
2025-01-28 23:44:01.146 UTC client backend[20184] pg_regress/query_cancel STATEMENT:  SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d;
2025-01-28 23:44:01.147 UTC client backend[20185] fdw_conn_check ERROR:  canceling statement due to user request
2025-01-28 23:44:01.147 UTC client backend[20185] fdw_conn_check STATEMENT:  FETCH 100 FROM c2
2025-01-28 23:44:01.151 UTC postmaster[20104] LOG:  received fast shutdown request
2025-01-28 23:44:01.151 UTC postmaster[20104] 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: 20104
0xaa7202 <ExceptionalCondition+0x72> at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres
0x89f9d4 <PostmasterStateMachine+0x5c4> at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres
0x89d9b5 <ServerLoop+0x465> at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres
0x89ccc4 <PostmasterMain+0x11c4> at /tmp/cirrus-ci-build/build/tmp_install//usr/local/pgsql/bin/postgres