Re: Explanation for bug #13908: hash joins are badly broken - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Explanation for bug #13908: hash joins are badly broken
Date
Msg-id CA+TgmoZgKkvvmTjPbqRyCsnKM6KK8c_0P=NdQjDTTMDs2ykpew@mail.gmail.com
Whole thread Raw
In response to Re: Explanation for bug #13908: hash joins are badly broken  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Explanation for bug #13908: hash joins are badly broken
List pgsql-hackers
On Sat, Feb 6, 2016 at 12:47 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So I'm of the opinion that a great deal more work is needed here.
> But it's not something we're going to be able to get done for 9.5.1,
> or realistically 9.5.anything.  Whereas adding additional klugery to
> ExecHashRemoveNextSkewBucket probably is doable over the weekend.

Tom, are you taking care of this, or should I be getting involved here?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Way to check whether a particular block is on the shared_buffer?
Next
From: Tom Lane
Date:
Subject: Re: Explanation for bug #13908: hash joins are badly broken