BTW, the windows service also can remain in an inconsistent state when the
pg_ctl can't stop the postgres server.
I think that pg_ctl uses stop "fast" so, if for some reason postgres don't
response to stop fast, the service in windows service UI appear as stopping
for long time and finally after some kind of timeout it show as not started.
Obviously, if it appear as not started you want to start, but you can't. And
maybe some inexperienced user get crazy, "database is stopped and can't
start" but really DB is started.
What the inexperienced do is the only thing he can do... Restart the server,
when he restart the postgres server receive a KILL message and then
everything get worse
I live this situation time ago and obviously learn :)
De: Anibal David Acosta [mailto:aa(at)devshock(dot)com]
Enviado el: lunes, 17 de septiembre de 2012 09:27 p.m.
Para: 'Craig Ringer'; 'Vincent Dautremont'
Asunto: RE: [ADMIN] Windows Services and Postgresql 9.1.3
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
Due to this bug I always use the pg_ctl command directly and not the windows
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.
[mailto:pgsql-admin-owner(at)postgresql(dot)org] En nombre de Craig Ringer Enviado
el: lunes, 17 de septiembre de 2012 12:43 a.m.
Para: Vincent Dautremont
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.
Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org) To make
changes to your subscription:
In response to
pgsql-admin by date
|Next:||From: himanshu.joshi||Date: 2012-09-18 08:57:40|
|Subject: Problem in taking the database dump|
|Previous:||From: Tom Lane||Date: 2012-09-18 01:36:34|
|Subject: Re: Linux: ps output shows multiple instances of PostgreSQL running on the same port|
pgsql-general by date
|Next:||From: François Beausoleil||Date: 2012-09-18 03:15:05|
|Subject: State of the art for foreign keys to child tables?|
|Previous:||From: Anibal David Acosta||Date: 2012-09-18 01:27:20|
|Subject: Re: Windows Services and Postgresql 9.1.3|