From: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
---|---|
To: | Paul Smith <paulsmith(at)pobox(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Out of memory error |
Date: | 2009-07-07 00:26:01 |
Message-ID: | 30fe546d0907061726h7c290ddfl72c2babd0caa772a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If you are on PostGIS < 1.3.4 there are substantial memory leaks in
intersects() for point/polygon cases. Upgrading to 1.3.6 is
recommended.
P
On Mon, Jul 6, 2009 at 1:39 PM, Paul Smith<paulsmith(at)pobox(dot)com> wrote:
> On Mon, Jul 6, 2009 at 3:34 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Clearly a memory leak, but it's not so clear exactly what's causing it.
>> What's that intersects() function? Can you put together a
>> self-contained test case?
>
> It's actually ST_Intersects from PostGIS (some of the PostGIS function
> names are still recognize without the leading "ST_").
>
> http://postgis.refractions.net/documentation/manual-1.3/ch06.html#id2574404
>
> # select postgis_version();
> postgis_version
> ---------------------------------------
> 1.3 USE_GEOS=1 USE_PROJ=1 USE_STATS=1
>
> -Paul
>
> --
> Paul Smith
> http://www.pauladamsmith.com/
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Smith | 2009-07-07 01:45:17 | Re: Out of memory error |
Previous Message | Ivan Sergio Borgonovo | 2009-07-07 00:22:35 | Re: combine multiple row values in to one row |