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:[EMAIL PROTECTED] | www.logi-track.com

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to