| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Date: | 2018-11-27 09:10:27 |
| Message-ID: | 3206661543309827@sas2-b4ed770db137.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-11-27 12:29:27 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | Peter Eisentraut | 2018-11-27 09:02:52 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kato, Sho | 2018-11-27 10:05:29 | Planning time of Generic plan for a table partitioned into a lot |
| Previous Message | Kyotaro HORIGUCHI | 2018-11-27 09:06:06 | Re: tab-completion debug print |