From: Joshua D. Drake <jd@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Patches <pgsql-patches@postgresql.org>
Cc: pgsql-docs@postgresql.org
Subject: Re: [PATCHES] Patch to update log levels
Date: Thu, 20 Sep 2007 18:27:57 -0700
Message-ID: <46F31E1D.3040906@commandprompt.com> (raw)
In-Reply-To: <46F319EF.40301@commandprompt.com>
References: <46F31362.1080301@commandprompt.com>
<17733.1190336531@sss.pgh.pa.us>
<46F319EF.40301@commandprompt.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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-W...
>
> 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 }
Sincerely,
Joshua D. Drake
> Log Level
> PostgreSQL Syslog EventLog
> Panic LOG_CRIT Usual Behavior
>
> Sincerely,
>
> Joshua D. Drake
>
>
>> regards, tom lane
>
>
>
- ---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG8x4cATb/zqfZUUQRAmaPAKCQIpHDRBCFP9pLlyi88huJKyWbFgCfd4K3
EGs9/5lJEkV1UxJuqJBUXFY=
=f9R/
-----END PGP SIGNATURE-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: jd@commandprompt.com, tgl@sss.pgh.pa.us, pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Patch to update log levels
In-Reply-To: <46F31E1D.3040906@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox