Re: trace_recovery_messages
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-08-18T19:23:02Z
Lists: pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes: > The explanation of trace_recovery_messages in the document > is inconsistent with the definition of it in guc.c. Setting the default to WARNING is confusing and useless, because there are no trace_recovery calls with that debug level. IMO the default setting should be LOG, which makes trace_recovery() a clear no-op (rather than not clearly a no-op). There is circumstantial evidence in the code that this was the original intention: int trace_recovery_messages = LOG; The documentation of the parameter is about as clear as mud, too. We need to explain what it does rather than just copy-and-paste a lot of text from log_min_messages. regards, tom lane