Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBjMd-0000RM-Vj for pgsql-bugs@arkaria.postgresql.org; Wed, 03 Apr 2019 17:07:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hBjMa-0003Tg-DY for pgsql-bugs@arkaria.postgresql.org; Wed, 03 Apr 2019 17:07:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBjMa-0003TZ-2Z for pgsql-bugs@lists.postgresql.org; Wed, 03 Apr 2019 17:07:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBjMX-0006Vb-R1 for pgsql-bugs@lists.postgresql.org; Wed, 03 Apr 2019 17:07:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x33H7fC7026762; Wed, 3 Apr 2019 13:07:41 -0400 From: Tom Lane To: David Rowley cc: Marko Tiikkaja , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5 In-reply-to: <22099.1552086256@sss.pgh.pa.us> References: <153683552113.22350.18441286362867559841@wrigleys.postgresql.org> <12829.1536861465@sss.pgh.pa.us> <25545.1537388318@sss.pgh.pa.us> <22099.1552086256@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 08 Mar 2019 18:04:16 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26760.1554311261.1@sss.pgh.pa.us> Date: Wed, 03 Apr 2019 13:07:41 -0400 Message-ID: <26761.1554311261@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > I think we'd have to redesign those cost calculations completely to > get ideal answers, and I don't especially want to do that right now. > So I'm wondering about the attached as a stopgap. It seems like it's > an improvement over what we have, even if not a full fix. > Thoughts? Ping? If nobody has any further ideas here, I'm going to clean up the regression test issue and push this. regards, tom lane