Re: ACCESS EXCLUSIVE lock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Atesz <atesz(at)ritek(dot)hu>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: ACCESS EXCLUSIVE lock
Date: 2006-10-18 16:56:07
Message-ID: 27872.1161190567@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Atesz <atesz(at)ritek(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Treat 2006-10-18 16:59:20 Re: Hints proposal
Previous Message Scott Marlowe 2006-10-18 15:28:20 Re: ACCESS EXCLUSIVE lock