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
On 2015.08.18 at 08:32:28 +, Albe Laurenz wrote:
I wonder how useful this is at the present time.
If the primary goes down and the client gets connected to the standby,
it would have read-only access there. Most applications wouldn't cope
well with that.
It is supposed that somebody
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
On 2015.08.19 at 07:15:30 +, Albe Laurenz wrote:
Idea is that we don't need any extra administration actions such as IP
migration to do it. Clients have list of alternate servers and discover
which one to work with by trial and error.
Yes, but that will only work reliably if the
