Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 16DC09FA3EF; Thu, 20 Sep 2007 22:10:21 -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 24162-01; Thu, 20 Sep 2007 22:10:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 8DB6A9FA3BA; Thu, 20 Sep 2007 22:10:12 -0300 (ADT) Received: from [192.168.1.9] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l8L1ABjg028560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Sep 2007 18:10:15 -0700 Message-ID: <46F319EF.40301@commandprompt.com> Date: Thu, 20 Sep 2007 18:10:07 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 2.0.0.6 (X11/20070919) MIME-Version: 1.0 To: Tom Lane CC: Patches , pgsql-docs@postgresql.org Subject: Re: Patch to update log levels References: <46F31362.1080301@commandprompt.com> <17733.1190336531@sss.pgh.pa.us> In-Reply-To: <17733.1190336531@sss.pgh.pa.us> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.1/4349/Wed Sep 19 15:46:46 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Thu, 20 Sep 2007 18:10:15 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/14 X-Sequence-Number: 4412 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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: Log Level PostgreSQL Syslog EventLog Panic LOG_CRIT Usual 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-----