aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-12-31 12:47:57 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-12-31 12:47:57 -0500
commit3e6e86abca0138abd7265306beb6346dc2d9e221 (patch)
treed3c10dbe007713513d8477f65a1d6f1d4cb1fed0 /src/backend/access/gist/gistxlog.c
parentd5e8930f50e31d836d84b353b9dadedd5007bb70 (diff)
downloadpostgresql-3e6e86abca0138abd7265306beb6346dc2d9e221.tar.gz
postgresql-3e6e86abca0138abd7265306beb6346dc2d9e221.zip
pg_dump: avoid unsafe function calls in getPolicies().
getPolicies() had the same disease I fixed in other places in commit e3fcbbd62, i.e., it was calling pg_get_expr() for expressions on tables that we don't necessarily have lock on. To fix, restrict the query to only collect interesting rows, rather than doing the filtering on the client side. Like the previous patch, apply to HEAD only for now. Discussion: https://postgr.es/m/2273648.1634764485@sss.pgh.pa.us Discussion: https://postgr.es/m/7d7eb6128f40401d81b3b7a898b6b4de@W2012-02.nidsa.loc
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions