| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Ahmed Et-tanany <ahmed(dot)ettanany(at)aiven(dot)io> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Add max_logical_replication_slots GUC |
| Date: | 2026-01-28 12:54:32 |
| Message-ID: | 202601281248.qjv5oru7hxlz@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2026-01-28 12:57:49 | Re: pgsql: Prevent invalidation of newly synced replication slots. |
| Previous Message | Euler Taveira | 2026-01-28 12:44:55 | Re: Pasword expiration warning |