Skip site navigation (1) Skip section navigation (2)

Re: adding foreign key constraint locks up table

From: Lew <noone(at)lewscanon(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: adding foreign key constraint locks up table
Date: 2010-12-28 13:34:30
Message-ID: ifcp05$odt$1@news.albasani.net (view raw or flat)
Thread:
Lists: pgsql-performance
On 12/28/2010 02:08 AM, kakarukeys wrote:
> I have a table "aaa" which is not very big. It has less than 10'000
> rows. However read operations on this table is very frequent.
>
> Whenever I try to create a new table "bbb" with foreign key pointing
> to "aaa". The operation locks, and reading "aaa" is not possible. The
> query also never seems to finish.

How long did you wait?

> ALTER TABLE "bbb" ADD CONSTRAINT "topic_id_refs_id_3942a46c6ab2c0b4"
> FOREIGN KEY ("topic_id") REFERENCES "aaa" ("id") DEFERRABLE INITIALLY
> DEFERRED;
>
> The current workaround is to create any new table at off-peak hours,
> e.g. [sic] midnight after restarting the db.
>
> I would like to know if there's any proper solution of this. Is this
> an issue affecting all relational databases? My db is PostgreSQL 8.3.

Naturally the system has to lock the table to alter it.  It also has to check 
that all records already in "bbb" satisfy the new constraint.

What's the longest you've waited for ALTER TABLE to release its lock?

-- 
Lew
Ceci n'est pas une pipe.

In response to

pgsql-performance by date

Next:From: Gurjeet SinghDate: 2010-12-28 13:37:33
Subject: Re: adding foreign key constraint locks up table
Previous:From: kakarukeysDate: 2010-12-28 07:08:45
Subject: adding foreign key constraint locks up table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group