Re: Update does not move row across foreign partitions in v11
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>, David Rowley <david.rowley@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Alvaro Herrera <alvherre@2ndquadrant.com>, Derek Hans <derek.hans@gmail.com>
Date: 2019-03-07T13:54:17Z
Lists: pgsql-hackers, pgsql-general
On Thu, Mar 7, 2019 at 7:35 AM Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote: > Thanks for the patch! > > The patch looks good to me, but one thing I'm wondering is: as suggested > by David, it would be better to rephrase this mention in the UPDATE > reference page, in a single commit: > > "Currently, rows cannot be moved from a partition that is a foreign > table to some other partition, but they can be moved into a foreign > table if the foreign data wrapper supports it." > > I don't think it needs to be completely rephrased; it's enough for me to > rewrite it to something like this: > > "Currently, rows cannot be moved from a foreign-table partition to some > other partition, but they can be moved into a foreign-table partition if > the foreign data wrapper supports tuple routing." I prefer David's wording. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Fix documentation on partitioning vs. foreign tables
- fc84c05acd15 12.0 landed
- cadead6c3c8e 10.8 landed
- b16f8a290582 11.3 landed