| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Moving 'hot' pages from buffer pool to heap |
| Date: | 2013-08-05 20:27:39 |
| Message-ID: | 4267.1375734459@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Atri Sharma <atri(dot)jiit(at)gmail(dot)com> writes:
> 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rodrigo Gonzalez | 2013-08-05 20:31:08 | Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters |
| Previous Message | Tom Lane | 2013-08-05 20:24:23 | Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters |