| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 16:58:12 |
| Message-ID: | 20190826165812.GH7201@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.)
That's a question for Devrim ?
Can you tell which glibc headers were installed when compiling this package?
postgresql11-server-11.5-1PGDG.rhel6.x86_64
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
Maybe it doesn't matter, since, for better or worse, is not a "late model" cc.
https://www.gnu.org/software/gcc/gcc-4.4/
GCC 4.4.7
March 13, 2012 (changes)
This release series is no longer maintained.
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-08-26 17:01:52 | Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev) |
| Previous Message | Tom Lane | 2019-08-26 16:45:24 | Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev) |