pgsql: Skip pg_database.dathasloginevt cleanup on standby

From: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Skip pg_database.dathasloginevt cleanup on standby
Date: 2026-05-26 23:46:30
Message-ID: E1wS1Ti-001GYD-0d@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Skip pg_database.dathasloginevt cleanup on standby

EventTriggerOnLogin() tries to clear pg_database.dathasloginevt when
the database no longer has any login event triggers but the flag is
still set. To make that safe against concurrent flag setters, it
takes a conditional AccessExclusiveLock on the database object.

On a hot standby, that lock acquisition fails outright with

FATAL: cannot acquire lock mode AccessExclusiveLock on database
objects while recovery is in progress

because LockAcquireExtended() refuses locks stronger than
RowExclusiveLock on database objects during recovery. The standby
already replays the flag's value from the primary, so the dangling
flag is the result of replaying a state in which the primary had
already dropped its login event triggers but not yet run a login
event trigger pass to clear the flag. Any session connecting to the
standby in that window therefore fails to connect.

Skip the cleanup on a standby. The flag will be cleared via WAL
replay once the primary clears it on its side.

Add a recovery TAP test that reproduces the original report: create
and drop a login event trigger on the primary in one session, wait
for the standby to replay, then verify that a fresh connection to
the standby succeeds.

Backpatch to v17, where the login event triggers were introduced.

Author: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Reported-by: Egor Chindyaskin <kyzevan23(at)mail(dot)ru>
Reviewed-by: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Reviewed-by: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Discussion: https://postgr.es/m/19488-d7ccfca2bf6b74b0%40postgresql.org
Backpatch-through: 17

Branch
------
REL_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/4a375527a19545dff0321349c42659e5f097d94b

Modified Files
--------------
src/backend/commands/event_trigger.c | 10 +-
src/test/recovery/meson.build | 3 +-
.../recovery/t/053_standby_login_event_trigger.pl | 125 +++++++++++++++++++++
3 files changed, 136 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2026-05-27 00:10:01 pgsql: Clean up 019_replslot_limit.pl comments
Previous Message Alexander Korotkov 2026-05-26 23:46:29 pgsql: Skip pg_database.dathasloginevt cleanup on standby