| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rudolf Potucek <potucek(at)ucalgary(dot)ca> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: postmaster will not start with stale lockfile but not report why |
| Date: | 2002-10-07 14:49:32 |
| Message-ID: | 23641.1034002172@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-ports |
Rudolf Potucek <potucek(at)ucalgary(dot)ca> writes:
> Oct 4 14:05:45 antimony3 postgresql: Starting postgresql service:
> failed
> Maybe, just maybe, it would be nice if the server croaked a bit more
> vebously?
The postmaster croaks as verbosely as it can. I'll bet lunch that your
system's startup script is redirecting the postmaster's stderr to
/dev/null (or using the -S switch which has the same effect). If so,
we are not the people to complain to ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-10-07 15:17:14 | Re: Query optimizer bug |
| Previous Message | Tom Lane | 2002-10-07 14:42:36 | Re: Possible bug in PostgreSQL query planner |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lee Kindness | 2002-10-07 15:17:54 | Re: postmaster will not start with stale lockfile but not report why |
| Previous Message | Rudolf Potucek | 2002-10-04 20:21:20 | postmaster will not start with stale lockfile but not report why |