X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9F5199DC842 for ; Fri, 3 Mar 2006 07:19:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 29711-03 for ; Fri, 3 Mar 2006 07:19:45 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from pjetlic.mobart.hr (pjetlic.mobart.hr [80.80.51.10]) by postgresql.org (Postfix) with ESMTP id D8EB99DC806 for ; Fri, 3 Mar 2006 07:19:40 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by pjetlic.mobart.hr (Postfix) with ESMTP id 7E8E317D6D for ; Fri, 3 Mar 2006 12:19:41 +0100 (CET) Received: from pjetlic.mobart.hr ([127.0.0.1]) by localhost (pjetlic [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19554-01-13 for ; Fri, 3 Mar 2006 12:19:41 +0100 (CET) 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 6347117A92 for ; Fri, 3 Mar 2006 12:19:41 +0100 (CET) Subject: SELECT statements in log files From: Mario Splivalo Reply-To: mario.splivalo@mobart.hr To: pgsql-admin@postgresql.org Content-Type: text/plain Organization: Mob-Art Date: Fri, 03 Mar 2006 12:19:40 +0100 Message-Id: <1141384781.8893.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by OpenSource AV+AS Mail Server X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.137 required=5 tests=[AWL=0.137] X-Spam-Score: 0.137 X-Spam-Level: X-Archive-Number: 200603/34 X-Sequence-Number: 20791 We're using JDBC to connect to postgres server. I've setup logging so that any query that executes over 100ms gets logged. But, the log file looks like this: 2006-03-03 12:17:08 CET [31591] SELECTLOG: duration: 253.307 ms statement: EXECUTE [PREPARE: select * from create_mt_sms_message($1, $2, $3, $4, $5, $6, $7, $8, $9) as result] Now, I guess this happened when we switched to the fresh JDBC driver for postgres 8.1. Before that I could see the actuall values for the $1, $2, $3 parameters... Is this a known 'issue', or am I doing something wrong here? Is there a way to see actuall values using new JDBC driver? The java client code didn't change a bit. We just switched to postgres8.1, and upgraded the JDBC driver used by tomcat. When I connect to postgres from PHP or Python or using just psql, I can see full SELECT querries logged, with the actuall values for the parameters. Mario -- Mario Splivalo Mob-Art mario.splivalo@mobart.hr "I can do it quick, I can do it cheap, I can do it well. Pick any two."