Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 503DB9F9E80; Fri, 21 Sep 2007 05:30:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 80331-05; Fri, 21 Sep 2007 05:30:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 3A15D9F9C4F; Fri, 21 Sep 2007 05:30:05 -0300 (ADT) Received: by svr2.hagander.net (Postfix, from userid 1000) id D9B03DCC7C6; Fri, 21 Sep 2007 10:30:01 +0200 (CEST) Date: Fri, 21 Sep 2007 10:30:01 +0200 From: Magnus Hagander To: "Joshua D. Drake" Cc: Tom Lane , Patches , pgsql-docs@postgresql.org Subject: Re: [PATCHES] Patch to update log levels Message-ID: <20070921083001.GB14383@svr2.hagander.net> References: <46F31362.1080301@commandprompt.com> <17733.1190336531@sss.pgh.pa.us> <46F319EF.40301@commandprompt.com> <46F31E1D.3040906@commandprompt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F31E1D.3040906@commandprompt.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/16 X-Sequence-Number: 4414 On Thu, Sep 20, 2007 at 06:27:57PM -0700, Joshua D. Drake wrote: > Joshua D. Drake wrote: > > Tom Lane wrote: > >> "Joshua D. Drake" 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