On Wed, 12 Jun 2002, Joshua b. Jore wrote:
> I found the function in src/backend/utils/adt/ri_triggers.c. A previous
> note in the archives says it might be an invalid SPI command/statement. So
> how do I debug that? Which traces ought to be turned on?
Turn on query logging probably is the first step. A common cause of this
would be if there's a rule that might be rewriting the query to something
else (for cascade_del I'd guess that'd be a delete rule on the foreign
key table).