aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorNathan Bossart <nathan@postgresql.org>2024-07-01 10:18:26 -0500
committerNathan Bossart <nathan@postgresql.org>2024-07-01 10:18:26 -0500
commit6e16b1e42003d811562d30b572ac3972238e2957 (patch)
treec9d788526c1f8f072d8512c5fa937a6af9881612 /src/backend/tcop/postgres.c
parent3fb59e789dd9f21610101d1ec106ad58095e24f3 (diff)
downloadpostgresql-6e16b1e42003d811562d30b572ac3972238e2957.tar.gz
postgresql-6e16b1e42003d811562d30b572ac3972238e2957.zip
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
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions