Re: Questions regarding contrib/tsearch

Andrew Sullivan <andrew(at)libertyrms(dot)info> writes:
> On Fri, Aug 02, 2002 at 09:39:54AM -0400, Tom Lane wrote:
>> If the database is being accessed heavily then it will tend to remain
>> swapped in; you don't have to (and really can't) do anything to tweak
>> the kernel-level and Postgres-level algorithms that determine this.
>> What you want is to ensure there's enough RAM to hold not only all the
>> database hotspots, but also all the other programs and working data
>> that the server machine will be running.

> I was wondering: is there an in-principle reason that there isn't any
> mechanism for locking a table in memory, or is it just that no-one
> has ever done it?

Why would you? If the table is being heavily accessed then it will stay
in memory. If it gets dropped from memory then the memory was needed
for something else that's more heavily used at the moment.

I'll grant you that buffer management algorithms are not perfect,
but I really doubt that "lock this table in core" is an improvement
over letting the system do its thing.

regards, tom lane