Re: ERROR: XX000: function 60821C60 returned NULL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: ERROR: XX000: function 60821C60 returned NULL
Date: 2007-01-02 18:36:00
Message-ID: 7128.1167762960@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov> writes:
> I have an SQL job on SQL Server that dumps data to a table in
> PostGreSQL. This job worked fine when it was going against a PG 8.1.3
> server, but since my upgrade to PG 8.3, it has been working
> intermittently. Mostly not working and erroring out with
>
> ERROR: XX000: function 60821C60 returned NULL

That's a pretty low-level error; you shouldn't be able to trigger it
yourself without writing your own datatype or some such. Given the
set of types in your table, I'm betting that the bug is actually in
PostGIS, either in the geometry input converter or one of the index
support functions for geometry (you didn't show an index on the_point,
but is there one?). Try asking over there if they know of any such
problems as of 8.2.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry D. Khlebnikov 2007-01-03 04:24:47 BUG #2870: incorrect man page for postgres
Previous Message Obe, Regina 2007-01-02 17:38:22 Re: ERROR: XX000: function 60821C60 returned NULL