| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tommi Maekitalo <t(dot)maekitalo(at)epgmbh(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_ctl reports succes when start fails |
| Date: | 2003-10-23 14:48:17 |
| Message-ID: | 29828.1066920497@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> I've also noticed that on our production 7.3.4 server logging to syslog,
> that if I change the postgresql.conf to enable log_statement, and then
> do pg_ctl reload, it works, but then when I disable it again, pg_ctl
> reload does not cause postgres to pick up the changes.
By "disable" do you mean "turn off", or "comment out again"? The latter
is not going to affect the state of the postmaster ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregor Zeitlinger | 2003-10-23 14:53:38 | Re: is GiST still alive? |
| Previous Message | Christopher Kings-Lynne | 2003-10-23 14:36:35 | Re: pg_ctl reports succes when start fails |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-10-23 15:04:07 | Re: pg_ctl reports succes when start fails |
| Previous Message | Christopher Kings-Lynne | 2003-10-23 14:36:35 | Re: pg_ctl reports succes when start fails |