| From: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
|---|---|
| To: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | hardware failure - data recovery |
| Date: | 2006-10-19 00:57:40 |
| Message-ID: | DDB90018-67B9-44AD-B634-924D0296E3BF@alpinenetworking.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
To make a long story short lets just say that I had a bit of a
hardware failure recently.
If I got an error like this when trying to dump a db from the mangled
data directory is it safe to say it's totally hosed or is there some
chance of recovery?
pg_dump: ERROR: could not open relation 1663/18392/18400: No such
file or directory
pg_dump: SQL command to dump the contents of table "file" failed:
PQendcopy() failed.
pg_dump: Error message from server: ERROR: could not open relation
1663/18392/18400: No such file or directory
pg_dump: The command was: COPY public.file (vfs_id, vfs_type,
vfs_path, vfs_name, vfs_modified, vfs_owner, vfs_data) TO stdout;
Thanks,
Rick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2006-10-19 01:23:41 | Re: hardware failure - data recovery |
| Previous Message | Taras Kopets | 2006-10-19 00:10:43 | Re: Link error: LNK2019: unresolved external symbol _pg_detoast_datum |