Re: syslog_line_prefix

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Joshua Tolley <eggyknap(at)gmail(dot)com>, jd <jd(at)commandprompt(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: syslog_line_prefix
Date: 2009-09-28 17:44:12
Message-ID: 11569.1254159852@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane escribi:
>> 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.

Hmm, I guess I missed where you proposed an implementation that would
support that?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2009-09-28 17:44:58 Re: Review handling of MOVE and FETCH (ToDo)
Previous Message Tom Lane 2009-09-28 17:32:21 Re: [PATCH] DefaultACLs