On Thu, May 12, 2022 at 02:27:26PM +0900, Amit Langote wrote:
> > Yes, this is what I needed to know.  The updated text is:
> >
> >         <!--
> >         Author: Alvaro Herrera <alvhe...@alvh.no-ip.org>
> >         2022-03-20 [ba9a7e392] Enforce foreign key correctly during 
> > cross-partition upd
> >         -->
> >
> >         <listitem>
> >         <para>
> >         Improve foreign key behavior of updates on partitioned tables
> >         that move rows between partitions (Amit Langote)
> >         </para>
> >
> >         <para>
> >         Previously, such updates ran delete actions on the source partition
> >         and insert actions on the target partition.  PostgreSQL will now
> >         run update actions on the partition root.
> >         </para>
> >         </listitem>
> 
> Looks fine to me.  Though I think maybe we should write the last
> sentence as "PostgreSQL will now run update actions on the partition
> root mentioned in the query" to be less ambiguous about which "root",
> because it can also mean the actual root table in the partition tree.
> A user may be updating only a particular subtree by mentioning that
> subtree's root in the query, for example.

Okay, I went with:

        Previously, such updates ran delete actions on the source
        partition and insert actions on the target partition.  PostgreSQL will
        now run update actions on the referenced partition root.

-- 
  Bruce Momjian  <br...@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson



Reply via email to