Re: Moving 'hot' pages from buffer pool to heap
От | Atri Sharma |
---|---|
Тема | Re: Moving 'hot' pages from buffer pool to heap |
Дата | |
Msg-id | 7F0B3991-6051-416C-A23D-D2670846AEC9@gmail.com обсуждение исходный текст |
Ответ на | Re: Moving 'hot' pages from buffer pool to heap (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Sent from my iPad On 06-Aug-2013, at 1:57, Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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? > > Yeah,long term pins are something I was thinking of solving with this.Now that you mention it, I think my main concern wasn'tlong term pins,rather,anything that doesn't allow for page eviction for a long time. Regards, Atri
В списке pgsql-hackers по дате отправления: