See also https://github.com/2ndQuadrant/bdr/issues/233
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Increase wal_sender_timeout to resolve the issue.
I've been investigating just this issue recently. See
https://www.postgresql.org/message-id/camsr+ye2dsfhvr7iev1gspzihitwx-pmkd9qalegctya+sd...@mail.gmail.com
.
It would be very useful to me to know more about the transaction that
caused this
Hi there,
We have some problems with BDR and would appreciate any hints and advice with
it. Here's the short story:
We are testing BDR with PostgreSQL 9.4 and it seems to work quite ok after
getting it up and running, but we ran into a quite disturbing weakness also. A
basic two node cluster
