Re: Further pg_upgrade analysis for many tables - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Further pg_upgrade analysis for many tables
Date
Msg-id CAMkU=1yP3x3ZZNMfYVOzxVEszM3OhVVASpGnXsEkU4=ODSzW3Q@mail.gmail.com
Whole thread Raw
In response to Re: Further pg_upgrade analysis for many tables  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Further pg_upgrade analysis for many tables  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Thu, Nov 8, 2012 at 7:25 PM, Bruce Momjian <bruce@momjian.us> wrote:
>
> I did some more research and realized that I was not using --schema-only
> like pg_upgrade uses.  With that setting, things look like this:
>
...

For profiling pg_dump in isolation, you should also specify
--binary-upgrade.  I was surprised that it makes a big difference,
slowing it down by about 2 fold.

Cheers,

Jeff



pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: Inadequate thought about buffer locking during hot standby replay
Next
From: Tom Lane
Date:
Subject: Re: Inadequate thought about buffer locking during hot standby replay