From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Excessive number of replication slots for 12->14 logical replication |
Date: | 2022-07-15 07:45:40 |
Message-ID: | 20220715074540.GA26521@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jul 15, 2022 at 01:55:32PM +0900, Kyotaro Horiguchi wrote:
> Thus, not just about logical replication, some spare slots are
> necessary to keep things running smoothly. I guess that it is
> widely(?) recommended to provide at least one or two spare slots to
> allow replication reconnection in case of silent disconnections, but I
> haven't found something like that in the documentation.. In your case,
> it seems to me larger number of spare slots makes the server run more
> smoothly, *I* don't think 10 spare slots affect anything badly.
OK. The explanation makes sense, but leads to problem - we have 50
max replication slots, which gives me 20 spare slots.
And I'm not sure how much should I increase it so that it will still
work.
Plus - there is the problem that increasing max_replication_slots
requires restart :(
Anyway, will deal with it, now that I understand the issue. Thanks
a lot.
Best regards,
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2022-07-15 07:58:35 | Re: BUG #17496: to_char function resets if interval exceeds 23 hours 59 minutes |
Previous Message | Andres Freund | 2022-07-15 07:26:51 | Re: [15] Custom WAL resource managers, single user mode, and recovery |