mirror of https://github.com/postgres/postgres
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.REL8_4_STABLE
parent
f49b2eab23
commit
32e5768390
Loading…
Reference in new issue