Re: BUG #1220: "alter table rename to" inside a transaction

From: Adam Sah <asah(at)speakeasy(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: adam sah <asah(at)midgard(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1220: "alter table rename to" inside a transaction
Date: 2004-08-17 15:14:24
Message-ID: 412220D0.7010209@speakeasy.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

well, that's fine I suppose -- but then why does it work the other way
for DROP TABLE?

i.e. feels like we're confusing "implementation" and "desired semantics"

adam

Tom Lane wrote:

> "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
>
>>==> yikes! in window 2, it should have errored.
>
>
> Why are you of the opinion that this is a bug? The catalog lookup has
> to happen before the second xact can hope to obtain a lock on the table,
> no?
>
> regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2004-08-17 15:22:01 Re: [BUGS] 8.0.0beta1: -lpthread missing
Previous Message Tom Lane 2004-08-17 15:09:58 Re: BUG #1220: "alter table rename to" inside a transaction violates ACID ordering