rotating log files and adding timestamps to postgres logs

From: Kenny W Drobnack <kenny(dot)w(dot)drobnack(at)jpmchase(dot)com>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: rotating log files and adding timestamps to postgres logs
Date: 2009-06-01 16:34:25
Message-ID: 6E25A151103CC340A1CB2CD7D44DCA45098E0E56C9@EMASC218VS01.exchad.jpmchase.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I'm working with an application running on PostgreSQL 7.4.17 on RedHat Enterprise Linux. When asked to troubleshoot a problem, I found out the script that starts the PostgreSQL server (/etc/rc.d/init.d/postgresql) was logging to /dev/null To try to fix this, I changed PGLOG=/dev/null to

PGLOG="| /usr/sbin/rotatelogs /var/log/pgsql 86400"

Similar to what is detailed here: http://www.postgresql.org/docs/8.1/interactive/logfile-maintenance.html

When I restarted the server it caused an error that the file "| /usr/sbin/rotatelogs /var/log/pgsql 86400" I made sure rotatelogs is installed, available, and working.

Is this a setup that only works with new versions of PostgreSQL? As far as I know upgrading is not an option and syslog is not available for use. Any suggestions to get log rotation working?

On a related note, I'm currently just doing "PGLOG=/var/log/pgsql". It is working, but there are no timestamps in the file except for when the database was restarted. Any configuration option that can be changed to get timestamps in the log file?

This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Browne 2009-06-01 16:40:12 Re: Security question UNIX Sockets vs CIDR style access
Previous Message Andy Shellam 2009-06-01 16:13:22 Re: Security question UNIX Sockets vs CIDR style access