From: "Anibal David Acosta" <aa@devshock.com>
To: "'Craig Ringer'" <ringerc@ringerc.id.au>,
	"'Vincent Dautremont'" <vincent@searidgetech.com>
Cc: <pgsql-admin@postgresql.org>
References: 
 <CAA4Vp4_LMVE8eTga6-cb=xDuwFoQ_o0X=UhgRESAgRRdVyCrMw@mail.gmail.com>
	<5056AA3F.7020407@ringerc.id.au>
In-Reply-To: <5056AA3F.7020407@ringerc.id.au>
Subject: Re: Windows Services and Postgresql 9.1.3
Date: Mon, 17 Sep 2012 21:27:20 -0400
Message-ID: <001201cd953c$c16f84e0$444e8ea0$@devshock.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQJq8rvavygXY/ZAeCUAlEuYNxpZmwHJwSgflkZBDGA=
Content-Language: es-py

Yes, is a Bug, sometimes in some circumstances pg_ctl go down but postgres
server still running.

You can easily reproduce.

Go to "task manager", kill the process "pg_ctl" (simulate some kind of crash
or something else).
Now go to services management and try to start again. Start command will
through an error because pg_ctl can't start database because is already
started.

Due to this bug I always use the pg_ctl command directly and not the windows
service.

Running pg_ctl command from command prompt show that postgres server is
running, but windows service show stopped and is not possible to start again
from windows service UI

Maybe a resolution of this is that pg_ctl ignore the start call from windows
(just success it) when it is already running.

Regards

-----Mensaje original-----
De: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] En nombre de Craig Ringer
Enviado el: lunes, 17 de septiembre de 2012 12:43 a.m.
Para: Vincent Dautremont
CC: pgsql-admin@postgresql.org
Asunto: Re: [ADMIN] Windows Services and Postgresql 9.1.3

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


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin