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 | 0A3221C70F24FB45833433255569204D1F80E4BF@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: pgsql-hackers-owner@postgresql.org > [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Michael Paquier > So you are basically ready to lose any message that could be pushed > here if there is no memory context? That does not sound like a good > trade-off to me. A static buffer does not look like the best idea > either to not truncate message, so couldn't we envisage to just use > malloc? pgwin32_message_to_UTF16() is called in two places in elog.c, > and there is a full control on the error code paths. Thank you for reviewing a rare bug fix on Windows that most people wouldn't be interested in. When CurrentMemoryContext isNULL, the message is logged with ReportEventA(). This is similar to write_console(). 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 по дате отправления: