2025-01-18 18:37:49.514 GMT postmaster[7668] LOG:  starting PostgreSQL 18devel on x86_64-windows, compiled by msvc-19.29.30158, 64-bit
2025-01-18 18:37:49.515 GMT postmaster[7668] LOG:  listening on Unix socket "c:/cirrus/.s.PGSQL.40055"
2025-01-18 18:37:49.552 GMT startup[4556] LOG:  database system was shut down at 2025-01-18 18:33:55 GMT
2025-01-18 18:37:49.572 GMT client backend[5272] [unknown] FATAL:  the database system is starting up
2025-01-18 18:37:49.584 GMT postmaster[7668] LOG:  database system is ready to accept connections
2025-01-18 18:37:50.143 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  column name must be qualified
2025-01-18 18:37:50.143 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON COLUMN dummy_seclabel_tbl1 IS 'unclassified';
2025-01-18 18:37:50.144 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  '...invalid label...' is not a valid security label
2025-01-18 18:37:50.144 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS '...invalid label...';
2025-01-18 18:37:50.144 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  security label provider "unknown_seclabel" is not loaded
2025-01-18 18:37:50.144 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL FOR 'unknown_seclabel' ON TABLE dummy_seclabel_tbl1 IS 'classified';
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  must be owner of table dummy_seclabel_tbl2
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl2 IS 'unclassified';
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  only superuser can set 'secret' label
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS 'secret';
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  relation "dummy_seclabel_tbl3" does not exist
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl3 IS 'unclassified';
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  must be owner of table dummy_seclabel_tbl1
2025-01-18 18:37:50.145 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON TABLE dummy_seclabel_tbl1 IS 'unclassified';
2025-01-18 18:37:50.147 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  '...invalid label...' is not a valid security label
2025-01-18 18:37:50.147 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user3 IS '...invalid label...';
2025-01-18 18:37:50.147 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  security label provider "unknown_seclabel" is not loaded
2025-01-18 18:37:50.147 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL FOR 'unknown_seclabel' ON ROLE regress_dummy_seclabel_user1 IS 'unclassified';
2025-01-18 18:37:50.148 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  only superuser can set 'secret' label
2025-01-18 18:37:50.148 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user3 IS 'secret';
2025-01-18 18:37:50.148 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  role "regress_dummy_seclabel_user4" does not exist
2025-01-18 18:37:50.148 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user4 IS 'unclassified';
2025-01-18 18:37:50.148 GMT client backend[6904] pg_regress/dummy_seclabel ERROR:  permission denied
2025-01-18 18:37:50.148 GMT client backend[6904] pg_regress/dummy_seclabel DETAIL:  The current user must have the CREATEROLE attribute.
2025-01-18 18:37:50.148 GMT client backend[6904] pg_regress/dummy_seclabel STATEMENT:  SECURITY LABEL ON ROLE regress_dummy_seclabel_user2 IS 'unclassified';
2025-01-18 18:37:50.154 GMT client backend[6904] pg_regress/dummy_seclabel WARNING:  "wal_level" is insufficient to publish logical changes
2025-01-18 18:37:50.154 GMT client backend[6904] pg_regress/dummy_seclabel HINT:  Set "wal_level" to "logical" before creating subscriptions.
2025-01-18 18:37:50.157 GMT client backend[6904] pg_regress/dummy_seclabel WARNING:  subscription was created, but is not connected
2025-01-18 18:37:50.157 GMT client backend[6904] pg_regress/dummy_seclabel HINT:  To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription.
2025-01-18 18:37:50.252 GMT postmaster[7668] LOG:  received fast shutdown request
2025-01-18 18:37:50.252 GMT postmaster[7668] LOG:  aborting any active transactions
TRAP: failed Assert("(remainMask.mask | targetMask.mask) == BTYPE_MASK_ALL.mask"), File: "../src/backend/postmaster/postmaster.c", Line: 2909, PID: 7668
abort() has been called