Skip site navigation (1) Skip section navigation (2)

Re: BUG #2784: Performance serious degrades over a period of a month

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 02:59:06
Message-ID: 27598.1164682746@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-performance
"Michael Simms" <michael(at)tuxgames(dot)com> writes:
> 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 probably need significantly-more-frequent vacuuming.  Have you
considered autovacuum?

This is not a bug --- you'd get better help on the pgsql-performance
mailing list.

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Bruno Wolff IIIDate: 2006-11-28 04:26:27
Subject: Re: BUG #2784: Performance serious degrades over a period of a month
Previous:From: Kevin GrittnerDate: 2006-11-27 18:59:48
Subject: Re: When to vacuum a table?

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-11-28 03:01:06
Subject: Re: BUG #2782: Too Many open files in system
Previous:From: Tom LaneDate: 2006-11-28 02:56:50
Subject: Re: BUG #2781: database dump/restore problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group