Re: pg_ctl / SCM interaction
От | Dave Page |
---|---|
Тема | Re: pg_ctl / SCM interaction |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B889FE91@mail.vale-housing.co.uk обсуждение исходный текст |
Ответ на | pg_ctl / SCM interaction (Andrew Dunstan <andrew@dunslane.net>) |
Список | pgsql-hackers-win32 |
> -----Original Message----- > From: Andrew Dunstan [mailto:andrew@dunslane.net] > Sent: 24 May 2004 15:30 > To: pgsql-hackers-win32 > Subject: [pgsql-hackers-win32] pg_ctl / SCM interaction > > Ok, help me out a bit here. We start postmaster using the SCM. As I > understand it, that gives us 2 processes, one (process X) > that interacts > with the SCM and one that it creates (process Y) which is the "real" > postmaster, and the one that writes its id in postmaster.pid. > > Now we use pg_ctl restart. It sends, say, TERM to process Y. > I presume > process X notices that Process Y has gone away, and registers > that the > service is stopped. Then pg_ctl starts another postmaster. How does > process X know that the new postmaster is its replacement process for > process X? It doesn't. I was chatting to Magnus earlier suggesting an integrated solution rather than a wrapper. The more I think about it the more I think this is the only way to be certain that the service code is singing from the same hymnsheet as the postmaster. /D
В списке pgsql-hackers-win32 по дате отправления: