Re: Standby accepts recovery_target_timeline setting?

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Steele <david(at)pgmasters(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Standby accepts recovery_target_timeline setting?
Date: 2019-10-09 20:52:30
Message-ID: a6b96094-8458-9a49-7023-11c353baad1b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-09-30 03:48, Fujii Masao wrote:
> Also we need to do the same thing for other recovery options like
> restore_command. Attached is the patch which makes crash recovery
> ignore restore_command and recovery_end_command.

This patch looks correct to me.

Do we need to handle archive_cleanup_command? Perhaps not.

A check in recoveryApplyDelay() might be necessary.

That should cover everything then.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Williams 2019-10-09 21:32:25 Re: pg_dump compatibility level / use create view instead of create table/rule
Previous Message Tom Lane 2019-10-09 20:51:27 Re: Change atoi to strtol in same place