Re: Questions about Rollback - after insert, update,

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Yonatan Ben-Nes <da(at)canaan(dot)co(dot)il>
Cc: Emi Lu <emilu(at)cs(dot)concordia(dot)ca>, pgsql-general(at)postgresql(dot)org
Subject: Re: Questions about Rollback - after insert, update,
Date: 2005-09-23 14:30:30
Message-ID: 20050923143030.GE2298@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Sep 23, 2005 at 13:19:34 +0200,
Yonatan Ben-Nes <da(at)canaan(dot)co(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-09-23 14:38:41 Re: COPY - permission denied
Previous Message Michael Fuhr 2005-09-23 14:21:10 Re: COPY - permission denied