diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-06-17 18:19:09 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-06-17 18:19:09 -0400 |
| commit | a95cfd085df5f146d67390344b588629e0efa8f1 (patch) | |
| tree | a604613cc9f2bf34ef7b6cd5efb96969682b5344 /src/backend/access/gist/gist.c | |
| parent | 925079063fc429b94c52c5f9174c20157bc39e66 (diff) | |
| download | postgresql-a95cfd085df5f146d67390344b588629e0efa8f1.tar.gz postgresql-a95cfd085df5f146d67390344b588629e0efa8f1.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/gist.c')
0 files changed, 0 insertions, 0 deletions