public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: Ahmed Et-tanany <[email protected]>
To: [email protected]
Subject: Re: Operational issues when max_replication_slots is exhausted
Date: Mon, 15 Dec 2025 16:17:52 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAD7nQBASDnsxiThkH3=SZLb-=uBT7GJvZBxqY9PYUNHJdSeESA@mail.gmail.com>
References: <CAD7nQBASDnsxiThkH3=SZLb-=uBT7GJvZBxqY9PYUNHJdSeESA@mail.gmail.com>

On Mon, 2025-12-15 at 12:58 +0100, Ahmed Et-tanany wrote:
> Our problem is that when our customers use up all available replication slots for logical replication,
> our database management tasks that also require a slot fail (for example, creating the required
> replication slot for a new physical standby). Since increasing `max_replication_slots` requires
> a restart, we would like to avoid that if possible.
> 
> One idea we have considered is patching PostgreSQL to add a new GUC parameter that would allow
> a superuser to reserve a certain number of replication slots usable only for management tasks.
> 
> Is this a known issue that might be addressed in PostgreSQL at some point? If not,
> what would be a good way to solve this problem?

It is conceivable that somebody might change the behavior at some point (compare
"reserved_connections").  If you write or sponsor a patch, that would increase
the likelihood.

Right now, my only suggestion is to set "max_replication_slots" high.

Yours,
Laurenz Albe

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Operational issues when max_replication_slots is exhausted
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox