Re: How to enumerate foreign key constraints after migrating from 7.1.3?

>> Okay, more questions:
>> I see that adddepend detects old-style foreign key constraints by
>> looking for groups of 3 triggers having 6 or more identical function
>> arguments. Is that the best way to do it? It occurs to me that an
>> alternative might be to find triggers that call RI_FKey_check_ins()
>> and have the tgisconstraint flag set. Will either approach be safe in
>> postgres 7.4? Perhaps a combination of the two would be best?
>
>Without looking at the other triggers, you can't determine the referential
>action information since that's encoded in the functions the other two
>triggers call.

I understand that. I just want a list of the foreign key constraints
that are set on the columns of a table. I don't really need to know
what happens when a referenced column gets modified.