pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nicola Mauri <nicola.mauri@saga.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: Abnormal storage consumption with autovacuum enabled
Date: Thu, 24 May 2007 12:40:06 -0400
Message-ID: <6032.1180024806@sss.pgh.pa.us> (raw)
In-Reply-To: <4655B59A.7080409@saga.it>
References: <4655B59A.7080409@saga.it>

Nicola Mauri <nicola.mauri@saga.it> writes:
> Data stored in the database didn't groove very much in the last months 
> (pg_dump still generates a 4GB compressed file), but data files now 
> occupies 20 GB on disk.
> I know that a vacuum full or a full dump/restore is needed to reclaim 
> filesystem space. However, my question is: how this could have been 
> happened?

What do you have max_fsm_pages set to?  If it's too small, you'll get
bloat regardless of whether autovac is doing its thing.

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <6032.1180024806@sss.pgh.pa.us>
Permalink:  ../6032.1180024806@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6032.1180024806@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, nicola.mauri@saga.it
  Subject: Re: Abnormal storage consumption with autovacuum enabled
  In-Reply-To: <6032.1180024806@sss.pgh.pa.us>

* 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