Tom Lane <t...@sss.pgh.pa.us> wrote: > 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? You're thinking that pg_ctl would capture it's parent PID and pass it to the postmaster one way or the other? That seems like it covers the specific issue you were referencing up-thread. It has been bubbling around in my head that we have other processes which run under the same user ID for such things as vacuum and purge scripts, as well as rsync of backup files. These would still create some risk of a false match, right? Just a much smaller risk? I was tinkering with the idea of having the init script use lsof to pin it down more precisely. Does that sound remotely sane? -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers