From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca>, 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 11:45:49 |
Message-ID: | 2f616e51-0bd6-b983-b3f7-d8943b21b7ba@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020/04/01 19:37, Fujii Masao wrote:
>
>
> On 2020/04/01 18:56, movead(dot)li(at)highgo(dot)ca wrote:
>>
>> >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.
>
> Yeah, I'm thinking to emit the message to log file, like the startup process
> does in other places :)
So I'd like to propose the attached patch. The patch changes the message
logged when a promotion is requested, based on whether the recovery is
in paused state or not.
Regards,
--
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters
Attachment | Content-Type | Size |
---|---|---|
add_log_msg_when_promotion_is_triggered_while_recovery_is_paused.patch | text/plain | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2020-04-01 11:53:41 | Re: [PATCH] Opclass parameters |
Previous Message | Amit Kapila | 2020-04-01 11:30:59 | Re: WAL usage calculation patch |