| From: | Ahmed Et-tanany <ahmed(dot)ettanany(at)aiven(dot)io> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Add max_logical_replication_slots GUC |
| Date: | 2026-01-28 13:02:01 |
| Message-ID: | CAD7nQBCfgCeTwO=45OXhGc=wpYBrWXJfzJKRy+T26_jALxatLg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Yes, that's what I meant.
On Wed, Jan 28, 2026 at 1:55 PM Álvaro Herrera <alvherre(at)kurilemu(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2026-01-28 13:03:02 | Re: pg_waldump: support decoding of WAL inside tarfile |
| Previous Message | Robert Haas | 2026-01-28 12:57:49 | Re: pgsql: Prevent invalidation of newly synced replication slots. |