Add option -N/--no-sync to pg_upgrade
authorMichael Paquier <michael@paquier.xyz>
Sat, 18 Dec 2021 07:18:45 +0000 (16:18 +0900)
committerMichael Paquier <michael@paquier.xyz>
Sat, 18 Dec 2021 07:18:45 +0000 (16:18 +0900)
commit3d5ffccb6df323f528cf870c26d0d0517ffe3eaa
tree696c88d229622f37bdb4248678a5033437b6d36c
parent944dc45d1b633c4d612cdff9f15153ed609eaa35
Add option -N/--no-sync to pg_upgrade

This is an option consistent with what the other tools of src/bin/
(pg_checksums, pg_dump, pg_rewind and pg_basebackup) provide which is
useful for leveraging the I/O effort when testing things.  This is not
to be used in a production environment.

All the regression tests of pg_upgrade are updated to use this new
option.  This happens to cut at most a couple of seconds in environments
constrained on I/O, by avoiding a flush of data folder for the new
cluster upgraded.

Author: Michael Paquier
Reviewed-by: Peter Eisentraut
Discussion: https://postgr.es/m/YbrhzuBmBxS/DkfX@paquier.xyz
doc/src/sgml/ref/pgupgrade.sgml
src/bin/pg_upgrade/option.c
src/bin/pg_upgrade/pg_upgrade.c
src/bin/pg_upgrade/pg_upgrade.h
src/bin/pg_upgrade/test.sh
src/tools/msvc/vcregress.pl