Re: [HACKERS] Proposal for changes to recovery.conf API - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] Proposal for changes to recovery.conf API
Date
Msg-id CANP8+jL+BXF=7NxBGDAi+cCdgXyL=UvKo111+f2ipZYERLHrUQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Proposal for changes to recovery.conf API  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Proposal for changes to recovery.conf API  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 3 January 2017 at 15:50, Robert Haas <robertmhaas@gmail.com> wrote:
> On Sun, Jan 1, 2017 at 4:14 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> Trying to fit recovery targets into one parameter was really not
>> feasible, though I tried.
>
> What was the problem?

There are 5 different parameters that affect the recovery target, 3 of
which are optional. That is much more complex than the two compulsory
parameters suggested when the proposal was made and in my view tips
the balance over the edge into pointlessness. Michael's suggestion for
2 parameters works well for this case.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] What is "index returned tuples in wrong order" forrecheck supposed to guard against?
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] multivariate statistics (v19)