Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A8F429FB656 for ; Tue, 19 Jun 2007 12:17:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 61344-05 for ; Tue, 19 Jun 2007 12:17:26 -0300 (ADT) X-Greylist: delayed 00:46:07.37395 by SQLgrey-1.7.4 Received: from pjetlic.mobart.hr (pjetlic.mobart.hr [80.80.51.10]) by postgresql.org (Postfix) with ESMTP id 844689FB571 for ; Tue, 19 Jun 2007 12:17:25 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by pjetlic.mobart.hr (Postfix) with ESMTP id 3E4EF3C90B; Tue, 19 Jun 2007 17:17:24 +0200 (CEST) Received: from pjetlic.mobart.hr ([127.0.0.1]) by localhost (pjetlic [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16302-07-2; Tue, 19 Jun 2007 17:17:22 +0200 (CEST) Received: from mike.mobart.hr (mike.mobart.hr [192.168.10.94]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pjetlic.mobart.hr (Postfix) with ESMTP id 3D0753C908; Tue, 19 Jun 2007 17:17:21 +0200 (CEST) Subject: Re: Postgres8.2 - turning off BINGLOG/PARSELOG From: Mario Splivalo Reply-To: mario.splivalo@mobart.hr To: Alvaro Herrera Cc: pgsql-admin@postgresql.org In-Reply-To: <20070619145211.GM4265@alvh.no-ip.org> References: <1182263472.13561.43.camel@localhost.localdomain> <20070619145211.GM4265@alvh.no-ip.org> Content-Type: text/plain Organization: Mob-Art d.o.o. Date: Tue, 19 Jun 2007 17:17:21 +0200 Message-Id: <1182266241.13561.52.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by OpenSource AV+AS Mail Server X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/173 X-Sequence-Number: 25841 On Tue, 2007-06-19 at 10:52 -0400, Alvaro Herrera wrote: > Mario Splivalo wrote: > > I'm finaly switching to 8.2. I notice that ugly 'feature' from pg8.1 has > > been fixed: logging the parametars of prepared statements. It's a bit > > ugly, but it's there :) > > > 2007-06-19 16:22:15.555 CEST [4596] BINDLOG: duration: > > 0.027 ms bind S_2: COMMIT > > 2007-06-19 16:22:15.556 CEST [4596] COMMITLOG: duration: > > 0.029 ms execute S_2: COMMIT > > > > log_line_prefix = '%m [%p] <%d> %i' > > One thing you should be aware of is that PARSELOG etc are really "PARSE" > and "LOG", but there is no intervening space since you put no space at > the end of log_line_prefix. So I suggest changing it to > > log_line_prefix = '%m [%p] <%d> %i ' Huh, thnx! :) Silly me, I tought that %i actually stands for 'SELECT * FROM ...' :) > Now, regarding your question, > > > Is there a way to turn off these PARSELOG and BINDLOG messages? I realy > > need only the SELECTLOG (and SELECTDETAIL because there are the actuall > > parametars)? > > I don't think so. You can increase log_min_duration_statement a bit so > that only statements that take "long" are logged. Why not? I need to have log_min_duration_statement set to 0 because I do want every SQL sent to the postgres loged. It's essential in debugging. But since for every SELECT i have at least 3 lines in my log file, debugging is much harder (ok, not that harder, but still, it would be much easier without it). It would be realy nice if one could turn that off. When I switch to JDBC driver for pg (pg74.215.jdbc3.jar), I have single SELECT in a log for a SELECT sent from the client. I guess that's because there is no prepared statements in pg74.215.jdbc3.jar, but that is for pg-jdbc mailinglist. 10x again! Mike