Re: pg_rewind vs superuser
Michael Banck <mbanck@gmx.net>
From: Michael Banck <mbanck@gmx.net>
To: Michael Paquier <michael@paquier.xyz>
Cc: Magnus Hagander <magnus@hagander.net>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2019-04-05T07:41:58Z
Lists: pgsql-hackers
Hi, On Thu, Apr 04, 2019 at 01:11:29PM +0900, Michael Paquier wrote: > At the same time, let's also document that we need to use a checkpoint > on the promoted standby so as the control file gets a refresh and > pg_rewind is able to work properly. I promised that some time ago and > got reminded of that issue after seeing this thread... Is there a good reason why Postgres doesn't just issue a CHECKPOINT after promote itself? After all, this seems to be about making the control file having the proper content, which sounds like a good thing to have in general. Could this be a problem for anything else besides pg_rewind? This looks like a needless footgun waiting to happen, and just documenting it in pg_rewind's notes section looks a bit too hidden to me (but is certainly an improvement). Michael
Commits
-
Fix some documentation in pg_rewind
- 1f63f69c43b5 9.5.17 landed
- 7ff7c0d7b71c 9.6.13 landed
- 4b482e94a006 10.8 landed
- 064b3fcbdb19 11.3 landed
- bfc80683ce51 12.0 landed