Re: Proposal: Implement failover on libpq connect level.

From: ''Victor Wagner *EXTERN*' *EXTERN*' *EXTERN* <vitus(at)wagner(dot)pp(dot)ru>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: Implement failover on libpq connect level.
Date: 2015-08-19 14:45:26
Message-ID: 20150819144526.GA3623@wagner.pp.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

On 2015.08.19 at 15:35:17 +0100, Simon Riggs wrote:

>
> I think we do need some way of saying that a readonly connection is OK. So

I had such thing in my propsal (boolean parameter readonly).
But haven't yet checked if it is compatible with jdbc syntax.

> the default would be to connect to each in turn until we find the master.
> It should keep retrying for a period of time since for a short period it is
> possible there is no master. If you specify readonly, then a connection to

It is very important addition - to specify that if no host is able to
establish read-write session, we should retry and give a chance for
sever administration to promote one of standbys to master. Probably
there should be additional timeout parameter (we have
connection_timeout, and this would be failover_timeout) with some
reasonaable default.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-08-19 14:45:40 Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows
Previous Message Simon Riggs 2015-08-19 14:35:17 Re: Proposal: Implement failover on libpq connect level.

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tatsuo Ishii 2015-08-19 15:17:35 Re: Proposal: Implement failover on libpq connect level.
Previous Message Simon Riggs 2015-08-19 14:35:17 Re: Proposal: Implement failover on libpq connect level.