Re: trace_recovery_messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: trace_recovery_messages
Date: 2010-06-17 17:48:43
Message-ID: 22539.1276796923@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2010-06-17 18:02:33 Re: to enable O_DIRECT within postgresql
Previous Message Alvaro Herrera 2010-06-17 17:41:41 Re: ANNOUNCE list (was Re: New PGXN Extension site)