Re: PG 8.3 and large shared buffer settings
От | Gerhard Wiesinger |
---|---|
Тема | Re: PG 8.3 and large shared buffer settings |
Дата | |
Msg-id | alpine.LFD.2.00.0909261854410.11991@bbs.intern обсуждение исходный текст |
Ответ на | Re: PG 8.3 and large shared buffer settings (Greg Smith <gsmith@gregsmith.com>) |
Ответы |
Re: PG 8.3 and large shared buffer settings
|
Список | pgsql-performance |
On Sat, 26 Sep 2009, Greg Smith wrote: > On Fri, 25 Sep 2009, Jeff Janes wrote: > >> Does it do this even if the block was already in shared_buffers? > > Usually not. The buffer ring algorithm is used to manage pages that are read > in specifically to satisfy a sequential scan (there's a slightly different > ring method used for VACUUM too). If the buffer you need is already > available and not "pinned" (locked by someone else), it's not read from disk > again. Instead, its usage count is incremently only if it's at zero (this > doesn't count as a use unless it's about to be evicted as unused), and it's > returned without being added to the ring. > Hello Greg, What happens when a postmaster dies (e.g. core dump, kill -9, etc.). How is reference counting cleaned up and the lock removed? Thnx. Ciao, Gerhard -- http://www.wiesinger.com/
В списке pgsql-performance по дате отправления: