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

From Bruce Momjian
Subject Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date
Msg-id 7310fbe23167cb3f7c55a3ad071d827b
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
>
> 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.

- --
Bruce Momjian
maillist@candle.pha.pa.us

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

pgsql-hackers by date:

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