From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Matthew Wakeling" <matthew(at)flymine(dot)org> |
Cc: | tv(at)fuzzy(dot)cz, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Postgres using more memory than it should |
Date: | 2008-12-03 19:14:43 |
Message-ID: | dcc563d10812031114v4dfe5f7chd6c35fa939cf8205@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Dec 3, 2008 at 9:59 AM, Matthew Wakeling <matthew(at)flymine(dot)org> wrote:
> On Wed, 3 Dec 2008, Scott Marlowe wrote:
>> Also, you should REALLY update to 8.3.5 as there are some nasty bugs
>> fixed from 8.3.0 you don't want to run into. Who knows, you might be
>> being bitten by one right now. Unlike other bits of software floating
>> around, pgsql updates are bug fix / security fix only, with no major
>> code changes allowed, since those go into the next release which is
>> usually ~1 year later anyway.
>
> It's possible, although I didn't see any relevant memory leaks in the
> release notes. This is one of the only machines we have that has not been
> upgraded, and it is on our schedule. Because it is running a slightly old
> version of RedHat Fedora, upgrading involves more horribleness than our
> sysadmin is willing to do on the fly with the server up.
That makes absolutely no sense. If it's an in house built rpm, you
just create a new one with the same .spec file, if it was built from
source it's a simple ./configure --youroptionshere ;make;make install.
You need a new sysadmin.
From | Date | Subject | |
---|---|---|---|
Next Message | Kynn Jones | 2008-12-03 19:31:02 | How to profile an "SQL script"? |
Previous Message | hubert depesz lubaczewski | 2008-12-03 17:53:47 | Re: Postgres using more memory than it should |