| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade on high number tables database issues |
| Date: | 2014-03-11 01:13:36 |
| Message-ID: | 20140311011336.GA6658@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 in
mlti-statement transactions that hold many locks; it is
particularly useful for <application>pg_dump</>.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-03-11 01:19:45 | Re: jsonb and nested hstore |
| Previous Message | Alvaro Herrera | 2014-03-11 00:12:39 | Re: Cleaner build output when not much has changed |