Re: [PATCH] Add max_logical_replication_slots GUC

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Ahmed Et-tanany <ahmed(dot)ettanany(at)aiven(dot)io>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Add max_logical_replication_slots GUC
Date: 2026-02-11 12:09:37
Message-ID: CAA4eK1JWGgQ-6MTBPTEvK9ttBqMAbxsAHNay8RjEg9AaxeyS2A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 29, 2026 at 6:31 PM Ahmed Et-tanany <ahmed(dot)ettanany(at)aiven(dot)io> wrote:
>
> On Thu, Jan 29, 2026 at 12:39 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mircea Cadariu 2026-02-11 12:15:56 Re: Propagate XLogFindNextRecord error to callers
Previous Message Amit Kapila 2026-02-11 11:53:44 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart