Comments on: Waiting for 8.5 – Add log_line_prefix placeholder %e to contain the current SQL state http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-add-log_line_prefix-placeholder-e-to-contain-the-current-sql/ Thu, 29 Jul 2010 21:40:44 +0000 hourly 1 http://wordpress.org/?v=3.0 By: depesz http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-add-log_line_prefix-placeholder-e-to-contain-the-current-sql/comment-page-1/#comment-27867 depesz Tue, 07 Jul 2009 08:31:51 +0000 http://www.depesz.com/?p=1445#comment-27867 @Guillaume: thanks for clarification. The fact that it will be possible clearly escaped me. @Guillaume:
thanks for clarification. The fact that it will be possible clearly escaped me.

]]> By: Guillaume http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-add-log_line_prefix-placeholder-e-to-contain-the-current-sql/comment-page-1/#comment-27866 Guillaume Tue, 07 Jul 2009 05:56:01 +0000 http://www.depesz.com/?p=1445#comment-27866 Thanks for your article. The main point is not especially to have a fixed reference compared to a localized message (they are in only one language in the server logs usually). It's to be able to categorize errors based on the first 2 characters of the error code which define the class of the error. You can then separate end user errors (syntax errors and so on) from system ones: it's very useful to filter the error the system administrator have to take seriously into account. Thanks for your article.

The main point is not especially to have a fixed reference compared to a localized message (they are in only one language in the server logs usually).

It’s to be able to categorize errors based on the first 2 characters of the error code which define the class of the error. You can then separate end user errors (syntax errors and so on) from system ones: it’s very useful to filter the error the system administrator have to take seriously into account.

]]>