From: | "Chad Wagner" <chad(dot)wagner(at)gmail(dot)com> |
---|---|
To: | RPK <rohitprakash123(at)indiatimes(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Option to undo last update on table. |
Date: | 2007-02-16 00:12:28 |
Message-ID: | 81961ff50702151612q32873abdo4889dafc7307e2f2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/15/07, RPK <rohitprakash123(at)indiatimes(dot)com> wrote:
>
> Is there any option in PGSQL to undo last changes done on a table? Any
> feature similar to "FlashBack Query" in Oracle.
>
The only way I could imagine that you could implement a flashback query in
PostgreSQL is if you ignored everyone's advice and didn't vacuum <not a
good idea>.
Oracle uses an undo tablespace which records all of the information to
"rollback" to an older version of row xyz, but PostgreSQL stores a "new
version of row xyz" in the same data file and vacuum flags the "old version
of row xyz" for deletion which may quickly get overwritten (or may be
unusable for other reasons???).
As for others that may be interested, the flashback feature allows you to
specify essentially the "version" to use when executing the query. And it
is typically done by specifying the SCN (which should be equivalent to the
xid for PostgreSQL) OR a timestamp.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-02-16 00:24:19 | Re: postgresql 8.2 Installation error at "gmake" |
Previous Message | David Legault | 2007-02-16 00:12:12 | Re: ROLE INHERIT |