From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Steve Wolfe" <steve(at)iboats(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: A question on EFFECTIVE_CACHE_SIZE |
Date: | 2001-06-01 00:54:20 |
Message-ID: | 25266.991356860@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Steve Wolfe" <steve(at)iboats(dot)com> writes:
> The docs list EFFECTIVE_CACHE_SIZE as being a run-time parameter with
> the postmaster's assumptions about the kernel disk cache size. Is that
> something that is determined by querying the kernel, or by other means?
It's just a constant by default. Even if there were a portable way to
query the kernel about how much memory there is, by what factor should
we reduce the result to allow for other applications? There's really
no way I can see to get a useful number automatically. This of course
begs the question whether the estimates derived using this number mean
much of anything :-(
> If it is determined in a less-than-precise manner, will setting it to a
> more precise value benefit much?
Probably not, but feel free to experiment and report back. I'd suggest
doing the experiments with current sources, since the cost estimation
code has changed noticeably since 7.1.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-01 00:58:34 | Re: [HACKERS] extra syntax on INSERT |
Previous Message | Tom Lane | 2001-06-01 00:49:09 | Re: dumping strategy |