Re: Moving 'hot' pages from buffer pool to heap - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Moving 'hot' pages from buffer pool to heap
Date
Msg-id 4267.1375734459@sss.pgh.pa.us
Whole thread Raw
In response to Re: Moving 'hot' pages from buffer pool to heap  (Atri Sharma <atri.jiit@gmail.com>)
Responses Re: Moving 'hot' pages from buffer pool to heap  (Atri Sharma <atri.jiit@gmail.com>)
List pgsql-hackers
Atri Sharma <atri.jiit@gmail.com> writes:
> Just experimenting though.I was thinking of scenarios where a page is pinned for long period of time.My concern was
thatit would lead to blocking of a buffer pool slot for that entire duration. The idea is to allocate a separate data
structurefor such hot pages in memory,and maintain them there.
 

You can't do that; such a copy could easily become stale, leading to wrong
query answers.  Perhaps more to the point, long-term pins (as opposed to
locks) aren't that problematic.  What problem do you think you're solving?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters
Next
From: Rodrigo Gonzalez
Date:
Subject: Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters