Re: Need Force flag for pg_drop_replication_slot()

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Need Force flag for pg_drop_replication_slot()
Date: 2015-05-29 18:30:18
Message-ID: 20150529183018.GD26667@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Josh Berkus (josh(at)agliodbs(dot)com) wrote:
> On 05/29/2015 11:01 AM, Stephen Frost wrote:
> > * Josh Berkus (josh(at)agliodbs(dot)com) wrote:
> >> > 1. you're almost out of disk space due to a replica falling behind, like
> >> > down to 16mb left. Or maybe you are out of disk space.
> > This right here is a real issue. What I'd personally like to see is an
> > option which says "you have X GB of disk space. Once it's gone, forget
> > about all replicas or failing archive commands or whatever, and just
> > stop holding on to ancient WAL that you no longer need to operate."
>
> The substantial challenge here is how do we determine that you're
> "almost out of disk space"?

Eh? That "X GB" above was intended to be the value of a GUC.

I know how big my WAL partition is. Let me tell PG how big it is and to
not do anything that'll end up going over that amount, and we'll never
see a crash due to out of disk space for WAL again.

Thanks!

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2015-05-29 18:35:24 Re: Need Force flag for pg_drop_replication_slot()
Previous Message Stephen Frost 2015-05-29 18:28:36 Re: fsync-pgdata-on-recovery tries to write to more files than previously