Bruno Wolff III wrote:
On Thu, Sep 22, 2005 at 15:20:17 -0400,
Emi Lu <emilu@xxxxxxxxxxxxxxx> wrote:
greetings,
I remembered I read something in the mailing list about "*rollback*" a
while ago. People mentioned that some operations cannot rollback.
I cannot remember what kinds of perations are not be able to rollback?
I actually have the message saved for reference, so it is easier attach it
rather than try to figure out how to link to it in the archives.
------------------------------------------------------------------------
Subject:
Re: Table modifications with dependent views - best
From:
Tom Lane <tgl@xxxxxxxxxxxxx>
Date:
Fri, 22 Apr 2005 11:36:43 -0400
To:
Bruno Wolff III <bruno@xxxxxxxx>
To:
Bruno Wolff III <bruno@xxxxxxxx>
CC:
David Roussel <pgsql-general@xxxxxxxxxxxxxxxxxxxx>, Michael Fuhr
<mike@xxxxxxxx>, John Browne <jkbrowne@xxxxxxxxx>,
pgsql-general@xxxxxxxxxxxxxx
Bruno Wolff III <bruno@xxxxxxxx> writes:
I wasn't able to find where this is spelled out in the documentation,
but I believe all DDL commands except DROP DATABASE can be rolled back now.
I don't think there's any all-in-one-place statement about it, but
anything that doesn't explicitly object to being put inside a
transaction block can be rolled back. Grepping for
PreventTransactionChain, I see that the current suspects are
CLUSTER (only the multi-table variants)
CREATE DATABASE
DROP DATABASE
REINDEX DATABASE
CREATE TABLESPACE
DROP TABLESPACE
VACUUM
regards, tom lane
------------------------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
You can add to that list the command TRUNCATE though it can be rollback
its not useful in cases where the truncated data should continue to be
accessed till the transaction be commited.
By the way I posted at the manual a comment about it (at the TRUNCATE
page) but it wasnt autorized, anyone know why? maybe im mistaken? maybe
its a bug and it should work?
Cheers,
Yonatan Ben-Nes
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
