Re: pg_rewind vs superuser
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Michael Banck <mbanck@gmx.net>
Cc: Magnus Hagander <magnus@hagander.net>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2019-04-05T07:56:32Z
Lists: pgsql-hackers
On Fri, Apr 05, 2019 at 09:41:58AM +0200, Michael Banck wrote: > 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. The startup process requests a checkpoint since 9.3, and before that it was doing the checkpoint by itself (grep for fast_promoted and RequestCheckpoint() around line 7579 in xlog.c). This allows the recovery to finish much faster. > Could this be a problem for anything else besides pg_rewind? Not that I know of, at least not in the tree. > 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). We had a couple of reports on the matter over the past years. Perhaps we could use a big fat warning but that feels a bit overdoing it. -- 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