From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Bruce Momjian" <maillist(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: [HACKERS] md.c is feeling much better now, thank you |
Date: | 1999-09-03 03:07:03 |
Message-ID: | 001501bef5b9$6556e120$2801007e@cadzone.tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Bruce Momjian [mailto:maillist(at)candle(dot)pha(dot)pa(dot)us]
> Sent: Friday, September 03, 1999 12:22 AM
> To: Tom Lane
> Cc: Hiroshi Inoue; pgsql-hackers(at)postgreSQL(dot)org
> Subject: Re: [HACKERS] md.c is feeling much better now, thank you
>
>
> > BTW, it appears that DROP TABLE physically deletes the relation
> > *immediately*, which means that aborting a transaction that contains
> > a DROP TABLE does not work. But we knew that, didn't we?
>
> Yes, on TODO.
>
Hmm,Data Define commands are unrecoverable in many DBMS-s.
Is it necessary to allow PostgreSQL to execute Data Define
commands inside transactions ?
If so,is it possible ?
For example,should the following be possible ?
[A table t exists.]
begin;
drop table t;
create table t (dt int4);
insert into t values (1);
drop table t;
abort;
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 1999-09-03 04:41:19 | RE: [HACKERS] md.c is feeling much better now, thank you |
Previous Message | Hiroshi Inoue | 1999-09-03 03:05:15 | RE: [HACKERS] md.c is feeling much better now, thank you |