Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
From: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>,
Rushabh Lathia <rushabh.lathia@gmail.com>,
Michael Paquier <michael.paquier@gmail.com>,
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Date: 2018-02-08T05:53:38Z
Lists: pgsql-hackers
(2018/02/08 5:39), Robert Haas wrote: > On Thu, Jan 11, 2018 at 2:58 AM, Etsuro Fujita > <fujita.etsuro@lab.ntt.co.jp> wrote: >> (2017/12/27 20:55), Etsuro Fujita wrote: >>> Attached is an updated version of the patch. >> >> I revised code/comments a little bit. PFA new version. > > 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. Thanks for committing, Robert! Thanks for reviewing, Rushabh and Ashutosh! Best regards, Etsuro Fujita
Commits
-
Temporarily instrument postgres_fdw test to look for statistics changes.
- c2c537c56dc3 11.0 landed
-
postgres_fdw: Fourth attempt to stabilize regression tests.
- 1733460f0205 11.0 landed
-
postgres_fdw: Third attempt to stabilize regression tests.
- 4fa396464e5f 11.0 landed
-
postgres_fdw: Attmempt to stabilize regression tests.
- 958e20e42d6c 11.0 landed
-
postgres_fdw: Push down UPDATE/DELETE joins to remote servers.
- 1bc0100d270e 11.0 landed