Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id D955C2E0137 for ; Wed, 13 Feb 2008 16:18:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 03435-03 for ; Wed, 13 Feb 2008 16:18:02 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 97BC32E021E for ; Wed, 13 Feb 2008 16:18:05 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m1DKI1cx022806; Wed, 13 Feb 2008 15:18:01 -0500 (EST) To: "Michael Shapiro" cc: "Michael Fuhr" , pgsql-admin@postgresql.org Subject: Re: CONTEXT messages for raise EXCEPTION In-reply-to: References: <20080213191136.GA91063@winnie.fuhr.org> Comments: In-reply-to "Michael Shapiro" message dated "Wed, 13 Feb 2008 13:25:47 -0600" Date: Wed, 13 Feb 2008 15:18:01 -0500 Message-ID: <22805.1202933881@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/161 X-Sequence-Number: 28235 "Michael Shapiro" writes: > The $dbh->{errorlevel} is set to 1 (default), which implies the extra > verbosity is some setting in the server, right? > The server log_error_verbosity is set to terse, so the server shouldn't add > the CONTEXT. log_error_verbosity just controls what goes into the server log. The amount of detail shown on the client side is entirely determined by client-side logic. If DBD::Pg hasn't got a knob that lets you suppress the CONTEXT field, you'll need to take that up with the DBD::Pg authors. regards, tom lane