From: Anibal David Acosta <aa@devshock.com>
To: pgsql-performance@postgresql.org
Subject: best practice to avoid table bloat?
Date: Thu, 16 Aug 2012 16:33:56 -0400
Message-ID: <009d01cd7bee$785b1380$69113a80$@devshock.com> (raw)
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!
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-performance@postgresql.org
Cc: aa@devshock.com
Subject: Re: best practice to avoid table bloat?
In-Reply-To: <009d01cd7bee$785b1380$69113a80$@devshock.com>
* 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