Re: Is There Any Way ....

From: Stefan Weiss <spaceman(at)foo(dot)at>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Is There Any Way ....
Date: 2005-10-04 10:31:42
Message-ID: 43425A0E.2050305@foo.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 2005-09-30 01:21, Lane Van Ingen wrote:
> (3) Assure that a disk-based table is always in memory (outside of keeping
> it in
> memory buffers as a result of frequent activity which would prevent
> LRU
> operations from taking it out) ?

I was wondering about this too. IMO it would be useful to have a way to tell
PG that some tables were needed frequently, and should be cached if
possible. This would allow application developers to consider joins with
these tables as "cheap", even when querying on columns that are not indexed.
I'm thinking about smallish tables like users, groups, *types, etc which
would be needed every 2-3 queries, but might be swept out of RAM by one
large query in between. Keeping a table like "users" on a RAM fs would not
be an option, because the information is not volatile.

cheers,
stefan

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Simon Riggs 2005-10-04 11:24:54 Re: [PERFORM] A Better External Sort?
Previous Message Jan Aerts 2005-10-04 10:10:28 Re: index on custom function; explain