Re: Feature request -- Log Database Name
От | ohp@pyrenet.fr |
---|---|
Тема | Re: Feature request -- Log Database Name |
Дата | |
Msg-id | Pine.UW2.4.53.0307241718410.23482@server.pyrenet.fr обсуждение исходный текст |
Ответ на | Re: Feature request -- Log Database Name (Larry Rosenman <ler@lerctr.org>) |
Ответы |
Re: Feature request -- Log Database Name
|
Список | pgsql-hackers |
On Wed, 23 Jul 2003, Larry Rosenman wrote: > Date: Wed, 23 Jul 2003 15:22:49 -0500 > From: Larry Rosenman <ler@lerctr.org> > To: Robert Treat <xzilla@users.sourceforge.net> > Cc: Josh Berkus <josh@agliodbs.com>, ohp@pyrenet.fr, > pgsql-hackers list <pgsql-hackers@postgresql.org> > Subject: Re: [HACKERS] Feature request -- Log Database Name > > > > --On Wednesday, July 23, 2003 16:20:20 -0400 Robert Treat > <xzilla@users.sourceforge.net> wrote: > > > > > > Should it be a GUC like log_timestamp that can be applied to all log > > messages? > IMHO, Yes, and it probably can be localized to elog(), although I haven't > looked > at the current elog() function code since 7.0 when I futzed with the > syslog() code. > > the question is: > > Is this a feature change, or a bug fix given the error reporting change for > 7.4? I hope it can go into 7.4 (could we have a port on 7.3.4 if it's comming?) Also I was thinking that we could "hide" a log table into a "special" schema like this: CREATE TABLE log ( when timestamp, user text, table name, query text, error text); So that iff this table exists in a databse, all error reporting would be logged in this table. This sounds complicated but IMHO would be unvaluable for debugging help Regards -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 6, Chemin d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp@pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)
В списке pgsql-hackers по дате отправления: