Re: BUG #15383: Join Filter cost estimation problem in 10.5 - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #15383: Join Filter cost estimation problem in 10.5
Date
Msg-id 20200227192455.GA1788@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #15383: Join Filter cost estimation problem in 10.5  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2019-Nov-30, Tom Lane wrote:

> Or, since I think we're out of the realm of what would be sane to
> back-patch anyway, maybe it's time to take two steps back and try
> to find a real, non-stopgap solution.  As I said upthread, I think
> the core problem here is failure to distinguish quals associated with
> the uniqueness condition from additional "filter" quals that have to
> be checked anyway.  I wonder how hard that is to fix.

So does anyone have a way to move this forward?  David, any input on
this?

Thanks

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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16280: dead tuples (probably) effect plan and query performance
Next
From: Philip Semanchuk
Date:
Subject: Re: BUG #16279: Permissions doc incorrect for pg_buffercache