Re: PG 8.3 and large shared buffer settings - Mailing list pgsql-performance

From Gerhard Wiesinger
Subject Re: PG 8.3 and large shared buffer settings
Date
Msg-id alpine.LFD.2.00.0909261854410.11991@bbs.intern
Whole thread Raw
In response to Re: PG 8.3 and large shared buffer settings  (Greg Smith <gsmith@gregsmith.com>)
Responses Re: PG 8.3 and large shared buffer settings  (Jeff Janes <jeff.janes@gmail.com>)
List 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 by date:

Previous
From: Paul Ooi
Date:
Subject: Re: Bad performance of SELECT ... where id IN (...)
Next
From: Tom Lane
Date:
Subject: Re: Bad performance of SELECT ... where id IN (...)