Re: Postgres server output log

On Thu, 2003-01-30 at 05:22, Rajesh Kumar Mallah. wrote:
>
> This is someones' elses' posting that i have preserved
> shud be useful.
...
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
>
> Well,
> the most correct way to do a logrotate is ( Redhat ):
...
> 2) Put on the directory /etc/logrotate.d a file called
> 'postgres' with the following lines:
>
> /var/log/postgresql.log {
> compress
> rotate 2
> size=10000k
> errors mendola(at)bigfoot(dot)com
> create 0664 postgres postgres
> daily
> postrotate
> /usr/bin/killall -HUP syslogd
> endscript
> }
...

This won't work as it stands with PostgreSQL, because the hangup signal
does not make the postmaster reopen the log file. Instead of that
postrotate section, you need to use logrotate's copytruncate option,
which will copy the logfile to another file before zeroing the logfile.

Depending on what is being logged, you may want to change the
permissions to 660; there may be stuff in the logs that you don't want
to reveal to the world. (With copytruncate, I think the create option
applies to the copy files rather than to the original logfile.)

--
Oliver Elphick Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"The Lord knoweth how to deliver the godly out of
temptations, and to reserve the unjust unto the day of
judgment to be punished;" II Peter 2:9