Horton

Re: First draft of the PG 15 release notes

Amit Langote <amitlangote09@gmail.com>

View thread View on postgr.es
From: Amit Langote <amitlangote09@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2022-05-12T05:27:26Z
Lists: pgsql-hackers 
On Wed, May 11, 2022 at 11:41 PM Bruce Momjian <bruce@momjian.us> wrote:
> On Wed, May 11, 2022 at 04:02:31PM +0900, Amit Langote wrote:
> > On Wed, May 11, 2022 at 12:44 AM Bruce Momjian <bruce@momjian.us> wrote:
> > > I have completed the first draft of the PG 15 release notes
> > The commit is intended to only change the behavior of RI triggers,
> > while leaving user-defined triggers firing as before.  I think it
> > might be a good idea to be specific by wording this, maybe as follows?
> >
> > Improve the firing of foreign key triggers during cross-partition
> > updates of partitioned tables (Amit Langote)
> >
> > Previously, such updates fired delete triggers on the source partition
> > and insert triggers on the target partition, whereas PostgreSQL will
> > now fire update triggers on the partitioned table mentioned in the
> > query, which makes the behavior of foreign keys pointing into that
> > table more consistent.  Note that other user-defined triggers are
> > fired as they were before.
>
> Yes, this is what I needed to know.  The updated text is:
>
>         <!--
>         Author: Alvaro Herrera <alvherre@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.


--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com

Commits

  1. Doc: last minute adjustment to the release notes

  2. Doc: more tweaking of v15 release notes.

  3. Doc: further adjust notes about pg_upgrade_output.d.

  4. Doc: add list of major features to the v15 release notes.

  5. relnotes: update item about public schema permission change

  6. relnotes: update ordered partition scan item

  7. relnotes: add Heikki to UTF8 item

  8. relnotes: improve UTF8 text item in relation to ASCII

  9. relnotes: add null logical replication item

  10. relnotes: adjust several logical replication items and FK text

  11. relnotes: mention non-exclusive backup mode was deprecated

  12. relnotes: add author to in-memory sorts item

  13. relnotes: update for non-exclusive backup mode removal

  14. relnote: improve sorting entries

  15. relnotes: adjustments from Álvaro Herrera

  16. relnotes: update foreign key partition and add sort items

  17. relnotes: more adjustments

  18. relnotes: logical replication permissions checked by subscrib.

  19. relnotes: adjustments

  20. relnotes: remove sequence replication and update 'postgres -C'

  21. relnote: extensive updates

  22. relnotes: "training" -> "trailing"

  23. Standardize references to Zstandard as <productname>

  24. pgstat: Update docs to match the shared memory stats reality.

  25. Raise a WARNING for missing publications.

  26. Skip empty transactions for logical replication.

  27. Optionally disable subscriptions on error.

  28. Allow root-owned SSL private keys in libpq, not only the backend.

  29. Use COPY FREEZE in pgbench for faster benchmark table population.