From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #11991: dangerous action of pg_dump |
Date: | 2014-11-18 03:02:15 |
Message-ID: | 546AB6B7.2070606@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 11/17/2014 1:42 PM, tomek(at)rai(dot)pl wrote:
> Bug reference: 11991
> Logged by: Tomasz Kimaczynski
> Email address:tomek(at)rai(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David G Johnston | 2014-11-18 05:22:30 | Re: BUG #11991: dangerous action of pg_dump |
Previous Message | David G Johnston | 2014-11-18 01:55:44 | Re: BUG #11990: Installation of OPM |