From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org Admin <pgsql-admin@postgresql.org>
Subject: Re: 8.3 Logging Question
Date: Thu, 24 Jan 2008 19:36:43 -0500
Message-ID: <17905.1201221403@sss.pgh.pa.us> (raw)
In-Reply-To: <1d219a6f0801241611k2521da69j706f18d032f5a104@mail.gmail.com>
References: <1d219a6f0801241031p4faa7b3cr2260f97e76bc71e0@mail.gmail.com>
<16614.1201214339@sss.pgh.pa.us>
<1d219a6f0801241611k2521da69j706f18d032f5a104@mail.gmail.com>
"Chris Hoover" <revoohc@gmail.com> writes:
> On Jan 24, 2008 5:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> The .log file is to catch any non-csv-format data that comes down the
>> pipe. You can't turn it off.
> What type of data would you expect this to be?
Any bit of code that doesn't know about elog, for instance
--- shared library linking problems from the dynamic loader
--- complaints from perl, python, or other libraries you might have
loaded into the backend
--- corrupted-memory messages out of glibc (malloc)
--- yadda yadda yadda
One of the main strikes against syslog logging has always been that
it fails to capture this type of stuff. You don't realize you need
this until you need it, but then you really do.
regards, tom lane
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, revoohc@gmail.com
Subject: Re: 8.3 Logging Question
In-Reply-To: <17905.1201221403@sss.pgh.pa.us>
* 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