Re: syslog_line_prefix - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: syslog_line_prefix
Date
Msg-id 20090928170705.GB5269@alvh.no-ip.org
Whole thread Raw
In response to Re: syslog_line_prefix  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: syslog_line_prefix
Re: syslog_line_prefix
List pgsql-hackers
Tom Lane escribió:
> [ please trim the quoted material a bit, folks ]
> 
> Magnus Hagander <magnus@hagander.net> writes:
> > 2009/9/28 Robert Haas <robertmhaas@gmail.com>:
> >> The problem with having the syslogger send the data directly to an
> >> external process is that the external process might be unable to
> >> process the data as fast as syslogger is sending it. �I'm not sure
> >> exactly what will happen in that case, but it will definitely be bad.
> 
> This is the same issue already raised with respect to syslog versus
> syslogger, ie, some people would rather lose log data than have the
> backends block waiting for it to be written.

That could be made configurable; i.e. let the user choose whether to
lose messages or to make everybody wait.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Chris Browne
Date:
Subject: Re: 8.5 TODO: Add comments to output indicating version of pg_dump and of the database server
Next
From: Robert Haas
Date:
Subject: Re: syslog_line_prefix