Feedback-ID: i76984098:Fastmail
Message-ID: <733844b2-2926-49cc-9bd9-ff06999c3933@aklaver.com>
Date: Mon, 15 Dec 2025 08:25:23 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Operational issues when max_replication_slots is exhausted
To: Ahmed Et-tanany <ahmed.ettanany@aiven.io>,
 pgsql-general@lists.postgresql.org
References: <CAD7nQBASDnsxiThkH3=SZLb-=uBT7GJvZBxqY9PYUNHJdSeESA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAD7nQBASDnsxiThkH3=SZLb-=uBT7GJvZBxqY9PYUNHJdSeESA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/733844b2-2926-49cc-9bd9-ff06999c3933%40aklaver.com>
Precedence: bulk

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.klaver@aklaver.com