[postgis-users] Is 2.1.8 stable?
pella.samu at gmail.com
Tue Sep 29 08:14:50 PDT 2015
>We recently upgraded from 32bit PostgreSQL 9.3.4 + PostGIS 2.1.2 to 64bit
> ...was crashing PostgreSQL.
64bit Postgresql 9.4 is very strange on Solaris 7 and older.
"184.108.40.206. 64-bit Build Sometimes Crashes"
"On Solaris 7 and older, the 64-bit version of libc has a buggy vsnprintf
routine, which leads to erratic core dumps in PostgreSQL. The simplest
known workaround is .... " >
Maybe this is related to (postgis) vsnprintf ?
2015-09-29 16:52 GMT+02:00 Paul J. Caritj <caritj at gmail.com>:
> My 2 cents.:
> My recent [bad] experience with a Postgis bug, described in my email to
> this list last week, was on 2.1.8 (but running on Windows 7, not Solaris).
> Fortunately for me, I was just using it to do a little GIS hacking on my
> desktop. But after my experiences of the last few weeks, it would take a
> lot of convincing to get me to use Postgis 2.1.8 in a production
> environment. (Although, supposedly, the bug I encountered was also present
> in 2.1.2, so YMMV.)
> On Tue, Sep 29, 2015 at 6:17 AM, Kiriakos Georgiou <zebekias at gmail.com>
>> We recently upgraded from 32bit PostgreSQL 9.3.4 + PostGIS 2.1.2 to 64bit
>> PostgreSQL 9.4.4 + PostGIS 2.1.8. All the required packages for PostGIS
>> were upgraded to their latest versions. This is on Solaris 10 with the gcc
>> that ships by sun (v3.x)
>> All went well, except when we did regression testing we noticed a
>> complex spatial query that goes from geometry to geography and back (with
>> SRID changes along the way) was crashing PostgreSQL. We broke down that
>> code to simpler pieces and it worked, but later we found other code that
>> worked before that would crash the database backend process too.
>> Unfortunately our application is complex to the point that we haven't
>> been able to distill the query down to something simple that I can open a
>> ticket with. All I have are core dumps and my hunch that downgrading
>> PostGIS might give some clues (if things go back to being stable.)
>> Any experiences with 2.1.8 with regards to stability that you can share?
>> We haven't tested 2.1.5, I'll update on how that goes.
>> postgis-users mailing list
>> postgis-users at lists.osgeo.org
> postgis-users mailing list
> postgis-users at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-users