2025-01-28 23:48:03.478 UTC postmaster[20701] LOG:  starting PostgreSQL 18devel on x86_64-freebsd, compiled by clang-17.0.6, 64-bit
2025-01-28 23:48:03.478 UTC postmaster[20701] LOG:  listening on Unix socket "/tmp/pg_regress-opJuAP/.s.PGSQL.40058"
2025-01-28 23:48:03.479 UTC startup[20704] LOG:  database system was shut down at 2025-01-28 23:48:03 UTC
2025-01-28 23:48:03.481 UTC postmaster[20701] LOG:  database system is ready to accept connections
2025-01-28 23:48:03.573 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  column name must be qualified
2025-01-28 23:48:03.573 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON COLUMN dummy_seclabel_tbl1 IS 'unclassified';
2025-01-28 23:48:03.573 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  '...invalid label...' is not a valid security label
2025-01-28 23:48:03.573 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS '...invalid label...';
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  security label provider "unknown_seclabel" is not loaded
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL FOR 'unknown_seclabel' ON TABLE dummy_seclabel_tbl1 IS 'classified';
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  must be owner of table dummy_seclabel_tbl2
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl2 IS 'unclassified';
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  only superuser can set 'secret' label
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS 'secret';
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  relation "dummy_seclabel_tbl3" does not exist
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl3 IS 'unclassified';
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  must be owner of table dummy_seclabel_tbl1
2025-01-28 23:48:03.574 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS 'unclassified';
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  '...invalid label...' is not a valid security label
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user3 IS '...invalid label...';
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  security label provider "unknown_seclabel" is not loaded
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL FOR 'unknown_seclabel' ON ROLE regress_dummy_seclabel_user1 IS 'unclassified';
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  only superuser can set 'secret' label
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user3 IS 'secret';
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  role "regress_dummy_seclabel_user4" does not exist
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user4 IS 'unclassified';
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel ERROR:  permission denied
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel DETAIL:  The current user must have the CREATEROLE attribute.
2025-01-28 23:48:03.575 UTC client backend[20712] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user2 IS 'unclassified';
2025-01-28 23:48:03.576 UTC client backend[20712] pg_regress/dummy_seclabel WARNING:  "wal_level" is insufficient to publish logical changes
2025-01-28 23:48:03.576 UTC client backend[20712] pg_regress/dummy_seclabel HINT:  Set "wal_level" to "logical" before creating subscriptions.
2025-01-28 23:48:03.577 UTC client backend[20712] pg_regress/dummy_seclabel WARNING:  subscriptions created by regression test cases should have names starting with "regress_"
2025-01-28 23:48:03.577 UTC client backend[20712] pg_regress/dummy_seclabel WARNING:  subscription was created, but is not connected
2025-01-28 23:48:03.577 UTC client backend[20712] pg_regress/dummy_seclabel HINT:  To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription.
2025-01-28 23:48:03.606 UTC postmaster[20701] LOG:  received fast shutdown request
2025-01-28 23:48:03.606 UTC postmaster[20701] 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: 20701
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