Re: best practice to avoid table bloat?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Anibal David Acosta" <aa(at)devshock(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: best practice to avoid table bloat?
Date: 2012-08-16 20:52:23
Message-ID: 502D173702000025000497D1@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Anibal David Acosta" <aa(at)devshock(dot)com> wrote:

> 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?

Deleting a high percentage of the rows should cause autovacuum to
deal with the table the next time it wakes up, so an explicit VACUUM
ANALYZE shouldn't be needed.

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

How are you measuring the data and how are you measuring the space?
And what version of PostgreSQL is this?

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Anibal David Acosta 2012-08-16 21:10:31 Re: best practice to avoid table bloat?
Previous Message Andrew Dunstan 2012-08-16 20:48:29 Re: best practice to avoid table bloat?