Re: SQL state in log_line_prefix
От | Andrew Dunstan |
---|---|
Тема | Re: SQL state in log_line_prefix |
Дата | |
Msg-id | 4A06D6C2.9020107@dunslane.net обсуждение исходный текст |
Ответ на | SQL state in log_line_prefix (Guillaume Smet <guillaume.smet@gmail.com>) |
Ответы |
Re: SQL state in log_line_prefix
|
Список | 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
В списке pgsql-hackers по дате отправления: