From: Alpha Shuro <alphashuro@gmail.com>
Message-Id: <8E0BD202-AB51-4FE7-972A-D83838A29D8C@gmail.com>
Content-Type: multipart/mixed;
	boundary="Apple-Mail=_BE986CF0-2EBD-44FF-BA27-47E5C0471682"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: (docs): add missing info about ShareLocks
Date: Thu, 27 Nov 2025 12:33:42 +0100
In-Reply-To: <58e8295701c9e15c251ed608c5ed297688c785a2.camel@cybertec.at>
Cc: pgsql-docs@lists.postgresql.org
To: Laurenz Albe <laurenz.albe@cybertec.at>
References: <4274DCF3-177F-43D8-8547-90B8540B6619@gmail.com>
 <58e8295701c9e15c251ed608c5ed297688c785a2.camel@cybertec.at>
Archived-At: 
 <https://www.postgresql.org/message-id/8E0BD202-AB51-4FE7-972A-D83838A29D8C%40gmail.com>
Precedence: bulk


--Apple-Mail=_BE986CF0-2EBD-44FF-BA27-47E5C0471682
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Ah thanks for pointing this out, I've moved it to the xact-locking page =
instead


--Apple-Mail=_BE986CF0-2EBD-44FF-BA27-47E5C0471682
Content-Disposition: attachment;
	filename=document-ShareLock-when-using-deferred-unique.patch
Content-Type: application/octet-stream;
	x-unix-mode=0644;
	name="document-ShareLock-when-using-deferred-unique.patch"
Content-Transfer-Encoding: 7bit

diff --git a/doc/src/sgml/xact.sgml b/doc/src/sgml/xact.sgml
index 3aa7ee1383e..d753869cc88 100644
--- a/doc/src/sgml/xact.sgml
+++ b/doc/src/sgml/xact.sgml
@@ -102,6 +102,13 @@
    of multixact IDs (<literal>mxid</literal>;  see <xref
    linkend="vacuum-for-multixact-wraparound"/>).
   </para>
+
+  <para>
+   If there is a DEFERRED UNIQUE constraint on a row inserted in a transaction,
+   and there are multiple concurrent transactions inserting the same unique key,
+   the earlier transactions will wait for later transactions by
+   acquiring a <structfield>ShareLock</structfield> on the transaction ID.
+  </para>
  </sect1>
 
  <sect1 id="subxacts">

--Apple-Mail=_BE986CF0-2EBD-44FF-BA27-47E5C0471682
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> Den 22. nov. 2025 kl. 13.07 skrev Laurenz Albe =
<laurenz.albe@cybertec.at>:
>=20
> On Sat, 2025-11-22 at 09:07 +0100, Alpha Shuro wrote:
>> I had a production incident a few weeks ago while using deferred =
indexes, where
>> the Postgres docs lead me down the wrong path of investigation due to =
missing details.
>> Specifically, the docs implied that a `ShareLock` was only acquired =
when creating
>> indexes, but only after looking at the code did I learn that this =
lock is also
>> acquired when transactions are waiting for other transactions to =
complete.
>> I think this would be helpful to someone who might find themselves on =
the same path
>> in the future, and as I understand it this mailing list is the way to =
submit patches
>> to the docs?
>=20
> No, that is wrong.  This section is about table locks, and a lock on a =
transaction ID
> should, if anywhere, be documented elsewhere.  Actually, there is =
already something
> about transaction ID locks in =
https://www.postgresql.org/docs/current/xact-locking.html
>=20
> Perhaps you could improve that short documentation?
>=20
> Yours,
> Laurenz Albe
>=20
> PS: There are also SHARE locks on rows.


--Apple-Mail=_BE986CF0-2EBD-44FF-BA27-47E5C0471682--