So, there is a way to call replication, to client restart connection and try
again ?
Because aparently it stays disconnected for hours to try again, gets that
timeout message and remains disconnected for hours again
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.htm
On publisher it shows me "terminating walsender process due to replication
timeout"
But the problem is that this message is occurring 3 or 4 times a day only.
It tries to send data, gets a timeout then shows the message. Then it waits
a long long long time to try again, I don´t know why.
wal_send
On Wed, 2021-04-07 at 04:16 -0700, PegoraroF10 wrote:
> I have a server which replicates using Publication/Subscription. On
> subscriber server I have some ETL processes running on it and from this
> second server I´ve created a new publication to send this database to a
> third server. While this
I have a server which replicates using Publication/Subscription. On
subscriber server I have some ETL processes running on it and from this
second server I´ve created a new publication to send this database to a
third server. While this second server was copying data with COPY to third,
everything
