Justin Pryzby <pryzby@telsasoft.com> writes:
> It shows that the process is running FK triggers.
Indeed, and doing a seqscan therein. Normally I'd suppose that
this reflects a lack of an index, but RI_FKey_check should always
be doing something that matches the referenced table's unique
constraint, so why isn't it using that?
regards, tom lane
