aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2011-07-04 14:35:44 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2011-07-04 14:35:44 +0300
commitf7ea6beaf4ca02b8e6dc576255e35a5b86035cb9 (patch)
tree0ef88fcecc2198c300a3e7a691ec690ab0848141 /doc/src
parentf563afd433e07a2eb7db614005141f21613d4d61 (diff)
downloadpostgresql-f7ea6beaf4ca02b8e6dc576255e35a5b86035cb9.tar.gz
postgresql-f7ea6beaf4ca02b8e6dc576255e35a5b86035cb9.zip
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.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml30
1 files changed, 0 insertions, 30 deletions
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
</listitem>
</varlistentry>
- <varlistentry id="guc-silent-mode" xreflabel="silent_mode">
- <term><varname>silent_mode</varname> (<type>boolean</type>)</term>
- <indexterm>
- <primary><varname>silent_mode</> configuration parameter</primary>
- </indexterm>
- <listitem>
- <para>
- 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.
- </para>
-
- <caution>
- <para>
- When this parameter is set,
- the server's standard output and standard error are redirected
- to the file <filename>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 <varname>log_destination</>
- be set to <literal>syslog</> or that <varname>logging_collector</> be
- enabled when using this option. Even with those measures, errors
- reported early during startup may appear in
- <filename>postmaster.log</> rather than the normal log destination.
- </para>
- </caution>
- </listitem>
- </varlistentry>
-
</variablelist>
</sect2>
<sect2 id="runtime-config-logging-when">