SELECT blocking on ALTER TABLE ADD FOREIGN KEY

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: SELECT blocking on ALTER TABLE ADD FOREIGN KEY
Date: 2003-06-11 18:39:08
Message-ID: 20030611183908.GN40542@flake.decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Is it really necessary to block reads on a table that is affected by
adding a foreign key constraint? I can see why you wouldn't want UPDATES
or INSERTS on the child table or DELETEs on the parent, but select
should be fine on both tables, no?
--
Jim C. Nasby (aka Decibel!) jim(at)nasby(dot)net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-06-11 18:46:10 Re: Please, apply patch for current CVS
Previous Message Forest Wilkinson 2003-06-11 17:43:50 Re: [GENERAL] How to enumerate foreign key constraints after migrating from 7.1.3?