| From: | Frans Hals <fhals7(at)googlemail(dot)com> |
|---|---|
| To: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Large index operation crashes postgres |
| Date: | 2010-03-29 07:39:35 |
| Message-ID: | 39af1ed21003290039l157bafb9lc74631dbaa10d72f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)cleverelephant(dot)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(at)cleverelephant(dot)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.
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2010-03-29 08:15:00 | Re: Why index occupy less amount of space than the table with same structure. |
| Previous Message | Wappler, Robert | 2010-03-29 07:34:52 | Re: Connection Pooling |