Re: Log rotation?
| От | Ken Hirsch |
|---|---|
| Тема | Re: Log rotation? |
| Дата | |
| Msg-id | OE53pH71yEXUIEAOeIi00005251@hotmail.com обсуждение исходный текст |
| Ответ на | Log rotation? (Peter Eisentraut <peter_e@gmx.net>) |
| Список | pgsql-hackers |
You may be interested in http://www.ietf.org/internet-drafts/draft-ietf-syslog-reliable-12.txt which builds a reliable syslog protocol on top of BEEP. There are free implementations of BEEP in C and Java at http://beepcore.org ----- Original Message ----- From: "Matthew Hagerty" <mhagerty@voyager.net> To: "Ian Lance Taylor" <ian@airs.com>; "Tom Lane" <tgl@sss.pgh.pa.us> Cc: "Peter Eisentraut" <peter_e@gmx.net>; "PostgreSQL Development" <pgsql-hackers@postgresql.org> Sent: Thursday, September 06, 2001 10:08 AM Subject: Re: [HACKERS] Log rotation? > At 08:54 PM 9/5/2001 -0700, Ian Lance Taylor wrote: > >Tom Lane <tgl@sss.pgh.pa.us> writes: > > > > > > And no, "use syslog" doesn't count. > > > > > > Why not? > > > >The standard implementations of syslog lose log entries under heavy > >load, because they rely on a daemon which reads from a named pipe with > >a limited buffer space. This is not acceptable in a production > >system, since heavy load is often just the time you need to see the > >log entries. > > > >It would be possible to implement the syslog(3) interface in a > >different way, of course, which did not use syslogd. I don't know of > >any such implementation. > > > >(My personal preference these days is an approach like DJB's > >daemontools, which separates the handling of log entries from the > >program doing the logging.) > > > >Ian > > Greetings, > > Kind of ironic, I have been working on a similar logging system for Apache > that works with PostgreSQL, and I just released 2.0-beta last night. My > post to announcements was delayed, but you can check it out here: > http://www.digitalstratum.com/pglogd/ > > If pgLOGd looks like something similar to what you are looking for, I could > probably modify it to log for PostgreSQL. Two of its requirements during > development were fast and robust, and similar to what you described above > it does not "process" the entries, that is done later. You also got me > thinking that maybe syslogd needs an overhaul too... > > Matthew > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
В списке pgsql-hackers по дате отправления: