aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2018-07-07 08:10:10 +0900
committerMichael Paquier <michael@paquier.xyz>2018-07-07 08:10:10 +0900
commiteb270b00b2d60e751545d4b808642395c901b668 (patch)
treeb3ad9dcc273eaae60cd446398d2404d72552d8ad /contrib/postgres_fdw/postgres_fdw.c
parent2e78c5b522a91c7893decd92d6f5b31fef0027bd (diff)
downloadpostgresql-eb270b00b2d60e751545d4b808642395c901b668.tar.gz
postgresql-eb270b00b2d60e751545d4b808642395c901b668.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 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions