| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Markus Bertheau <twanger(at)bluetwanger(dot)de> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: pg_ctl telling only half the truth |
| Date: | 2004-11-05 15:46:32 |
| Message-ID: | 26408.1099669592@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Markus Bertheau <twanger(at)bluetwanger(dot)de> writes:
> Guess what happend here:
> [bertheau(at)dicaprio pg80]$ bin/pg_ctl -D data -l log start
> postmaster starting
> [bertheau(at)dicaprio pg80]$
> No, postmaster was not starting - it was configured to listen on the
> default port - and there was already another postmaster running on 5432.
> This information was of course in the log file, but pg_ctl should have
> said that the postmaster did not start successfully.
It did not say that the postmaster had started; it said it was starting,
which was true. If you want it to wait around to verify whether the
postmaster started OK, use the -w switch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Bertheau | 2004-11-05 15:50:59 | Re: pg_ctl telling only half the truth |
| Previous Message | SZŰCS Gábor | 2004-11-05 14:52:39 | Killed backend won't rollback transaction? |