Re: BUG #11991: dangerous action of pg_dump - Mailing list pgsql-bugs

From John R Pierce
Subject Re: BUG #11991: dangerous action of pg_dump
Date
Msg-id 546AB6B7.2070606@hogranch.com
Whole thread Raw
In response to BUG #11991: dangerous action of pg_dump  (tomek@rai.pl)
List pgsql-bugs
On 11/17/2014 1:42 PM, tomek@rai.pl wrote:
> Bug reference:      11991
> Logged by:          Tomasz Kimaczynski
> Email address:tomek@rai.pl
> PostgreSQL version: 9.2.9
> Operating system:   Windows 2003,2008,2012 & FreeBSD
> Description:
>
> Recently, I realized pg_dump dangerous activity. In case when no dump is
> made because of any error, created file size is 0 bytes. In case when this
> file is used in simple backup procedure which make copy of dump file - 0
> bytes files overwrite earlier correct dump files.
> And we have no copies.
> Conclusion: pg_dump can not create 0 bytes files - it should create
> nothing.
> I think it's important.

perhaps your pg_dump script should check for errors from the pg_dump
run, and if any errors, delete the erroneous dump.



--
john r pierce                                      37N 122W
somewhere on the middle of the left coast

pgsql-bugs by date:

Previous
From: tomek@rai.pl
Date:
Subject: BUG #11991: dangerous action of pg_dump
Next
From: David G Johnston
Date:
Subject: Re: BUG #11991: dangerous action of pg_dump