pgsql: Fix --dry-run mode of pg_rewind

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix --dry-run mode of pg_rewind
Date: 2019-10-04 00:16:56
Message-ID: E1iGBHE-0000Zg-1c@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix --dry-run mode of pg_rewind

Even if --dry-run mode was specified, the control file was getting
updated, preventing follow-up runs of pg_rewind to work properly on the
target data folder. The origin of the problem came from the refactoring
done by ce6afc6.

Author: Alexey Kondratov
Discussion: https://postgr.es/m/7ca88204-3e0b-2f4c-c8af-acadc4b266e5@postgrespro.ru
Backpatch-through: 12

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c2e3b311d9ef85e99b04944e7e6f98e3a336de84

Modified Files
--------------
src/bin/pg_rewind/pg_rewind.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2019-10-04 03:08:07 Re: pgsql: pgbench: add --partitions and --partition-method options.
Previous Message Tom Lane 2019-10-03 21:34:49 pgsql: Avoid unnecessary out-of-memory errors during encoding conversio