accidental drop table recoverable?

From: Paul Libbrecht <paul(at)activemath(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Subject: accidental drop table recoverable?
Date: 2008-07-14 13:13:21
Message-ID: 53CDF98F-0AE1-49ED-A2A3-C3B1E2AF2E2E@activemath.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello fellow Postgres administrators,

right now we experienced the loss of backups (due to wrong
communication) and a list of accidental drop table statements (due to
wrong database choice).

We sure have clues how to avoid that in the future but right now we do
not seem to find the solution to actually rollback this accidental
drop table.

Having searched around, the only recipe I found was:
http://archives.postgresql.org/pgsql-docs/2004-12/msg00027.php
which is pretty convoluted but seems like it could do the job.

Now... is there a simpler way?
I seem to see a fixed set of files in data/base that seemed to have
been changed at the right time of the drop db... any chance to fiddle
with them?

thanks for hints.

paul

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2008-07-14 14:47:27 Re: accidental drop table recoverable?
Previous Message sftf 2008-07-14 05:26:05 Rewrite SELECT WHERE clause on per-session bases. Modifing view source code in one session (user's) from another session (admin's)?