pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Enzo D'addario <enzo@pienetworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuum taking longer over time
Date: Tue, 28 Jun 2005 00:55:17 -0400
Message-ID: <42C0D835.7000603@zeut.net> (raw)
In-Reply-To: <1119919340.4885.5.camel@tuppy.pienetworks.com>
References: <1119919340.4885.5.camel@tuppy.pienetworks.com>

Enzo D'addario wrote:

>Hi All,
>
>I currently have postgres 7.4.2 running on a dedicated server which has
>1GB RAM, a Pentium 4 2600 Mhz processor, uses ReiserFS filesystem and is
>running Debian stable.
>
>After approximately 1 month I have to dump & restore the database
>because vacuum time spirals out of control. To give you an idea of what
>I experience, when the DB is restored it takes 1 hour to vacuum, however
>by the time the restore is 30 days old it can take up to 6 hours. I
>never experienced such issues with earlier versions of postgres.
>
>The DB is approximately 6 GB in size and is vacuumed analyzed nightly
>because of a relatively high number of transactions per day. 
>
>Another thing that I noticed from the vacuum logs is that the total
>pages needed shortly after restore is approximately 17000 and ends up
>over 50000 by the time the restore is 30 days old. 
>
>Does this mean the DB is becoming fragmented?
>  
>

Not fragmented, but bloated.  Sounds like you need to vacuum more often 
and / or increase your FSM settings.

>Will upgrading to postgres 8.0 resolve this problem?
>  
>

No, I think a more agressive vacuum regiment and / or larger FSM 
settings will solve this even 7.4.  Lots of people either setup cron to 
hit their more active tables more often, or use pg_autovacuum.

Good luck.




view thread (3+ messages)

Message-ID: <42C0D835.7000603@zeut.net>
Permalink:  ../42C0D835.7000603@zeut.net/
Also on:    postgresql.org/message-id/42C0D835.7000603@zeut.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: matthew@zeut.net, enzo@pienetworks.com
  Subject: Re: vacuum taking longer over time
  In-Reply-To: <42C0D835.7000603@zeut.net>
  References: <1119919340.4885.5.camel@tuppy.pienetworks.com> <42C0D835.7000603@zeut.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox