| From: | Scott Frankel <leknarf(at)pacbell(dot)net> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: urgent: another postmaster |
| Date: | 2005-05-23 20:27:01 |
| Message-ID: | e2af43ef5b5185905cba31621d854847@pacbell.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bingo -
Thanks!
On May 23, 2005, at 1:14 PM, Scott Marlowe wrote:
> On Mon, 2005-05-23 at 14:58, Scott Frankel wrote:
>> After a server crash forced a reboot, `pg_ctl start` fails with a
>> FATAL
>> error. Log output says that the lock file, postmaster.pid, already
>> exists.
>>
>> Can I just su to root and delete the .pid file to relaunch? Or will
>> this have nasty
>
> Just check first to make sure there really are no postmasters running
> and you should be safe
>
> ps aex|grep post
>
> and if there's no output, delete the pid file. If there really are
> other postmasters or postgreses running, then kill them first.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F. O'Connell | 2005-05-23 20:56:32 | Re: pg_dump in a production environment |
| Previous Message | Martijn van Oosterhout | 2005-05-23 20:25:23 | Re: pg_dump in a production environment |