Re: Oddity in tuple routing for foreign partitions
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: fujita.etsuro@lab.ntt.co.jp
Cc: Langote_Amit_f8@lab.ntt.co.jp, robertmhaas@gmail.com,
alvherre@alvh.no-ip.org, pgsql-hackers@postgresql.org
Date: 2018-04-27T01:01:11Z
Lists: pgsql-hackers
At Thu, 26 Apr 2018 21:16:38 +0900, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote in <5AE1C326.6040201@lab.ntt.co.jp> > (2018/04/26 20:06), Kyotaro HORIGUCHI wrote: > > Please rewrite it to use not array reference, but pointer > > reference if one mtstate logically holds just one resultRelInfo. > > Maybe I don't understand your words correctky, but in that UPDATE > case, I think that mtstate can have multiple ResultRelInfo. Ah, mtstate has the same number of resultRelInfo with subplans and it is *written* in the comment just above:( And it is exactly for the UPDATE case. Sorry for the silly comment. > >>>> Anyway, I think that > >>>> the former is more like an improvement rather than a fix, so it would > >>>> be > >>>> better to leave that for another patch for PG12? > >>> > >>> I agree, so I'm dropping the patch for 1. > >> > >> OK, let's focus on #2! > >> > >>> See attached an updated version with changes as described above. > >> > >> Looks good to me. Thanks for the updated version! > > > > Agreed on all points above. > > Thanks for reviewing! I'm happy if it helps you. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Remove now-unnecessary cast.
- a365f52d5831 11.0 landed
-
Fix interaction of foreign tuple routing with remote triggers.
- 37a3058bc7c8 11.0 landed