Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: "Mike Mascari" <mascarm(at)mascari(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Lincoln Yeoh" <lylyeoh(at)mecomb(dot)com>, <pgsql-general(at)postgresql(dot)org>, "PostgreSQL Developers List" <hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: 1999-11-26 21:51:55
Message-ID: 99112616564608.00541@lorc.wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Fri, 26 Nov 1999, Mike Mascari wrote:
> The DCOM remark was just a joke ;-). My remark concerning ORACLE was in
> response to Andreas' comment that implicit COMMITs of DDL statements was
> absurd. I wanted to simply point out that, since ORACLE has 70% market
> share,

I did not see the response to Andreas, nor did I see Andreas' assertion that it
was absurd. My apologies.

> counterparts and to be able to "undo" filesystem operations. That, it seems
> to
> me, will be a major undertaking and not going to happen any time soon...

Yes, that is true. As long as the storage manager relies on the filesystem for
table names, this will be a problem, unless filesystem deletions are delayed
until COMMIT, and filesystem creates are undone at a ROLLBACK.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthew Leo 1999-11-26 23:12:58 Re: PostgreSQL
Previous Message Mike Mascari 1999-11-26 20:32:04 Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 1999-11-26 22:48:05 RE: [HACKERS] Concurrent VACUUM: first results
Previous Message Mike Mascari 1999-11-26 20:32:04 Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions