| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | "Callahan, Drew" <callaan(at)amazon(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss |
| Date: | 2023-10-17 04:20:52 |
| Message-ID: | CAA4eK1+ytq53_GmDLCmxkDqvwgbgxBNg-694grxxaVSQadZA5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Oct 17, 2023 at 4:46 AM Callahan, Drew <callaan(at)amazon(dot)com> wrote:
>
> On the server side, we did not see evidence of WALSenders being launched. As a result, the gap kept increasing further
> and further since they workers would not transition to the catchup state after several hours due to this.
>
One possibility is that the system has reached
'max_logical_replication_workers' limit due to which it is not
allowing to launch the apply worker. If so, then consider increasing
the value of 'max_logical_replication_workers'. You can query
'pg_stat_subscription' to know more information about workers. See the
description of subscriber-side parameters [1].
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Le Thai Hoa | 2023-10-17 08:00:58 | Error “Unable to Write Inside Temp Environment Variable Path” |
| Previous Message | Laurenz Albe | 2023-10-17 01:09:47 | Re: BUG #18159: Database Integrity Concerns: Missing FK Constraint |