Re: Bug: Buffer cache is not scan resistant

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug: Buffer cache is not scan resistant
Date: 2007-03-05 18:20:26
Message-ID: 200703051020.26226.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

> Yes, autovacuum is off, and bgwriter shouldn't have anything useful to
> do either, so I'm a bit at a loss what's going on --- but in any case,
> it doesn't look like we are cycling through the entire buffer space
> for each fetch.

I'd be happy to DTrace it, but I'm a little lost as to where to look in the
kernel. I'll see if I can find someone who knows more about memory
management than me (that ought to be easy).

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Luke Lonergan 2007-03-05 18:21:05 Re: Bug: Buffer cache is not scan resistant
Previous Message Stefan Kaltenbrunner 2007-03-05 18:06:22 Re: PrivateRefCount (for 8.3)