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

From Euler Taveira
Subject Re: [PATCH] Add max_logical_replication_slots GUC
Date
Msg-id 09577e49-f53e-4829-916c-662bbed0922b@app.fastmail.com
Whole thread Raw
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 10:01 AM, Ahmed Et-tanany wrote:
>
> 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.
>
> This way, the limit on logical slots would also indirectly cap
> the number of logical WAL senders, helping protect physical
> replication connections without adding another configuration
> parameter.
>

You have 2 resources (walsender and replication slot). You are restricting a
resource based on a configuration from another resource. That seems a potential
source of confusion.


-- 
Euler Taveira
EDB   https://www.enterprisedb.com/



pgsql-hackers by date:

Previous
From: Ahmed Et-tanany
Date:
Subject: Re: [PATCH] Add max_logical_replication_slots GUC
Next
From: Matheus Alcantara
Date:
Subject: Re: [PATCH] llvmjit: always add the simplifycfg pass