Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
От | Tom Lane |
---|---|
Тема | Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND |
Дата | |
Msg-id | 26332.1557863524@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #15804: Assertion failure when using logging_collector withEXEC_BACKEND (Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com>) |
Ответы |
Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND
Re: BUG #15804: Assertion failure when using logging_collector withEXEC_BACKEND |
Список | pgsql-bugs |
Yuli Khodorkovskiy <yuli.khodorkovskiy@crunchydata.com> writes: > Attached is a patch that fixes the issue in the bug report. I do not think this is a very good way to fix it (even assuming that it works, which I'm unsure of --- in particular, doing this would alter the order of changes to postmaster.pid, possibly breaking pg_ctl or other tools that look at that file). The whole point of commit 57431a911 was to switch to log-collector logging before we've done anything very interesting, and that would surely include shmem setup. I'm a bit surprised actually that Peter didn't move the SysLogger_Start call even further up; in principle it ought to be safe to do it as soon as we have the data directory lock file. It might be better to give up the assertion in PGSharedMemoryNoReAttach, and just make it work more like PGSharedMemoryDetach, ie "detach if UsedShmemSegAddr is set, else do nothing". I don't remember for sure, but if we do that, there might be no functional difference anymore between those two functions, in which case we might as well merge 'em. regards, tom lane
В списке pgsql-bugs по дате отправления: