Are there any tools that help with postgres/postgis performance tuning?
So they measure the acutal tuple costs and cpu power, or suggest optimal
values for the index sample counts?
I could imagine that some profiling on a typical workload (or realistic
simulation thereof) could be automatically converted into hints how to
tweak the config file.
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios(at)logi-track(dot)com | www.logi-track.com
pgsql-performance by date
|Next:||From: Markus Schaber||Date: 2004-07-27 14:13:25|
|Subject: Re: best way to fetch next/prev record based on index|
|Previous:||From: Merlin Moncure||Date: 2004-07-27 13:07:02|
|Subject: best way to fetch next/prev record based on index|