| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | fuminori ido <ido(at)netlab(dot)jp>, 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 08:58:35 |
| Message-ID: | Pine.BSO.4.64.0708300457530.9326@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fuminori Ido | 2007-08-30 10:01:54 | Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement |
| Previous Message | Magnus Hagander | 2007-08-30 07:57:27 | Re: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement |