Tom Lane wrote:
> I'm confused ... is this patch being proposed for inclusion? I
> understood your previous message to say that it didn't help much.
This is only the patch for carving where there is any problem.
> The patch is buggy as posted, because it will try to do this:
> if (s
Katsuhiko Okano <[EMAIL PROTECTED]> writes:
>> (A) The algorithm which replaces a buffer is bad.
>> A time stamp does not become new until swapout completes
>> the swapout page.
>> If access is during swap at other pages, the swapout page will be
>> in the state where it is not used most,
>> It i
Katsuhiko Okano wrote:
> Since the cause was found and the provisional patch was made
> and solved about the CSStorm problem in previous mails, it reports.
(snip)
> (A) The algorithm which replaces a buffer is bad.
> A time stamp does not become new until swapout completes
> the swapout page.
> I
Hi,All.
Since the cause was found and the provisional patch was made
and solved about the CSStorm problem in previous mails, it reports.
> Subject: [HACKERS] poor performance with Context Switch Storm at TPC-W.
> Date: Tue, 11 Jul 2006 20:09:24 +0900
> From: Katsuhiko Okano <[EMAIL PROTECTED]>
>
Hi hackers,
I tackled the performance problem on SUBTRANS module with Okano.
He and I reach a conclusion that SubTrans log is heavily read on a specific
access pattern in my TPC-W implementation. There seems to be awful traffic
on SUBTRANS to check visivility of tuples in HeapTupleSatisfiesSnapsho
