Re: [PATCH] Add max_logical_replication_slots GUC - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [PATCH] Add max_logical_replication_slots GUC
Date
Msg-id CAA4eK1JWGgQ-6MTBPTEvK9ttBqMAbxsAHNay8RjEg9AaxeyS2A@mail.gmail.com
Whole thread
In response to Re: [PATCH] Add max_logical_replication_slots GUC  (Ahmed Et-tanany <ahmed.ettanany@aiven.io>)
List pgsql-hackers
On Thu, Jan 29, 2026 at 6:31 PM Ahmed Et-tanany <ahmed.ettanany@aiven.io> wrote:
>
> On Thu, Jan 29, 2026 at 12:39 PM Fujii Masao <masao.fujii@gmail.com> wrote:
>>
>>
>> Would something like max_logical_wal_senders also be needed for your purpose?
>> Otherwise, logical replication connections could exhaust max_wal_senders and
>> prevent physical replication connections from being established.
>>
>> That said, adding two separate GUC parameters (i.e.,
>> max_logical_replication_slots
>> and max_logical_wal_senders) for this purpose doesn't seem like a
>> great solution,
>> though...
>>
>
> That's a great point! I'm thinking we could potentially avoid
> introducing a separate max_logical_wal_senders GUC by reusing
> max_logical_replication_slots to decide whether a WAL sender can
> start for logical replication.
>

Won't the walsender automatically exit if the
max_logical_replication_slots is reached? If so, do we really need a
separate GUC to control logical walsenders?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Next
From: Mircea Cadariu
Date:
Subject: Re: Propagate XLogFindNextRecord error to callers