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 1ejYj3-0002dn-RL for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Feb 2018 23:02:01 +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 1ejYj2-0003Gr-Vq for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Feb 2018 23:02:00 +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.84_2) (envelope-from ) id 1ejYj2-0003Gh-Ov for pgsql-hackers@lists.postgresql.org; Wed, 07 Feb 2018 23:02:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ejYiz-0008FW-U8 for pgsql-hackers@postgresql.org; Wed, 07 Feb 2018 23:02:00 +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 w17N1rxQ006167; Wed, 7 Feb 2018 18:01:53 -0500 From: Tom Lane To: Robert Haas cc: Etsuro Fujita , Pg Hackers , Rushabh Lathia , Michael Paquier , Ashutosh Bapat Subject: Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly In-reply-to: References: <5A438A45.2000909@lab.ntt.co.jp> <5A57193A.2080003@lab.ntt.co.jp> Comments: In-reply-to Robert Haas message dated "Wed, 07 Feb 2018 15:39:33 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6165.1518044513.1@sss.pgh.pa.us> Date: Wed, 07 Feb 2018 18:01:53 -0500 Message-ID: <6166.1518044513@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > I spent a while reading through this today. I see a few decisions > here or there that are debatable, in the sense that somebody else > might have chosen to do it differently, but I don't see anything that > actually looks wrong. So, committed. The buildfarm's opinion of it is lower than yours. Just eyeballing the failures, I'd say there was some naivete about the reproducibility of tuple CTIDs across different platforms. Is there a good reason these test cases need to print CTID? regards, tom lane