From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Clarification to catalog-pg-class |
Date: | 2009-02-13 18:22:41 |
Message-ID: | 4995BA71.3030800@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2009-02-18 16:27:49 | Doc enhancements |
Previous Message | Peter Eisentraut | 2009-02-13 09:13:42 | Re: Clarification to catalog-pg-class |