Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E135F2E0154 for ; Wed, 13 Feb 2008 15:25:56 -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 31567-09 for ; Wed, 13 Feb 2008 15:25:50 -0400 (AST) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.188]) by postgresql.org (Postfix) with ESMTP id A75592E00E8 for ; Wed, 13 Feb 2008 15:25:50 -0400 (AST) Received: by rv-out-0910.google.com with SMTP id g13so76875rvb.43 for ; Wed, 13 Feb 2008 11:25:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=VVgmgeDn9NlNO21XoB5XrN0MLg5+DYqoDutgmZCWIf0=; b=QSffNXLHH62t8LCKyTDuWOJDFyLIdlsHrhwnNPmwdj53LMuJ7eh+fEG8R6rqQDEKneopQoI5nRfH/dSB3Ms+LnQp6g4SJbfYo81pd0XIriRrNr5DlLYhPq5R3aFpwimC7xSLUYwFjCKIG7v0uLNwuE4eAQIg2HMSoSBvWng6mxs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=WW2g9tM4KuYxGwk5QQU5UYhy3qS9CjeF7NHNkMIMUOCk/i2PaJ0qRKJdif6aLYbTtVv3PGucbGOdyvd6l1bgOcIvYS/dJek4o66NfKpLdtOBFxsviCIwxDZK+MdVdHMSzww50f/0fC9WO2CrrZ0Tt+cIokPcOQ1ZdUSFy2hi7Qo= Received: by 10.141.13.16 with SMTP id q16mr234155rvi.99.1202930747387; Wed, 13 Feb 2008 11:25:47 -0800 (PST) Received: by 10.141.18.20 with HTTP; Wed, 13 Feb 2008 11:25:47 -0800 (PST) Message-ID: Date: Wed, 13 Feb 2008 13:25:47 -0600 From: "Michael Shapiro" To: "Michael Fuhr" Subject: Re: CONTEXT messages for raise EXCEPTION Cc: pgsql-admin@postgresql.org In-Reply-To: <20080213191136.GA91063@winnie.fuhr.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15588_9714270.1202930747358" References: <20080213191136.GA91063@winnie.fuhr.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/157 X-Sequence-Number: 28231 ------=_Part_15588_9714270.1202930747358 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. I remain baffled by what I am seeing. On Feb 13, 2008 1:11 PM, Michael Fuhr wrote: > On Wed, Feb 13, 2008 at 11:27:16AM -0600, Michael Shapiro wrote: > > I am getting a lot of CONTEXT information along with the message when an > > EXCEPTION is raised. Does anyone know what controls whether EXCEPTIONS > add > > the CONTEXT or not? > > In the server logs the log_error_verbosity configuration setting > controls how much much detail is logged. For client-side display, > in psql you can use the VERBOSITY variable. > > > NOTE: We are using Perl's DBI (which may or not be the cause). > > For client-side display, see the pg_errorlevel database handle > attribute in the DBD::Pg manual page. > > $dbh->{pg_errorlevel} = 0; # terse > $dbh->{pg_errorlevel} = 1; # default > $dbh->{pg_errorlevel} = 2; # verbose > > -- > Michael Fuhr > ------=_Part_15588_9714270.1202930747358 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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.

I remain baffled by what I am seeing.


On Feb 13, 2008 1:11 PM, Michael Fuhr <mike@fuhr.org> wrote:
On Wed, Feb 13, 2008 at 11:27:16AM -0600, Michael Shapiro wrote:
> I am getting a lot of CONTEXT information along with the message when an
> EXCEPTION is raised. Does anyone know what controls whether EXCEPTIONS add
> the CONTEXT or not?

In the server logs the log_error_verbosity configuration setting
controls how much much detail is logged.  For client-side display,
in psql you can use the VERBOSITY variable.

> NOTE:  We are using Perl's DBI (which may or not be the cause).

For client-side display, see the pg_errorlevel database handle
attribute in the DBD::Pg manual page.

$dbh->{pg_errorlevel} = 0;  # terse
$dbh->{pg_errorlevel} = 1;  # default
$dbh->{pg_errorlevel} = 2;  # verbose

--
Michael Fuhr

------=_Part_15588_9714270.1202930747358--