| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Alpha Shuro <alphashuro(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: (docs): add missing info about ShareLocks |
| Date: | 2025-11-27 13:49:48 |
| Message-ID: | e1f76708f9824163a9dcc3c08b68a445c30a0bde.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, 2025-11-27 at 12:33 +0100, Alpha Shuro wrote:
> Ah thanks for pointing this out, I've moved it to the xact-locking page instead
I think that is too specific. You can see a session waiting for a SHARE
lock on a transaction whenever it is waiting for a row lock, since row
locks are not permanently stored in the shared memory lock table.
Rather than adding a paragraph about the specific incident that happened
to you, you should describe the general mechanism.
Some reading material:
https://www.cybertec-postgresql.com/en/row-locks-in-postgresql/
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Jackson | 2025-11-27 18:55:11 | Add Restart=on-failure To Example Systemd File |
| Previous Message | Alpha Shuro | 2025-11-27 11:33:42 | Re: (docs): add missing info about ShareLocks |