Re: Tuple-routing for certain partitioned tables not working as expected
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-08-25T13:26:31Z
Lists: pgsql-hackers
On Wed, Aug 23, 2017 at 4:55 AM, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote: > Agreed, but I'd vote for fixing this in v10 as proposed; I agree that just > ripping the CheckValidResultRel checks out entirely is not a good idea, but > that seems OK to me at least as a fix just for v10. I'm still not on-board with having this be the one case where we don't do CheckValidResultRel. If we want to still call it but pass down some additional information that can selectively skip certain checks, I could probably live with that. At some point we've got to stop developing v10 and just let it be what it is. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Even if some partitions are foreign, allow tuple routing.
- 08cb36417aa2 10.0 landed
- 9d71323daca4 11.0 landed