Ah I see. That's an enlightening web page. I'm going to reconstruct from
backup + application log (yes, I store the exact SQL that does the
If I weren't already doing a gazillion things that undelete program would
be a fun one to hack at.
Minneapolis Ward 3, precinct 10
On Thu, 25 Oct 2001, Einar Karttunen wrote:
> On Thu, Oct 25, 2001 at 07:11:39AM -0500, Joshua b. Jore wrote:
> > So I did a bad thing and did a bad DELETE command and deleted *all* the
> > records. I also goofed by not doing that in a transaction. Is there any
> > way to undo the change? I stopped the daemon right after I broke it.
> The easiest way is to restore the db from your backups. (You have backups don't you?)
> If that is not possible for some weird reason the data is not deleted just
> marked to be deleted. If you did *nothing* to that table it might be possible
> to resque them as described in http://www.geocrawler.com/archives/3/12/2000/7/0/4119316/.
> (Do wal-logs change this in anyway?)
> The first thing to do is to take a backup of the database dir. If the log trick fails
> then study the table format use a hex editor, write a tool to do the undelete and
> share it with us.
> - Einar Karttunen
In response to
pgsql-novice by date
|Next:||From: Josh Berkus||Date: 2001-10-25 15:17:14|
|Subject: Re: Visual Database Design Tools|
|Previous:||From: Per Aronsson||Date: 2001-10-25 14:04:00|