pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marco Furetto <furetto@bluestudio.it>
To: pgsql-performance@postgresql.org
Subject: Re: Query Feromance
Date: Tue, 21 Mar 2006 10:56:34 +0100
Message-ID: <441FCDD2.8010905@bluestudio.it> (raw)
In-Reply-To: <200603210943.57454.mlists@rp-online.de>
References: <441EC34D.1000901@bluestudio.it>
	<001301c64c3c$3404b3f0$8b00000a@reimer>
	<441FB88E.2060801@bluestudio.it>
	<200603210943.57454.mlists@rp-online.de>

ok, I enable query duration logging in postgresql.conf.

where is the instruments for analyze the statistics queries executing on 
my  db?

Eg.: Number of query executing, total time for executing a single query, 
etc...


Thank's

Marco "Furetto" Berri


Thomas Pundt wrote:
> Hi,
> 
> On Tuesday 21 March 2006 09:25, Marco Furetto wrote:
> | I'm managing the db of a "Content Management environment" and I'm
> | searching for a "Query analyzer" to improve performance because i don't
> | know how many and what type of queries are executing on the system (for
> | the "where and join" block).
> 
> as a first step, I'd enable query duration logging; in postgresql.conf
> I have set
> 
>   log_min_duration_statement = 3000
> 
> this will log each query that needs more than 3 seconds to complete.
> 
> The next step would be to "explain analyze" the problematic queries.
> 
> Ciao,
> Thomas
> 



view thread (7+ messages)  latest in thread

Message-ID: <441FCDD2.8010905@bluestudio.it>
Permalink:  ../441FCDD2.8010905@bluestudio.it/
Also on:    postgresql.org/message-id/441FCDD2.8010905@bluestudio.it

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: furetto@bluestudio.it
  Subject: Re: Query Feromance
  In-Reply-To: <441FCDD2.8010905@bluestudio.it>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox