On Mon, Mar 25, 2013 at 2:50 AM, Greg Smith <g...@2ndquadrant.com> wrote: > The idea I was thinking about is refactoring the background writer's role in > hint bit maintenance
A good first step might be to separate the "dirty" bit into two bits. "mandatory dirty" and "optional dirty". (Or maybe "hard dirty" and "soft dirty"). Hint bit updates could set the latter and then some later policy decision could be made about whether to bother writing out the buffer if it's only optionally dirty. My personal suspicion is that the right policy will look something like writing out 1/nth of the hint bit dirtied pages. Where n is something like MaxTuplesPerPage or perhaps the actual number of tuples per page. And perhaps that should only happen if there are any mandatory dirty pages waiting to be written or something like that. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
