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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: pg11.5: ExecHashJoinNewBatch: glibc detected...double free or corruption (!prev)
Date: 2019-08-25 03:15:34
Message-ID: CAH2-WznuM_UvJONuzYjrd7_54UcehY47K_ew0cYBWrHnPNZmVw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 24, 2019 at 7:25 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> Merlin: what OS are you running on and what postgres package, or was it
> compiled locally ?

I was reminded of this issue from last year, which also appeared to
involve BufFileClose() and a double-free:

https://postgr.es/m/87y3hmee19.fsf@news-spur.riddles.org.uk

That was a BufFile that was under the control of a tuplestore, so it
was similar to but different from your case. I suspect it's related.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message PG Bug reporting form 2019-08-25 06:11:05 BUG #15977: Inconsistent behavior in chained transactions
Previous Message Thomas Munro 2019-08-25 02:56:55 Re: LLVM breakage on seawasp