Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement

From: Fuminori Ido <ido(at)netlab(dot)jp>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement
Date: 2007-08-30 10:01:54
Message-ID: 46D69592.2090502@netlab.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)netlab(dot)jp>
===================================

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2007-08-30 10:02:24 to_tsquery stack overflow
Previous Message Kris Jurka 2007-08-30 08:58:35 Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement