From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | chris(at)bitmead(dot)com |
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 14:24:56 |
Message-ID: | 23162.958659896@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> writes:
> On the postgres side, what if you actually made the cache _smaller_,
> only caching important stuff like system tables or indexes. You yourself
> said it doesn't matter if you get it from the cache or the kernel, so
> why not let the kernel do it and prevent double buffering?
In fact I don't think it's productive to use an extremely large -B
setting. This is something that easily could be settled by experiment
--- do people actually see any significant improvement in performance
from increasing -B above, say, a few hundred?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2000-05-18 15:20:55 | Re: LONG: How to migrate data from MS-SQL7 to PostgreSQL 7.0 |
Previous Message | Jeffery Collins | 2000-05-18 12:39:46 | Re: initdb and "exit_nicely"... |