Fujita-san,
On 2019/03/06 13:04, Etsuro Fujita wrote:
> (2019/03/06 11:34), Amit Langote wrote:
>> 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.)
>
> I'm not sure it's a good idea to make changes to the release notes like
> that, because 1) that would make the release notes verbose, and 2) it
> might end up doing the same thing to items that have some limitations in
> the existing/future release notes (eg, FOR EACH ROW triggers on
> partitioned tables added to V11 has the limitation listed on the
> limitation section, so the same link would be needed.), for consistency.
OK, sure. It just seemed to me that the original complainer found it
quite a bit surprising that such a limitation is not mentioned in the
release notes, but maybe that's fine. It seems we don't normally list
feature limitations in the release notes, which as you rightly say, would
make them verbose.
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. I've updated my patch to remove the release-11.sgml
changes.
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
