Re: pg_ctl is fragile - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_ctl is fragile
Date
Msg-id 29593.1036707283@sss.pgh.pa.us
Whole thread Raw
In response to pg_ctl is fragile  (Neil Conway <neilc@samurai.com>)
Responses Re: pg_ctl is fragile
List pgsql-bugs
Neil Conway <neilc@samurai.com> writes:
> After an unclean shutdown (e.g. a kernel crash), pg_ctl isn't smart
> enough to realize that it won't be able to successfully shut down the
> postmaster:

> $ pg_ctl -D /pgsql/data stop
> /pgsql/bin/pg_ctl: line 269: kill: (2039) - No such process
> waiting for postmaster to shut down................................................................ failed
> pg_ctl: postmaster does not shut down

> We should probably check the exit code produced by kill(1).

Doesn't seem like kill's exit code is going to tell you enough.
If you got, say, "Permission denied" rather than "No such process",
you shouldn't report that the postmaster isn't running.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Neil Conway
Date:
Subject: Re: Cannot assign ROWTYPE, RECORD variables in PL/pgSQL
Next
From: Neil Conway
Date:
Subject: Re: pg_ctl is fragile