Jelle Ouwerkerk writes:
> I'm running 'Linux 2.2.16-22smp #1 SMP i686 unknown' and a solution that
> was proposed to me was to use cron and a program called logrotate:
> Unfortunately, after replacing/rotating/compressing the database log file,
> the new log file remains empty. I have a feeling that postgres has lost
> the reference to the original log file and that the new log data is lost
> into the void.
The logrotate program just moves the log file to a different name, but the
PostgreSQL server has the file open so it just keeps writing to the same
file no matter what name it has. What you need to do is pipe the log
output through a separate program that closes and reopens the file once in
a while. Apache has such a program, for example.
--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter
