public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ahmed Et-tanany <[email protected]>
To: [email protected]
Subject: Operational issues when max_replication_slots is exhausted
Date: Mon, 15 Dec 2025 12:58:43 +0100
Message-ID: <CAD7nQBASDnsxiThkH3=SZLb-=uBT7GJvZBxqY9PYUNHJdSeESA@mail.gmail.com> (raw)

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,
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?

Thanks in advance.

Best regards,

-- 
Ahmed Et-tanany
Aiven: https://aiven.io/

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]
  Subject: Re: Operational issues when max_replication_slots is exhausted
  In-Reply-To: <CAD7nQBASDnsxiThkH3=SZLb-=uBT7GJvZBxqY9PYUNHJdSeESA@mail.gmail.com>

* 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