Re: Big 7.1 open items - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Big 7.1 open items
Date
Msg-id 14752.960996980@sss.pgh.pa.us
Whole thread Raw
In response to Re: Big 7.1 open items  ("Oliver Elphick" <olly@lfix.co.uk>)
Responses Re: Big 7.1 open items  (Peter Eisentraut <peter_e@gmx.net>)
Re: Big 7.1 open items  (JanWieck@t-online.de (Jan Wieck))
List pgsql-hackers
"Oliver Elphick" <olly@lfix.co.uk> writes:
> I suggest that DROP TABLE in a transaction should not be allowed.

I had actually made it do that for a short time early this year,
and was shouted down.  On reflection I have to agree; it's too useful
to be able to do
begin;drop table foo;create table foo(new schema);...end;

You do indeed lose big if you suffer an error partway through, but
the answer to that is to fix our file naming conventions so that we
can support rollback of drop table.

Also note the complaints we've been getting about CREATE USER not
working inside a transaction block.  That is a case where someone
(Peter IIRC) took the more hard-line approach of emitting an error
instead of a warning.  I think it was not the right choice to make.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Developer's snapshot docs
Next
From: Peter Eisentraut
Date:
Subject: Re: Big 7.1 open items