From: Kong Man <kong_mansatiansin@hotmail.com>
To: pgsql-admin@postgresql.org
Subject: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
Date: Sat, 22 Dec 2012 21:52:13 -0800
Message-ID: <DUB116-W200DF672981FC04C6A52768B340@phx.gbl> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
We ran into a production issue during our maintenance window when I switched over LifeKeeper/PostgreSQL nodes from one to another. We noticed that the database was 1000 times slower than it usually is, then realized that the log_min_messages setting was set to 'debug5' for no reason.
Facts:
The postgresql.conf file has always been using the default value, which is 'warning'.An attempt to explicitly set log_min_messages=warning and reload could not override the setting of 'debug5'.The heavy debug5 logging on our production system drastically slowed down our database, and eventually filled up the root file system (due to the huge /var/log/postgresql)The LifeKeeper failover has been done in a recent past with the same unmodified postgresql.log file without such an excessive logging behavior.Changing log_destination from syslog to stderr appeared to have done the trick, after hours of troubleshooting. The log_min_messages value took the explicit setting from postgresql.log ('warning') and restored our database performance.
I could not find any relevant issue reported and want to see if anyone has a clue about this issue.
Thank you,
-Kong
=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: kong_mansatiansin@hotmail.com
Subject: Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
In-Reply-To: <DUB116-W200DF672981FC04C6A52768B340@phx.gbl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox