Database Reference
In-Depth Information
Unfortunately, this can go wrong at each step, due to various reasons, such as nobody feeling
that this is his/her area of expertise, the right people not having time and hoping for someone
else to deal with it, and these other people may just not be reading the list at the right
moment.
If this happens, follow up your question in a day or two to try to understand why there was
no reaction.
See also
The official PostgreSQL bug/problem reporting guides
If you follow the following URLs, you have a high chance of getting your questions answered:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
http://wiki.postgresql.org/wiki/SlowQueryQuestions
Producing a daily summary of logfile errors
PostgreSQL can generate gigabytes of logs per day. Lots of data is good in case you want
to investigate some specific event, but it is not what you will use for daily monitoring of
database health.
Getting ready
Make sure that your PostgreSQL is set up to rotate the log files daily.
A default setup will do exactly the following:
log_rotation_age = 1d
Then get a PostgreSQL log processing program. Here, we describe how to do it using pgFouine.
For most Linux systems, you should be able to use your default package manager to install
pgFouine.
Configure your PostgreSQL to produce
logfiles
in a format that pgFouine understands.
Select logging to
syslog
. Use a modern version of
syslogd
for high-traffic databases.
How to do it...
Set up a cron job to run a few minutes after the default log rotation time. You can find the time
by looking at timestamps of already rotated log files; they all have similar times.
