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

[David Pradier <david.pradier@xxxxxxxxxxx>]

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