Re: Proposal: Implement failover on libpq connect level.
Victor Wagner <vitus@wagner.pp.ru>
From: ''Victor Wagner *EXTERN*' *EXTERN*' *EXTERN* <vitus@wagner.pp.ru>
To: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2015-08-19T14:45:26Z
Lists: pgsql-hackers
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.
Commits
-
libpq: Add target_session_attrs parameter.
- 721f7bd3cbcc 10.0 landed
-
Remove superuser checks in pgstattuple
- fd321a1dfd64 10.0 cited
-
Fix unwanted flushing of libpq's input buffer when socket EOF is seen.
- c405918858c0 9.6.0 cited