gt;
Cc: PostgreSql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] BDR replication port
That's weird. Another idea: Do changes on that server get replicated to the
other servers? I'm not sure if incomming connections are used to receive WAL or
to send it.
Regards,
Alvaro Ag
017 3:23 PM
To: Zhu, Joshua <j...@thalesesec.net>
Cc: PostgreSql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] BDR replication port
Just a guess: How did you blocked the port? Depending on that, you could be
blocking only new connections, but connections already est
greSql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] BDR replication port
Just a guess: How did you blocked the port? Depending on that, you could be
blocking only new connections, but connections already established would
continue to transmit data; remember BDR only rec
.
Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103 | RPC: (+51)
954183248
Website: www.ocs.pe
- Original Message -
From: "Zhu, Joshua" <j...@vormetric.com>
To: "PostgreSql-general" <pgsql-general@postgresql.org>
Sent: Friday, 25 August, 2017 16:49:44
Su
Hi, I am experimenting how network configuration impacts BDR replication, ran
into something that I can't explain, and wonder if someone can shed light.
Here it goes:
With a four node BDR group configured and running (all using default port
5432), I purposely blocked port 5432 on one of the
