Re: Common slow query reasons - help with a special log

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Common slow query reasons - help with a special log
Date: 2011-12-10 17:25:52
Message-ID: 4EE39620.5020703@fuzzy.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

There's auto_explain contrib module that does exactly what you're asking
for. Anyway, explain analyze is quite expensive - think twice before
enabling that on production server where you already have performance
issues.

Tomas

On 10.12.2011 17:52, Daniel Cristian Cruz 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.
>
> I'm thinking to write a paper that needs this information for my
> postgraduate course. The focus of my work will be the log data, not
> PostgreSQL itself. If I succeed, maybe it can be a tool to help all of us.
>
> Thank you,
> --
> Daniel Cristian Cruz
> クルズ クリスチアン ダニエル

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Daniel Cristian Cruz 2011-12-10 22:40:23 Re: Common slow query reasons - help with a special log
Previous Message Andreas Kretschmer 2011-12-10 17:25:43 Re: Common slow query reasons - help with a special log