| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Atesz <atesz(at)ritek(dot)hu> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: ACCESS EXCLUSIVE lock |
| Date: | 2006-10-18 15:28:20 |
| Message-ID: | 1161185300.8706.82.camel@state.g2switchworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, 2006-10-18 at 09:24, Atesz wrote:
> Hi!
>
> I have a problem with ACCESS EXCLUSIVE lock when I drop a reference in
> transaction. I have 2 tables:
> create table a(id SERIAL primary key);
> create table b(id SERIAL primary key references a(id));
>
> After that I have 2 processes: P1, P2
> In P1:
> begin;
> ALTER TABLE b DROP CONSTRAINT b_id_fkey;
>
> In P2:
> SELECT * FROM a;
>
> And I'm waiting for the result, but I don't get until P1 finishes.
> I know the DROP CONSTRAINT put an ACCESS EXCLUSIVE table LOCK into the
> TABLE a, and the SELECT is stopped by this LOCK in P2.
> Note: I cannot commit the P1 earlier, because it's a very long
> transaction (more hours, data conversion transaction)
> My question: Why need this strict locking?
>
> In my opinion there isn't exclusion between the DROP CONSTRAINT and the
> SELECT.
What if, a minute or two after the drop contraint, you issue a rollback?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-18 16:56:07 | Re: ACCESS EXCLUSIVE lock |
| Previous Message | Arnaud Lesauvage | 2006-10-18 15:05:48 | Re: Index on two columns not used |