Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del()

Поиск
Список
Период
Сортировка
Искать
От
Stephan Szabo
Тема
Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del()
Дата
Msg-id
20020612144317.F95080-100000@megazone23.bigpanda.com
Ответ на
Список
Дерево обсуждения
Troubleshooting SPI_execp() failed in RI_FKey_cascade_del() "Joshua b. Jore" <josh@greentechnologist.org>
Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del() Stephan Szabo <sszabo@megazone23.bigpanda.com>
Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del() "Joshua b. Jore" <josh@greentechnologist.org>
Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del() Stephan Szabo <sszabo@megazone23.bigpanda.com>
Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del() Tom Lane <tgl@sss.pgh.pa.us>
Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del() Stephan Szabo <sszabo@megazone23.bigpanda.com>
Re: Troubleshooting SPI_execp() failed in RI_FKey_cascade_del() "Joshua b. Jore" <josh@greentechnologist.org>

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).


В списке pgsql-general по дате отправления
От: Bruce Momjian
Дата:
От: Joshua b. Jore
Дата:
FAQ