Date: Sat, 10 Dec 2011 18:25:43 +0100
From: Andreas Kretschmer <akretschmer@spamfence.net>
To: pgsql-performance@postgresql.org
Subject: Re: Common slow query reasons - help with a special log
Message-ID: <20111210172543.GA21157@tux>
References: 
 <CACffM9E1d9bR=xdWYoAPF2Y2NMpfE4gpRQf6vjV3QXQ5SSSLbw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CACffM9E1d9bR=xdWYoAPF2Y2NMpfE4gpRQf6vjV3QXQ5SSSLbw@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)

Daniel Cristian Cruz <danielcristian@gmail.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°