On 2019/03/06 11:29, David Rowley wrote:
> On Wed, 6 Mar 2019 at 15:26, Amit Langote <[email protected]>
> wrote:
>>
>>> I've tried to put all this right again in the attached. However, I was
>>> a bit unsure of what "but they can be moved into a foreign table if
>>> the foreign data wrapper supports it." is referring to. Copying Robert
>>> and Etsuro as this was all added in 3d956d9562aa. Hopefully, they can
>>> confirm what is meant by this.
>>
>> Did you miss my reply on that thread?
>>
>> https://www.postgresql.org/message-id/CA%2BHiwqF3gma5HfCJb4_cOk0_%2BLEpVc57EHdBfz_EKt%2BNu0hNYg%40mail.gmail.com
>
> Yes. I wasn't aware that there were two threads for this.
Ah, indeed. In the documentation fix patch I'd posted, I also made
changes to release-11.sgml to link to the limitations section. (I'm
attaching it here for your reference.)
Thanks,
Amit
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 7bed4f56f0..3b20e73a61 100644
--- 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>
+
<listitem>
<para>
<literal>BEFORE ROW</literal> triggers, if necessary, must be defined
diff --git a/doc/src/sgml/release-11.sgml b/doc/src/sgml/release-11.sgml
index 14e2726f0c..d6fc5a3e31 100644
--- a/doc/src/sgml/release-11.sgml
+++ b/doc/src/sgml/release-11.sgml
@@ -2578,6 +2578,13 @@ Branch: REL9_3_STABLE [84261eb10] 2018-10-19 17:02:26
-0400
column now cause affected rows to be moved to the appropriate
partitions (Amit Khandekar)
</para>
+
+ <para>
+ However, not all cases where such row movment would be necessary
+ are handled currently; see
+ <link linkend="ddl-partitioning-declarative-limitations">declarative
+ partitioning limitations</link> for more information.
+ </para>
</listitem>
<listitem>
