Re: best practice to avoid table bloat?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Anibal David Acosta <aa(at)devshock(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: best practice to avoid table bloat?
Date: 2012-08-16 20:48:29
Message-ID: 502D5C9D.4020502@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On 08/16/2012 04:33 PM, Anibal David Acosta wrote:
>
> 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.
>
>

Check out pg_reorg.

cheers

andrew

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2012-08-16 20:52:23 Re: best practice to avoid table bloat?
Previous Message Anibal David Acosta 2012-08-16 20:33:56 best practice to avoid table bloat?