| From: | Frans Hals <fhals7(at)googlemail(dot)com> |
|---|---|
| To: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Large index operation crashes postgres |
| Date: | 2010-03-27 20:27:32 |
| Message-ID: | 39af1ed21003271327s2f8bcb44y15018eacbf333139@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Paul,
do you know, if Postgis 1.3.6 will survive, if I install Geos 3.2 over
it? Currently, there's Geos 3.1.1 installed.
I remember, I had to downgrade Postgis/Geos to be compatible with
Postgres 8.3.9. As I "herited" the database from a 8.3.9 dump, I
needed to fit my installation before restoring the dump.
Thanks
Frans
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 | Faheem Mitha | 2010-03-28 06:08:45 | simultaneously reducing both memory usage and runtime for a query |
| Previous Message | Frans Hals | 2010-03-27 20:16:19 | Re: Large index operation crashes postgres |