Re: new autovacuum criterion for visible pages - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: new autovacuum criterion for visible pages
Date
Msg-id 90960589-eb00-e973-0711-e9e4581d6ae9@2ndquadrant.com
Whole thread Raw
In response to Re: new autovacuum criterion for visible pages  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: new autovacuum criterion for visible pages  (Vik Fearing <vik@2ndquadrant.fr>)
List pgsql-hackers
On 8/11/16 11:59 AM, Jeff Janes wrote:
> Insertions and HOT-updates clear vm bits but don't increment the
> counters that those existing parameters are compared to.
> 
> Also, the relationship between number of updated/deleted rows and the
> number of hint-bits cleared can be hard to predict due to possible
> clustering of the updates into the same blocks.  So it would be hard
> to know what to set the values to.

Well, the current threshold formulas aren't an exact science either.
They just trigger autovacuum often enough relative to table size and
activity.  Just fudging in the insert and HOT update counters times some
factor might be enough, and it would get this functionality out to all
users without more effort.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Relocation of tuple between release and re-acquire of tuple lock
Next
From: amul sul
Date:
Subject: Server crash due to SIGBUS(Bus Error) when trying to access the memory created using dsm_create().