Re: [DOCS] Patch to update log levels - Mailing list pgsql-patches

From Magnus Hagander
Subject Re: [DOCS] Patch to update log levels
Date
Msg-id 20070921083001.GB14383@svr2.hagander.net
Whole thread Raw
In response to Re: [DOCS] Patch to update log levels  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-patches
On Thu, Sep 20, 2007 at 06:27:57PM -0700, Joshua D. Drake wrote:
> Joshua D. Drake wrote:
> > Tom Lane wrote:
> >> "Joshua D. Drake" <jd@commandprompt.com> writes:
> >>> Here is a patch that documents the syslog log levels and their
> >>> correlation to the PostgreSQL log levels per:
> >> This seems like quite the wrong place to document it --- I'd have
> >> thought somewhere near the discussion of syslog logging would be
> >> appropriate.  Putting it here means you're in the face of people
> >> who do not even have syslog (ie, Windows users)
> >
> > Fair enough. Except that we don't really talk about syslog anywhere. We
> > do here:
> >
> > http://developer.postgresql.org/pgdocs/postgres/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHERE
> >
> > Which is pretty much where I put it.
> >
> > Do we have some kind of correlation for eventlog on windows? Then I
> > could just use a table to show the relationships. Something like:
> >
>
> Is this correct for Windows?
>
> 1392         switch (level)
> 1393         {
> 1394             case DEBUG5:
> 1395             case DEBUG4:
> 1396             case DEBUG3:
> 1397             case DEBUG2:
> 1398             case DEBUG1:
> 1399             case LOG:
> 1400             case COMMERROR:
> 1401             case INFO:
> 1402             case NOTICE:
> 1403                 eventlevel = EVENTLOG_INFORMATION_TYPE;
> 1404                 break;
> 1405             case WARNING:
> 1406                 eventlevel = EVENTLOG_WARNING_TYPE;
> 1407                 break;
> 1408             case ERROR:
> 1409             case FATAL:
> 1410             case PANIC:
> 1411             default:
> 1412                 eventlevel = EVENTLOG_ERROR_TYPE;
> 1413                 break;
> 1414         }

Yes.

//Magnus

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: adjust chr()/ascii() to prevent invalidly encoded data
Next
From: "Marshall, Steve"
Date:
Subject: Re: PL/TCL Patch to prevent postgres from becoming multithreaded