From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Derek Hans <derek(dot)hans(at)gmail(dot)com> |
Subject: | Re: Update does not move row across foreign partitions in v11 |
Date: | 2019-03-06 06:10:38 |
Message-ID: | 5C7F645E.2080805@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
(2019/03/06 13:18), Amit Langote wrote:
> The main problem here is indeed that the limitation is not listed under
> the partitioning limitations in ddl.sgml, where it's easier to notice than
> in the UPDATE's page.
Agreed.
> I've updated my patch to remove the release-11.sgml
> changes.
Thanks for the updated patch!
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -3376,6 +3376,13 @@ ALTER TABLE measurement ATTACH PARTITION
measurement_y2008m02
</para>
</listitem>
+ <listitem>
+ <para>
+ <command>UPDATE</command> row movement is not supported in the cases
+ where the old row is contained in a foreign table partition.
+ </para>
+ </listitem>
ISTM that it's also a limitation that rows can be moved from a local
partition to a foreign partition *if the FDW support tuple routing*, so
I would vote for mentioning that as well here.
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2019-03-06 06:16:25 | Re: Update does not move row across foreign partitions in v11 |
Previous Message | Sameer Kumar | 2019-03-06 05:56:56 | Re: Non-pausing table scan on 9.6 replica? |
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2019-03-06 06:16:25 | Re: Update does not move row across foreign partitions in v11 |
Previous Message | Masahiko Sawada | 2019-03-06 05:58:20 | Re: Tab completion for SKIP_LOCKED option |