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 1h16NI-0003RY-AR for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Mar 2019 09:28:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h16NG-00088F-Hw for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Mar 2019 09:28:34 +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 1h16NG-000888-Ar for pgsql-hackers@lists.postgresql.org; Tue, 05 Mar 2019 09:28:34 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h16N8-0007Z7-De for pgsql-hackers@postgresql.org; Tue, 05 Mar 2019 09:28:33 +0000 Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id x259SAI8032474; Tue, 5 Mar 2019 18:28:10 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 26F99639185; Tue, 5 Mar 2019 18:28:10 +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 1AEE263900B; Tue, 5 Mar 2019 18:28:10 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.241.75]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 1442D400662; Tue, 5 Mar 2019 18:28:10 +0900 (JST) Message-ID: <5C7E4127.2030802@lab.ntt.co.jp> Date: Tue, 05 Mar 2019 18:28:07 +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> <10994.1549559088@localhost> <5C5D778F.3080501@lab.ntt.co.jp> <5C6D474F.5010703@lab.ntt.co.jp> <30939.1550848901@localhost> <5C73B7FB.2010309@lab.ntt.co.jp> <7520.1551439018@localhost> In-Reply-To: <7520.1551439018@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Antonin Houska Cc: Tom Lane , Andrew Gierth , pgsql-hackers@postgresql.org X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk (2019/03/01 20:16), Antonin Houska wrote: > Etsuro Fujita wrote: >> Conversely, it appears that add_foreign_ordered_paths() added by the patchset >> would generate such pre-sorted paths *redundantly* when the input_rel is the >> final scan/join relation. Will look into that. > > Currently I have no idea how to check the plan created by FDW at the > UPPERREL_ORDERED stage, except for removing the sort from the > UPPERREL_GROUP_AGG stage as I proposed here: > > https://www.postgresql.org/message-id/11807.1549564431%40localhost I don't understand your words "how to check the plan created by FDW". Could you elaborate on that a bit more? Best regards, Etsuro Fujita