DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=uL5maoKeM37Pkbe400pZ+/EUX/fumpdAJmRhtvmRL9BuZCujG1RTNMW9SeSa53aI1c9Ilfi7dhr3rNuTvUDKzgGp4Df/sOea9j2N5GGnxhuLeoP82evkGryU9K7GIcDeySPxnmz0aCR4c2FR1/xHTOR8DX77U5JuF5aSxjWqEts=
	;
Message-ID: <20050712062247.37243.qmail@web33902.mail.mud.yahoo.com>
Date: Mon, 11 Jul 2005 23:22:47 -0700 (PDT)
From: Brent Henry <bh_pgperf@yahoo.com>
Subject: General DB Tuning
To: pgsql-performance@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Help!  After recently migrating to Postgres 8, I've
discovered to my horror that I can't determine which
queries are poorly performing anymore because the
logging has drastically changed and no longer shows
durations for anything done through JDBC.

So I'm desperately trying to do performance tuning on
my servers and have no way to sort out which
statements are the slowest.

Does anyone have any suggestions?  How do you
determine what queries are behaving badly when you
can't get durations out of the logs?

I have a perl script that analyzes the output from
Postgres 7 logs and it works great!  But it relies on
the duration being there.

I did some searches on postgresql.org mailing lists
and have seen a few people discussing this problem,
but noone seems to be too worried about it.  Is there
a simple work-around?

Sincerely,

Brent


____________________________________________________
Sell on Yahoo! Auctions – no fees. Bid on great items.  
http://auctions.yahoo.com/