Re: Proposal: Implement failover on libpq connect level.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>
Cc: Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: Implement failover on libpq connect level.
Date: 2015-08-18 17:01:29
Message-ID: CA+TgmoadWzS=WbP_aJL5B=pnmbZsnjSwrX8njK=fJJoGfQYXQA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

On Tue, Aug 18, 2015 at 12:53 PM, Jaime Casanova
<jaime(dot)casanova(at)2ndquadrant(dot)com> wrote:
> This is not completely true, you can always use something like
> pgbouncer or other middleware to change the server to which clients
> connect. you still need to solve the fact that you will have a
> read-only server at the other side.
>
> something like repmgr + pgbouncer will work fine.

Sure, but pgbouncer is an extra hop, and has its own foibles. There's
real appeal to doing this in the client.

> i agree that once/if we ever have multimaster included then this could
> be a good idea

I think it has a lot of appeal *now*.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-08-18 17:04:27 Re: [patch] psql tab completion for grant execute
Previous Message Jaime Casanova 2015-08-18 16:53:28 Re: Proposal: Implement failover on libpq connect level.

Browse pgsql-jdbc by date

  From Date Subject
Next Message Balázs Zsoldos 2015-08-18 18:54:19 Concurrent read and write access of LargeObject via getBlob() can raise exception
Previous Message Jaime Casanova 2015-08-18 16:53:28 Re: Proposal: Implement failover on libpq connect level.