MIME-Version: 1.0
References: <CAD7nQBD1iy3NAS2YRDUH+zk0g=50px_h_wRsLcFkai7R_RF6VQ@mail.gmail.com>
 <202601281248.qjv5oru7hxlz@alvherre.pgsql> <CAD7nQBCfgCeTwO=45OXhGc=wpYBrWXJfzJKRy+T26_jALxatLg@mail.gmail.com>
In-Reply-To: <CAD7nQBCfgCeTwO=45OXhGc=wpYBrWXJfzJKRy+T26_jALxatLg@mail.gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
Date: Wed, 4 Feb 2026 09:54:57 +0900
Message-ID: <CAD21AoBpEGfeX3ce_biQn6wsD+7vb5iEDbu5BV85P8kvOmotnQ@mail.gmail.com>
Subject: Re: [PATCH] Add max_logical_replication_slots GUC
To: Ahmed Et-tanany <ahmed.ettanany@aiven.io>
Cc: =?UTF-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>, 
	pgsql-hackers@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAD21AoBpEGfeX3ce_biQn6wsD%2B7vb5iEDbu5BV85P8kvOmotnQ%40mail.gmail.com>
Precedence: bulk

On Wed, Jan 28, 2026 at 10:02=E2=80=AFPM Ahmed Et-tanany
<ahmed.ettanany@aiven.io> wrote:
>
> Yes, that's what I meant.

FYI there is a related discussion on another thread[1]; Now that
wal_level=3D'replica' can dynamically become 'logical' WAL level
depending on the logical slot presence, there might be users who want
to allow physical replication while not for logical replication
(decoding) to avoid overheads due to logical WAL logging. Having
separate limits for logical slots and physical slots might help such
use cases too.

Regards,

[1] https://www.postgresql.org/message-id/CAEze2WjP0NpAjNioXzLiNkpNQcxCMtaN=
ajaQXfufYVcyFyqW1g%40mail.gmail.com

--=20
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com