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

From Rod Taylor
Subject Re: Scope of constraint names
Date
Msg-id 1025818048.250.135.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
> > Anyway, the index example is a
> > bad example isn't it?  It already takes an lock on pg_class which is
> > just as global.
> 
> Au contraire; there is no exclusive lock needed at present.

Oh..  I thought pg_class was locked for any relation creation.  If thats
not the case, then I wouldn't want constraints to impose additional
limitations.

Misunderstanding on my part.





pgsql-hackers by date:

Previous
From: "J. R. Nield"
Date:
Subject: Re: Issues Outstanding for Point In Time Recovery (PITR)
Next
From: Rod Taylor
Date:
Subject: Re: BETWEEN Node & DROP COLUMN