Re: pg_upgrade on high number tables database issues - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade on high number tables database issues
Date
Msg-id 20140311011336.GA6658@momjian.us
Whole thread Raw
In response to Re: pg_upgrade on high number tables database issues  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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 inmlti-statement transactions that hold many locks; it
isparticularlyuseful for <application>pg_dump</>.
 

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Cleaner build output when not much has changed
Next
From: Peter Geoghegan
Date:
Subject: Re: jsonb and nested hstore