| From: | Dennis Gearon <gearond(at)cvc(dot)net> |
|---|---|
| To: | Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> |
| Cc: | PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_dump corrupts database? |
| Date: | 2003-08-06 15:15:34 |
| Message-ID: | 3F311B96.5060306@cvc.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
seems like that shouldn't happen.
Stephen Robert Norris wrote:
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Tocci | 2003-08-06 15:16:20 | Re: INSERT RULE QUERY ORDER |
| Previous Message | Teodor Sigaev | 2003-08-06 14:53:29 | Re: Tsearch2 or openFTS ? |