Re: replay pause vs. standby promotion - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: replay pause vs. standby promotion
Date
Msg-id 908291584974317@sas8-7ec005b03c91.qloud-c.yandex.net
Whole thread Raw
In response to Re: replay pause vs. standby promotion  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: replay pause vs. standby promotion  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
Hello

> You meant that the promotion request should cause the recovery
> to finish immediately even if there are still outstanding WAL records,
> and cause the standby to become the master?

Oh, I get your point. But yes, I expect that in case of promotion request during a pause, the user (me too) will want
tohave exactly the current state, not latest available in WALs.
 

Real usercase from my experience:
The user wants to update a third-party application. In case of problems, he wants to return to the old version of the
applicationand the unchanged replica. Thus, it sets a pause on standby and performs an update. If all is ok - he will
resumereplay. In case of some problems he plans to promote standby.
 
But oops, standby will ignore promote signals during pause and we need get currect LSN from standby and restart it with
recovery_target_lsn= ? and recovery_target_action = promote to achieve this state.
 

regards, Sergei



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line
Next
From: "Joel Mariadasan (jomariad)"
Date:
Subject: RE: ASLR support for Postgres12