Re: pgsql: Integrate recovery.conf into postgresql.conf - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: pgsql: Integrate recovery.conf into postgresql.conf
Date
Msg-id 3206661543309827@sas2-b4ed770db137.qloud-c.yandex.net
Whole thread Raw
In response to Re: pgsql: Integrate recovery.conf into postgresql.conf  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: pgsql: Integrate recovery.conf into postgresql.conf  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Hello

>>  - recovery_target = immediate was replaced with recovery_target_immediate bool GUC
>
> Why?
Due this comment: https://www.postgresql.org/message-id/20181126172118.GY3415%40tamriel.snowman.net
> I've not been following this very closely, but seems like
> recovery_target_string is a bad idea.. Why not just make that
> 'recovery_target_immediate' and make it a boolean? Having a GUC that's
> only got one valid value seems really odd.

regards, Sergei


pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: tab-completion debug print
Next
From: "Kato, Sho"
Date:
Subject: Planning time of Generic plan for a table partitioned into a lot