Re: trace_recovery_messages - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: trace_recovery_messages
Date
Msg-id 1282728960.3865.34.camel@ebony
Whole thread Raw
In response to Re: trace_recovery_messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: trace_recovery_messages
List pgsql-hackers
On Thu, 2010-08-19 at 19:06 -0400, Tom Lane wrote:
> 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.
> 
> I've applied a patch for this.
> 
> I was tempted to propose that we just rip out trace_recovery_messages
> altogether, but I suppose Simon would object.

Thanks for keeping it in, hopefully it will help diagnose any errors.

I laughed when I saw the commit message, so thanks for that.

This is definitely a stop-gap facility. If you were to propose a more
general facility for increasing log level of specific modules, I'm sure
the rest of us would see that implemented across the rest of the code.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Backups from the standby (Incrementally Updated Backups), open item
Next
From: Andres Freund
Date:
Subject: Re: gSoC add MERGE command new patch -- merge_v104