Re: Problems with batch using jdbc on postgresql 7.4.2 - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: Problems with batch using jdbc on postgresql 7.4.2
Date
Msg-id 407E11F6.403@opencloud.com
Whole thread Raw
In response to Problems with batch using jdbc on postgresql 7.4.2  ("Manuel García H." <mgarciah@ife.org.mx>)
List pgsql-jdbc
Manuel García H. wrote:
> Hi, somebody can help me?
>
> I using a batch sentence to update some data in distinct tables, one of
> that tables have a foreing key, then when I execute the batch using jdbc
> on postgresql 7.4.2 abort the batch and send me the next message:
>
> ERROR:  SPI_connect failed
> DEBUG:  AbortCurrentTransaction
> LOG:  statement: rollback; begin;
>
> the exactly sentence is a insert into table (,,,) values (,,,), the
> message was send just after execute the insert. If I removed the foreing
> key from the table , the batch worked correctly, but can´t drop the
> foreing key because I don´t want lost the integrity of data

On the face of it, this doesn't look like a JDBC problem: those messages
are not generated by the JDBC driver, and the driver does not do
anything special for INSERTs involving foreign keys.

What happens if you run the same transaction via psql?

-O

pgsql-jdbc by date:

Previous
From: James Robinson
Date:
Subject: JBoss and Statement Pooling endgame.
Next
From: Tom Lane
Date:
Subject: Re: Problems with batch using jdbc on postgresql 7.4.2