| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, 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-29 10:05:53 |
| Message-ID: | 73e3649ecec2b31c1b31b222c8b1d3aede283149.camel@oopsware.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Mittwoch, dem 28.01.2026 um 10:43 -0300 schrieb Euler Taveira:
> Another idea is to not differentiate between physical and
> logical but have a reserved_replication_slots parameter. The concept
> is similar
> to reserved_connections. It defines the number of (physical or
> logical)
> replication slots that are reserved by roles with privileges of the
> pg_use_reserved_replication_slots. (Maybe this role name is long but
> descriptive.) It defaults to 0.
I like your second idea. That makes it independent from what you like
to reserve for, either logical or physical and supports flexible pool
configurations.
--
Thanks,
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2026-01-29 11:03:00 | Re: Import Statistics in postgres_fdw before resorting to sampling. |
| Previous Message | Amit Langote | 2026-01-29 10:04:17 | Re: Batching in executor |