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

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

From: "Michael Simms" <michael(at)tuxgames(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2784: Performance serious degrades over a period of a month
Date: 2006-11-26 16:35:52
Message-ID: 200611261635.kAQGZqKE025405@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-performance
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.

The database is for a counter, not the most critical part of the system, but
a part of the system nonetheless. Other tables we have also degrade over
time, but the counter is the most pronounced. There seems to be no common
feature of the tables that degrade. All I know is that a series of queries
that are run on the database every 24 hours, after a dump/restore takes 2
hours. Now, 2 months after, it is taking over 12. We are seriously
considering switching to mysql to avoid this issue. 

But I wanted to let you guys have a chance to resolve the issue, we dont
have the manpower or expertise to fix it ourselves. I am willing to let
someone from the postgres development team have access to our server for a
period of time to have a look at the issue. This would need to be someone
extremely trustworthy as the database contains confidential client
information.

I am willing to wait 2 days for a response and for someone to take a look at
the problem. The performance degridation isnt something we can leave as it
is for long, and in 2 days time I will have to dump and restore the
database, which will reset it to a good state, and will mean I will have to
resort to the mysql switch instead.

Sorry this sounds a bit rushed, but it cant be helped, this is causing
*problems* and we need a solution, either a fix or a switch to another
database. Id rather a fix cos I like postgres, but Im willing to bite the
mysql bullet if I have to...

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2006-11-26 17:06:06
Subject: Re: When to vacuum a table?
Previous:From: Craig A. JamesDate: 2006-11-26 16:26:52
Subject: Re: When to vacuum a table?

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-11-26 16:36:52
Subject: Re: BUG #2769: "invalid memory alloc request size <n>" on startup
Previous:From: mikeDate: 2006-11-26 16:30:23
Subject: BUG #2783: insufficient base table information for updating or refreshing

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