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

From Fujii Masao
Subject Re: recovery_target_action=pause with confusing hint
Date
Msg-id b007be90-572a-f735-8900-75d011afc97f@oss.nttdata.com
Whole thread Raw
In response to Re: recovery_target_action=pause with confusing hint  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: recovery_target_action=pause with confusing hint  (movead li <movead.li@highgo.ca>)
List pgsql-hackers

On 2020/03/10 2:27, Robert Haas wrote:
> On Mon, Mar 9, 2020 at 12:03 PM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
>> I started the discussion about the topic very related to this.
>> I'm thinking to apply the change that Sergei proposes after applying
>> the patch I attached in this thread.
>> https://postgr.es/m/00c194b2-dbbb-2e8a-5b39-13f14048ef0a@oss.nttdata.com
> 
> I think it would be good to change the primary message, not just the hint.  e.g.
> 
> LOG: pausing at end of recovery
> HINT: Execute pg_wal_replay_resume() to promote.
> 
> vs.
> 
> LOG: recovery has paused
> HINT: Execute pg_wal_replay_resume() to continue.

Looks good to me.
Attached is the updated version of the patch.
This is based on Sergei's patch.

Regards,


-- 
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters

Attachment

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: weird hash plan cost, starting with pg10
Next
From: Daniel Gustafsson
Date:
Subject: Re: Option to dump foreign data in pg_dump