diff options
| author | Michael Paquier <michael@paquier.xyz> | 2018-07-07 08:10:53 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2018-07-07 08:10:53 +0900 |
| commit | 378f78da86285aba98196201bf5db4eb6c5c0fed (patch) | |
| tree | 752ffb15100fad7a3cbb57858f3d1e0003492829 /src/backend/executor/nodeNestloop.c | |
| parent | 02bfd6d415bfacdf16a273420fd86c67189556ff (diff) | |
| download | postgresql-378f78da86285aba98196201bf5db4eb6c5c0fed.tar.gz postgresql-378f78da86285aba98196201bf5db4eb6c5c0fed.zip | |
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
Diffstat (limited to 'src/backend/executor/nodeNestloop.c')
0 files changed, 0 insertions, 0 deletions