Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall
Date
Msg-id ZjwS7KMcRq7YGvt5@paquier.xyz
Whole thread Raw
In response to Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall
List pgsql-hackers
On Wed, May 08, 2024 at 02:49:58PM -0400, Tom Lane wrote:
> Nathan Bossart <nathandbossart@gmail.com> writes:
>> Thanks for looking.  I noticed that the version check is unnecessary since
>> we always use the new binary's pg_dump[all], so I removed that in v2.
>
> +1

+1.  Could there be an argument in favor of a backpatch?  This is a
performance improvement, but one could also side that the addition of
sync support in pg_dump[all] has made that a regression that we'd
better fix because the flushes don't matter in this context.  They
also bring costs for no gain.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: ALTER EXTENSION SET SCHEMA versus dependent types
Next
From: David Rowley
Date:
Subject: Re: Expand applicability of aggregate's sortop optimization