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

From tomek@rai.pl
Subject BUG #11991: dangerous action of pg_dump
Date
Msg-id 20141117214211.2475.5375@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #11991: dangerous action of pg_dump  (John R Pierce <pierce@hogranch.com>)
Re: BUG #11991: dangerous action of pg_dump  (David G Johnston <david.g.johnston@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

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.

pgsql-bugs by date:

Previous
From: David G Johnston
Date:
Subject: Re: BUG #11990: Installation of OPM
Next
From: John R Pierce
Date:
Subject: Re: BUG #11991: dangerous action of pg_dump