Re: [HACKERS] DROP TABLE inside a transaction block - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] DROP TABLE inside a transaction block
Date
Msg-id 200003072340.SAA00329@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] DROP TABLE inside a transaction block  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [HACKERS] DROP TABLE inside a transaction block  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> Tatsuo Ishii writes:
> 
> > I see following in HISTORY:
> > 
> >     Disallow DROP TABLE/DROP INDEX inside a transaction block
> > 
> > However, it seems that this is not done with current?
> > 
> > test=# create table t1(i int);
> > CREATE
> > test=# begin;
> > BEGIN
> > test=# drop table t1;
> > NOTICE:  Caution: DROP TABLE cannot be rolled back, so don't abort now
> 
> Wow, with all due respect, that's pretty sh^H^Hpoor. That's like saying
> "Haha, either you commit your transaction or your database is fried." Any
> reason that's not an ERROR before anything destructive is done?

I tried it and the ABORT worked, so I have no idea now what is happening
here.


--  Bruce Momjian                        |  http://www.op.net/~candle pgman@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
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] pg_pwd trigger to be removed
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] xlog.c.patch for cygwin port.