Re: BUG #15383: Join Filter cost estimation problem in 10.5

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5
Date: 2019-06-28 22:10:49
Message-ID: 20190628221049.GA12500@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 2019-Jun-28, Tom Lane wrote:

> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > On 2019-Apr-03, Tom Lane wrote:
> >> Ping? If nobody has any further ideas here, I'm going to clean up
> >> the regression test issue and push this.
>
> > Is this still live? If so, is it something for pg12?
>
> It's still live --- Rowley seemed not happy with my proposal so
> I didn't push it. I'm not sure that it's must-fix-for-v12;
> the problem is older than that.

Hmm, but we cannot backpatch because of plan stability, right? So it's
a commitfest item for pg13?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Paul Ramsey 2019-06-28 22:15:16 Re: Re: Querying foreign table with SP-GiST index results in “ERROR: cache lookup failed for type 0”
Previous Message Tom Lane 2019-06-28 22:05:57 Re: BUG #15383: Join Filter cost estimation problem in 10.5

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2019-06-28 22:23:13 Re: Avoid full GIN index scan when possible
Previous Message Tom Lane 2019-06-28 22:05:57 Re: BUG #15383: Join Filter cost estimation problem in 10.5