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.
Branch
------
REL9_0_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/7975f2baa955397fbeb64b5301235ed1dd0f9be6
Modified Files
--------------
src/bin/pg_dump/common.c | 16 +++++++++++-----
1 files changed, 11 insertions(+), 5 deletions(-)
