pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nicola Mauri <nicola.mauri@saga.it>
To: pgsql-admin@postgresql.org
Subject: Abnormal storage consumption with autovacuum enabled
Date: Thu, 24 May 2007 17:56:10 +0200
Message-ID: <4655B59A.7080409@saga.it> (raw)


I'm using 8.1.4 on linux.
Autovacuum is enable with these settings:

stats_start_collector = on
stats_row_level = on
autovacuum = on                        
autovacuum_naptime = 60
autovacuum_vacuum_threshold = 1000   
autovacuum_analyze_threshold = 500  

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?
I'm quite sure that data in tables never reached that size, during 
normal operations.
Could be autovacuum not working properly?
How to diagnose or make sure that autovacuum is doing its job?

Thanks in advance!

Nicola





view thread (4+ messages)  latest in thread

Message-ID: <4655B59A.7080409@saga.it>
Permalink:  ../4655B59A.7080409@saga.it/
Also on:    postgresql.org/message-id/4655B59A.7080409@saga.it

 · 

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: nicola.mauri@saga.it
  Subject: Re: Abnormal storage consumption with autovacuum enabled
  In-Reply-To: <4655B59A.7080409@saga.it>

* 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