Re: Postgres service stops when I kill client backend on Windows
| От | Andres Freund |
|---|---|
| Тема | Re: Postgres service stops when I kill client backend on Windows |
| Дата | |
| Msg-id | 20151012102537.GR30738@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: Postgres service stops when I kill client backend on Windows (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
Re: Postgres service stops when I kill client backend on Windows
|
| Список | pgsql-hackers |
On 2015-10-12 11:25:35 +0530, Amit Kapila wrote: > /* > + * Close the shared memory handle as the syslogger doesn't need to > + * attach to it. For EXEC_BACKEND case, the shared memory handle > + * is inherited by all postmaster child processes irrespective of > + * whether they need it or not. > + */ > +#ifdef EXEC_BACKEND > + if (!CloseHandle(UsedShmemSegID)) > + elog(LOG, "could not close handle to shared memory: error code %lu", GetLastError()); > +#endif > + It feels wrong to do this in syslogger.c - I mean it's not the only process that's not attached to shared memory. Sure, the others get killed, but nonetheless... Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: