{"Entry":{"collection":"guc","key":"log_error_verbosity","name":"log_error_verbosity","aliases":[],"metadata":{"baseline":true,"boot_human":"Not specified","boot_val":null,"category":"Reporting and Logging / What 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.4","status":"changed","to":"9.0"},{"documentation_changed":true,"fields":{},"from":"14","status":"changed","to":"15"}],"content_hash":"37c74fdfb8bab99c0faa3814b7225a0ecb8eb0a1e2616c49fc58d603d0098823","context":"","default_changed_in":[],"default_history":[{"from":"9.0","to":"19","value":"default"}],"editorial":{"advice":{"olap":"Analytical jobs can justify richer log_error_verbosity telemetry, but account for long statements, large bind values, and bursty completion patterns in the log pipeline.","oltp":"Tune log_error_verbosity against an explicit observability question and a measured log-volume budget. Prefer selective thresholds, sampling, or role-level overrides over indiscriminate capture.","small":"Keep log_error_verbosity useful but bounded: verify disk, collector, retention, and redaction capacity before increasing detail or frequency."},"mechanism":["log_error_verbosity sets the verbosity of logged messages. TERSE suppresses detail and hints, DEFAULT retains normal diagnostics, and VERBOSE adds SQLSTATE plus source file, function, and line information.","log_error_verbosity is a SUPERUSER-context setting. Superuser or a role granted the appropriate SET privilege can change it for a session, while ALTER ROLE or ALTER DATABASE can establish a default for future sessions.","It changes emitted diagnostic data rather than query semantics, but volume, sensitive content, log_line_prefix, destinations, collector throughput, and retention determine operational cost and usefulness."],"pitfalls":["Changing log_error_verbosity in one session and assuming role defaults, database defaults, or other pooled sessions changed with it.","Enabling richer logging without budgeting collector throughput, storage, retention, and downstream query cost.","Writing SQL text, bind values, identities, or host data without a redaction and access-control policy.","Changing log_error_verbosity globally without a rollback plan and a client or operational compatibility test."],"references":[{"title":"PostgreSQL 19 Beta 4: log_error_verbosity","url":"https://www.postgresql.org/docs/19/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY"},{"title":"PostgreSQL 19 release notes","url":"https://www.postgresql.org/docs/19/release-19.html"}],"related":["log_statement","log_duration","log_connections","log_disconnections","log_parameter_max_length","log_parameter_max_length_on_error"],"summary":"log_error_verbosity is the PostgreSQL setting that defines the verbosity of logged messages."},"enumvals":[],"first_version":"7.4","group":"Reporting and Logging","group_slug":"logging","imported_at":"2026-09-30T00:40:57.320559+08:00","intro_commit":{},"key":"log_error_verbosity","last_version":"20","max_val":"","min_val":"","name":"log_error_verbosity","position":225,"present_in":["7.4","8.0","8.1","8.2","8.3","8.4","9.0","9.1","9.2","9.3","9.4","9.5","9.6","10","11","12","13","14","15","16","17","18","19","20"],"short_desc":"Controls the amount of detail written in the server log for each message that is logged.","short_desc_zh":"","source_rev":"english-manuals:5f7e743da121fef3937ecd541f2f3b421c0cb34fe9bc55bfad9da100ec2f7b57","unit":"","vartype":"enum"}},"Definition":{"Collection":"guc","Key":"log_error_verbosity","SourceDatabase":"center","Version":"18","SourceTable":"guc","SourceKey":"log_error_verbosity","SourceRevision":"english-manuals:5f7e743da121fef3937ecd541f2f3b421c0cb34fe9bc55bfad9da100ec2f7b57","Facts":{"boot_val":"default","category":"Reporting and Logging / What to Log","context":"superuser","description":"Controls the amount of detail written in the server log for each message that is logged. Valid values are TERSE, DEFAULT, and VERBOSE, each adding more fields to displayed messages. TERSE excludes the logging of DETAIL, HINT, QUERY, and CONTEXT error information. VERBOSE output includes the SQLSTATE error code (see also Appendix A) and the source code file name, function name, and line number that generated the error. Only superusers and users with the appropriate SET privilege can change this setting.","doc":{"anchor":"GUC-LOG-ERROR-VERBOSITY","file":"runtime-config-logging.html","lang":"en","sha256":"93c48c522a72fca19705c4c91a71e951eae653662008eee2e4a9a74a11127fde","slug":"18"},"documented":true,"enumvals":["terse","default","verbose"],"extra_desc":null,"lang":"en","max_val":null,"metadata_version":"18","min_val":null,"name":"log_error_verbosity","short_desc":"Sets the verbosity of logged messages.","source":"pg-settings-source-snapshot","unit":null,"vartype":"enum"},"ManualEvidence":{"doc":{"anchor":"GUC-LOG-ERROR-VERBOSITY","file":"runtime-config-logging.html","lang":"en","sha256":"93c48c522a72fca19705c4c91a71e951eae653662008eee2e4a9a74a11127fde","slug":"18"}},"MeasuredEvidence":{"metadata_version":"18"}},"Text":{"Collection":"guc","Key":"log_error_verbosity","SourceDatabase":"pgweb","Version":"18","Locale":"zh-Hans","Title":"log_error_verbosity","Summary":"","BodyHTML":"\u003cp\u003e控制在服务器日志中记录的每条消息的详细程度。有效值为\u003ccode\u003eTERSE\u003c/code\u003e，\u003ccode\u003eDEFAULT\u003c/code\u003e和\u003ccode\u003eVERBOSE\u003c/code\u003e，它们依次在显示的消息中增加更多字段。\u003ccode\u003eTERSE\u003c/code\u003e不包括\u003ccode\u003eDETAIL\u003c/code\u003e，\u003ccode\u003eHINT\u003c/code\u003e，\u003ccode\u003eQUERY\u003c/code\u003e和\u003ccode\u003eCONTEXT\u003c/code\u003e错误信息的记录。\u003ccode\u003eVERBOSE\u003c/code\u003e输出包括\u003ccode\u003eSQLSTATE\u003c/code\u003e错误代码（另请参见\u003ca href=\"/docs/18/errcodes-appendix.html\" rel=\"nofollow\"\u003e附录 A\u003c/a\u003e）以及生成错误的源代码文件名、函数名和行号。只有超级用户和具有适当\u003ccode\u003eSET\u003c/code\u003e权限的用户才能更改此设置。\u003c/p\u003e","SourceRevision":"2026-09-11@29c86d9","ContentHash":"e75e2cb8cb591005f4d276dc13e3bd567a74cbc9e699a37ef3a5c6adad1aeb49","Payload":{"carried_from":"","carry_reason":"","doc_html":"\u003cp\u003e控制在服务器日志中记录的每条消息的详细程度。有效值为\u003ccode class=\"literal\"\u003eTERSE\u003c/code\u003e，\u003ccode class=\"literal\"\u003eDEFAULT\u003c/code\u003e和\u003ccode class=\"literal\"\u003eVERBOSE\u003c/code\u003e，它们依次在显示的消息中增加更多字段。\u003ccode class=\"literal\"\u003eTERSE\u003c/code\u003e不包括\u003ccode class=\"literal\"\u003eDETAIL\u003c/code\u003e，\u003ccode class=\"literal\"\u003eHINT\u003c/code\u003e，\u003ccode class=\"literal\"\u003eQUERY\u003c/code\u003e和\u003ccode class=\"literal\"\u003eCONTEXT\u003c/code\u003e错误信息的记录。\u003ccode class=\"literal\"\u003eVERBOSE\u003c/code\u003e输出包括\u003ccode class=\"symbol\"\u003eSQLSTATE\u003c/code\u003e错误代码（另请参见\u003ca href=\"/docs/18/errcodes-appendix.html\" title=\"附录 A. PostgreSQL错误代码\"\u003e附录 A\u003c/a\u003e）以及生成错误的源代码文件名、函数名和行号。只有超级用户和具有适当\u003ccode class=\"literal\"\u003eSET\u003c/code\u003e权限的用户才能更改此设置。\u003c/p\u003e","doc_same_as":""}},"RequestedLocale":"zh-Hans","Fallback":false,"Versions":["10","11","12","13","14","15","16","17","18","19","20","7.4","8.0","8.1","8.2","8.3","8.4","9.0","9.1","9.2","9.3","9.4","9.5","9.6"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}