On 27 February 2018 at 16:50, Greg Stark <st...@mit.edu> wrote:
> On 27 February 2018 at 02:04, Michael Paquier <mich...@paquier.xyz> wrote:
>> On Mon, Feb 26, 2018 at 05:38:56PM +0000, Greg Stark wrote:
>> Hm. I have just loaded jsonlog on a 9.6 and 10 instance where
>> log_checkpoints is enabled with this background worker which logs a
>> simple string every 10s:
>> Both checkpoint logs and the logs of the bgworker are showing up for me.
> Weird. I guess I have some more debugging with gdb to do.
I think I see what's going on. The log_min_messages is set to the
default value of warning. Which is a higher level than "LOG" so this
code in jsonlog.c is ignoring these messages:
if (edata->elevel < log_min_messages)
But the normal processing for logs uses is_log_level_output to compare
error levels with log_min_messages which treats LOG (and
LOG_SERVER_ONLY) as logically equivalent to ERROR:
* is_log_level_output -- is elevel logically >= log_min_level?
* We use this for tests that should consider LOG to sort out-of-order,
* between ERROR and FATAL. Generally this is the right thing for testing
* whether a message should go to the postmaster log, whereas a simple >=
* test is correct for testing whether the message should go to the client.
is_log_level_output(int elevel, int log_min_level)
if (elevel == LOG || elevel == LOG_SERVER_ONLY)
if (log_min_level == LOG || log_min_level <= ERROR)
else if (log_min_level == LOG)
/* elevel != LOG */
if (elevel >= FATAL)
/* Neither is LOG */
else if (elevel >= log_min_level)