| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, pgsql-bugs mailing list <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Logical replication stops dropping used initial-sync replication slots |
| Date: | 2022-03-29 12:01:41 |
| Message-ID: | 20220329120140.GA29363@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Mar 29, 2022 at 04:57:42PM +0530, Amit Kapila wrote:
> What was your setting for max_logical_replication_workers? It should
4 on source, and 50 on replica. That could be related. Should I increase this on source?
> be more than max_sync_workers_per_subscription as that is taken from
> the pool of max_logical_replication_workers. One possible reason for
The thing is that, in next tests, it seemed to *usually* work. And break
just sometimes.
> It is good if you are able to proceed but we might get some clue about
> the problem you are seeing if you can show subscriber-side logs.
Will keep that in mind. The boxes I was testing it are gone, but if the
problem will resurface, I'll make the logs available.
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-03-29 12:03:08 | Re: BUG #17438: Logical replication hangs on master after huge DB load |
| Previous Message | Amit Kapila | 2022-03-29 11:27:42 | Re: Logical replication stops dropping used initial-sync replication slots |