| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Devrim Gündüz <devrim(at)gunduz(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev) |
| Date: | 2019-08-26 17:01:52 |
| Message-ID: | 3277.1566838912@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> On Mon, Aug 26, 2019 at 12:45:24PM -0400, Tom Lane wrote:
>> However ... there is some pretty interesting info at
>> https://bugzilla.redhat.com/show_bug.cgi?id=1338673
>> suggesting that compiling with a late-model gcc against older RHEL6
>> headers could result in bad code. I wonder whether the reporters'
>> servers were built using such a configuration. (Although the linkage,
>> if any, to this report still wouldn't be very clear.)
> I can tell it was compiled using
> version | PostgreSQL 11.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-23), 64-bit
Ah, that appears to be the default compiler for RHEL6, so that theory
is out the window. It's still interesting that we're only seeing this
reported from RHEL6 ... maybe there's something specific to the code
that this gcc version generates?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2019-08-26 17:02:24 | Re: Procedure support improvements |
| Previous Message | Justin Pryzby | 2019-08-26 16:58:12 | Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev) |