Re: More performance improvements for pg_dump in binary upgrade mode

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: More performance improvements for pg_dump in binary upgrade mode
Date: 2024-05-15 20:21:36
Message-ID: 20240515202136.GA1432094@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 15, 2024 at 10:15:13PM +0200, Daniel Gustafsson wrote:
> With the typarray caching from the patch attached here added *and* Nathan's
> patch from [0] added:
>
> $ time ./bin/pg_dump --schema-only --quote-all-identifiers --binary-upgrade \
> --format=custom --file a postgres > /dev/null
>
> real 0m1.566s
> user 0m0.309s
> sys 0m0.080s
>
> The combination of these patches thus puts binary uphrade mode almost on par
> with a plain dump, which has the potential to make upgrades of large schemas
> faster. Parallel-parking this patch with Nathan's in the July CF, just wanted
> to type it up while it was fresh in my mind.

Nice! I'll plan on taking a closer look at this one. I have a couple
other ideas in-flight (e.g., parallelizing the once-in-each-database
operations with libpq's asynchronous APIs) that I'm hoping to post soon,
too. v18 should have a lot of good stuff for pg_upgrade...

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2024-05-15 20:22:43 Re: [DOC] Add detail regarding resource consumption wrt max_connections
Previous Message Robert Haas 2024-05-15 20:18:53 Re: add function argument names to regex* functions.