Hello Everyone!
Sorry for being persistent.
> I do not think anybody thinks this is a bug. Setting wal_sender_timeout
> too small is a configuration mistake.
Why is it a configuration mistake? This value is allowed to be set. There
is no any restriction about it.
I would like to ask a questio
Hello Everyone!
> I do not think anybody thinks this is a bug. Setting
wal_sender_timeout
> too small is a configuration mistake.
I don't understand why it is a mistake. 1second is acceptable value for
wal_sender_timeout.
Moreover the behaviour contradicts with the official description for
wa
Hello Everyone!
Do you have any thoughts regarding this issue?
Best regards,
Andrei Yahorau
From: Andrei Yahorau/IBA
To: pgsql-gene...@postgresql.org,
Date: 21/06/2019 11:14
Subject:Active connections are terminated because of small
wal_sender_timeout
Hello PostgreSQL Comm
Hello PostgreSQL Community!
Not long ago I opened an issue regarding the problem about:
"terminating walsender process due to replication timeout" problem:
https://www.postgresql.org/message-id/OF85C33E30.171C1C23-ON432583F9.003F5B16-432583F9.003FBAD7%40iba.by
Thanks Everyone for your comprehe
Hello,
I took a look in postgresql source code. As far as I understood walsender
can send some data to walreceiver regarding some changes and so-called
keepalive messages.
Exactly these keepalive messages walsender sends periodically once per
wal_sender_timeout seconds (once per 1 second in my
Hello Everyone!
I can simplify and describe the issue I faced.
I have 2 nodes in db cluster: master and standby.
I create a simple table on master node by a command via psql:
CREATE TABLE table1 (a INTEGER);
After this I fill the table by COPY command from a file which contains
200 (2 millio
Hello.
Thanks for the answer.
Can frequent database operations cause getting a standby server behind? Is
there a way to avoid this situation?
I checked that walsender works well in my test if I set
wal_sender_timeout at least to 5 second.
Best regards,
Andrei Yahorau
From: Kyotaro HORIG
Hello,
Thank You for the response.
Yes that's possible to monitor replication delay. But my questions were
not about monitoring network issues.
I use exactly wal_sender_timeout=1s because it allows to detect
replication problems quickly.
So, I need clarification to the following questions:
Is
Hello PostgreSQL Community!
I faced an issue on my linux machine using Postgres 11.3 .
I have 2 nodes in db cluster: master and standby.
I tried to perform a plenty of long-running queries which lead to the
databases desynchronization:
terminating walsender process due to replication timeout
He
