Skip site navigation (1) Skip section navigation (2)

Re: A tool to extract the problematic points of the postgresl log.

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: David Pradier <david(dot)pradier(at)clarisys(dot)fr>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: A tool to extract the problematic points of the postgresl log.
Date: 2005-10-11 13:46:26
Message-ID: 20051011134626.GR23883@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-admin
Yes, someone has. Take a look on http://pgfoundry.org; I'm pretty sure
it's there.

On Tue, Oct 11, 2005 at 11:59:29AM +0200, David Pradier wrote:
> Hi everybody,
> 
> i'd like to know if my database (settings, indexes, materialized views,
> etc) is correctly tuned.
> To do this, i think the best way is to watch the queries actually
> processed and the time needed.
> 
> The postgres log is the right way to do this, i think.
> 
> But well, it's a bit dense.
> Nothing i can't go through, but would you know a better tool than grep
> to parse the file and extract the problematic points ?
> 
> As it might be a common problem, maybe somebody as already written a
> generic tool to do this ?
> 
> Thanks in advance,
> David
> -- 
> David Pradier -- Directeur Technique de Clarisys Informatique -- Chef de projet logiciels libres / open-source
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2005-10-11 13:49:11
Subject: Re: Memory/Performance issue: server closed the connection unexpectedly
Previous:From: Pieter-Jan SavatDate: 2005-10-11 10:18:17
Subject: Memory/Performance issue: server closed the connection unexpectedly

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group