diff options
author | Michael Paquier <michael@paquier.xyz> | 2018-07-07 08:10:32 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2018-07-07 08:10:32 +0900 |
commit | 0e4a46670e3a731eae177d8fa961f97b89298922 (patch) | |
tree | 48ad1b0c82ccd659b08dbe4ca85af0172c22bc9f /src/backend/utils/adt/tsquery_gist.c | |
parent | d89348976c51952293ffe35845c372ffa7e93b47 (diff) | |
download | postgresql-0e4a46670e3a731eae177d8fa961f97b89298922.tar.gz postgresql-0e4a46670e3a731eae177d8fa961f97b89298922.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/utils/adt/tsquery_gist.c')
0 files changed, 0 insertions, 0 deletions