Re: trace_recovery_messages - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: trace_recovery_messages
Date
Msg-id AANLkTilhOhiC3p5SOQz0R2XZrtGNBImxaRX7BRKq18a4@mail.gmail.com
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 Fri, Jun 18, 2010 at 2:48 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Fujii Masao <masao.fujii@gmail.com> writes:
>> We should make trace_recovery_messages available only when
>> the WAL_DEBUG macro was defined?
>
> No, because it's used in a lot of other contexts besides that.
>
>> Currently it's always
>> available, so the standby seems to call elog() too frequently.
>
> Where?  I don't see very many messages that would actually get emitted
> at the default setting of the parameter.

Yes. I was just concerned that frequent calls themselves may increase
the overhead.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: KaiGai Kohei
Date:
Subject: Re: modular se-pgsql as proof-of-concept
Next
From: Takahiro Itagaki
Date:
Subject: Re: Partitioning syntax