| From: | "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca> |
|---|---|
| To: | "Fujii Masao" <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "Sergei Kornilov" <sk(at)zsrv(dot)org>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: recovery_target_action=pause with confusing hint |
| Date: | 2020-04-01 09:56:14 |
| Message-ID: | 20200401175611855203128@highgo.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-04-01 10:37:15 | Re: recovery_target_action=pause with confusing hint |
| Previous Message | Fujii Masao | 2020-04-01 09:35:36 | Re: recovery_target_action=pause with confusing hint |