Re: optimizing pg_upgrade's once-in-each-database steps - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: optimizing pg_upgrade's once-in-each-database steps
Date
Msg-id 3b97ab8e295ec3db22baa2dfdd49073449ae1696.camel@j-davis.com
Whole thread Raw
In response to optimizing pg_upgrade's once-in-each-database steps  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: optimizing pg_upgrade's once-in-each-database steps
List pgsql-hackers
On Thu, 2024-05-16 at 16:16 -0500, Nathan Bossart wrote:
> I am posting this early to get thoughts on the general approach.  If
> we
> proceeded with this strategy, I'd probably create some generic
> tooling that
> each relevant step would provide a set of callback functions.

The documentation states:

"pg_dump -j uses multiple database connections; it connects to the
database once with the leader process and once again for each worker
job."

That might need to be adjusted.

How much complexity do you avoid by using async instead of multiple
processes?

Also, did you consider connecting once to each database and running
many queries? Most of those seem like just checks.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Underscore in positional parameters?
Next
From: Michael Paquier
Date:
Subject: Re: open items