From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: First draft of the PG 15 release notes |
Date: | 2022-05-12 13:52:03 |
Message-ID: | Yn0RA8IM8fR4PT2G@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 <alvherre(at)alvh(dot)no-ip(dot)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 <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2022-05-12 13:53:45 | Re: First draft of the PG 15 release notes |
Previous Message | Andrew Dunstan | 2022-05-12 13:51:47 | Re: Reproducible coliisions in jsonb_hash |