Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Mark Llewellyn <mark_llewellyn(at)adp(dot)com>, pgsql-hackers(at)postgresql(dot)org, Sujeet Rajguru <sujeet(dot)rajguru(at)enterprisedb(dot)com>
Subject: Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Date: 2010-11-12 15:03:26
Message-ID: 9721.1289574206@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Uh, I still cannot reproduce the failure:

I would imagine you need -w option on the start. The whole issue
here is whether start's wait-for-server-start code works.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2010-11-12 16:47:27 Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Previous Message Michael Feldmann 2010-11-12 14:19:01 BUG #5751: pg_restore does not work correctly with BLOBs

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-11-12 15:25:51 Re: wCTE behaviour
Previous Message Alvaro Herrera 2010-11-12 14:54:18 Re: We need index-only scans