BUG #18331: Why is the session lock (DEFAULT_LOCKMETHOD) not automatically released during process exit? - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #18331: Why is the session lock (DEFAULT_LOCKMETHOD) not automatically released during process exit?
Date
Msg-id 18331-b44b290d8d84d690@postgresql.org
Whole thread Raw
Responses Re: BUG #18331: Why is the session lock (DEFAULT_LOCKMETHOD) not automatically released during process exit?
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      18331
Logged by:          Why is the session lock (DEFAULT_LOCKMETHOD) not automatically released
during process exit?
Email address:      dafoer_x@163.com
PostgreSQL version: 16.1
Operating system:   centos_x86
Description:

I have some doubts about the implementation of session locks. Can you help
me clarify my questions?

The comment for the function LockRelationIdForSession mentions “It will be
removed  when UnlockRelationIdForSession() is called, or if an
ereport(ERROR) occurs,  or if the backend exits.”
However, the callback function ShutdownPostgres, which is triggered during
process exit, only cleans up locks of type USER_LOCKMETHOD. Is it possible
to automatically clean up session locks of type DEFAULT_LOCKMETHOD?

What risks or implications would there be if session locks of type
USER_LOCKMETHOD were automatically cleaned up during process exit?


pgsql-bugs by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Potential data loss due to race condition during logical replication slot creation
Next
From: PG Bug reporting form
Date:
Subject: BUG #18332: The conditional lock cannot be granted even if the process holds a stronger lock