Re: [BUG] Re-entering malloc problem when use --enable-nls build postgresql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: 158306855 <anderson2013(at)qq(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: [BUG] Re-entering malloc problem when use --enable-nls build postgresql
Date: 2018-05-08 06:07:08
Message-ID: 2367.1525759628@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-05-08 01:32:33 -0400, Tom Lane wrote:
>> There are not any better alternatives. We can't just set a flag in the
>> signal handler and hope that control will someday reach a place that
>> notices the flag. We could exit without attempting to report anything,
>> but nobody would find that user-friendly. So we try to report, in the
>> full understanding that sometimes it won't work.

> It'd be fairly unproblematic to write an untranslated message out.

To stderr, maybe. Across an SSL-encrypted client connection? You're
dreaming.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 158306855 2018-05-08 06:48:30 Re: [BUG] Re-entering malloc problem when use --enable-nls buildpostgresql
Previous Message PG Bug reporting form 2018-05-08 06:02:16 BUG #15189: Could not connect to server