Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fviii-0001lE-Mi for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Aug 2018 12:40:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fviih-0001KP-6e for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Aug 2018 12:40:11 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1fviig-0001K9-Uo for pgsql-hackers@lists.postgresql.org; Fri, 31 Aug 2018 12:40:10 +0000 Received: from tama50.ecl.ntt.co.jp ([129.60.39.147]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fviie-0006SI-3l; Fri, 31 Aug 2018 12:40:10 +0000 Received: from vc1.ecl.ntt.co.jp (vc1.ecl.ntt.co.jp [129.60.86.153]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id w7VCdtvY001619; Fri, 31 Aug 2018 21:39:55 +0900 Received: from vc1.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id F1C5FEA8670; Fri, 31 Aug 2018 21:39:54 +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 DD368EA866A; Fri, 31 Aug 2018 21:39:54 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.241.75]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id D58D1400B6B; Fri, 31 Aug 2018 21:39:54 +0900 (JST) Message-ID: <5B893738.2020007@lab.ntt.co.jp> Date: Fri, 31 Aug 2018 21:40:24 +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: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled. References: <5B717A7B.4010308@lab.ntt.co.jp> <5B739D46.6040000@lab.ntt.co.jp> <3585ad1d-d610-ad53-80e2-296050cd73f3@lab.ntt.co.jp> <5B74101B.9080402@lab.ntt.co.jp> <5B74E8C0.5040300@lab.ntt.co.jp> <5B7D4449.9090704@lab.ntt.co.jp> <5B7EB001.4010907@lab.ntt.co.jp> <20180824024710.GH30782@paquier.xyz> <5B7FFC58.7060208@lab.ntt.co.jp> <5B8669F3.2070905@lab.ntt.co.jp> <5B87D414.5030702@lab.ntt.co.jp> <5B892C65.9050008@lab.ntt.co.jp> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: "Jonathan S. Katz" Cc: Michael Paquier , Robert Haas , Amit Langote , Tom Lane , Andres Freund , Ashutosh Bapat , Rajkumar Raghuwanshi , pgsql-hackers X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk (2018/08/31 21:30), Jonathan S. Katz wrote: > On 8/31/18 7:54 AM, Etsuro Fujita wrote: >> (2018/08/30 20:25), Etsuro Fujita wrote: >>> (2018/08/29 18:40), Etsuro Fujita wrote: >>>> (2018/08/29 0:21), Jonathan S. Katz wrote: >>>>>> On Aug 24, 2018, at 8:38 AM, Etsuro >>>>>> Fujita wrote: >>>>>> (2018/08/24 11:47), Michael Paquier wrote: >>>>>>> On Thu, Aug 23, 2018 at 10:00:49PM +0900, Etsuro Fujita wrote: >>>>>>>> I tried this today, but doing git behind the corporate firewall >>>>>>>> doesn't >>>>>>>> work. I don't know the clear cause of that, so I'll investigate >>>>>>>> that >>>>>>>> tomorrow. >>>>>>> >>>>>>> You may be able to tweak that by using https as origin point or >>>>>>> proper >>>>>>> git proxy settings? >>>>>> >>>>>> Yeah, my proxy settings were not correct. With the help of my >>>>>> colleagues Horiguchi-san and Yamada-san, I corrected them but still >>>>>> can't clone the master repository. Running git with GIT_CURL_VERBOSE >>>>>> shows that there is another issue in my terminal environment, so I'm >>>>>> trying to resolve that. >>>>> >>>>> Are there any updates on getting this patch committed? >>>> >>>> That investigation has shown that the cause is my company firewall, not >>>> my terminal environment; that firewall has to be configured to allow me >>>> to access to that repository. So, I'm asking my company about that. >>> >>> I got the approval from my boss today, so I think that I can have that >>> access soon. >> >> I fixed typos in the commit message, which Alvaro pointed out >> off-list, and revised the message a little bit. Also, I reread the >> patch and noticed that the latest version includes now-unnecessary >> regression test cases; those were added to the previous version >> (refuse-pwj-when-wrvs-involved-2.patch in [1]) to check that >> apply_scanjoin_target_to_paths() and create_ordinary_grouping_paths() >> work for cases where whole-row Vars are involved, because I modified >> those functions, but the latest version doesn't touch those functions >> anymore, so those test cases seems unnecessary. So I removed those >> (no other changes), and committed the patch. > > Thank you for taking care of that and for committing the patch. I have > now closed this issues on the open items list. Thanks! Best regards, Etsuro Fujita