Re: recovery_target_action=pause with confusing hint - Mailing list pgsql-hackers

From movead.li@highgo.ca
Subject Re: recovery_target_action=pause with confusing hint
Date
Msg-id 20200401175611855203128@highgo.ca
Whole thread Raw
In response to recovery_target_action=pause with confusing hint  (Sergei Kornilov <sk@zsrv.org>)
Responses Re: recovery_target_action=pause with confusing hint  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers

>This happens because the startup process detects the trigger file
>after pg_wal_replay_pause() succeeds, and then make the recovery
>get out of the paused state. 
Yes that is.

>It might be problematic to end the paused
>state silently? So, to make the situation less confusing, what about
>emitting a log message when ending the paused state because of
>the promotion?
But where to emit it? I think it not so good by emitting to log file,
because the user will not check it everytime. BTW, why
CheckForStandbyTrigger() can not be called in backend.


Regards,
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: recovery_target_action=pause with confusing hint
Next
From: Fujii Masao
Date:
Subject: Re: recovery_target_action=pause with confusing hint