Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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.
Aren't there log-rotation utilities out there already? (I seem to
recall mention that Apache has one, for instance.) Seems like this
is a wheel we shouldn't have to reinvent.
Also, I kinda thought the long-range solution was to encourage everyone
to migrate to syslog logging ...
> And no, "use syslog" doesn't count.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Doug McNaught||Date: 2001-09-06 03:28:10|
|Subject: Re: Is there a problem running vacuum in the middle of a transaction?|
|Previous:||From: Tom Lane||Date: 2001-09-06 03:05:21|
|Subject: Re: cannot detect too many clients |