Horton

Re: [HACKERS] Patch: Implement failover on libpq connect level.

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Kevin Grittner <kgrittn@gmail.com>
Cc: Mithun Cy <mithun.cy@enterprisedb.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Peter van Hardenberg <pvh@pvh.ca>, "pgsql-jdbc@postgresql.org" <pgsql-jdbc@postgresql.org>
Date: 2016-11-16T15:13:14Z
Lists: pgsql-hackers 
On Wed, Nov 16, 2016 at 9:02 AM, Kevin Grittner <kgrittn@gmail.com> wrote:
> [moving this branch of discussion to pgsql-jdbc]
>
> On Tue, Nov 15, 2016 at 10:31 PM, Mithun Cy <mithun.cy@enterprisedb.com> wrote:
>
>> JDBC is sending "show transaction_read_only" to find whether it
>> is master or not.
>
> If true, that's insane.  That can be different on each connection
> to the cluster and can change tens of thousands of times per second
> on any connection!

I don't think that's insane.  The command is only being issued at
connection startup, and will only be different on different
connections if it's been configured that way.

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

Commits

  1. libpq: Add target_session_attrs parameter.

  2. Remove superuser checks in pgstattuple

  3. Fix unwanted flushing of libpq's input buffer when socket EOF is seen.