Re: ACCESS EXCLUSIVE lock - Mailing list pgsql-performance

From Tom Lane
Subject Re: ACCESS EXCLUSIVE lock
Date
Msg-id 27872.1161190567@sss.pgh.pa.us
Whole thread Raw
In response to ACCESS EXCLUSIVE lock  (Atesz <atesz@ritek.hu>)
Responses Re: ACCESS EXCLUSIVE lock  (Atesz <atesz@ritek.hu>)
List pgsql-performance
Atesz <atesz@ritek.hu> writes:
> My question:  Why need this strict locking?
> In my opinion there isn't exclusion between the DROP CONSTRAINT and the
> SELECT.

This isn't going to be changed, because the likely direction of future
development is that the planner will start making use of constraints
even for SELECT queries.  This means that a DROP CONSTRAINT operation
could invalidate the plan of a SELECT query, so the locking will be
essential.

            regards, tom lane

pgsql-performance by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: ACCESS EXCLUSIVE lock
Next
From: Robert Treat
Date:
Subject: Re: Hints proposal