Re: We should Axe /contrib/start-scripts - Mailing list pgsql-hackers

From Tom Lane
Subject Re: We should Axe /contrib/start-scripts
Date
Msg-id 2155.1251231091@sss.pgh.pa.us
Whole thread Raw
In response to Re: We should Axe /contrib/start-scripts  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: We should Axe /contrib/start-scripts  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: We should Axe /contrib/start-scripts  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Thanks Andrew, Alvaro, and Chander.  You've given me some thoughts to
> toss around.  Of course, any of these is going to be somewhat more
> complex than using [ pg_ctl -w ]

Yeah.  I wonder if we shouldn't expend a bit more effort to make that
way bulletproof.  As I mentioned the other day, if there were a way for
pg_ctl to pass down its parent's PID then we could have the postmaster
exclude that as a false match, and then using pg_ctl would be just as
safe as invoking the postmaster directly.

The two ways I can see to do that are to add a command line switch
to the postmaster, or to pass the PID as an environment variable,
say "PG_GRANDPARENT_PID".  The latter is a bit uglier but it would
require touching much less code (and documentation).

Thoughts?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: We should Axe /contrib/start-scripts
Next
From: "Kevin Grittner"
Date:
Subject: Re: We should Axe /contrib/start-scripts