Re: Assembling "top features" list for beta announcement

From: Justin Clift <justin(at)postgresql(dot)org>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Josh Berkus <josh(at)berkus(dot)org>, 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 16:04:05
Message-ID: 872CA281-30A1-4CA6-9C3E-BBCA081ADA87@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

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.

+ 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

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Josh Berkus 2017-04-10 18:10:11 Re: Assembling "top features" list for beta announcement
Previous Message Peter Eisentraut 2017-04-10 15:42:34 Re: Assembling "top features" list for beta announcement