| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ahmed Et-tanany <ahmed(dot)ettanany(at)aiven(dot)io>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Operational issues when max_replication_slots is exhausted |
| Date: | 2025-12-15 16:25:23 |
| Message-ID: | 733844b2-2926-49cc-9bd9-ff06999c3933@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/15/25 03:58, Ahmed Et-tanany wrote:
> Hello PostgreSQL community,
>
> We have an issue related to `max_replication_slots` that I am not sure
> would qualify as a bug,
> so I thought I would ask here first.
>
> Our problem is that when our customers use up all available replication
> slots for logical replication,
The above would be the issue. Allowing customers to be DBA's for an
installation that they are not ultimately responsible for does not seem
sound to me. I would think a request mechanism is in order.
>
> Thanks in advance.
>
> Best regards,
>
> --
> Ahmed Et-tanany
> Aiven: https://aiven.io/ <https://aiven.io/>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-12-16 04:07:36 | Re: Advent of Code Day 8 |
| Previous Message | Laurenz Albe | 2025-12-15 15:17:52 | Re: Operational issues when max_replication_slots is exhausted |