pgsql: Doc: clarify locking requirements for ALTER TABLE ADD FOREIGN KE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: clarify locking requirements for ALTER TABLE ADD FOREIGN KE
Date: 2020-04-10 17:13:15
Message-ID: E1jMxDP-0000bv-9b@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: clarify locking requirements for ALTER TABLE ADD FOREIGN KEY.

The docs explained that a SHARE ROW EXCLUSIVE lock is needed on the
referenced table, but failed to say the same about the table being
altered. Since the page says that ACCESS EXCLUSIVE lock is taken
unless otherwise stated, this left readers with the wrong conclusion.

Discussion: https://postgr.es/m/834603375.3470346.1586482852542@mail.yahoo.com

Branch
------
REL9_5_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2cab4ad81bcb44ccd6591ed1fb54495c7301b42d

Modified Files
--------------
doc/src/sgml/ref/alter_table.sgml | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2020-04-10 21:48:21 Re: pgsql: doc: add examples of creative use of unique expression indexes
Previous Message Tom Lane 2020-04-10 16:00:40 pgsql: Suppress unused-variable warning.