From: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "''Victor Wagner *EXTERN*' *EXTERN*' *EXTERN*" <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-29 13:14:34 |
Message-ID: | CACACo5QSXo_1mXbnQvQaaSZmN6m5NyhV43Q2ArWRHW_txd74qA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Fri, Aug 28, 2015 at 6:10 PM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
> +1 for bringing the jdbc driver URI syntax into libpq, so that all
>> interfaces
>> can be optionally specified this way. This doesn't preclude the use of
>> ipfailover, in fact it might be work well together. If you don't like it,
>> don't
>> use it.
>>
>
> +1
>
> Another thought: multiple hosts in URI could be used in simple
> configuration for read-only clients. I faced with customers which manages
> two connections in process - to master and to one of several slaves.
Hm, but do they suffer any trouble while doing that *outside* of libpq?
What is the benefit in adding this to libpq itself while it already
provides very rich and finely grained connection control functions?
--
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2015-08-29 13:28:51 | Re: to_json(NULL) should to return JSON null instead NULL |
Previous Message | Tom Lane | 2015-08-29 13:10:45 | Re: [BUGS] Compile fails on AIX 6.1 |
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2015-08-29 19:10:16 | Re: Version 1202 released |
Previous Message | Sehrope Sarkuni | 2015-08-28 23:08:34 | Re: Version 1202 released |