From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: David Rowley <david.rowley@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
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, 5 Sep 2019 19:20:14 -0400
Message-ID: <20190905232014.GA32014@alvherre.pgsql> (raw)
In-Reply-To: <CAKJS1f94GPHjbnGg1_xzqfzzKDRc2O6Bq8ge64xCg8UbP09ZqA@mail.gmail.com>
On 2019-Jul-01, David Rowley wrote:
> One thing we could look at would be to charge an additional
> cpu_tuple_cost per outer row for all joins except semi, anti and
> unique joins. This would account for the additional lookup for
> another matching row which won't be found and cause the planner to
> slightly favour keeping the unique rel on the inner side of the join,
> when everything else is equal.
So does this proposal fix the problem that David was describing earlier?
If it does, Tom, would you like to get this finalized and pushed?
I've bcc'ed someone who might be interested in chiming in and/or helping
out. Please look here:
https://postgr.es/m/153683552113.22350.18441286362867559841@wrigleys.postgresql.org
Thanks,
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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, david.rowley@2ndquadrant.com, tgl@sss.pgh.pa.us, marko@joh.to, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5
In-Reply-To: <20190905232014.GA32014@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