Re: Heavily modified big table bloat even in auto vacuum is running

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Haribabu kommi <haribabu(dot)kommi(at)huawei(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Heavily modified big table bloat even in auto vacuum is running
Date: 2013-10-11 23:10:49
Message-ID: 1381533049.83343.YahooMailNeo@web162906.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Haribabu kommi <haribabu(dot)kommi(at)huawei(dot)com> wrote:

> To handle the above case instead of directly resetting the dead
> tuples as zero, how if the exact dead tuples are removed from the
> table stats. With this approach vacuum gets triggered frequently
> thus it reduces the bloat.
> Patch for the same is attached in the mail.

Please add this to the open CommitFest to ensure that it gets
reviewed:

https://commitfest.postgresql.org/action/commitfest_view/open

For more information about the process, see:

http://wiki.postgresql.org/wiki/CommitFest

You may also want to reveiw:

http://wiki.postgresql.org/wiki/Developer_FAQ

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2013-10-12 00:14:36 Re: Auto-tuning work_mem and maintenance_work_mem
Previous Message Kevin Grittner 2013-10-11 22:39:51 Re: Auto-tuning work_mem and maintenance_work_mem