Re: Running a query twice to ensure cached results.

Martin,

On 6/13/06 6:00 AM, "Martijn van Oosterhout" <kleptog(at)svana(dot)org> wrote:

> What you might be able to do is to reduce its effect. The thing that
> occurs to me is to make hint bit changes only mark a page half-dirty.
> If the page is evicted because the space is needed in the buffer cache,
> it can be just dropped. However, the bgwriter will write it as normal.
> Hence, setting hint bits will become a sort of background operation,
> done when there's time.
>
> It seems to me that if a large table is loaded in a single transaction,
> the check for if the transaction is committed should be cheap because
> it's checking the same transaction id over and over.

Thanks for the tip - it's now in the mill for mulling over and finding
someone with the time to work something in...

- Luke