X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 2E7689FA9BD for ; Thu, 4 May 2006 15:13:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 98803-09 for ; Thu, 4 May 2006 15:13:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 798CF9F9B76 for ; Thu, 4 May 2006 15:13:05 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 35FD856431; Thu, 4 May 2006 13:13:04 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Thu, 4 May 2006 13:13:03 -0500 Date: Thu, 4 May 2006 13:13:03 -0500 From: "Jim C. Nasby" To: bfraci@aol.com Cc: pgsql-admin@postgresql.org Subject: Re: Can we adjust postgres logging to also dump the bind variable data when an error occurs Message-ID: <20060504181303.GP97354@pervasive.com> References: <8C83B8555225B23-1658-67F4@FWM-D25.sysops.aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8C83B8555225B23-1658-67F4@FWM-D25.sysops.aol.com> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060504:bfraci@aol.com::IaXL2RoXOPwjOeJ1:0000vIo X-Hashcash: 1:20:060504:pgsql-admin@postgresql.org::4mKABqj6CcHXEsy3:00000000000 0000000000000000000000007x7C X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/39 X-Sequence-Number: 21571 On Mon, May 01, 2006 at 06:25:49PM -0400, bfraci@aol.com wrote: > I am using Postgres version 8.0.3. I have noticed that when I set the log_statement parameter to 'all', I get the values for the bind variables. Is it possible to get all of the same information that I get when I set log_statement to 'all' just for the statement that has an error? I don't want to clutter up my log file with this detail information for all statements, just those that produce an error. Setting log_error_verbosity to verbose might do the trick... -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461