aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-02-18 12:23:40 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2015-02-18 12:23:40 -0500
commit297b2c1ef9878f84a9951beadf831ef390227238 (patch)
tree2713533d2598eb62bb0410d3086c9a4b0ca19c6f /src/backend/access/gist
parent0e7e355f27302b62af3e1add93853ccd45678443 (diff)
downloadpostgresql-297b2c1ef9878f84a9951beadf831ef390227238.tar.gz
postgresql-297b2c1ef9878f84a9951beadf831ef390227238.zip
Fix placement of "SET row_security" command issuance in pg_dump.
Somebody apparently threw darts at the code to decide where to insert these. They certainly didn't proceed by adding them where other similar SETs were handled. This at least broke pg_restore, and perhaps other use-cases too.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions