| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | abhishek(dot)bhola(at)japannext(dot)co(dot)jp |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgresql 11: terminating walsender process due to replication timeout |
| Date: | 2021-09-10 00:21:28 |
| Message-ID: | 20210910.092128.1069811594081544599.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
At Thu, 9 Sep 2021 16:06:25 +0900, Abhishek Bhola <abhishek(dot)bhola(at)japannext(dot)co(dot)jp> wrote in
> sourcedb:~$ postgres --version
> postgres (PostgreSQL) 11.6
>
> Sorry for missing this information.
> But looks like this fix is already included in the version I am running.
Ok. I'm not sure but there may be a case where too-busy (or too poor
relative to the publisher) subscriber cannot send a response for a
long time. Usually keep-alive packets sent from publisher causes
subscriber response even while busy time but it seems that if
subscriber applies changes more than two times slower than the
publisher sends, subscriber doesn't send a response in the timeout
window.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhishek Bhola | 2021-09-10 07:55:48 | Re: Postgresql 11: terminating walsender process due to replication timeout |
| Previous Message | Peter J. Holzer | 2021-09-09 21:45:25 | Re: update non-indexed value is slow if some non-related index/fk are enabled |