> Hum. So the immediate problem is that st_transform() is failing to
> schema-qualify its reference to spatial_ref_sys. Think you need to
> be filing that one against PostGIS, not us.
Yah was sort of thinking that.
Though what about this -- isn't this case a bit more common
http://postgis.re
schema issue in restore.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thu 6/18/2009 1:59 PM
To: Obe, Regina
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4860: Indexes gone after restore
"Obe, Regina" writes:
> Your example seems to work fin
they have
similar issues or if its just something about my config.
Thanks,
Regina
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thu 6/18/2009 12:53 PM
To: Obe, Regina
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4860: Indexes gone after restore
&q
"Regina Obe" <[EMAIL PROTECTED]> writes:
> Description:Clustering on GIST INDEX clobbers records in table
> intermittently
> This doesn't always happen to me but does intermittently, and for others it
> happens all the time.
> I wonder whether this is fixed by this recent patch:
> http://
Correction upgrade to PG 8.2
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Obe, Regina
Sent: Tuesday, January 02, 2007 12:36 PM
To: pgsql-bugs@postgresql.org
Subject: [BUGS] ERROR: XX000: function 60821C60 returned NULL
I have an SQL job on SQL
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
