| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Pandurangan R S <pandurangan(dot)r(dot)s(at)gmail(dot)com> |
| Cc: | "surabhi(dot)ahuja" <surabhi(dot)ahuja(at)iiitb(dot)ac(dot)in>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: accidentally deleted rows |
| Date: | 2006-02-06 20:00:40 |
| Message-ID: | 1139256040.22740.86.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2006-02-05 at 23:41, Pandurangan R S wrote:
> You may be able to recover them, but you could make things worser if
> you do not do it correctly.
>
> http://archives.postgresql.org/pgsql-patches/2005-02/msg00126.php
> http://archives.postgresql.org/pgsql-general/2006-02/msg00091.php
I was under the impression that pg_reset_xlog (I think that's how it's
spelt) could allow you to see the old tuples assuming they hadn't been
vacuumed and reused.
But of course, like those two messages make it clear, seeing deleted
tuples can cause some serious issues. Always copy your data/base
directory to another computer and play with that copy in case something
bad happens.
Oh, and to the OP... start taking backups.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | josue | 2006-02-06 20:06:34 | ODBC driver for ps81 win32 |
| Previous Message | Steve Atkins | 2006-02-06 18:32:57 | Re: SELECT with REAL... |