Re: Bloom index cost model seems to be wrong - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Bloom index cost model seems to be wrong
Date
Msg-id CA+hUKGLxYST2cu28oiS_FRZKg8E4JrOVVHO19rx0AoKWxHXi2Q@mail.gmail.com
Whole thread Raw
In response to Re: Bloom index cost model seems to be wrong  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On Fri, Mar 1, 2019 at 7:11 AM Jeff Janes <jeff.janes@gmail.com> wrote:
> I'm adding it to the commitfest targeting v13.  I'm more interested in feedback on the conceptual issues rather than
stylisticones, as I would probably merge the two functions together before proposing something to actually be
committed.

From the trivialities department, this patch shows up as a CI failure
with -Werror, because there is no declaration for
genericcostestimate2().  I realise that's just a temporary name in a
WIP patch anyway so this isn't useful feedback, but for the benefit of
anyone going through CI failures in bulk looking for things to
complain about: this isn't a real one.

-- 
Thomas Munro
https://enterprisedb.com



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Cached plans and statement generalization
Next
From: Thomas Munro
Date:
Subject: Re: Built-in connection pooler