From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Rainer Mager <rainer(at)vanten(dot)com> |
Cc: | Ognjen Blagojevic <ognjen(at)etf(dot)bg(dot)ac(dot)yu>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Postgres 8.x on Windows Server in production |
Date: | 2009-04-12 23:58:00 |
Message-ID: | dcc563d10904121658v65d9b4b1h2b0dfb79901afbfa@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sun, Apr 12, 2009 at 5:49 PM, Rainer Mager <rainer(at)vanten(dot)com> wrote:
> We're running 8.3, but when we started this server about 2 years ago it was
> an earlier 8.x, I don't remember which.
Cool. PostgreSQL is one of the few projects where I've always
recommended upgrading and keeping on the latest major version as soon
as possible after it comes out. This stands in stark contrast to
apache 2.0, which was out for over two years before it was worth the
effort to migrate to. The improvements just weren't worth the effort
to upgrade. I've seen enough performance and capability in each major
version of pgsql to make it worth the upgrade since 7.0 came out. I
think we've skipped one or two short releases, like 7.1 or 8.2, but
in general even those represented useful gains over previous versions.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-04-13 08:25:46 | Re: 2.6.26 kernel and PostgreSQL |
Previous Message | Rainer Mager | 2009-04-12 23:49:24 | Re: Postgres 8.x on Windows Server in production |