Re: SQL state in log_line_prefix

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL state in log_line_prefix
Date: 2009-05-10 13:29:38
Message-ID: 4A06D6C2.9020107@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Guillaume Smet wrote:
> Hi -hackers,
>
> A customer of us recently wanted to separate user errors from system
> errors as different teams are working on these 2 types of errors and
> while they might want to ignore user errors (bad-written SQL queries
> and so on), they want to be sure system errors are analyzed carefully.
>
> A good way to differentiate the 2 types of errors is to use the SQL state.
>
> Currently, the only way to have the SQL state in the standard log file
> is to do verbose logging which is, well..., verbose.
>
> I attached a patch which allows to add the SQL state code into the
> log_line_prefix. I used %e (as in error) as %s is already used.
>
> Any comment?
>
>

If we're going to do this I think it needs to be added to CSV log output
too.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Smet 2009-05-10 13:34:29 Re: SQL state in log_line_prefix
Previous Message Pavel Stehule 2009-05-10 13:21:36 Re: Implementation of GROUPING SETS (T431: Extended grouping capabilities)