From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Fix some documentation in pg_rewind |
Date: | 2019-04-05 01:39:36 |
Message-ID: | E1hCDpQ-0007wX-S1@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix some documentation in pg_rewind
A confusion which comes a lot from users is that it is necessary to
issue a checkpoint on a freshly-promoted standby so as its control file
has up-to-date timeline information which is used by pg_rewind to
validate the operation. Let's document that properly. This is
back-patched down to 9.5 where pg_rewind has been introduced.
Author: Michael Paquier
Reviewed-by: Magnus Hagander
Discussion: https://postgr.es/m/CABUevEz5bpvbwVsYCaSMV80CBZ5-82nkMzbb+Bu=h1m=rLdn=g@mail.gmail.com
Backpatch-through: 9.5
Branch
------
REL9_6_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/7ff7c0d7b71c6ec638549c3accd54ccdddf3232e
Modified Files
--------------
doc/src/sgml/ref/pg_rewind.sgml | 9 +++++++++
1 file changed, 9 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2019-04-05 01:47:30 | Re: pgsql: Generated columns |
Previous Message | Andres Freund | 2019-04-05 00:43:50 | pgsql: Remove unused struct member, enforce multi_insert callback prese |