| From: | Josh Berkus <josh(at)berkus(dot)org> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| 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 18:10:11 |
| Message-ID: | 47c70fec-6791-82e5-9497-aae9e395873b@berkus.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
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.
--
Josh Berkus
Containers & Databases Oh My!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-10 19:17:19 | Re: Assembling "top features" list for beta announcement |
| Previous Message | Justin Clift | 2017-04-10 16:04:05 | Re: Assembling "top features" list for beta announcement |