Re: BUG #2294: SPI_connect() fails in trigger when a Foreignkey constraint exists on same table as trigger.

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "SPI_connect() failure(dot)" <jfitz(at)spacelink(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2294: SPI_connect() fails in trigger when a Foreignkey constraint exists on same table as trigger.
Date: 2006-03-01 18:57:59
Message-ID: 20060301185759.GA8165@surnet.cl
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

SPI_connect() failure. wrote:

> SPI_connect() throws "ERROR: SPI_connect failed" message (from
> backend/utils/adt/ri_trigger.c:378) when called from (at least) a before
> insert trigger on a table which also contains a foreign key constraint. The
> exit from the trigger function is inconsistent. This error message is
> emitted from ri_trigger.c but the return result
> from SPI_connect() in the trigger is SPI_OK_CONNECT. The insert operation
> does not commit to the database.

Do you call SPI_finish() in your trigger? You should not leave the
SPI connection open.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruno Wolff III 2006-03-01 19:18:23 Re: BUG #2292: Calling conventions in docs
Previous Message SPI_connect() failure. 2006-03-01 18:36:25 BUG #2294: SPI_connect() fails in trigger when a Foreignkey constraint exists on same table as trigger.