Re: Hash Joins vs. Bloom Filters / take 2

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hash Joins vs. Bloom Filters / take 2
Date: 2018-03-01 23:52:56
Message-ID: 82765cf1-b326-31b5-aa1a-7f3c0b150041@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/02/2018 12:31 AM, Andres Freund wrote:
>
>
> On March 1, 2018 3:22:44 PM PST, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
>>
>>
>> On 03/01/2018 11:01 PM, Andres Freund wrote:
>>> Hi,
>>>
>>> On 2018-02-20 22:23:54 +0100, Tomas Vondra wrote:
>>>> So I've decided to revive the old patch, rebase it to current
>> master,
>>>> and see if we can resolve the issues that killed it in 2016.
>>>
>>> There seems to be some good discussion in the thread. But the patch
>>> arrived just before the last commitfest and certainly isn't a trivial
>>> cleanup patch. Therefore I think it should be moved to the next CF?
>>>
>>
>> It isn't a massive invasive patch either, though, so I object to moving
>> it to 2018-09 right away.
>
> Why do we have rules around not submitting large stuff to the last
> cf, if we just not follow through? We're neck deep in patches that
> are older. And you've already gotten a fair bit of feedback..
>

It was not my intention to break (or even bend) the CF rules, of course.
I haven't considered the patch to be "large stuff", while you do. I see
Peter Geoghegan agrees with your conclusion on another thread, so go
ahead and move it to 2018-09.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2018-03-01 23:58:57 Re: [HACKERS] Bug in to_timestamp().
Previous Message Tom Lane 2018-03-01 23:49:20 Re: [patch] BUG #15005: ANALYZE can make pg_class.reltuples inaccurate.