Re: Scope of constraint names - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Scope of constraint names
Date
Msg-id 1025732431.250.30.camel@jester
Whole thread Raw
In response to Re: Scope of constraint names  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Scope of constraint names  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> I don't buy that argument even for foreign keys --- and remember that
> pg_constraint will also hold entries for CHECK, UNIQUE, and PRIMARY KEY
> constraints.  I don't want to have to take a global lock whenever we
> create an index.

I don't understand why a global lock is necessary -- and not simply a
lock on the pg_constraint table and the relations the constraint is
applied to (foreign key locks two, all others one).





pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: libpq++ build problems
Next
From: Hans-Jürgen Schönig
Date:
Subject: Compiling PostgreSQL with Intel C Compiler 6.0