Re: Exposing the lock manager's WaitForLockers() to SQL - Mailing list pgsql-hackers

From Will Mortensen
Subject Re: Exposing the lock manager's WaitForLockers() to SQL
Date
Msg-id CAMpnoC7HU=4TiyakGgBBaGGXoJPqGPcTO7UKa+tqphjqzdCKRA@mail.gmail.com
Whole thread Raw
In response to Re: Exposing the lock manager's WaitForLockers() to SQL  (Will Mortensen <will@extrahop.com>)
List pgsql-hackers
I should add that the latest patches remove permissions checks because
pg_locks doesn't have any, and improve the commit messages. Hope I
didn't garble anything doing this late after the dev conference. :-)

Robert asked me about other existing functions that could be
leveraged, such as GetConflictingVirtualXIDs(), but I didn't see any
with close-enough semantics that handle fast-path locks as needed for
tables/relations.



pgsql-hackers by date:

Previous
From: Will Mortensen
Date:
Subject: Re: Exposing the lock manager's WaitForLockers() to SQL
Next
From: Aleksander Alekseev
Date:
Subject: Re: meson "experimental"?