Re: CONTEXT messages for raise EXCEPTION
| От | Michael Shapiro |
|---|---|
| Тема | Re: CONTEXT messages for raise EXCEPTION |
| Дата | |
| Msg-id | ca3a8da20802131125if8cb921h2912f2b41c262bb0@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: CONTEXT messages for raise EXCEPTION (Michael Fuhr <mike@fuhr.org>) |
| Ответы |
Re: CONTEXT messages for raise EXCEPTION
|
| Список | pgsql-admin |
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.
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:In the server logs the log_error_verbosity configuration setting
> 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?
controls how much much detail is logged. For client-side display,
in psql you can use the VERBOSITY variable.For client-side display, see the pg_errorlevel database handle
> NOTE: We are using Perl's DBI (which may or not be the cause).
attribute in the DBD::Pg manual page.
$dbh->{pg_errorlevel} = 0; # terse
$dbh->{pg_errorlevel} = 1; # default
$dbh->{pg_errorlevel} = 2; # verbose
--
Michael Fuhr
В списке pgsql-admin по дате отправления: