| From: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Common slow query reasons - help with a special log |
| Date: | 2011-12-10 17:25:43 |
| Message-ID: | 20111210172543.GA21157@tux |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Daniel Cristian Cruz <danielcristian(at)gmail(dot)com> wrote:
> Hi all,
>
> I'm trying to figure out some common slow queries running on the server, by
> analyzing the slow queries log.
>
> I found debug_print_parse, debug_print_rewritten, debug_print_plan, which are
> too much verbose and logs all queries.
>
> I was thinking in something like a simple explain analyze just for queries
> logged with log_min_duration_statement with the query too.
>
> Is there a way to configure PostgreSQL to get this kind of information, maybe
> I'm missing something? Is it too hard to hack into sources and do it by hand? I
> never touched PostgreSQL sources.
Consider auto_explain, it's a contrib-modul, see
http://www.postgresql.org/docs/9.1/interactive/auto-explain.html
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." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2011-12-10 17:25:52 | Re: Common slow query reasons - help with a special log |
| Previous Message | Daniel Cristian Cruz | 2011-12-10 16:52:09 | Common slow query reasons - help with a special log |