Thread: FATAL 1: SPI: improper call to spi_printtup

I'm trying to get OpenNMS (which uses a lot JDBC) ported to MacOSX.
The backend runs just fine, but the frontend (a tomcat webapp) fails
when accessing the database, and in the postgresql log, I get the error
in the subject line.

I'm really not sure where to even try debugging, this.  I can find
absolutely nothing about it on the web.  Is this a JDBC issue?  A
postgresql one?  Tomcat?

Not a clue, this isn't enough information.

Can you show us more of the postgres logs?

AFAIK, the driver knows nothing about spi_printtup

Dave

On Sun, 2003-02-02 at 10:31, Benjamin Reed wrote:
> I'm trying to get OpenNMS (which uses a lot JDBC) ported to MacOSX.
> The backend runs just fine, but the frontend (a tomcat webapp) fails
> when accessing the database, and in the postgresql log, I get the error
> in the subject line.
>
> I'm really not sure where to even try debugging, this.  I can find
> absolutely nothing about it on the web.  Is this a JDBC issue?  A
> postgresql one?  Tomcat?
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
--
Dave Cramer <Dave@micro-automation.net>

On Sunday, February 2, 2003, at 11:33 AM, Dave Cramer wrote:

> Not a clue, this isn't enough information.
>
> Can you show us more of the postgres logs?
>
> AFAIK, the driver knows nothing about spi_printtup

Well, I don't know what's different exactly, but upgrading to
postgresql 7.3.1 (from 7.2.x) fixed it.

Thanks anyways...