Re: terminating walsender process due to replication timeout - Mailing list pgsql-general

From Kyotaro HORIGUCHI
Subject Re: terminating walsender process due to replication timeout
Date
Msg-id 20190524.153404.138479543.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to Re: terminating walsender process due to replication timeout  (AYahorau@ibagroup.eu)
Responses Re: terminating walsender process due to replication timeout
List pgsql-general
Hello.

At Fri, 17 May 2019 11:04:58 +0300, AYahorau@ibagroup.eu wrote in
<OFE11EC62A.504EB2B3-ON432583FD.002BE231-432583FD.002C666E@iba.by>
> 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.

It depends on the transaction (WAL) traffic and the bandwidth of
your network. The performacne difference between master and
standby also affects.

The possibilities I can guess are:

- The bandwidth is narrow to the traffic.

- The standby performs poorer than the master.

- Your network is having a sort of trouble. Virtual network
  (local network in a virtual environment) tends to suffer
  network troubles caused by CPU saturation or something else.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center




pgsql-general by date:

Previous
From: Achilleas Mantzios
Date:
Subject: Re: terminating walsender process due to replication timeout
Next
From: Julie Nishimura
Date:
Subject: POSTGRES_FSM_RELATIONS CRITICAL: DB control fsm relations used: 79569of 80000 (99%)