| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 11:46:37 |
| Message-ID: | 603c8f070909280446k52459fcco908e49efa0a9c1a2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 28, 2009 at 6:51 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> I think it's better to spool the log messages to files, and then let
>> the external utility read the files. The external utility can still
>> fall behind, but even if it does the cluster will continue running.
>
> The difficulty there is to make it "live enough". But I guess if it
> implements the same method as tail -f, it would do that - the only
> issue then would be the fact that this would require much more I/O on
> disk.
The I/O issue is a tricky one. If that's an issue, then maybe a pipe
or socket is a better fit. But if the pipe fills up, then the logging
collector needs to begin spooling the messages to disk so that the
whole system doesn't pile up on the external log analyzer. Figuring
out the right design here is a bit tricky.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-09-28 12:00:01 | Re: Newbie's question: How can I connect to my postgresql-server? |
| Previous Message | Andrew Dunstan | 2009-09-28 11:35:03 | Re: Rejecting weak passwords |