Re: Large index operation crashes postgres - Mailing list pgsql-general

From Frans Hals
Subject Re: Large index operation crashes postgres
Date
Msg-id 39af1ed21003290039l157bafb9lc74631dbaa10d72f@mail.gmail.com
Whole thread Raw
In response to Large index operation crashes postgres  (Frans Hals <fhals7@googlemail.com>)
Responses Re: Large index operation crashes postgres  (strk <strk@keybit.net>)
List pgsql-general
Paul,

took your advice and installed Geos 3.2.0.
Index is now running for 14 hrs, postmaster is taking all the RAM.
Sadly it looks like the Geos update didn't save me.

Regards
Frans

2010/3/28 Paul Ramsey <pramsey@cleverelephant.ca>:
> GEOS 3.2 is backwards compatible, so you can install it overtop of 3.1
> and things will still work.
>
> P

>>
>> 2010/3/26 Paul Ramsey <pramsey@cleverelephant.ca>:
>>> Occams razor says it's PostGIS. However, I'm concerned about how old
>>> the code being run is. In particular, the library underneath PostGIS,
>>> GEOS, had a *lot* of memory work done on it over the last year. I'd
>>> like to see if things improve if you upgrade to GEOS 3.2.
>>
>

pgsql-general by date:

Previous
From: "Wappler, Robert"
Date:
Subject: Re: Connection Pooling
Next
From: Alban Hertroys
Date:
Subject: Re: Why index occupy less amount of space than the table with same structure.