{"Entry":{"collection":"guc","key":"silent_mode","name":"silent_mode","aliases":[],"metadata":{"baseline":true,"boot_human":"off","boot_val":"off","category":"Reporting and Logging / Where to Log","category_zh":"","changed_in":[],"changes":[{"documentation_changed":true,"fields":{},"from":"7.4","status":"changed","to":"8.0"},{"documentation_changed":true,"fields":{},"from":"8.1","status":"changed","to":"8.2"},{"documentation_changed":true,"fields":{},"from":"8.2","status":"changed","to":"8.3"},{"documentation_changed":true,"fields":{},"from":"8.3","status":"changed","to":"8.4"},{"documentation_changed":false,"fields":{},"from":"9.1","status":"removed","to":"9.2"}],"content_hash":"126d2280f971d263318875f1a4546d65d41723c50385283a1697df5f7b48be89","context":"postmaster","default_changed_in":[],"default_history":[{"from":"9.0","to":"9.1","value":"off"}],"editorial":{"advice":{"olap":"For an upgrade or analytical estate, inventory every generated configuration before cutover. Map the old control to its successor and compare plans, throughput, WAL, or logging behavior rather than assuming the old numeric value is portable.","oltp":"Do not add this retired name to a current OLTP configuration. Translate its intent to the documented successor, test the migration under connection and write concurrency, and remove stale automation that still emits it.","small":"Delete the obsolete override after recording why it existed. On a small node, prefer the successor's default until measurements justify a new value; an unknown startup parameter can otherwise stop the server."},"mechanism":["PostgreSQL describes silent_mode as follows: “Runs the server silently.” The value is fixed when the server starts, so changing it requires a controlled restart. The atlas measures it in PG9.0–9.1; boot_val is the compiled or initialized baseline, not proof of a running cluster's effective setting.","Silent mode was an early background-server convenience that redirected or suppressed terminal-facing output. It was removed in PostgreSQL 9.2; service managers and PostgreSQL's logging_collector, log_destination, and log_directory settings now provide explicit process and log ownership.","Read it together with logging_collector, log_destination, log_directory, log_filename. Check SHOW and pg_settings on the target server, verify the source and pending_restart fields, and compare workload, logs, and resource metrics before and after any change."],"pitfalls":["Treating the measured boot_val for silent_mode as proof of the effective value on an initialized or managed cluster.","Applying a change as though it were immediate while pg_settings reports postmaster context.","Changing this setting in isolation without checking the linked limits, observability, and rollback path.","Copying the removed name into a modern postgresql.conf instead of migrating to its documented successor."],"references":[{"title":"PostgreSQL 9.1: silent_mode","url":"https://www.postgresql.org/docs/9.1/runtime-config-logging.html#GUC-SILENT-MODE"}],"related":["logging_collector","log_destination","log_directory","log_filename"],"summary":"silent_mode — Runs the server silently. Observed in PG9.0–9.1; its last measured boot default is off in PG9.1, with postmaster context. It was removed in PG9.2."},"enumvals":[],"first_version":"7.4","group":"Reporting and Logging","group_slug":"logging","imported_at":"2026-09-27T17:57:31.980951+08:00","intro_commit":{},"key":"silent_mode","last_version":"9.1","max_val":"","min_val":"","name":"silent_mode","position":362,"present_in":["7.4","8.0","8.1","8.2","8.3","8.4","9.0","9.1"],"short_desc":"Runs the server silently.","short_desc_zh":"","source_rev":"english-manuals:a75d37cf4fbfebdc466001c47a27f4f16376685eeb009912d37ced020a17322c","unit":"","vartype":"bool"}},"Definition":{"Collection":"guc","Key":"silent_mode","SourceDatabase":"center","Version":"9.1","SourceTable":"guc","SourceKey":"silent_mode","SourceRevision":"english-manuals:a75d37cf4fbfebdc466001c47a27f4f16376685eeb009912d37ced020a17322c","Facts":{"boot_val":"off","category":"Reporting and Logging / Where to Log","context":"postmaster","description":"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. Caution 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.","doc":{"anchor":"GUC-SILENT-MODE","file":"runtime-config-logging.html","lang":"en","sha256":"d209b1d37af6df2055254fa04c09492710c4d64aa09bf354d811f7613401f499","slug":"9.1"},"documented":true,"enumvals":null,"extra_desc":"If this parameter is set, the server will automatically run in the background and any controlling terminals are dissociated.","lang":"en","max_val":null,"metadata_version":"9.1","min_val":null,"name":"silent_mode","short_desc":"Runs the server silently.","source":"pg-settings-source-snapshot","unit":null,"vartype":"bool"},"ManualEvidence":{"doc":{"anchor":"GUC-SILENT-MODE","file":"runtime-config-logging.html","lang":"en","sha256":"d209b1d37af6df2055254fa04c09492710c4d64aa09bf354d811f7613401f499","slug":"9.1"}},"MeasuredEvidence":{"metadata_version":"9.1"}},"Text":{"Collection":"guc","Key":"silent_mode","SourceDatabase":"pgweb","Version":"9.1","Locale":"zh-Hans","Title":"silent_mode","Summary":"","BodyHTML":"\u003cp\u003e静默地运行服务器。如果设置了这个参数，服务器将自动在后台运行并脱离控制终端。这个参数只能在服务器启动时设置。\u003c/p\u003e\u003cdiv\u003e\n小心\u003cp\u003e当设置了这个参数时，服务器的标准输出和标准错误会被重定向到数据目录中的\u003ccode\u003epostmaster.log\u003c/code\u003e文件。没有任何轮转这个文件的机制，所以除非服务器日志输出被其他设置重定向到别处，它将无限增长。建议在使用这个选项时将\u003ccode\u003elog_destination\u003c/code\u003e设置为\u003ccode\u003esyslog\u003c/code\u003e或者启用\u003ccode\u003elogging_collector\u003c/code\u003e。即使采取这些措施，启动早期报告的错误也可能出现在\u003ccode\u003epostmaster.log\u003c/code\u003e中而不是正常的日志目标中。\u003c/p\u003e\u003c/div\u003e","SourceRevision":"2026-09-11@29c86d9","ContentHash":"f5d553c0944e91ca0317b7914370abf56a5a09663c08d2228245da8a651691d8","Payload":{"carried_from":"","carry_reason":"","doc_html":"\u003cp\u003e静默地运行服务器。如果设置了这个参数，服务器将自动在后台运行并脱离控制终端。这个参数只能在服务器启动时设置。\u003c/p\u003e\u003cdiv class=\"caution\"\u003e\n小心\u003cp\u003e当设置了这个参数时，服务器的标准输出和标准错误会被重定向到数据目录中的\u003ccode class=\"filename\"\u003epostmaster.log\u003c/code\u003e文件。没有任何轮转这个文件的机制，所以除非服务器日志输出被其他设置重定向到别处，它将无限增长。建议在使用这个选项时将\u003ccode class=\"varname\"\u003elog_destination\u003c/code\u003e设置为\u003ccode class=\"literal\"\u003esyslog\u003c/code\u003e或者启用\u003ccode class=\"varname\"\u003elogging_collector\u003c/code\u003e。即使采取这些措施，启动早期报告的错误也可能出现在\u003ccode class=\"filename\"\u003epostmaster.log\u003c/code\u003e中而不是正常的日志目标中。\u003c/p\u003e\u003c/div\u003e","doc_same_as":""}},"RequestedLocale":"zh-Hans","Fallback":false,"Versions":["7.4","8.0","8.1","8.2","8.3","8.4","9.0","9.1"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}