| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Robert Treat <rob(at)xzilla(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New docs chapter on Transaction Management and related changes |
| Date: | 2022-11-18 19:34:34 |
| Message-ID: | Y3feSlJgVFwA74Go@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 10, 2022 at 11:31:25AM +0000, Simon Riggs wrote:
> > That's not true. Transactions waiting for table-level locks are shown
> > waiting for a "relation" lock in both "pg_stat_activity" and "pg_locks".
>
> Agreed.
>
> Lock waits on table-locks are shown waiting for a lock type of
> <literal>relation</literal>,
> while lock waits on row-level locks are shown waiting for a lock type
> of <literal>transactionid</literal>.
> Table-level locks require only a virtualxid when the lock is less than an
> AccessExclusiveLock; in other cases an xid must be allocated.
Yeah, I went with more generic wording since the point seems to be that
sometimes xid and sometimes vxids are waited on.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-11-18 19:37:39 | Re: New docs chapter on Transaction Management and related changes |
| Previous Message | Bruce Momjian | 2022-11-18 19:33:26 | Re: New docs chapter on Transaction Management and related changes |