Re: Continue work on changes to recovery.conf API - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Continue work on changes to recovery.conf API
Date
Msg-id CA+TgmoaobBWaQD0ZZJk1pV_0W-iMNk7rbJW9Cy59z6DCNWhuWQ@mail.gmail.com
Whole thread Raw
In response to Re: Continue work on changes to recovery.conf API  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Fri, Sep 28, 2018 at 4:20 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> > - recovery_target (immediate), recovery_target_name, recovery_target_time, recovery_target_xid, recovery_target_lsn
arereplaced to recovery_target_type and recovery_target_value (was discussed and changed in previous thread)
 
>
> I think this was the major point of contention.  I reread the old
> thread, and it's still not clear why we need to change this.  _type and
> _value look like an EAV system to me.  GUC variables should be
> verifiable independent of another variable.  The other idea of using
> only one variable seems better, but using two variables seems like a
> poor compromise between one and five.

+1.  I like one best, I can live with five, and I think two stinks.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgbench doc fix
Next
From: Tom Lane
Date:
Subject: Re: Super PathKeys (Allowing sort order through precision loss functions)