Thank you Regina for posting this information, excelent research indeed.
As for your message on
USING UNIQUE gid USING SRID=2249"
I have been using that part of the clause since I installed my postgres
database about 6 months ago, there the error on not using this info popped up
too.
I will dive into the stack and see if I can get my own test install.
The workaround I have for now is that when Postgres collapses in the production
environment it runs into the maximum number of restarts (3 times) that the
Microsoft Windows Service Manager offers it. So I guess that is a way to tackle
the problem for now.
Thanks for the help!
Obe, Regina schreef:
Slight update to my problem. I discovered I was able to get the
problematic layer to work in new Postgis 8.3RC 1.3.2 by changing my
mapserver condition from
DATA "the_geom FROM landparcels"
to
DATA "the_geom FROM landparcels USING UNIQUE gid USING SRID=2249"
The old way worked when using version
"PostgreSQL 8.2.1 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.4.2 (mingw-special)"
"POSTGIS="1.3.1" GEOS="3.0.0rc4-CAPI-1.3.3" PROJ="Rel. 4.5.0, 22 Oct
2006" USE_STATS"
The new one is running
"PostgreSQL 8.3RC2, compiled by Visual C++ build 1400"
"POSTGIS="1.3.2" GEOS="3.0.0rc4-CAPI-1.3.3" PROJ="Rel. 4.5.0, 22 Oct
2006" USE_STATS"
In both cases, I verified that I do have landparcels registered in the
geometry_columns table.
What is different about landparcels is that it's a view against
partitioned (inherited) tables.
The simple table layers work fine either way (e.g. they don't need the
USING....)
So I'm not sure its an issue with 1.3.1 vs. 1.3.2 against Mapserver
Postgis driver or PostreSQL 8.2 vs. 8.3RC2. Anyrate it is not a show
stopper.
Hope that helps,
Regina
-----Original Message-----
From: Obe, Regina
Sent: Friday, February 01, 2008 8:09 AM
To: 'PostGIS Users Discussion'
Subject: RE: [postgis-users] upgrade to postgres 8.3.2 on Windows
I've been playing with the 8.3.2 with PostGIS stackbuilder install and
comparing with my production install. Most went okay -> moved over one
of my spatial dbs to it. Did some simple spatial queries. I do seem to
be running into an issue with Mapserver 5.0 recognizing it. Strange it
works for some layers, but my more complex layers involving views a
Mapserver error.
Error in msPOSTGISLayerRetrievePGVersion(): Error executing POSTGIS
statement (msPOSTGISLayerRetrievePGVersion():select substring(version()
from 12 for (position('on' in version()) - 13))
Although querying the view directly in postgresql works fine.
I haven't done enough work to determine if its an issue with the way I
upgraded or some incompatibility between Mapserver and the new
PostgreSQL install. The same map file worked fine under 8.2 1.3.1
server.
Hope that helps,
Regina
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark
Cave-Ayland
Sent: Friday, February 01, 2008 2:39 AM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] upgrade to postgres 8.3.2 on Windows
On Mon, 2008-01-28 at 23:19 +0100, Milo van der Linden wrote:
Hello list,
Today I ran into an error on my postGIS database server. The database
is
hosted on Windows Server 2003 and is currently postgres version 8.2.5
with postgis 1.3.1-1
The error that I recieved said:
FATAL: could not create sigchld waiter thread: error code 1455
2008-01-28 12:03:39 LOG: logger shutting down
I found that this is a known bug with postgres on windows when you
reach
more then 300 concurrent connections.
Is it safe for me to upgrade to postGres 8.3.x? Will I be able to use
the latest windows postgis build that seems to be on: 1.3.2?
My system is in production so I just want to make sure.
Kind regards!
Milo van der Linden
Hi Milo,
Win32 PostGIS 1.3.2 for PostgreSQL 8.3 is available as part of the
StackBuilder infrastructure. Unfortunately due to the large amount of
manual work involved for an upgrade, I've had to mark the package as
non-upgradeable, however it should install just fine and you should be
able to move tables across from an old installation with pg_dump with no
problem.
Note: Make sure you are running the latest 8.3RC2 release - the
installer would hang part way through in earlier releases due to a
PostgreSQL bug.
Let us know how you get on!
ATB,
Mark.
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
