Re: WIP - syslogger infrastructure changes - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: WIP - syslogger infrastructure changes
Date
Msg-id 20090925202342.GQ3914@alvh.no-ip.org
Whole thread Raw
In response to Re: WIP - syslogger infrastructure changes  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas escribió:

> $ With that, it's no longer necessary to restart your server just to
> $ reconfigure the logging, and it also takes away a confusing parameter
> $ (really "log_destination=stderr, logging_collector=on" is *not* a logical
> $ way to say "log to file"). Instead, it adds a log_destination of "file" that
> $ is the standard log to file."
> 
> Do we have any positive or negative experience with logging_collector
> as a performance bottleneck?  Are there people running with
> logging_collector=off to avert disaster?

The collector can be a bottleneck, yes, but for this to happen it needs
to be in active use.  So if the collector is always running but the
messages are being sent to syslog, no harm is done.

(A customer of ours found the hard way that the collector can block
backends when things are tight.  They have since switched to syslog.)

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Hot Standby 0.2.1
Next
From: Andrew Dunstan
Date:
Subject: Re: syslog_line_prefix