From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
---|---|
To: | "Michael Simms" <michael(at)tuxgames(dot)com> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #2784: Performance serious degrades over a period of a month |
Date: | 2006-11-28 11:08:15 |
Message-ID: | 456C189F.7080103@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-performance |
Michael Simms wrote:
> The following bug has been logged online:
>
> Bug reference: 2784
> Logged by: Michael Simms
> Email address: michael(at)tuxgames(dot)com
> PostgreSQL version: 8.1.4
> Operating system: Linux kernel 2.6.12
> Description: Performance serious degrades over a period of a month
> Details:
>
> OK, we have a database that runs perfectly well after a dump and restore,
> but over a period of a month or two, it just degrades to the point of
> uselessness.
> vacuumdb -a is run every 24 hours. We have also run for months at a time
> using -a -z but the effect doesnt change.
You might have a hung transaction that never finishes open, which
prevents vacuum from removing old tuple versions. Or you might have too
low FSM settings as others suggested.
I'd try running VACUUM VERBOSE by hand, and taking a good look at the
output. If there's nothing obviously wrong with it, please send the
output back to the list (or pgsql-performance, as Tom suggested), and
maybe we can help.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2006-11-28 11:34:39 | Re: BUG #2784: Performance serious degrades over a period |
Previous Message | Dave Page | 2006-11-28 08:58:41 | Re: BUG #2786: PGADMIN 1.6 |
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2006-11-28 11:34:39 | Re: BUG #2784: Performance serious degrades over a period |
Previous Message | Bruno Wolff III | 2006-11-28 04:26:27 | Re: BUG #2784: Performance serious degrades over a period of a month |