Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] DROP TABLE inside a transaction block

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] DROP TABLE inside a transaction block
Date: 2000-03-07 23:40:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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);
> > test=# 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

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2000-03-07 23:48:55
Subject: Re: [HACKERS] xlog.c.patch for cygwin port.
Previous:From: Bruce MomjianDate: 2000-03-07 23:39:24
Subject: Re: [HACKERS] pg_pwd trigger to be removed

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group