Re: [HACKERS] [bug fix] postgres.exe crashes with access violationon Windows while starting up
От | Tsunakawa, Takayuki |
---|---|
Тема | Re: [HACKERS] [bug fix] postgres.exe crashes with access violationon Windows while starting up |
Дата | |
Msg-id | 0A3221C70F24FB45833433255569204D1F80EBBD@G01JPEXMBYT05 обсуждение исходный текст |
Ответ на | Re: [HACKERS] [bug fix] postgres.exe crashes with access violation onWindows while starting up (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] [bug fix] postgres.exe crashes with access violation onWindows while starting up
|
Список | pgsql-hackers |
From: Michael Paquier [mailto:michael.paquier@gmail.com] > On Tue, Oct 31, 2017 at 6:59 AM, Tsunakawa, Takayuki > <tsunakawa.takay@jp.fujitsu.com> wrote: > > When CurrentMemoryContext is NULL, the message is logged with > ReportEventA(). This is similar to write_console(). > > My point is that as Postgres is running as a service, isn't it wrong to > write a message to stderr as a fallback if the memory context is not set? > You would lose a message. It seems to me that for an operation that can > happen at a low-level like the postmaster startup, we should really use > a low-level operation as well. I'm sorry I may not have been clear. With this patch, write_eventlog() outputs the message to event log with ReportEventA()when CurrentMemoryContext is NULL. It doesn't write to stderr. So the message won't be lost. Regards Takayuki Tsunakawa -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: