Re: Suggestion: pg_dump self-cleanup if out-of-disk

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: David Johnston <polobo(at)yahoo(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Suggestion: pg_dump self-cleanup if out-of-disk
Date: 2013-11-18 17:31:31
Message-ID: CAMkU=1w99MtdnzAmEsya_9GuH1eDDKvAACeKCC4=0dHZvN0WeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Nov 17, 2013 at 11:12 PM, David Johnston <polobo(at)yahoo(dot)com> wrote:

> Having recently had a pg_dump error out due to not having enough disk it
> occurs to me that it would be nice for pg_dump to remove the partial dump
> file it was creating (if possible/known) instead of having it sit around
> taking up that last bit of available space and itself being unusable for
> restore purposes anyway. Given these tend to be large the benefit to
> cleanup seems quite strong and fairly direct to accomplish since we just
> created the file only a short while previous. Call it a beginner or
> part-time-dba usability feature.
>

I don't think I like this. If I unexpectedly filled up a partition with a
dump file, I think the first thing I would want to do is 'head' or 'more'
the partial dump to see what is making it so big--e.g. that I am dumping
the wrong cluster/database/schema. I wouldn't want the software to hide
the evidence.

Cheers,

Jeff

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Janes 2013-11-18 18:20:44 Re: Postgres as In-Memory Database?
Previous Message Elliot 2013-11-18 17:02:09 Re: Help : Sum 2 tables based on key from other table