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 1hgz0U-0003Jr-Lw for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Jun 2019 22:06:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hgz0T-0006Ri-E9 for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Jun 2019 22:06:09 +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 1hgz0T-0006Or-1D for pgsql-bugs@lists.postgresql.org; Fri, 28 Jun 2019 22:06:09 +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 1hgz0M-0006HO-EC for pgsql-bugs@lists.postgresql.org; Fri, 28 Jun 2019 22:06:07 +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 x5SM5vci012088; Fri, 28 Jun 2019 18:05:57 -0400 From: Tom Lane To: Alvaro Herrera cc: David Rowley , Marko Tiikkaja , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5 In-reply-to: <20190628212610.GA11635@alvherre.pgsql> References: <20190628212610.GA11635@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Fri, 28 Jun 2019 17:26:10 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12086.1561759557.1@sss.pgh.pa.us> Date: Fri, 28 Jun 2019 18:05:57 -0400 Message-ID: <12087.1561759557@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera 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. regards, tom lane