Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free orcorruption (!prev)
От | Justin Pryzby |
---|---|
Тема | Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free orcorruption (!prev) |
Дата | |
Msg-id | 20190826165812.GH7201@telsasoft.com обсуждение исходный текст |
Ответ на | Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev)
|
Список | 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
В списке pgsql-hackers по дате отправления: