| From: | Lucas Lersch <lucaslersch(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Buffer Requests Trace |
| Date: | 2014-10-14 17:27:44 |
| Message-ID: | CAGR3jZB0kv717YY61bMuoyjKQGymJnnNZ_QT=xwpQ0ZeioyN-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I see this... but ReleaseBuffer() simply decrements the reference count of
page the buffer currently holds. Assuming that a ReadBuffer() -
ReleaseBuffer() pattern is used for interacting with the shared_buffers,
there will be a ReleaseBuffer() call for any page (heap or index) "loaded"
into the shared_buffers.
On Tue, Oct 14, 2014 at 7:21 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * Lucas Lersch (lucaslersch(at)gmail(dot)com) wrote:
> > Aren't heap and index requests supposed to go through the shared buffers
> > anyway?
>
> Sure they do, but a given page in shared_buffers can be used over and
> over again for different heap and index pages..
>
> Thanks,
>
> Stephen
>
--
Lucas Lersch
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-10-14 17:40:59 | Re: Buffer Requests Trace |
| Previous Message | Robert Haas | 2014-10-14 17:27:08 | Re: Expose options to explain? (track_io_timing) |