From: | Markus Bertheau <twanger(at)bluetwanger(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: pg_ctl telling only half the truth |
Date: | 2004-11-05 15:50:59 |
Message-ID: | 1099669859.2646.48.camel@dicaprio.akademie1.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
В Птн, 05.11.2004, в 16:46, Tom Lane пишет:
> 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.
Why is the -w switch not on by default then? (I guess this also answers
the question why it is there at all - i.e. why you have to be able to
not wait for the postmaster to start.)
Thanks
--
Markus Bertheau <twanger(at)bluetwanger(dot)de>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-11-05 15:53:55 | Re: Delayed result from another connection |
Previous Message | Tom Lane | 2004-11-05 15:46:32 | Re: pg_ctl telling only half the truth |