Re: Feature request -- Log Database Name - Mailing list pgsql-hackers

From Robert Treat
Subject Re: Feature request -- Log Database Name
Date
Msg-id 1058991620.22273.709.camel@camel
Whole thread Raw
In response to Re: Feature request -- Log Database Name  (Larry Rosenman <ler@lerctr.org>)
Responses Re: Feature request -- Log Database Name  (Larry Rosenman <ler@lerctr.org>)
Re: Feature request -- Log Database Name  (Josh Berkus <josh@agliodbs.com>)
List 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@agliodbs.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



pgsql-hackers by date:

Previous
From: "Paulo Scardine"
Date:
Subject: Re: SELECT FOR UPDATE NOWAIT
Next
From: Larry Rosenman
Date:
Subject: Re: Feature request -- Log Database Name