projects / users / gsingh / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 401418c) | patch
Doc: clarify locking requirements for ALTER TABLE ADD FOREIGN KEY.
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 10 Apr 2020 17:12:58 +0000 (13:12 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 10 Apr 2020 17:12:58 +0000 (13:12 -0400)
commitf333d35428c1cba8d35065b6dbb2dd46e18bd929
treeae2d1bb07c1a9637e800e78551df43c65debdb0atree
parent401418ca6a689f772cbfa1aedc7485cbbcde7a94commit | diff
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
doc/src/sgml/ref/alter_table.sgml diff | blob | blame | history
Postgres clone for personal branches