From: | Kong Man <kong_mansatiansin(at)hotmail(dot)com> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf |
Date: | 2012-12-24 05:59:35 |
Message-ID: | DUB116-W140DDBA75EBE24D4A5696EA8B3B0@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us
> To: kong_mansatiansin(at)hotmail(dot)com
> CC: pgsql-admin(at)postgresql(dot)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(at)hotmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | satish kumar | 2012-12-24 13:26:54 | Regarding Migaration from Mysql procedures to Postgresql Functions |
Previous Message | Tom Lane | 2012-12-23 17:21:12 | Re: log_min_messages=debug5, despite an explicit setting to warning on postgresql.conf |