Re: Annoying error messages in _dosmaperr

Поиск
Список
Период
Сортировка
От ITAGAKI Takahiro
Тема Re: Annoying error messages in _dosmaperr
Дата
Msg-id 20081016102603.897D.52131E4D@oss.ntt.co.jp
обсуждение исходный текст
Ответ на Re: Annoying error messages in _dosmaperr  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Annoying error messages in _dosmaperr  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> It's probably not worth the trouble to do that, but maybe we could just
> have a FRONTEND_DEBUG compile time switch:
> That would at least leave the code in place if anyone needed the
> debugging output badly enough to do a custom build.

It would be a simplest solution.

I grep-ed sources with #ifndef FRONTEND and #ifdef FRONTEND,
but there are no other "DEBUG or stderr" codes. All other codes
are "WARNING/LOG or stderr", so I keep all of them as-is.


Index: src/port/win32error.c
===================================================================
--- src/port/win32error.c    (HEAD)
+++ src/port/win32error.c    (working copy)
@@ -180,7 +180,7 @@            ereport(DEBUG5,                    (errmsg_internal("mapped win32 error code %lu to %d",
                                   e, errno)));
 
-#else
+#elif FRONTEND_DEBUG            fprintf(stderr, _("mapped win32 error code %lu to %d"), e, errno);#endif
return;


Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




В списке pgsql-hackers по дате отправления:

Предыдущее
От: ITAGAKI Takahiro
Дата:
Сообщение: Re: contrib/pg_stat_statements
Следующее
От: "Neil Conway"
Дата:
Сообщение: Memory leak on hashed agg rescan