X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E478E52AFD for ; Tue, 12 Jul 2005 18:54:50 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07286-02 for ; Tue, 12 Jul 2005 21:54:41 +0000 (GMT) Received: from mail.jobflash.com (oncallweb2.jobflash.com [64.62.211.41]) by svr1.postgresql.org (Postfix) with ESMTP id 9974952ACC for ; Tue, 12 Jul 2005 18:54:40 -0300 (ADT) Received: from [192.168.2.22] (user-38lc18a.dialup.mindspring.com [209.86.5.10]) by mail.jobflash.com (Postfix) with ESMTP id 883DC420E4; Tue, 12 Jul 2005 14:54:41 -0700 (PDT) Message-ID: <42D43C17.90005@jobflash.com> Date: Tue, 12 Jul 2005 14:54:31 -0700 From: Tom Arthurs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brent Henry Cc: pgsql-performance@postgresql.org Subject: Re: General DB Tuning References: <20050712062247.37243.qmail@web33902.mail.mud.yahoo.com> In-Reply-To: <20050712062247.37243.qmail@web33902.mail.mud.yahoo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200507/126 X-Sequence-Number: 13367 I have this in my postgresql.conf file and it works fine (set the min to whatever you want to log) log_min_duration_statement = 3000 # -1 is disabled, in milliseconds. Another setting that might get what you want: #log_duration = false uncomment and change to true. From the docs: (http://www.postgresql.org/docs/8.0/interactive/runtime-config.html) Causes the duration of every completed statement which satisfies log_statement to be logged. When using this option, if you are not using syslog, it is recommended that you log the PID or session ID using log_line_prefix so that you can link the statement to the duration using the process ID or session ID. The default is off. Only superusers can change this setting. Brent Henry wrote: > 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/ > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > > >