Message-ID: <4995BA71.3030800@agliodbs.com>
Date: Fri, 13 Feb 2009 10:22:41 -0800
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: Bruce Momjian <bruce@momjian.us>, pgsql-docs@postgresql.org
Subject: Re: Clarification to catalog-pg-class
References: <200902120317.n1C3HCO16080@momjian.us> <499539C6.9030700@gmx.net>
In-Reply-To: <499539C6.9030700@gmx.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Peter,

> I suppose a more constructive point would be, where are the other 
> constraint types kept track of?

AFAICT, we're not tracking them in pg_class at all anymore, except that 
FKs will set relhastrigger=true in the absensce of any other triggers.

The confusion on this particular line is caused by the "see 
pg_constraint catalog", which covers *all* constraints, whereas 
relconstrains only counts the CHECK constraints and not other types. 
That's why I think a small emphasis on CHECK would prevent people from 
being confused again.

Of course, at this point, we've spent more time discussing the issue 
than people have been confused by it, probably.

--Josh