From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Geoffrey <esoteric(at)3times25(dot)net> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: How to check postgres running or not ? |
Date: | 2004-09-19 16:25:00 |
Message-ID: | 19430.1095611100@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Geoffrey <esoteric(at)3times25(dot)net> writes:
> Worik wrote:
>> Assuming it is unix.... The command
>> ps xau|grep post
> You might want to change that to:
> ps aux|grep postgres
> As your suggestion will pick up extraneous data if one is running
> postfix on the same box.
Actually I'd recommend grepping for "postmaster". If your PG user is
named "postgres" then the above command will find any program the PG
user is running --- which might only be a shell, for instance. If your
PG user is not named "postgres" then the above might find nothing at
all, even though the postmaster is alive (since depending on the details
of your local ps command, it might report all the server processes as
"postmaster").
There is even another gotcha, which is that the "grep postmaster"
command could easily find itself in the ps output. So what really
works is
ps aux | grep postmaster | grep -v grep
(or use "ps -ef" if using a SysV-ish ps).
Obviously none of this matters if you are just going to eyeball the
output, but if you want something suitable for a test in a script,
you'd better use something like the last one.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | T E Schmitz | 2004-09-19 16:36:36 | Re: ORDER BY and NULLs |
Previous Message | Jean-Luc Lachance | 2004-09-19 16:19:55 | Re: ORDER BY and NULLs |