Re: Clock sweep not caching enough B-Tree leaf pages?
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Andres Freund <andres@2ndquadrant.com>,
Heikki Linnakangas <hlinnakangas@vmware.com>,
Greg Stark <stark@mit.edu>, Robert Haas <robertmhaas@gmail.com>,
Peter Geoghegan <pg@heroku.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2014-04-17T19:47:39Z
Lists: pgsql-hackers
On Thursday, April 17, 2014, Merlin Moncure <mmoncure@gmail.com> wrote: > > no -- I got you. My point was, that's a pure guess unless you base it > on evidence recorded on the page itself. Without that evidence, > (which requires writing) the operating is in a a better place to make > that guess so it's probably better to defer that decision. > Well, we'd only need that info to be stored in the buffer cache somehow- wouldn't have to go to disk or cause more I/O, of course. My thinking was that we could track it with the existing counter too, avoiding even that small amount of locking to write to the buffer page. Thanks, Stephen
Commits
-
Replace the BufMgrLock with separate locks on the lookup hashtable and
- 5d5087363d7c 8.1.0 cited