Add note about access permission checks by inherited TRUNCATE and LOCK TABLE.
authorFujii Masao <[email protected]>
Thu, 6 Feb 2020 15:33:11 +0000 (00:33 +0900)
committerFujii Masao <[email protected]>
Thu, 6 Feb 2020 15:45:38 +0000 (00:45 +0900)
commitbf1840255123d90e777c72341d36149d09bef0e5
tree6b459d73e0c771df55429f6e52d51809f8de27a6
parentd034ab0bb2ae9300e91f9272abd4872bf53ce8d7
Add note about access permission checks by inherited TRUNCATE and LOCK TABLE.

Inherited queries perform access permission checks on the parent
table only. But there are two exceptions to this rule in v12 or before;
TRUNCATE and LOCK TABLE commands through a parent table check
the permissions on not only the parent table but also the children
tables. Previously these exceptions were not documented.

This commit adds the note about these exceptions, into the document.

Back-patch to v9.4. But we don't apply this commit to the master
because commit e6f1e560e4 already got rid of the exception about
inherited TRUNCATE and upcoming commit will do for the exception
about inherited LOCK TABLE.

Author: Amit Langote
Reviewed-by: Fujii Masao
Discussion: https://postgr.es/m/CA+HiwqHfTnMU6SUkyHxCmpHUKk7ERLHCR3vZVq19ZOQBjPBLmQ@mail.gmail.com
doc/src/sgml/ddl.sgml