From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Catalin Iacob <iacobcatalin(at)gmail(dot)com> |
Cc: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Peter van Hardenberg <pvh(at)pvh(dot)ca>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Patch: Implement failover on libpq connect level. |
Date: | 2016-11-16 18:55:37 |
Message-ID: | CA+TgmoYLEgcc_A+QU+6hatqrbFUot2Db05znEcFHZofkDAzB+g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Wed, Nov 16, 2016 at 12:00 PM, Catalin Iacob <iacobcatalin(at)gmail(dot)com> wrote:
> On Wed, Nov 16, 2016 at 2:50 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Hmm, let's go back to the JDBC method, then. "show
>> transaction_read_only" will return true on a standby, but presumably
>> also on any other non-writable node. You could even force it to be
>> true artificially if you wanted to force traffic off of a node, using
>> ALTER {SYSTEM|USER ...|DATABASE ..} SET default_transaction_read_only
>> = on
>>
>> I think that would address Alvaro's concern, and it's nicer anyway if
>> libpq and JDBC are doing the same thing.
>
> Not sure I agree that using this is a good idea in the first place.
>
> But if we end up using this, I really think the docs should be very
> explicit about what's implemented and not just say master/any. With
> the master/any docs in the patch I would be *very* surprised if a
> master is skipped only because it was configured with
> default_transaction_read_only = on.
It seems like it is going to be difficult to please everyone here
100%, because there are multiple conflicting priorities. But we can
definitely document whatever choices we make.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-11-16 19:24:54 | Re: Password identifiers, protocol aging and SCRAM protocol |
Previous Message | Michael Paquier | 2016-11-16 18:53:17 | Re: Password identifiers, protocol aging and SCRAM protocol |
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2016-11-17 02:00:32 | Re: Patch: Implement failover on libpq connect level. |
Previous Message | Catalin Iacob | 2016-11-16 17:00:42 | Re: Patch: Implement failover on libpq connect level. |