From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-www(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Steve Wampler <swampler(at)noao(dot)edu>, Postgres-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: [PERFORM] Help speeding up delete |
Date: | 2005-11-16 20:00:06 |
Message-ID: | 1132171206.4959.60.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance pgsql-www |
On Mon, 2005-11-14 at 18:42 -0500, Tom Lane wrote:
> Steve Wampler <swampler(at)noao(dot)edu> writes:
> > We've got an older system in production (PG 7.2.4).
>
> Update to 7.4 or later ;-)
>
> Quite seriously, if you're still using 7.2.4 for production purposes
> you could justifiably be accused of negligence. There are three or four
> data-loss-grade bugs fixed in the later 7.2.x releases, not to mention
> security holes; and that was before we abandoned support for 7.2.
> You *really* need to be thinking about an update.
Perhaps we should put a link on the home page underneath LATEST RELEASEs
saying
7.2: de-supported
with a link to a scary note along the lines of the above.
ISTM that there are still too many people on older releases.
We probably need an explanation of why we support so many releases (in
comparison to licenced software) and a note that this does not imply the
latest releases are not yet production (in comparison to MySQL or Sybase
who have been in beta for a very long time).
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-11-16 20:08:03 | Re: Hardware/OS recommendations for large databases ( |
Previous Message | Vivek Khera | 2005-11-16 19:24:38 | Re: Hardware/OS recommendations for large databases (5TB) |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-11-17 01:38:42 | Re: [PERFORM] Help speeding up delete |
Previous Message | Magnus Hagander | 2005-11-16 19:58:51 | Re: Updated press FAQ |