RE: [bug fix] Produce a crash dump before main() on Windows
От | Tsunakawa, Takayuki |
---|---|
Тема | RE: [bug fix] Produce a crash dump before main() on Windows |
Дата | |
Msg-id | 0A3221C70F24FB45833433255569204D1FA55872@G01JPEXMBYT05 обсуждение исходный текст |
Ответ на | Re: [bug fix] Produce a crash dump before main() on Windows (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: [bug fix] Produce a crash dump before main() on Windows
|
Список | pgsql-hackers |
From: Michael Paquier [mailto:michael@paquier.xyz] > When you use pg_ctl start within the command prompt, then closing the prompt > session also causes Postgres to stop immediately. Would it be a problem? No. But that makes me think more of the startup on command prompt as non-production usage. > Another question I have is that I have seen Postgres fail to start because > of missing dependent libraries, which happened after the postmaster startup > as this was reported in the logs, could it be a problem with this patch? > If the system waits for an operator to close this pop-up window, then it > becomes harder to check automatically such failures and relies on the test > application to timeout, if it is wise enough to do, which is not always > the case.. I guess that is due to some missing files related to the libraries listed in shared_preload_library. If so, no, becausethis patch relates to failure before main(). Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: