From: Alpha Shuro <alphashuro@gmail.com>
Content-Type: multipart/mixed;
	boundary="Apple-Mail=_46F6913A-B0C3-4D66-AF2D-B1E716BF8DE4"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: (docs): add missing info about ShareLocks
Message-Id: <4274DCF3-177F-43D8-8547-90B8540B6619@gmail.com>
Date: Sat, 22 Nov 2025 09:07:01 +0100
To: pgsql-docs@lists.postgresql.org
Archived-At: 
 <https://www.postgresql.org/message-id/4274DCF3-177F-43D8-8547-90B8540B6619%40gmail.com>
Precedence: bulk


--Apple-Mail=_46F6913A-B0C3-4D66-AF2D-B1E716BF8DE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hello

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?


--Apple-Mail=_46F6913A-B0C3-4D66-AF2D-B1E716BF8DE4
Content-Disposition: attachment;
	filename=0001-document-ShareLock-behaviour-when-using-a-deferred-u.patch
Content-Type: application/octet-stream;
	x-unix-mode=0644;
	name="0001-document-ShareLock-behaviour-when-using-a-deferred-u.patch"
Content-Transfer-Encoding: quoted-printable

=46rom=2080741b41d6ff09fdd395775f87b99098b589c16e=20Mon=20Sep=2017=20=
00:00:00=202001=0AFrom:=20Alpha=20Shuro=20<alphashuro@gmail.com>=0ADate:=20=
Wed,=2015=20Oct=202025=2017:55:05=20+0200=0ASubject:=20[PATCH]=20=
document=20ShareLock=20behaviour=20when=20using=20a=20deferred=20unique=0A=
=20index=0A=0AThe=20logs=20that=20were=20printed=20by=20Postgres=0Awhen=20=
enforcing=20deferred=20unique=20indexes=20were=20misleading.=0A=0AThis=20=
change=20should=20make=20it=20easier=20to=20understand=20or=20=
investigate=0Awhen=20users=20see=20the=20`waits=20for=20ShareLock`=20log=20=
entry=0A---=0A=20doc/src/sgml/mvcc.sgml=20|=205=20+++++=0A=201=20file=20=
changed,=205=20insertions(+)=0A=0Adiff=20--git=20=
a/doc/src/sgml/mvcc.sgml=20b/doc/src/sgml/mvcc.sgml=0Aindex=20=
049ee75a4ba..4e36c59776a=20100644=0A---=20a/doc/src/sgml/mvcc.sgml=0A+++=20=
b/doc/src/sgml/mvcc.sgml=0A@@=20-1016,6=20+1016,11=20@@=20ERROR:=20=20=
could=20not=20serialize=20access=20due=20to=20read/write=20dependencies=20=
among=20transact=0A=20=20=20=20=20=20=20=20=20<para>=0A=20=20=20=20=20=20=
=20=20=20=20Acquired=20by=20<command>CREATE=20INDEX</command>=0A=20=20=20=
=20=20=20=20=20=20=20(without=20<option>CONCURRENTLY</option>).=0A+=0A+=20=
=20=20=20=20=20=20=20=20It=20is=20also=20acquired=20when=20enforcing=20a=20=
DEFERRED=20UNIQUE=20INDEX:=0A+=20=20=20=20=20=20=20=20=20If=20a=20=
transaction=20detects=20another=20transaction=20that=20might=20cause=0A+=20=
=20=20=20=20=20=20=20=20a=20potential=20conflict,=20it=20waits=20for=20=
the=20other=20transaction=20to=20complete,=0A+=20=20=20=20=20=20=20=20=20=
by=20acquiring=20a=20ShareLock=20on=20the=20other=20transaction's=20=
transaction=20id.=0A=20=20=20=20=20=20=20=20=20</para>=0A=20=20=20=20=20=20=
=20=20</listitem>=0A=20=20=20=20=20=20=20</varlistentry>=0A--=20=0A=
2.51.0=0A=0A=

--Apple-Mail=_46F6913A-B0C3-4D66-AF2D-B1E716BF8DE4--