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 1h1WCk-0002Zf-G9 for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Mar 2019 13:03:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h1WCj-0001g5-7T for pgsql-hackers@arkaria.postgresql.org; Wed, 06 Mar 2019 13:03:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h1WCj-0001fy-0O for pgsql-hackers@lists.postgresql.org; Wed, 06 Mar 2019 13:03:25 +0000 Received: from tama50.ecl.ntt.co.jp ([129.60.39.147]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h1WCc-00056s-1l for pgsql-hackers@postgresql.org; Wed, 06 Mar 2019 13:03:24 +0000 Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id x26D3FEw008478; Wed, 6 Mar 2019 22:03:15 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 74ED1639598; Wed, 6 Mar 2019 22:03:15 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 69441639562; Wed, 6 Mar 2019 22:03:15 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.241.75]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 6340740069C; Wed, 6 Mar 2019 22:03:15 +0900 (JST) Message-ID: <5C7FC516.10100@lab.ntt.co.jp> Date: Wed, 06 Mar 2019 22:03:18 +0900 From: Etsuro Fujita User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 Subject: Re: Problems with plan estimates in postgres_fdw References: <87pnz1aby9.fsf@news-spur.riddles.org.uk> <1175.1533220908@sss.pgh.pa.us> <5BB739CD.6040002@lab.ntt.co.jp> <5BBC4140.50403@lab.ntt.co.jp> <5C17A00E.5000005@lab.ntt.co.jp> <5C232F39.9060509@lab.ntt.co.jp> <5C25C7B5.2010802@lab.ntt.co.jp> <5C518631.5080401@lab.ntt.co.jp> <5C6FB014.9040403@lab.ntt.co.jp> In-Reply-To: <5C6FB014.9040403@lab.ntt.co.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Jeff Janes Cc: Tom Lane , Andrew Gierth , pgsql-hackers X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk (2019/02/22 17:17), Etsuro Fujita wrote: > (2019/02/21 6:19), Jeff Janes wrote: >> With your tweaks, I'm still not seeing the ORDER-less LIMIT get pushed >> down when using use_remote_estimate in a simple test case, either with >> this set of patches, nor in the V4 set. However, without >> use_remote_estimate, the LIMIT is now getting pushed with these patches >> when it does not in HEAD. > > Good catch! I think the root cause of that is: when using > use_remote_estimate, remote estimates obtained through remote EXPLAIN > are rounded off to two decimal places, which I completely overlooked. > Will fix. I think I can post a new version early next week. Done. Please see [1]. Sorry for the delay. Best regards, Etsuro Fujita [1] https://www.postgresql.org/message-id/5C7FC458.4020400%40lab.ntt.co.jp