On Sat, May 14, 2011 at 3:13 AM, Josh Berkus <josh@xxxxxxxxxxxx> wrote: > This is what the combination of random_page_cost and > effective_cache_size ought to supply, but I don't think it does, quite. I think random_page_cost causes problems because I need to combine disk random access time, which I can measure, with a guesstimate of the disk cache hit rate. It would be lovely if these two variables were separate. It would be even lovelier if the disk cache hit rate could be probed at run time and didn't need setting at all, but I suspect that isn't possible on some platforms. -- Stuart Bishop <stuart@xxxxxxxxxxxxxxxx> http://www.stuartbishop.net/ -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
