Re: Moving 'hot' pages from buffer pool to heap

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Moving 'hot' pages from buffer pool to heap
Date: 2013-08-05 20:09:11
Message-ID: AEBC7171-1216-4AE3-BFE1-1AF910ACEBB8@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sent from my iPad

On 06-Aug-2013, at 1:14, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Atri Sharma <atri(dot)jiit(at)gmail(dot)com> writes:
>> I was experimenting with the idea of moving hot buffer pages from the
>> buffer pool to heap, thus allowing for normal removal of the hot
>> buffer page from the buffer pool and freeing the corresponding buffer
>> pool slot.
>
> Uh ... what? Why in the world would you want to force a hot page out of
> shared buffers? I fail to conceive of any scenario where that'd be a
> good idea.
>
>

Just experimenting though.I was thinking of scenarios where a page is pinned for long period of time.My concern was that it would lead to blocking of a buffer pool slot for that entire duration. The idea is to allocate a separate data structure for such hot pages in memory,and maintain them there.

Sorry if it is naive though.

Regards,

Atri

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Atri Sharma 2013-08-05 20:10:22 Re: Moving 'hot' pages from buffer pool to heap
Previous Message Robert Haas 2013-08-05 20:08:05 Re: [9.4 CF 1]Commitfest ... over!