Re: Patch: Implement failover on libpq connect level.

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Thom Brown <thom(at)linux(dot)com>, Robert Haas <robertmhaas(at)gmail(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: Patch: Implement failover on libpq connect level.
Date: 2016-10-24 20:10:32
Message-ID: 9f4f66aa-e064-f69a-5323-fe8ff2006af6@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

On 10/24/16 6:36 AM, Thom Brown wrote:
> So should it be the case that it disallows UNIX socket addresses
> entirely? I can't imagine a list of UNIX socket addresses being that
> useful.

But maybe a mixed list of Unix-domain sockets and TCP connections?

The nice thing is that is it currently transparent and you don't have to
wonder.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-10-24 20:15:41 Re: Patch: Implement failover on libpq connect level.
Previous Message Peter Eisentraut 2016-10-24 20:04:24 Re: Rename max_parallel_degree?

Browse pgsql-jdbc by date

  From Date Subject
Next Message Peter Eisentraut 2016-10-24 20:15:41 Re: Patch: Implement failover on libpq connect level.
Previous Message Victor Wagner 2016-10-24 19:38:57 Re: Patch: Implement failover on libpq connect level.