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" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
