| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:36:35 |
| Message-ID: | 3F97E773.9020908@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
> If you don't use -w, then pg_ctl doesn't wait around to see whether the
> postmaster started or not. It'd probably be a good idea for it to issue
> a less positive message in this case, maybe only "postmaster launched".
>
> I also wonder why -w isn't the default.
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.
I haven't done too much investigation here in to the exact problem, but
there is something odd going on...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-23 14:48:17 | Re: pg_ctl reports succes when start fails |
| Previous Message | Andrew Dunstan | 2003-10-23 14:36:02 | Re: pg_ctl reports succes when start fails |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-23 14:48:17 | Re: pg_ctl reports succes when start fails |
| Previous Message | Andrew Dunstan | 2003-10-23 14:36:02 | Re: pg_ctl reports succes when start fails |