Re: Pg_upgrade speed for many tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Pg_upgrade speed for many tables
Date
Msg-id 24050.1352147432@sss.pgh.pa.us
Whole thread Raw
In response to Re: Pg_upgrade speed for many tables  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Pg_upgrade speed for many tables  (Bruce Momjian <bruce@momjian.us>)
Re: Pg_upgrade speed for many tables  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Mon, Nov 5, 2012 at 9:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> BTW, does pg_upgrade run pg_restore in --single-transaction mode?
>> That would probably make synchronous_commit moot, at least for that
>> step.

> It doesn't use pg_restore at all - it uses the dump from pg_dumpall, which
> you can't reload with pg_restore.

Sorry, I should've said psql --single-transaction.  Although that isn't
going to work either given the presence of \connect commands in the
script.  I wonder whether pg_dumpall ought to have some sort of "one
transaction per database please" option.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Pg_upgrade speed for many tables
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCH] Prefetch index pages for B-Tree index scans