| From: | Markus Schaber <schabios(at)logi-track(dot)com> |
|---|---|
| To: | PostgreSQL Performance List <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Automagic tuning |
| Date: | 2004-07-27 13:15:31 |
| Message-ID: | 20040727151531.4f60b5b0@kingfisher.intern.logi-track.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hello,
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
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2004-07-27 14:13:25 | Re: best way to fetch next/prev record based on index |
| Previous Message | Merlin Moncure | 2004-07-27 13:07:02 | best way to fetch next/prev record based on index |