From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 08:36:31 |
Message-ID: | 20180508083631.m4bom7rrfzy3xgt4@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2018-05-08 02:07:08 -0400, Tom Lane wrote:
> 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.
libpq invents an equivalent message when the server closes the
connection anyway, IIRC. So that'd not necessarily be too bad.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | SriRaghu Sai Kasyap | 2018-05-08 09:22:52 | Invalid precision for money datatype |
Previous Message | 158306855 | 2018-05-08 06:48:30 | Re: [BUG] Re-entering malloc problem when use --enable-nls buildpostgresql |