Log rotation?
От
Peter Eisentraut
Тема
Log rotation?
Дата
Msg-id
Pine.LNX.4.30.0109050253250.828-100000@peter.localdomain
Список
Дерево обсуждения
Log rotation? Peter Eisentraut <peter_e@gmx.net>
Re: Log rotation? Tom Lane <tgl@sss.pgh.pa.us>
Re: Log rotation? darcy@druid.net (D'Arcy J.M. Cain)
Re: Log rotation? Peter Eisentraut <peter_e@gmx.net>
Re: Log rotation? Tom Lane <tgl@sss.pgh.pa.us>
Re: Log rotation? Ian Lance Taylor <ian@airs.com>
Re: Log rotation? Tom Lane <tgl@sss.pgh.pa.us>
Re: Log rotation? Matthew Hagerty <mhagerty@voyager.net>
Re: Log rotation? "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Re: Log rotation? Peter Eisentraut <peter_e@gmx.net>
Re: Log rotation? "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Re: Log rotation? Peter Eisentraut <peter_e@gmx.net>
With all the great work put into allowing true 24/7 operation, as distributed we're still unable to rotate the log file. While the log file tends to be smaller than the database system as a whole, this is still going to annoy people because they can't control disk usage without taking the server down. I've been playing with a little program I wrote whose sole purpose is to write its stdin to a file and close and reopen that file when it receives a signal. I figured this could work well when integrated transparently into pg_ctl. So, is log rotation a concern? Is this a reasonable solution? Other ideas? (No Grand Unified Logging Solutions please. And no, "use syslog" doesn't count.) -- Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter
В списке pgsql-hackers по дате отправления