Re: Proposal: Implement failover on libpq connect level.
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Jaime Casanova <jaime.casanova@2ndquadrant.com>
Cc: Victor Wagner <vitus@wagner.pp.ru>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2015-08-18T17:01:29Z
Lists: pgsql-hackers
On Tue, Aug 18, 2015 at 12:53 PM, Jaime Casanova <jaime.casanova@2ndquadrant.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
Commits
-
libpq: Add target_session_attrs parameter.
- 721f7bd3cbcc 10.0 landed
-
Remove superuser checks in pgstattuple
- fd321a1dfd64 10.0 cited
-
Fix unwanted flushing of libpq's input buffer when socket EOF is seen.
- c405918858c0 9.6.0 cited