Re: trace_recovery_messages
От | Fujii Masao |
---|---|
Тема | Re: trace_recovery_messages |
Дата | |
Msg-id | AANLkTilhOhiC3p5SOQz0R2XZrtGNBImxaRX7BRKq18a4@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: trace_recovery_messages (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: trace_recovery_messages
|
Список | 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 по дате отправления: