Re: Proposal for changes to recovery.conf API

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal for changes to recovery.conf API
Date: 2017-01-03 16:21:10
Message-ID: CANP8+jL+BXF=7NxBGDAi+cCdgXyL=UvKo111+f2ipZYERLHrUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3 January 2017 at 15:50, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Jan 1, 2017 at 4:14 PM, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-01-03 16:22:48 Re: multivariate statistics (v19)
Previous Message Robert Haas 2017-01-03 16:18:55 Re: What is "index returned tuples in wrong order" for recheck supposed to guard against?