From 4334639f4bb9fb88c13b8dd5faca22b207248504 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Thu, 26 Sep 2013 17:54:20 -0400 Subject: Allow printf-style padding specifications in log_line_prefix. David Rowley, after a suggestion from Heikki Linnakangas. Reviewed by Albe Laurenz, and further edited by me. --- doc/src/sgml/config.sgml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 370aa09ee7c..697cf401374 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3941,8 +3941,14 @@ local0.* /var/log/postgresql that are replaced with status information as outlined below. Unrecognized escapes are ignored. Other characters are copied straight to the log line. Some escapes are - only recognized by session processes, and are ignored by - background processes such as the main server process. + only recognized by session processes, and will be treated as empty by + background processes such as the main server process. Status + information may be aligned either left or right by specifying a + numeric literal after the % and before the option. A negative + value will cause the status information to be padded on the + right with spaces to give it a minimum width, whereas a positive + value will pad on the left. Padding can be useful to aid human + readability in log files. This parameter can only be set in the postgresql.conf file or on the server command line. The default is an empty string. -- cgit v1.2.3