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

From Ahmed Et-tanany
Subject Re: [PATCH] Add max_logical_replication_slots GUC
Date
Msg-id CAD7nQBCfgCeTwO=45OXhGc=wpYBrWXJfzJKRy+T26_jALxatLg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Add max_logical_replication_slots GUC  (Ahmed Et-tanany <ahmed.ettanany@aiven.io>)
Responses Re: [PATCH] Add max_logical_replication_slots GUC
List pgsql-hackers
Yes, that's what I meant.

On Wed, Jan 28, 2026 at 1:55 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
On 2026-Jan-28, Ahmed Et-tanany wrote:

> In practice, a burst of logical replication activity can exhaust all
> available replication slots, which in turn prevents physical standbys
> from connecting or restarting.
>
> This is problematic because logical replication slots are often
> user-managed and can grow dynamically,

Ah, you mean that users doing CREATE SUBSCRIPTION could cause the limit
to be reached, possibly blocking streaming replication.  Yeah, it makes
sense to have a separate limit.

--
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"[PostgreSQL] is a great group; in my opinion it is THE best open source
development communities in existence anywhere."                (Lamar Owen)


--
Ahmed Et-tanany
Aiven: https://aiven.io/

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: Prevent invalidation of newly synced replication slots.
Next
From: Robert Haas
Date:
Subject: Re: pg_waldump: support decoding of WAL inside tarfile