best practice to avoid table bloat?

From: "Anibal David Acosta" <aa(at)devshock(dot)com>
To: <pgsql-performance(at)postgresql(dot)org>
Subject: best practice to avoid table bloat?
Date: 2012-08-16 20:33:56
Message-ID: 009d01cd7bee$785b1380$69113a80$@devshock.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi,

if I have a table that daily at night is deleted about 8 millions of rows
(table maybe has 9 millions) is recommended to do a vacuum analyze after
delete completes or can I leave this job to autovacuum?

This table is very active during the day but less active during night

I think that the only only thing where Postgres is weak, is in this area
(table and index bloat).

For some reason for the same amount of data every day postgres consume a
little more.

Thanks!

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andrew Dunstan 2012-08-16 20:48:29 Re: best practice to avoid table bloat?
Previous Message Strahinja Kustudić 2012-08-16 19:57:41 Re: Index Bloat Problem