public inbox for [email protected]
help / color / mirror / Atom feedFrom: Euler Taveira <[email protected]>
To: Ahmed Et-tanany <[email protected]>
To: Fujii Masao <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] Add max_logical_replication_slots GUC
Date: Thu, 29 Jan 2026 10:21:48 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAD7nQBCwWj=v0QE6HL3BDOPrbqE1raniZ6DRPi_cyLxv81+HJQ@mail.gmail.com>
References: <CAD7nQBD1iy3NAS2YRDUH+zk0g=50px_h_wRsLcFkai7R_RF6VQ@mail.gmail.com>
<[email protected]>
<CAD7nQBCfgCeTwO=45OXhGc=wpYBrWXJfzJKRy+T26_jALxatLg@mail.gmail.com>
<CAHGQGwEaBw9dd+Nzb2ETDJ-40nJTo6GRXrG_FcP0rmw3_-qU_Q@mail.gmail.com>
<CAD7nQBCwWj=v0QE6HL3BDOPrbqE1raniZ6DRPi_cyLxv81+HJQ@mail.gmail.com>
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/
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [PATCH] Add max_logical_replication_slots GUC
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox