Re: Questions regarding contrib/tsearch

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?

A

--
----
Andrew Sullivan                               87 Mowat Avenue
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M6K 3E3
                                         +1 416 646 3304 x110