Add --no-sync to pg_upgrade's uses of pg_dump and pg_dumpall.

Nathan Bossart <nathan@postgresql.org>

Commit: 6e16b1e42003d811562d30b572ac3972238e2957
Author: Nathan Bossart <nathan@postgresql.org>
Date: 2024-07-01T15:18:26Z
Releases: 18.0
Add --no-sync to pg_upgrade's uses of pg_dump and pg_dumpall.

There's no reason to ensure that the files pg_upgrade generates
with pg_dump and pg_dumpall have been written safely to disk.  If
there is a crash during pg_upgrade, the upgrade must be restarted
from the beginning; dump files left behind by previous pg_upgrade
attempts cannot be reused.

Reviewed-by: Peter Eisentraut, Tom Lane, Michael Paquier, Daniel Gustafsson
Discussion: https://postgr.es/m/20240503171348.GA1731524%40nathanxps13

Files

PathChange+/−
src/bin/pg_upgrade/dump.c modified +2 −2

Discussion