[postgis-users] Possible issue with Geos on PostgreSQL 8.0Nat iveWindows

Obe, Regina DND\MIS robe.dnd at cityofboston.gov
Thu Jan 13 05:32:37 PST 2005

Actually this is what the RC4 does too.  Crash was a little harsh of a term.
I think in the cygwin version when we had this problem - it would crash the
whole backend and I would have to restart the postmaster service.

In 8.0 its one step better in that it just kills the current connection -
not the backend service - so I can continue by just creating another

-----Original Message-----
From: strk at refractions.net [mailto:strk at refractions.net] 
Sent: Thursday, January 13, 2005 5:42 AM
To: Steffen Macke
Cc: PostGIS Users Discussion
Subject: Re: [postgis-users] Possible issue with Geos on PostgreSQL

On Thu, Jan 13, 2005 at 12:37:30PM +0200, Steffen Macke wrote:
> >         select geosnoop('POLYGON((0 0, 1 1, 0 0))');
> > 
> > This didn't crash my backend. However, I can't vouch for the version 
> > of
> I'm using PostGIS as provided by PostgreSQL 8.0.0 RC5:
> dcmms=# select geosnoop('POLYGON((0 0, 1 1,0 0))');
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> What does the "correct" output look like?

No, it looks like this:

strk=# select '130', geosnoop('POLYGON((0 0, 1 1, 0 0))');
NOTICE:  IllegalArgumentException: Number of points must be 0 or >3
ERROR:  POSTGIS2GEOS conversion failed

postgis-users mailing list postgis-users at postgis.refractions.net

More information about the postgis-users mailing list