|
Home > Archive > PostgreSQL Discussion > September 2005 > Re: Questions about Rollback - after insert, update,
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Questions about Rollback - after insert, update,
|
|
| Yonatan Ben-Nes 2005-09-23, 7:23 am |
| Bruno Wolff III wrote:
> On Thu, Sep 22, 2005 at 15:20:17 -0400,
> Emi Lu <emilu@cs.concordia.ca> wrote:
>
>
>
> 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: [GENERAL] Table modifications with dependent views - best
> From:
> Tom Lane <tgl@sss.pgh.pa.us>
> Date:
> Fri, 22 Apr 2005 11:36:43 -0400
> To:
> Bruno Wolff III <bruno@wolff.to>
>
> To:
> Bruno Wolff III <bruno@wolff.to>
> CC:
> David Roussel <pgsql-general@diroussel.xsmail.com>, Michael Fuhr
> <mike@fuhr.org>, John Browne <jkbrowne@gmail.com>,
> pgsql-general@postgresql.org
>
>
> Bruno Wolff III <bruno@wolff.to> writes:
>
>
>
> 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
> PreventTransactionCh
ain, 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
| |
| Bruno Wolff III 2005-09-23, 11:24 am |
| On Fri, Sep 23, 2005 at 13:19:34 +0200,
Yonatan Ben-Nes <da@canaan.co.il> wrote:
>
> 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.
I think that is a different issue. This is a problem in that truncate takes
an exclusive lock on the table which might block other things going on
in the database. It could still be useful to rollback a table truncated
in error.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
|
|
|
|
|