Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
Date
Msg-id 5A7BE8E6.200@lab.ntt.co.jp
Whole thread Raw
In response to Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
(2018/02/08 10:40), Robert Haas wrote:
> On Wed, Feb 7, 2018 at 6:01 PM, Tom Lane<tgl@sss.pgh.pa.us>  wrote:
>> 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?
>
> Uggh, I missed the fact that they were doing that.  It's probably
> actually useful test coverage, but it's not surprising that it isn't
> stable.

That was my purpose, but I agree with the instability.  Thanks again, 
Robert!

Best regards,
Etsuro Fujita


pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
Next
From: Michael Paquier
Date:
Subject: Disabling src/test/[ssl|ldap] when not building with SSL/LDAP support