Re: pg_rewind vs superuser
От | Michael Banck |
---|---|
Тема | Re: pg_rewind vs superuser |
Дата | |
Msg-id | 20190405074158.GA31167@nighthawk.caipicrew.dd-dns.de обсуждение исходный текст |
Ответ на | Re: pg_rewind vs superuser (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: pg_rewind vs superuser
|
Список | 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
В списке pgsql-hackers по дате отправления: