Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement - Mailing list pgsql-bugs

From Fuminori Ido
Subject Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement
Date
Msg-id 46D69592.2090502@netlab.jp
Whole thread Raw
In response to Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement  (Kris Jurka <books@ejurka.com>)
List pgsql-bugs
Dear Kris and Magnus,

Thanks you very much for your prompt reply.  I'm now clear the behavior
and its future plan.

Thanks again!

best regards,


Kris Jurka wrote:
>
>
> On Thu, 30 Aug 2007, Magnus Hagander wrote:
>
>> There's your problem right there: it does *not* mean that the default
>> setting would be effective. It means that the setting won't be changed.
>> Remove the comment and set it to false, and it'll work.
>> (if you restart the server instead of reload it *will* fall back to the
>> default, which isn't very consistent)
>>
>> This is a known problem (though arguably not actually a bug) but it's far
>> from trivial to fix which is why it hasn't been fixed yet.
>>
>
> Actually this will be fixed in 8.3:
>
> http://archives.postgresql.org/pgsql-committers/2007-03/msg00097.php
>
> Kris Jurka

--
===================================
株式会社 ネットワーク応用通信研究所
NaCl<http://www.netlab.jp/>
井戸 文則 <ido@netlab.jp>
===================================

pgsql-bugs by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: to_tsquery stack overflow
Next
From: Tom Lane
Date:
Subject: Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement