pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Marko Tiikkaja <marko@joh.to>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5
Date: Thu, 27 Feb 2020 16:24:55 -0300
Message-ID: <20200227192455.GA1788@alvherre.pgsql> (raw)
In-Reply-To: <30791.1575135158@sss.pgh.pa.us>

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





view thread (28+ messages)  latest in thread

Message-ID: <20200227192455.GA1788@alvherre.pgsql>
Permalink:  ../20200227192455.GA1788@alvherre.pgsql/
Also on:    postgresql.org/message-id/20200227192455.GA1788@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, michael@paquier.xyz, marko@joh.to, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5
  In-Reply-To: <20200227192455.GA1788@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox