| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Sven Clement" <sven(at)dsign(dot)lu> |
| Cc: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Kroeger" <andrew(at)sprocks(dot)gotdns(dot)com>, "Mark Lewis" <mark(dot)lewis(at)mir3(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Performance problems with large telemetric datasets on 7.4.2 |
| Date: | 2007-08-07 14:07:09 |
| Message-ID: | dcc563d10708070707qa57dd36q37f32014c1963bd7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 8/6/07, Sven Clement <sven(at)dsign(dot)lu> wrote:
> Ok thanks everybody for the calrification, after all now I allready learned
> something new... ;)
>
> My employer is currently thinking about migration to 8.2.x because of your
> feedback, so I think that the problem could be resolved... ;)
Note that whether the 8.2 migration is forthcoming, you should
definitely update to the latest patch version of 7.4. The update is
pretty much painless, although I remember there being a change around
7.4.13 that might have changed db behaviour for security reasons.
Release notes here:
http://www.postgresql.org/docs/8.2/static/release-7-4-13.html
Note that there are settings to work around the change in behaviour
should it create a problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2007-08-07 14:53:31 | Re: Update table performance |
| Previous Message | Piotr Kołaczkowski | 2007-08-07 13:44:17 | Re: Update table performance |