pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedlog_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
6+ messages / 4 participants
[nested] [flat]
* log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
@ 2012-12-23 05:52 Kong Man <kong_mansatiansin@hotmail.com>
2012-12-23 17:21 ` Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 6+ messages in thread
From: Kong Man @ 2012-12-23 05:52 UTC (permalink / raw)
To: pgsql-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
=
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
2012-12-23 05:52 log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kong Man <kong_mansatiansin@hotmail.com>
@ 2012-12-23 17:21 ` Tom Lane <tgl@sss.pgh.pa.us>
2012-12-24 05:59 ` Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kong Man <kong_mansatiansin@hotmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Tom Lane @ 2012-12-23 17:21 UTC (permalink / raw)
To: Kong Man <kong_mansatiansin@hotmail.com>; +Cc: pgsql-admin
Kong Man <kong_mansatiansin@hotmail.com> writes:
> 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.
How was the postmaster started? From memory, "-d5" on its command line
would do that, and would not have been overridable from postgresql.conf.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
2012-12-23 05:52 log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kong Man <kong_mansatiansin@hotmail.com>
2012-12-23 17:21 ` Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Tom Lane <tgl@sss.pgh.pa.us>
@ 2012-12-24 05:59 ` Kong Man <kong_mansatiansin@hotmail.com>
2012-12-26 22:56 ` Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kong Man <kong_mansatiansin@hotmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Kong Man @ 2012-12-24 05:59 UTC (permalink / raw)
To: tgl@sss.pgh.pa.us; +Cc: pgsql-admin
Hi Tom,
Thank you for some clue in this. So, I assume changing log_destination (from syslog to stderr) was a way around it to override log_min_messages when the -d option is specified?
I am checking with the vender, SIOS, on what scenarios LifeKeeper would start up PostgreSQL with the -d5 option.
Best regards,
-Kong
> From: tgl@sss.pgh.pa.us
> To: kong_mansatiansin@hotmail.com
> CC: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
> Date: Sun, 23 Dec 2012 12:21:12 -0500
>
> Kong Man <kong_mansatiansin@hotmail.com> writes:
> > 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.
>
> How was the postmaster started? From memory, "-d5" on its command line
> would do that, and would not have been overridable from postgresql.conf.
>
> regards, tom lane
=
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
2012-12-23 05:52 log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kong Man <kong_mansatiansin@hotmail.com>
2012-12-23 17:21 ` Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Tom Lane <tgl@sss.pgh.pa.us>
2012-12-24 05:59 ` Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kong Man <kong_mansatiansin@hotmail.com>
@ 2012-12-26 22:56 ` Kong Man <kong_mansatiansin@hotmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Kong Man @ 2012-12-26 22:56 UTC (permalink / raw)
To: tgl@sss.pgh.pa.us; +Cc: pgsql-admin
So, LifeKeeper default setting of LKPGSQLDEBUG=5 on
/etc/default/LifeKeeper was the culprit for this issue, probably by
starting postmaster with -d5 option.
Thank you for pointing us to the right direction.
-Kong
From: kong_mansatiansin@hotmail.com
To: tgl@sss.pgh.pa.us
CC: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
Date: Sun, 23 Dec 2012 21:59:35 -0800
Hi Tom,
Thank you for some clue in this. So, I assume changing log_destination (from syslog to stderr) was a way around it to override log_min_messages when the -d option is specified?
I am checking with the vender, SIOS, on what scenarios LifeKeeper would start up PostgreSQL with the -d5 option.
Best regards,
-Kong
> From: tgl@sss.pgh.pa.us
> To: kong_mansatiansin@hotmail.com
> CC: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
> Date: Sun, 23 Dec 2012 12:21:12 -0500
>
> Kong Man <kong_mansatiansin@hotmail.com> writes:
> > 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.
>
> How was the postmaster started? From memory, "-d5" on its command line
> would do that, and would not have been overridable from postgresql.conf.
>
> regards, tom lane
=
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
@ 2012-12-23 16:08 Kevin Grittner <kgrittn@mail.com>
2012-12-23 16:14 ` Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Walter Hurry <walterhurry@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Kevin Grittner @ 2012-12-23 16:08 UTC (permalink / raw)
To: Kong Man <kong_mansatiansin@hotmail.com>; pgsql-admin
Kong Man wrote:
> The postgresql.conf file has always been using the default value, which is 'warning'.
Maybe it's not using the postgresql.conf file you think it is. Does
this show the file you've been looking at?:
SHOW config_file;
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf
2012-12-23 16:08 Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kevin Grittner <kgrittn@mail.com>
@ 2012-12-23 16:14 ` Walter Hurry <walterhurry@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Walter Hurry @ 2012-12-23 16:14 UTC (permalink / raw)
To: pgsql-admin
On Sun, 23 Dec 2012 11:08:32 -0500, Kevin Grittner wrote:
> Kong Man wrote:
>
>> The postgresql.conf file has always been using the default value, which
>> is 'warning'.
>
> Maybe it's not using the postgresql.conf file you think it is. Does this
> show the file you've been looking at?:
>
> SHOW config_file;
Incidentally, I thought the default level was notice.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2012-12-26 22:56 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-12-23 05:52 log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kong Man <kong_mansatiansin@hotmail.com>
2012-12-23 17:21 ` Tom Lane <tgl@sss.pgh.pa.us>
2012-12-24 05:59 ` Kong Man <kong_mansatiansin@hotmail.com>
2012-12-26 22:56 ` Kong Man <kong_mansatiansin@hotmail.com>
2012-12-23 16:08 Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf Kevin Grittner <kgrittn@mail.com>
2012-12-23 16:14 ` Walter Hurry <walterhurry@gmail.com>
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