aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-06-17 18:19:21 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-06-17 18:19:21 -0400
commit32e5768390fe7c10230a1d02d9ee026461a609a9 (patch)
tree02c29d9f0abaaa8a3272274a8211aab1601b8f4c /src/backend/access/gist
parentf49b2eab23199229a322745b6480692056070301 (diff)
downloadpostgresql-32e5768390fe7c10230a1d02d9ee026461a609a9.tar.gz
postgresql-32e5768390fe7c10230a1d02d9ee026461a609a9.zip
Obtain table locks as soon as practical during pg_dump.
For some reason, when we (I) added table lock acquisition to pg_dump, we didn't think about making it happen as soon as possible after the start of the transaction. What with subsequent additions, there was actually quite a lot going on before we got around to that; which sort of defeats the purpose. Rearrange the order of calls in dumpSchema() to close the risk window as much as we easily can. Back-patch to all supported branches.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions