Re: BUG #11991: dangerous action of pg_dump
| От | John R Pierce |
|---|---|
| Тема | Re: BUG #11991: dangerous action of pg_dump |
| Дата | |
| Msg-id | 546AB6B7.2070606@hogranch.com обсуждение исходный текст |
| Ответ на | BUG #11991: dangerous action of pg_dump (tomek@rai.pl) |
| Список | 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 по дате отправления: