Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers@postgresql.org
Date: 2024-05-09T00:03:56Z
Lists: 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
Commits
-
Add --no-sync to pg_upgrade's uses of pg_dump and pg_dumpall.
- 6e16b1e42003 18.0 landed
-
Sync pg_dump and pg_dumpall output
- 96a7128b7b4c 10.0 cited