From f7ea6beaf4ca02b8e6dc576255e35a5b86035cb9 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Mon, 4 Jul 2011 14:35:44 +0300 Subject: Remove silent_mode. You get the same functionality with "pg_ctl -l postmaster.log", or nohup. There was a small issue with LINUX_OOM_ADJ and silent_mode, namely that with silent_mode the postmaster process incorrectly used the OOM settings meant for backend processes. We certainly could've fixed that directly, but since silent_mode was redundant anyway, we might as well just remove it. --- doc/src/sgml/config.sgml | 30 ------------------------------ 1 file changed, 30 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 3f6986fc1be..bce9520a650 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3201,36 +3201,6 @@ local0.* /var/log/postgresql - - silent_mode (boolean) - - silent_mode configuration parameter - - - - Runs the server silently. If this parameter is set, the server - will automatically run in background and disassociate from the - controlling terminal. - This parameter can only be set at server start. - - - - - When this parameter is set, - the server's standard output and standard error are redirected - to the file postmaster.log within the data directory. - There is no provision for rotating this file, so it will grow - indefinitely unless server log output is redirected elsewhere - by other settings. It is recommended that log_destination - be set to syslog or that logging_collector be - enabled when using this option. Even with those measures, errors - reported early during startup may appear in - postmaster.log rather than the normal log destination. - - - - - -- cgit v1.2.3