| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)berkus(dot)org>, Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Michael Banck <michael(dot)banck(at)credativ(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Assembling "top features" list for beta announcement |
| Date: | 2017-04-10 19:17:19 |
| Message-ID: | 4289b892-da34-d5fd-cdd4-60afb9252b86@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-04-10 19:21:25 | Re: Assembling "top features" list for beta announcement |
| Previous Message | Josh Berkus | 2017-04-10 18:10:11 | Re: Assembling "top features" list for beta announcement |