From: | Will Mortensen <will(at)extrahop(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Marco Slot <marco(dot)slot(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, marco(at)citusdata(dot)com |
Subject: | Re: Exposing the lock manager's WaitForLockers() to SQL |
Date: | 2023-02-02 05:55:28 |
Message-ID: | CAMpnoC7sxT+snzsZTj0sRTqjTaDfaDLR-Pg+r=sdXnUZX0YYHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Here is a first attempt at a WIP patch. Sorry about the MIME type.
It doesn't take any locks on the tables, but I'm not super confident
that that's safe, so any input would be appreciated.
I omitted view support for simplicity, but if that seems like a
requirement I'll see about adding it. I assume we would need to take
AccessShareLock on views (and release it, per above).
If the syntax and behavior seem roughly correct I'll work on updating the docs.
The commit message at the beginning of the .patch has slightly more commentary.
Thanks for any and all feedback!
Attachment | Content-Type | Size |
---|---|---|
0001-Add-WAIT-ONLY-option-to-LOCK.patch | application/octet-stream | 20.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2023-02-02 05:57:44 | Re: Add progress reporting to pg_verifybackup |
Previous Message | Amit Kapila | 2023-02-02 05:53:30 | Re: Exit walsender before confirming remote flush in logical replication |