pg_dump corrupts database?

Started by Stephen Robert Norrisover 22 years ago2 messagesgeneral
Jump to latest
#1Stephen Robert Norris
srn@commsecure.com.au

I've encountered this a few times with 7.2 and 7.3.

If I do pg_dump of some large (> 100Mb - the bigger the more likely)
database, and it gets interrupted for some reason (e.g. the target disk
fills up), the source database become corrupt. I start getting errors
like:

open of /var/lib/pgsql/data/pg_clog/0323 failed: No such file or
directory

and I have to drop/restore the table in question.

Is this a known problem? Is there some safe way to dump databases that
avoids it?

Stephen
--
Stephen Robert Norris <srn@commsecure.com.au>
CommSecure Australia Pty Ltd

#2Dennis Gearon
gearond@cvc.net
In reply to: Stephen Robert Norris (#1)
Re: pg_dump corrupts database?

seems like that shouldn't happen.

Stephen Robert Norris wrote:

Show quoted text

I've encountered this a few times with 7.2 and 7.3.

If I do pg_dump of some large (> 100Mb - the bigger the more likely)
database, and it gets interrupted for some reason (e.g. the target disk
fills up), the source database become corrupt. I start getting errors
like:

open of /var/lib/pgsql/data/pg_clog/0323 failed: No such file or
directory

and I have to drop/restore the table in question.

Is this a known problem? Is there some safe way to dump databases that
avoids it?

Stephen