| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP - syslogger infrastructure changes |
| Date: | 2009-09-28 15:05:39 |
| Message-ID: | 1254150339.26451.8.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2009-09-26 at 15:35 -0600, Joshua Tolley wrote:
> On Sat, Sep 26, 2009 at 11:43:46AM -0400, Tom Lane wrote:
> > complete but more complex solution. (dup2 works on Windows, no?)
>
> Unless I'm misreading syslogger.c, dup2() gets called on every platform.
>
> I've started the wiki page in question:
> http://wiki.postgresql.org/wiki/Logging_Brainstorm
Most of the items listed there you can already do with a sufficiently
non-ancient syslog implementation.
Has anyone ever actually tested rsyslog and syslog-ng for performance
and robustness with PostgreSQL? Half the ideas about on-disk queuing
and checkpointing and so on that have been mentioned recently seem to
come straight from their documentations.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-28 15:06:15 | Re: Rejecting weak passwords |
| Previous Message | Tom Lane | 2009-09-28 14:46:07 | Re: Rejecting weak passwords |