aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2020-02-03 12:40:22 +0900
committerFujii Masao <fujii@postgresql.org>2020-02-03 12:40:22 +0900
commitea7857dddb54c371f70be7215ea3b72cb70265bf (patch)
treeca16deae8120ff753c3f02fd9a47726454f7fdc3 /src/backend/access/gist/gist.c
parent600387f5dd286d6ca72a578b09ef3765f45d95e6 (diff)
downloadpostgresql-ea7857dddb54c371f70be7215ea3b72cb70265bf.tar.gz
postgresql-ea7857dddb54c371f70be7215ea3b72cb70265bf.zip
Revert commit a5b652f3a0.
This commit reverts the fix "Make inherited TRUNCATE perform access permission checks on parent table only" only in the back branches. It's not hard to imagine that there are some applications expecting the old behavior and the fix breaks their security. To avoid this compatibility problem, we decided to apply the fix only in HEAD and revert it in all supported back branches. Discussion: https://postgr.es/m/21015.1580400165@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions