Re: Draft back-branch release notes are up - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Draft back-branch release notes are up
Date
Msg-id 20210507192334.GA9670@alvherre.pgsql
Whole thread Raw
In response to Draft back-branch release notes are up  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Draft back-branch release notes are up
List pgsql-hackers
On 2021-May-07, Tom Lane wrote:

> See
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7f4bab7f4a0e42ee9fa14707f726017b7869386b

I suppose you're aware of this, so I just want to get it on record that
this entry

+<!--
+Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
+Branch: master [25936fd46] 2021-02-27 18:09:15 -0300
+Branch: REL_13_STABLE [2688852a4] 2021-02-27 18:09:15 -0300
+Branch: REL_12_STABLE [262eb990c] 2021-02-27 18:09:15 -0300
+Branch: REL_11_STABLE [d1c6edd31] 2021-02-27 18:09:15 -0300
+-->
+     <para>
+      Fix use-after-free bug in saving tuples for <literal>AFTER</literal>
+      triggers (Amit Langote)
+     </para>

only goes back to 12; the commit to 11 was just to add the test case.
This is obvious if you look at the commit, but if you just look at the
release note entry, that detail might be missed.

The notes look good.

Thanks,

-- 
Álvaro Herrera       Valdivia, Chile
"No renuncies a nada. No te aferres a nada."



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: plan with result cache is very slow when work_mem is not enough
Next
From: Andrew Dunstan
Date:
Subject: Re: Anti-critical-section assertion failure in mcxt.c reached by walsender