> > renaming at abort time has to be done in the right order relative to
> > dropping tables created during the xact, or else BEGIN; DROP TABLE foo;
> > CREATE TABLE foo; ABORT won't work right. Currently, an attempt to
> > lock a table always involves making a relcache entry first, and the
> > relcache will try to open the underlying files as soon as you do that,
> > so other backends trying to touch the dying table for the first time
> > would get unexpected error messages. Probably a few other things.
> >
> > In short, a lot of work for a very marginal feature. How many other
> > DBMSes permit DROP TABLE to be rolled back? How many users care?
>
> Oracle auto-commits current in-progress transaction before
> execution of any DDL statement and executes such statements in
> separate transaction.
That's cheating!
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
