Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev)

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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free orcorruption (!prev)
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Proposal: Better generation of values in GENERATED columns.