Re: Proposal: Implement failover on libpq connect level.
Victor Wagner <vitus@wagner.pp.ru>
From: Victor Wagner *EXTERN* <vitus@wagner.pp.ru>
To: pgsql-hackers@postgresql.org
Date: 2015-08-19T07:18:22Z
Lists: pgsql-hackers
On 2015.08.19 at 12:29:51 +0530, Amit Kapila wrote: > > It seems that most people discussing in this thread think in millisecond > > time intervals (failure and immediate reconnect). > > Why not have this as a separate parameter (*_timeout or something like > that)? Because it is not in the software configuration. It is in the people heads. Or may be in the organizational configuration of the environments we are talking about. Each of us imagining some use-case for discussed feature. And these cases are completely different, and have different typical time interval. I haven't explicitely stated my use cases in the proposal. So people thinking in terms of their use cases, and this is very significant feedback for me.
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