Re: Table bloat in 8.3

From: Sam Mason <sam(at)samason(dot)me(dot)uk>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Table bloat in 8.3
Date: 2008-11-13 19:26:26
Message-ID: 20081113192625.GW2459@frubble.xen.chris-lamb.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Nov 13, 2008 at 02:03:22PM -0500, pgsql-general(at)ian(dot)org wrote:
> I have several tables that when I run VACUUM FULL on, they are under 200k,
> but after a day of records getting added they grow to 10 to 20 megabytes.
> They get new inserts and a small number of deletes and updates.
>
> A normal VACUUM does not shrink the table size, but FULL does, or dumping
> and restoring the database to a test server.

I'd not expect to use a FULL vacuum as part of routine maintaince.
Normally, tables like this will grow until they reach some steady state
and then stay there. 14MB seems a bit big for something that you'd
expect to fit in 200KB though. Autovacuum is enabled by default in 8.3,
but has it been disabled for some reason here?

A useful thing to post would be the output of a VACUUM VERBOSE on this
table when it's grown for a day. It may give some clue as to what's
going on.

Sam

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nikolas Everett 2008-11-13 19:27:34 Re: Table bloat in 8.3
Previous Message Sam Mason 2008-11-13 19:14:02 Re: sort_mem param of postgresql.conf