Re: old synchronized scan patch - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: old synchronized scan patch
Date
Msg-id 87slfukyud.fsf@enterprisedb.com
Whole thread Raw
In response to Re: old synchronized scan patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: old synchronized scan patch
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Sure, it should hang around for awhile, and will.  The problem is that
> its lifetime will be artificially inflated, so that the seqscan ends up
> kicking out other blocks that are really of greater importance, rather
> than recycling its own old blocks as it should.

I thought you had switched this all to a clock sweep algorithm. The clock
sweep method is supposed to be especially resistant to this since it doesn't
really matter how many times something is accessed, only whether it has been
accessed recently. As long as all the synchronized scans get their work done
before the clock comes around the block will be recycled the next time the
clock sweeps around and it finds nobody else is interested in that block.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Volkan YAZICI
Date:
Subject: Preserving Cluster-Wise Data
Next
From: Patrick Welche
Date:
Subject: unique key and nulls