Re: BUG #1220: "alter table rename to" inside a transaction - Mailing list pgsql-bugs

From Adam Sah
Subject Re: BUG #1220: "alter table rename to" inside a transaction
Date
Msg-id 412220D0.7010209@speakeasy.net
Whole thread Raw
In response to Re: BUG #1220: "alter table rename to" inside a transaction violates ACID ordering  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@postgresql.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

pgsql-bugs by date:

Previous
From: Stefanos Harhalakis
Date:
Subject: pgsql 8.0.0b1 - openssl detection
Next
From: "Ken Egervari"
Date:
Subject: I/O Bug