| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Josh Goldberg" <josh(at)4dmatrix(dot)com> |
| Cc: | "postgres-admin" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: lost tables |
| Date: | 2003-04-01 03:42:44 |
| Message-ID: | 27717.1049168564@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Josh Goldberg" <josh(at)4dmatrix(dot)com> writes:
> I moved a few frequently used tables to a separate drive/partition with a=
> symlink to my real data dir. Thank you Murphy, my other drive died yester=
> day and I hadn't been making backups of those tables. Now I have my db bac=
> k up and running but those tables are hosed. I can't drop them using DROP =
> TABLE, and I can't do a pg_dump anymore either. everything complains about=
> pg_toast_xxxxxxxxxx where xxxxxxxx is the filename of the table. How do I=
> clean this up so I can rebuild the tables?
Can't tell without more details. What's the *exact* error message you
get from a DROP TABLE? Also it'd be useful to see the pg_class rows
for the problem tables ("select oid,* from pg_class where relname = 'xxx'")
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anil John | 2003-04-01 05:27:46 | Backup features available for postgres database |
| Previous Message | Kris | 2003-03-31 22:08:26 | Speed & Memory Management |