| From: | Hannes Erven <hannes(at)erven(dot)at> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Revert TRUNCATE CASCADE? |
| Date: | 2012-10-22 11:16:50 |
| Message-ID: | 50852B22.3070500@erven.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all,
today I ran into an issue I believed to be a FAQ, but fortunately it
doesn't seem so as I could find any resources related to this... :-/
A misguided click in PGADMIN executed a "TRUNCATE CASCADE" on a rather
central table of my schema, which resulted in most important tables
being emptied. Postgresql (9.0) was cleanly shut down immediately.
Is there any chance to get the data back?
There is a "pg_dumpall" backup from yesterday, and also pg_xlogs from
well before the dumpall-file until the TRUNCATE command. Unfortunately,
there is no file system backup from the xlog timeframe and as far as I
understood the documentation, a DUMP is no valid base for PITR. Time to
rework backup practices I guess...
Thank you very much for any advice,
best regards
-hannes
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-10-22 12:52:38 | Re: [ADMIN] Streaming Replication Server Crash |
| Previous Message | Heiko Wundram | 2012-10-22 09:54:47 | Re: Somewhat automated method of cleaning table of corrupt records for pg_dump |