Re: Heavily modified big table bloat even in auto vacuum is running - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Heavily modified big table bloat even in auto vacuum is running
Date
Msg-id CAA4eK1L5CQFsAT6REMQktAAr0RbVz5inXMwwQxA03ChzF4xrCw@mail.gmail.com
Whole thread Raw
In response to Re: Heavily modified big table bloat even in auto vacuum is running  (Haribabu kommi <haribabu.kommi@huawei.com>)
Responses Re: Heavily modified big table bloat even in auto vacuum is running
List pgsql-hackers
On Thu, Dec 12, 2013 at 12:24 PM, Haribabu kommi
<haribabu.kommi@huawei.com> wrote:
> On 06 December 2013 11:57 Amit Kapila wrote:
>
> A simplified test and updated patch by taking care the above comment are attached in the mail.
> I am not able to reduce the test duration but changed as the test automatically exists after 45 mins run.
> Please check vacuum_test.sh file more details for running the test.
>
>               Auto vacuum count   Bloat size
> Master           15                220MB
> Patched_nkeep    18                213MB


I ran the attached test and the numbers are as below:               Auto vacuum count   Bloat sizeMaster
16                222MBPatched_nkeep     23                216MB
 

Here by Bloat size, it means the table_size after the test finished and
by Auto vacuum count, it means number of times Auto Vacuum is
triggered during test run.

It clearly shows that by setting number of dead tuples at end of Vacuum improves
the situation.
I am marking this (based on patch vacuum_fix_v7_nkeep.patch) as Ready
For Committer.


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: "imagenesis@gmail.com"
Date:
Subject: Re: dpkg-buildpackage fails on 9.2.6 on ubuntu 12.04.3 LTS
Next
From: David Rowley
Date:
Subject: Re: [PATCH] Negative Transition Aggregate Functions (WIP)