From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Cc: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Pavan Deolasee" <pavan(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: HOT patch, missing things |
Date: | 2007-08-14 07:54:12 |
Message-ID: | 2e78013d0708140054k29fbc2b5h490fae74e6d82135@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/9/07, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> On Thu, 2007-08-09 at 15:46 +0530, Pavan Deolasee wrote:
> >
>
> > What if we just track the amount of potentially dead space in the
> > relation
> > (somebody had suggested that earlier in the thread) ? Every committed
> > UPDATE/DELETE and aborted UPDATE/INSERT would increment
> > the dead space. Whenever page fragmentation is repaired, either during
> > normal operation or during vacuum, the dead space is reduced by the
> > amount of reclaimed space. Autovacuum triggers whenever the percentage
> > of dead space increases beyond a threshold.
> >
> > We can some fine tuning to track the space consumed by redirect-dead
> > line pointers.
>
> Sounds great.
>
>
>
So do we have consensus here ? Fortunately, I think there won't be any
changes to user interface. Users can still use the vacuum_scale_factor to
tune autovacuum, but instead of percentage of dead tuples, it would
signify percentage of dead space in the relation.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-08-14 08:14:33 | Re: HOT patch, missing things |
Previous Message | Pavan Deolasee | 2007-08-14 07:44:42 | Re: HOT patch, missing things |