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

From Sergei Kornilov
Subject recovery_target_action=pause with confusing hint
Date
Msg-id 19168211580382043@myt5-b646bde4b8f3.qloud-c.yandex.net
Whole thread Raw
Responses Re: recovery_target_action=pause with confusing hint  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
Hello

Currently during point-in-time recovery with recovery_target_action = 'pause' we print log lines:

> LOG: recovery has paused
> HINT: Execute pg_wal_replay_resume() to continue.

My colleague told me that this is a terrible moment: to continue what exactly? It sounds like "to continue replay",
similarto normal pg_wal_replay_pause/pg_wal_replay_resume behavior. We have just small note in documentation:
 

> The paused state can be resumed by using pg_wal_replay_resume() (see Table 9.81), which then causes recovery to end.

But I think this is important place and can be improved.

Also the database does not respond to the promote signals at this stage. Attached patch 0001 with the test will fail.

0002 patch contains my proposed ideas:
- introduce separate message for pause due pg_wal_replay_pause call and for recovery_target_action.
- check for standby triggers only for recovery_target_action - I am not sure this would be safe for
pg_wal_replay_pause()call case
 

Maybe more verbose hint would be appropriate:

> Execute pg_promote() to end recovery or shut down the server, change the recovery target settings to a later target
andrestart to continue recovery
 

Thoughts?

regards, Sergei
Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions
Next
From: Sehrope Sarkuni
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)