Caching of frequently used objects

From: Yann Michel <yann-postgresql(at)spline(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Caching of frequently used objects
Date: 2005-01-19 16:44:00
Message-ID: 20050119164400.GA13764@zoom.spline.inf.fu-berlin.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

as there were several questions about increasing performance in dwh
systems I was looking for some hints about how to "pin" an object to the
buffer so that they are not aged out due to the space is needed by any
other process or object. I know that in oracle you can do this by
defining a seperate buffer cache and to asign an object to that special
buffer cache. So you could assign objects to one pool and all other
objects will use the default one. I think even count(*) queries could
benefit from this buffer-splitting due to indexes might be pinned to
this buffer pool.
So my question is if there is already any comparable functionality or if
it is planed. I didn't find any comparable feature or TODO on the list.

Regards,
Yann

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew T. O'Connor 2005-01-19 16:50:33 Re: ARC patent
Previous Message Bruno Wolff III 2005-01-19 16:16:38 Re: Much Ado About COUNT(*)