Steve Atkins wrote: > Would having a higher level process manager be adequate - one > that spawns the postmaster and a list of associated processes > (queue manager, job scheduler, random user daemons that are > used for database application maintenance). It sounds like > something like that would be able to start up and shut down > an entire family of daemons, of which the postmaster is the major > one, gracefully.
Sort of a super-pg_ctl, eh? Hmm, that sounds like it could work ... > It could also be developed almost independently of core code, > at most it might benefit from a way for the postmaster to tell it > when it's started up successfully. Right -- pg_ping pops up again ... I think it'd also want to be signalled when postmaster undergoes a restart cycle, so that it can handle the other daemons appropriately. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
