Re: BUG #17438: Logical replication hangs on master after huge DB load

On Thu, Mar 31, 2022 at 6:23 PM Sergey Belyashov
<sergey(dot)belyashov(at)gmail(dot)com> wrote:
>
> вт, 29 мар. 2022 г. в 15:03, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>:
> > Is my understanding correct that this problem occurs only when you are
> > doing large operations of tables that are not published (like C or D)
> > in your case?
>
> I do not try to do anything on published tables, because I do it on
> partitions and I detach them first from published tables.
>
> > It is difficult for me to deduce anything from the errors given. I
> > think we need some more information from the logs to find the reason.
> > One idea could be that we run the subscriber with log_min_messages as
> > debug1 as that might give some more information in logs.
>
> Most of errors are:
...
>
> log file is attached.
>

From the logs, I see the below errors:
...
2022-03-31 13:26:47.234 MSK [887763] ERROR: terminating logical
replication worker due to timeout
2022-03-31 13:26:47.241 MSK [888012] ERROR: terminating logical
replication worker due to timeout
...

Based on these errors and the information provided by you (operations
of non-published tables), I think you are facing the same problem as
being discussed in the thread [1]. If you can test the patch submitted
in email [2] and let us know your findings that would be great.

[1] - https://www.postgresql.org/message-id/CAA5-nLARN7-3SLU_QUxfy510pmrYK6JJb%3Dbk3hcgemAM_pAv%2Bw%40mail.gmail.com
[2] - https://www.postgresql.org/message-id/OS3PR01MB6275E0C2B4D9E488AD7CBA209E1F9%40OS3PR01MB6275.jpnprd01.prod.outlook.com

--
With Regards,
Amit Kapila.