Message-ID: <5056AA3F.7020407@ringerc.id.au>
Date: Mon, 17 Sep 2012 12:42:39 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: Vincent Dautremont <vincent@searidgetech.com>
CC: pgsql-admin@postgresql.org
Subject: Re: Windows Services and Postgresql 9.1.3
References: 
 <CAA4Vp4_LMVE8eTga6-cb=xDuwFoQ_o0X=UhgRESAgRRdVyCrMw@mail.gmail.com>
In-Reply-To: 
 <CAA4Vp4_LMVE8eTga6-cb=xDuwFoQ_o0X=UhgRESAgRRdVyCrMw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 09/12/2012 04:48 AM, Vincent Dautremont wrote:

> For example, after the server had rebooted, I would stop the service
> from services.msc
> Windows then reports it as stopped but I can still see that the database
> is running,  and can use it.

Check in the process monitor (or, better, with Process Explorer from 
Sysinternals) to see what user the `postgres.exe` processes are running as.

> When I would start the service again, I would end up with a timeout
> waiting for the service to be started. When in fact the database was
> always running.
>
> Anyone had that bug/problem before ?

Nope. Sounds completely crazy. More info needed, though.

--
Craig Ringer