On Wed, Jun 26, 2024 at 11:39:45AM +0530, Amit Kapila wrote:
> --- a/doc/src/sgml/release-17.sgml
> +++ b/doc/src/sgml/release-17.sgml
> @@ -1325,7 +1325,7 @@ Author: Michael Paquier <michael@paquier.xyz>
>
> <!--
> Author: Amit Kapila <akapila@postgresql.org>
> -2024-03-08 [bf279ddd1] Introduce a new GUC 'standby_slot_names'.
> +2024-03-08 [bf279ddd1] Introduce a new GUC 'synchronized_standby_slots'.
>
> I am not sure if it is a good idea to change release notes in the same
> commit as the code change. I would prefer to do it in a separate
> commit.
The existing commits referenced cannot change, but it's surely OK to
add a reference to the commit doing the rename for this item in the
release notes, and update the release notes to reflect the new GUC
name. Using two separate commits ensures that the correct reference
about the rename is added to the release notes, so that's the correct
thing to do, IMHO.
--
Michael