Re: Document recovery_target_action behavior?

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Document recovery_target_action behavior?
Date: 2019-09-28 15:14:44
Message-ID: CAHGQGwEowUH5YTG3YAYEP+JZ4gjcaa3ErOaLUZbkrFO8096G5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Sep 28, 2019 at 2:52 AM David Steele <david(at)pgmasters(dot)net> wrote:
>
> Hackers,
>
> In versions < PG12 recovery_target_action has a behavior that appears to
> be a bug, or is at least undocumented. If hot_standby = off and
> recovery_target_action is not specified then the cluster will promote
> when the target is found rather than shutting down as the documentation
> seems to indicate. If recovery_target_action is explicitly set to pause
> then the cluster will shutdown as expected.

Good catch!

> In PG12 the shutdown occurs even when recovery_target_action is not
> explicitly set. This seems like good behavior and it matches the
> documentation as I read it.

Agreed.

> The question for the old versions: is this something that should be
> fixed in the code or in the documentation?
>
> My vote is to make this explicit in the documentation, since changing
> the recovery behavior in old versions could lead to nasty surprises.

+1 to update the documentation.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2019-09-28 15:18:00 default partitions can be partitioned and have default partitions?
Previous Message Fujii Masao 2019-09-28 14:54:10 Re: Standby accepts recovery_target_timeline setting?