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

From Justin Clift
Subject Re: [pgsql-advocacy] Assembling "top features" list for beta announcement
Date
Msg-id 872CA281-30A1-4CA6-9C3E-BBCA081ADA87@postgresql.org
Whole thread Raw
In response to Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement  (Josh Berkus <josh@berkus.org>)
List pgsql-advocacy
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.

+ Justin

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi



pgsql-advocacy by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement
Next
From: Josh Berkus
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement