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

From Kris Jurka
Subject Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement
Date
Msg-id Pine.BSO.4.64.0708300457530.9326@leary.csoft.net
Whole thread Raw
In response to Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement  (Magnus Hagander <magnus@hagander.net>)
Responses Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement
Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement
List pgsql-bugs
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

pgsql-bugs by date:

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