From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Denis BUCHER <dbucherml(at)hsolutions(dot)ch> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Unable to stop postgresql ("failed") -> [SOLVED] |
Date: | 2010-08-06 17:14:43 |
Message-ID: | AANLkTi=DPvKhmKCkS6aKT8zh0kb5a0q5zxmuS5pAm_vy@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6 August 2010 17:49, Denis BUCHER <dbucherml(at)hsolutions(dot)ch> wrote:
> Dear all,
>
> For once, I will simply publish a solution instead of asking a question.
> Let's hope it will be useful to someone.
>
> I was unable to stop postgres, I always got "[FAILED] :
> * /etc/init.d/postgresql stop
> * service postgresql stop
> * /sbin/service postgresql stop
>
> The only solution that worked in that case was :
> * /usr/bin/pg_ctl stop
>
> Have a nice day !
>
> Denis
>
Surely it depends what the packager put into the init.d script? Plus
there's the "zap" option for some setups if you're desperate, although
I don't know if that issues a SIGINT or a SIGQUIT. Hopefully the
former. But really your init.d script should be issuing that pg_ctl
stop command anyway, so don't know why you're getting failed messages.
--
Thom Brown
Registered Linux user: #516935
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-06 17:25:57 | Re: Unable to stop postgresql ("failed") -> [SOLVED] |
Previous Message | Scott Frankel | 2010-08-06 17:02:07 | Re: MySQL versus Postgres |