From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Larry Rosenman <ler(at)lerctr(dot)org> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, ohp(at)pyrenet(dot)fr, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Feature request -- Log Database Name |
Date: | 2003-07-23 20:20:20 |
Message-ID: | 1058991620.22273.709.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2003-07-23 at 15:38, Larry Rosenman wrote:
>
>
> --On Wednesday, July 23, 2003 12:31:38 -0700 Josh Berkus
> <josh(at)agliodbs(dot)com> wrote:
>
> > Hackers,
> >
> >
> >> Today, logs are all going to a file or syslog or both. But there is no
> >> way at all you can automatically know upon witch database errors are
> >> thrown Therefore, would it be possible/hard to prefix all error/warning
> >> message with the database name on witch it occured.
> >
> > Olivier appears to be correct ... there is no log option which logs the
> > name of the database generating the message.
> >
> > Do we need to add this as a TODO?
> It would be VERY nice to do that, and maybe even the table?
>
Should it be a GUC like log_timestamp that can be applied to all log
messages?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2003-07-23 20:22:17 | Re: Feature request -- Log Database Name |
Previous Message | Paulo Scardine | 2003-07-23 20:15:10 | Re: SELECT FOR UPDATE NOWAIT |