Обсуждение: Is there something like MySQL enterprise monitor for Postgres?
or/and is there something to spot what are the most critical sql queries/function behind an application? Reading http://lstigile.wordpress.com/2007/12/27/cms_mysql/ it does look more a tool to tune MySQL configuration... what about tools to spot weak places in Postgres applications? thx -- Ivan Sergio Borgonovo http://www.webthatworks.it
Ivan Sergio Borgonovo <mail@webthatworks.it> schrieb: > or/and is there something to spot what are the most critical sql > queries/function behind an application? You can set "log_min_duration_statement" in your postgresql.conf to log all querys with a duration highter than that value. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknow) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
On Sat, 29 Dec 2007 10:16:50 +0100 Andreas Kretschmer <akretschmer@spamfence.net> wrote: > Ivan Sergio Borgonovo <mail@webthatworks.it> schrieb: > > > or/and is there something to spot what are the most critical sql > > queries/function behind an application? > > You can set "log_min_duration_statement" in your postgresql.conf to > log all querys with a duration highter than that value. That is interesting but it may be misleading (something that is below the threshold but get used thousands time won't be spotted). What about a log analyser? What about a configuration wizard that eat your logs and suggest improvement to the config? -- Ivan Sergio Borgonovo http://www.webthatworks.it
Log Analyzer : pgFouine http://pgfoundry.org/projects/pgfouine/ Regards, Le samedi 29 décembre 2007, Ivan Sergio Borgonovo a écrit : > On Sat, 29 Dec 2007 10:16:50 +0100 > > Andreas Kretschmer <akretschmer@spamfence.net> wrote: > > Ivan Sergio Borgonovo <mail@webthatworks.it> schrieb: > > > or/and is there something to spot what are the most critical sql > > > queries/function behind an application? > > > > You can set "log_min_duration_statement" in your postgresql.conf to > > log all querys with a duration highter than that value. > > That is interesting but it may be misleading (something that is below > the threshold but get used thousands time won't be spotted). > > What about a log analyser? > What about a configuration wizard that eat your logs and suggest > improvement to the config? -- Hervé Piedvache