"Luke Lonergan" <[EMAIL PROTECTED]> writes:
> I think you're missing my/our point:

> The Postgres shared buffer cache algorithm appears to have a bug.  When
> there is a sequential scan the blocks are filling the entire shared
> buffer cache.  This should be "fixed".

No, this is not a bug; it is operating as designed.  The point of the
current bufmgr algorithm is to replace the page least recently used,
and that's what it's doing.

If you want to lobby for changing the algorithm, then you need to
explain why one test case on one platform justifies de-optimizing
for a lot of other cases.  In almost any concurrent-access situation
I think that what you are suggesting would be a dead loss --- for
instance we might as well forget about Jeff Davis' synchronized-scan

In any case, I'm still not convinced that you've identified the problem
correctly, because your explanation makes no sense to me.  How can the
processor's L2 cache improve access to data that it hasn't got yet?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at


Reply via email to