Re: our buffer replacement strategy is kind of lame
От
Tom Lane
Тема
Re: our buffer replacement strategy is kind of lame
Дата
Msg-id
28052.1313341861@sss.pgh.pa.us
Ответ на
Re: our buffer replacement strategy is kind of lame (Simon Riggs)
Список
Дерево обсуждения
our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame daveg <daveg@sonic.net>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndquadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Greg Stark <stark@mit.edu>
Re: our buffer replacement strategy is kind of lame Greg Smith <greg@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Greg Stark <stark@mit.edu>
Re: our buffer replacement strategy is kind of lame Martijn van Oosterhout <kleptog@svana.org>
Re: our buffer replacement strategy is kind of lame Jim Nasby <jim@nasby.net>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Tom Lane <tgl@sss.pgh.pa.us>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Tom Lane <tgl@sss.pgh.pa.us>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndquadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Jim Nasby <jim@nasby.net>
Re: our buffer replacement strategy is kind of lame Greg Smith <greg@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Simon Riggs <simon@2ndQuadrant.com>
Re: our buffer replacement strategy is kind of lame Robert Haas <robertmhaas@gmail.com>
Simon Riggs writes: > On Sat, Aug 13, 2011 at 11:14 PM, Robert Haas wrote: >> I agree that something's missing. > I'm quoting you completely out of context here, but yes, something is missing. > We can't credibly do one test on usage count in shared buffers and > then start talking about how buffer management is all wrong. More generally: the originally presented facts suggest that there might be value in improving the "buffer access strategy" code that keeps particular operations from using all of shared_buffers. It seems to me to be a giant and unsubstantiated leap from that to the conclusion that there's anything wrong with the clock sweep algorithm. Moreover, several of the proposed "fixes" amount to reversion to methods that we already know are less good than the clock sweep, because we already tried them years ago. So I've been quite unimpressed with the quality of discussion in this thread. regards, tom lane
В списке pgsql-hackers по дате отправления