Re: [BUG] Re-entering malloc problem when use --enable-nls buildpostgresql - Mailing list pgsql-bugs

From Andres Freund
Subject Re: [BUG] Re-entering malloc problem when use --enable-nls buildpostgresql
Date
Msg-id 20180508083631.m4bom7rrfzy3xgt4@alap3.anarazel.de
Whole thread Raw
In response to Re: [BUG] Re-entering malloc problem when use --enable-nls build postgresql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUG] Re-entering malloc problem when use --enable-nls buildpostgresql  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
On 2018-05-08 02:07:08 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.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.

libpq invents an equivalent message when the server closes the
connection anyway, IIRC. So that'd not necessarily be too bad.

Greetings,

Andres Freund


pgsql-bugs by date:

Previous
From: "158306855"
Date:
Subject: Re: [BUG] Re-entering malloc problem when use --enable-nls buildpostgresql
Next
From: SriRaghu Sai Kasyap
Date:
Subject: Invalid precision for money datatype