Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c') - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date
Msg-id d8c28dd5c7079e9a54eacc319dae5540
Whole thread Raw
In response to Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')  (Mattias Kregert <matti@algonet.se>)
List pgsql-hackers
On Fri, 2 Jan 1998, Bruce Momjian wrote:

> >
> > Bruce Momjian wrote:
> > >
> >
> > > I just think the WARN word coming up on users terminals is odd.  I can
> > > make the change in all the source files easily if we decide what the new
> > > error word should be.  Error?  Failure?
> > >
> >
> > Yes, that's one of the things I don't understand with PostgreSQL.
> > ERROR would be much better.
> >
> > It would be even better if the backend would have an option to
> > log all messages via syslog. That would be much easier, especially
> > if you use syslog to send log messages to a separate log server, or
> > if you want different types of messages to go to different locations,
> > like FATAL to a console, WARN to a file somewhere and so on.
>
> Syslog functionality is on the TODO list.

    Mark me down for it...

------------------------------

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Next
From: Bruce Momjian
Date:
Subject: Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')