Re: elog() proposal
От | Karel Zak |
---|---|
Тема | Re: elog() proposal |
Дата | |
Msg-id | 20020221100622.A21620@zf.jcu.cz обсуждение исходный текст |
Ответ на | elog() proposal (Bruce Momjian <pgman@candle.pha.pa.us>) |
Список | pgsql-hackers |
On Wed, Feb 20, 2002 at 09:54:51PM -0500, Bruce Momjian wrote: > I just submitted a patch to fix various elog() issues. I have two > additional proposals. > > First, I think ERROR/DEBUG/NOTICE/FATAL, etc are too generic and cause > compile problems/warnings, especially with Perl. I suggest renaming all > elog levels to PG*, so it would be PGERROR and PGINFO. We could also do > E_* or E*. I am interested in other opinions. You forgot PG_* :-) > Second, I propose adding two GUC variables that control how much elog() > info is sent to the server and client logs. I suggest > 'server_message_min' with possible values DEBUG, LOG, NOTICE, ERROR, > FATAL, CRASH; and 'client_message_min' with possible values INFO, > NOTICE, ERROR, FATAL, CRASH. IMHO stop an example NOTICE by "SET NOTICE TO 'OFF'" is better and more common way than current the only one way in libpqand PQsetNoticeProcessor. Karel -- Karel Zak <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
В списке pgsql-hackers по дате отправления: