From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Add note in pg_rewind documentation about read-only files |
Date: | 2018-07-06 23:12:06 |
Message-ID: | E1fbZtW-0003JB-EZ@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Add note in pg_rewind documentation about read-only files
When performing pg_rewind, the presence of a read-only file which is not
accessible for writes will cause a failure while processing. This can
cause the control file of the target data folder to be truncated,
causing it to not be reusable with a successive run.
Also, when pg_rewind fails mid-flight, there is likely no way to be able
to recover the target data folder anyway, in which case a new base
backup is the best option. A note is added in the documentation as
well about.
Reported-by: Christian H.
Author: Michael Paquier
Reviewed-by: Andrew Dunstan
Discussion: https://postgr.es/m/20180104200633.17004.16377%40wrigleys.postgresql.org
Branch
------
REL_10_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/42303977916599074a96d760d645180fc8df9867
Modified Files
--------------
doc/src/sgml/ref/pg_rewind.sgml | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-07-07 09:42:57 | pgsql: Add separate error message for procedure does not exist |
Previous Message | Peter Eisentraut | 2018-07-06 21:38:26 | pgsql: Fix assert in nested SQL procedure call |