Re: replay pause vs. standby promotion
От | Sergei Kornilov |
---|---|
Тема | Re: replay pause vs. standby promotion |
Дата | |
Msg-id | 796401585060307@vla3-bebe75876e15.qloud-c.yandex.net обсуждение исходный текст |
Ответ на | Re: replay pause vs. standby promotion (Fujii Masao <masao.fujii@oss.nttdata.com>) |
Ответы |
Re: replay pause vs. standby promotion
|
Список | pgsql-hackers |
Hello > I pushed the latest version of the patch. If you have further opinion > about immediate promotion, let's keep discussing that! Thank you! Honestly, I forgot that the promotion is documented in high-availability.sgml as: > Before failover, any WAL immediately available in the archive or in pg_wal will be > restored, but no attempt is made to connect to the master. I mistakenly thought that promote should be "immediately"... > If a promotion is triggered while recovery is paused, the paused state ends and a promotion continues. Could we add a few words in func.sgml to clarify the behavior? Especially for users from my example above. Something like: > If a promotion is triggered while recovery is paused, the paused state ends, replay of any WAL immediately available inthe archive or in pg_wal will be continued and then a promotion will be completed. regards, Sergei
В списке pgsql-hackers по дате отправления: