aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2020-02-03 12:43:51 +0900
committerFujii Masao <fujii@postgresql.org>2020-02-03 12:43:51 +0900
commitdc06d0839a330d2a51ae10d1a168312b9daf7b0a (patch)
treef53c3df08fc424fbf670476e58919f5edd4504f8 /src/backend/access/gist/gistutil.c
parenta5f45c3dd3b569de07e9adf049e748c6a3a896a5 (diff)
downloadpostgresql-dc06d0839a330d2a51ae10d1a168312b9daf7b0a.tar.gz
postgresql-dc06d0839a330d2a51ae10d1a168312b9daf7b0a.zip
Revert commit 606f350de9.
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/gistutil.c')
0 files changed, 0 insertions, 0 deletions