Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement - Mailing list pgsql-advocacy

From Peter Eisentraut
Subject Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement
Date
Msg-id 4289b892-da34-d5fd-cdd4-60afb9252b86@2ndquadrant.com
Whole thread Raw
In response to Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement  (Josh Berkus <josh@berkus.org>)
Responses Re: [pgsql-advocacy] Assembling "top features" list for beta announcement
Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement
List pgsql-advocacy
On 4/10/17 14:10, Josh Berkus wrote:
> On 04/10/2017 09:04 AM, Justin Clift wrote:
>> On 10 Apr 2017, at 16:42, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>>> On 4/8/17 04:50, Michael Banck wrote:
>>>> "Client-Side Connection-Failover"
>>>
>>> I don't think the libpq feature can be considered "failover".  It just
>>> picks from a list of end points on the initial connection attempt.  It
>>> does not discover connection failures and reconnect.
>>
>> Yeah, after reading Roberts blog post, I'd also agree that "failover"
>> is a bad/misleading (in the "automatic" sense) description for it.
>
> Alternate phrasing?
>
> I do want to get this in the "extended list" of features, just because
> we want driver authors to add support for it.

I'm not sure what you mean by this.  If the driver is based on libpq,
they get it for free.  If the driver is not based on libpq, they have to
implement it themselves, but don't need to wait for libpq before doing so.

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


pgsql-advocacy by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement
Next
From: Magnus Hagander
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for beta announcement