Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers@postgresql.org
Date: 2024-05-09T19:34:25Z
Lists: pgsql-hackers
On Thu, May 09, 2024 at 09:03:56AM +0900, Michael Paquier wrote: > +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. I don't see a strong need to back-patch this, if for no other reason than it seems to have gone unnoticed for 7 major versions. Plus, based on my admittedly limited testing, this is unlikely to provide significant improvements. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
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