From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | "Jeff Hoffmann" <jeff(at)propertykey(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: question about index cost estimates |
Date: | 2000-05-18 05:44:04 |
Message-ID: | 22144.958628644@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> pages_fetched seems to be able to be greater than
> baserel->pages. But if there's sufficiently large buffer
> space pages_fetched would be <= baserel->pages.
> Are there any assupmtions about buffer space ?
Right now cost_index doesn't try to account for that, because
it doesn't have any way of knowing the relevant buffer-space
parameter. (As I said to Jeff, we have to consider kernel
buffer space not just the number of Postgres shared buffers.)
cost_nonsequential_access does have a dependence on (a totally
bogus estimate of) effective cache size, but it's a considerably
weaker dependence than you suggest above. If we had a reliable
estimate of cache size I'd be inclined to restructure this code
quite a bit...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-05-18 06:58:12 | Re: Trigger function languages |
Previous Message | Thomas Lockhart | 2000-05-18 05:41:37 | Re: Proposal for fixing numeric type-resolution issues |