Re: autocommit vs TRUNCATE et al - Mailing list pgsql-hackers

From Tom Lane
Subject Re: autocommit vs TRUNCATE et al
Date
Msg-id 10270.1035240397@sss.pgh.pa.us
Whole thread Raw
In response to Re: autocommit vs TRUNCATE et al  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: autocommit vs TRUNCATE et al  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
>> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>>> Maybe we can throw a WARNING when autocommit is on.  Would that make
>>> everyone happy?
>> 
>> I doubt it, because by the time you read the WARNING it's too late:
>> the statement's already committed.

> I assume the same limitation would hold for VACUUM, right, that you have
> to turn on autocommit mode to use it?

Yeah, it would, unless we wanted to throw in some additional hack to
distinguish VACUUM from the "more dangerous" cases.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: autocommit vs TRUNCATE et al
Next
From: Justin Clift
Date:
Subject: German version of the PostgreSQL "Advocacy and Marketing" site is ready