| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mike Mascari" <mascarm(at)mascari(dot)com> |
| Cc: | "Tim Perdue" <tperdue(at)valinux(dot)com>, pgsql-hackers(at)hub(dot)org |
| Subject: | Re: Fragged State in 7.0.2 |
| Date: | 2000-09-06 14:52:28 |
| Message-ID: | 14370.968251948@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mike Mascari" <mascarm(at)mascari(dot)com> writes:
> Rolling back DDL statements properly
> in a MVCC transaction environment is very difficult, as
> you can imagine. IIRC Oracle cheats, Informix and DEC Rdb
> lock the DDL target until transaction commit, etc. If
> the PostgreSQL team implements their stated goal in this
> area, it will be far superior to its commercial counterparts.
AFAIK we intend to keep the current behavior of exclusively
locking any table you try to drop or modify. So it'll be
pretty much like the Informix/RDB behavior.
But yes, at the moment DROP or RENAME inside a transaction is
pretty risky (and 7.0 tells you so, with an annoying NOTICE).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-09-06 15:02:01 | AW: AW: A fine point about OUTER JOIN semantics |
| Previous Message | Tom Lane | 2000-09-06 14:39:12 | Re: Re: [PATCHES] Important 7.0.* fix to ensure buffers are released |