On Mon, Mar 10, 2014 at 08:12:20PM +0100, Pavel Stehule wrote:
> Remember pg_upgrade is using pg_dump, which then connecting to a
> backend, so passing that super-lock mode there is not ideal. The fixes
> in 9.3 improve locking in all user cases, not just upgrades.
>
>
>
> nice
FYI, the 9.3.0 release notes have all the details on pg_upgrade
improvements. This is the pg_dump fix:
Add per-resource-owner lock caches (Jeff Janes)
This speeds up lock bookkeeping at statement completion in
mlti-statement transactions that hold many locks; it is
particularly useful for <application>pg_dump</>.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
