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:34:20 +0000 (00:34 +0900)
commit4988d7e96953ac858563e225079b6992810aab22
treecd7d32693ac56ab1212e9d6fbd4260fcf2b00662
parentc5060c15037e1d45fab78a341cff28f139f2163d
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