Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ejxnj-0004ta-4I for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Feb 2018 01:48:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ejxnh-0002u7-9K for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Feb 2018 01:48:29 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ejxng-0002tw-VQ for pgsql-hackers@lists.postgresql.org; Fri, 09 Feb 2018 01:48:29 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ejxnW-0006wU-R1 for pgsql-hackers@postgresql.org; Fri, 09 Feb 2018 01:48:25 +0000 Received: from vc1.ecl.ntt.co.jp (vc1.ecl.ntt.co.jp [129.60.86.153]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id w191mD9c018439; Fri, 9 Feb 2018 10:48:13 +0900 Received: from vc1.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 20BCEEA7843; Fri, 9 Feb 2018 10:48:13 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 15B43EA7577; Fri, 9 Feb 2018 10:48:13 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.241.75]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 0E767400D40; Fri, 9 Feb 2018 10:48:13 +0900 (JST) Message-ID: <5A7CFDDA.8050906@lab.ntt.co.jp> Date: Fri, 09 Feb 2018 10:48:10 +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: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly References: <5A438A45.2000909@lab.ntt.co.jp> <5A57193A.2080003@lab.ntt.co.jp> <6166.1518044513@sss.pgh.pa.us> <5A7BE8E6.200@lab.ntt.co.jp> <28606.1518105934@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Robert Haas Cc: Tom Lane , Pg Hackers , Rushabh Lathia , Michael Paquier , Ashutosh Bapat X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk (2018/02/09 4:32), Robert Haas wrote: > On Thu, Feb 8, 2018 at 11:05 AM, Tom Lane wrote: >> According to >> >> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2018-02-08%2001%3A45%3A01 >> >> there's still an intermittent issue. I ran "make installcheck" in >> contrib/postgres_fdw in a loop, and got a similar failure on the >> 47th try --- my result duplicates the second plan change shown by >> rhinoceros, but not the first one. I speculate that the plan change >> is a result of autovacuum kicking in partway through the run. Will look into this. > Hmm. Maybe inserting an ANALYZE command in the right place would fix it? VACUUM to the right tables in the right place might better fix it? Another idea would be to modify test cases added by that commit so that they don't modify the existing tables to not break the existing test cases? Best regards, Etsuro Fujita