Re: [PATCHES] [DOCS] Patch to update log levels
"Joshua D. Drake" <[EMAIL PROTECTED]> writes: >> Do we have some kind of correlation for eventlog on windows? Then I >> could just use a table to show the relationships. Done. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PATCHES] [DOCS] Patch to update log levels
On Thu, Sep 20, 2007 at 06:27:57PM -0700, Joshua D. Drake wrote:
> Joshua D. Drake wrote:
> > Tom Lane wrote:
> >> "Joshua D. Drake" <[EMAIL PROTECTED]> 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
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Re: [PATCHES] [DOCS] Patch to update log levels
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua D. Drake wrote:
> Tom Lane wrote:
>> "Joshua D. Drake" <[EMAIL PROTECTED]> 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?
1392switch (level)
1393{
1394case DEBUG5:
1395case DEBUG4:
1396case DEBUG3:
1397case DEBUG2:
1398case DEBUG1:
1399case LOG:
1400case COMMERROR:
1401case INFO:
1402case NOTICE:
1403eventlevel = EVENTLOG_INFORMATION_TYPE;
1404break;
1405case WARNING:
1406eventlevel = EVENTLOG_WARNING_TYPE;
1407break;
1408case ERROR:
1409case FATAL:
1410case PANIC:
1411default:
1412eventlevel = EVENTLOG_ERROR_TYPE;
1413break;
1414}
Sincerely,
Joshua D. Drake
> Log Level
> PostgreSQLSyslog EventLog
> Panic LOG_CRITUsual 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-
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Re: [PATCHES] [DOCS] Patch to update log levels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Lane wrote: > "Joshua D. Drake" <[EMAIL PROTECTED]> 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: Log Level PostgreSQL Syslog EventLog Panic LOG_CRITUsual Behavior Sincerely, Joshua D. Drake > > regards, tom lane > - -- === 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 iD8DBQFG8xnvATb/zqfZUUQRAjVLAKCaSj8FRfz4XXQmHsdzFKxEE49lNQCgiH0z yVIbB+YCyiP1HXLWrvujg38= =GtSc -END PGP SIGNATURE- ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PATCHES] [DOCS] Patch to update log levels
"Joshua D. Drake" <[EMAIL PROTECTED]> 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) regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
