From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Chris Hoover" <revoohc(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org Admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: 8.3 Logging Question |
Date: | 2008-01-25 00:36:43 |
Message-ID: | 17905.1201221403@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Chris Hoover" <revoohc(at)gmail(dot)com> writes:
> On Jan 24, 2008 5:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-01-25 00:47:42 | Re: Backup |
Previous Message | Phillip Smith | 2008-01-25 00:34:02 | Re: Backup |