| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] DROP TABLE inside a transaction block |
| Date: | 2000-03-05 13:36:22 |
| Message-ID: | Pine.LNX.4.21.0003051434090.347-100000@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
> DROP
> test=# end;
> COMMIT
> test=# \d
> No relations found.
> --
> Tatsuo Ishii
>
> ************
>
>
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-03-05 13:39:37 | Re: [HACKERS] TransactionStateData and AbsoluteTime |
| Previous Message | Peter Eisentraut | 2000-03-05 13:29:50 | pg_pwd trigger to be removed |