Subject: Re: [bug#74058] [PATCH 2/2] etc: news: Warn users about postgresql default update.

From: Ludovic Courtès <[email-masked]>
Date: Wed, 06 Nov 2024 17:33:06 +0100

Nicolas Graves <[email-masked]> skribis:

> * etc/news.scm: Add entry.

Nice.

> + (entry (commit "") ; fill-me based on the previous commit
> +        (title (en "Postgresql service upgrade")
> +               (fr "Mise à jour du service postgresql"))
> +        (body
> +         (en "This news entry concerns users of the postgresql-service-type.

s/the postgresql-service-type/@code{postgresql-service-type}/

> +The default postgresql used in @code{postgresql-configuration} has been

When used as a noun, I believe the correct spelling is “PostgreSQL”
(this needs to be changed throughout).

> +deprecated, and will be removed from Guix in a few months.  However, the value

s/from Guix//

> +of the default @code{postgresql-configuration-postgresql} can't be directly
> +changed to a newer major version of postgresql, because switching to a major
> +version currently requires a manual update of the database.
> +
> +Because of this, the default value of postgresql-configuration-postgresql has
> +been set to @code{#f}.  Current users of the service will have to set it
> +manually.  If it was unset, use @code{postgresql-10} and plan an upgrade in the
> +next month to a supported version of postgresql.  To upgrade, you will need to
> +either dump your database using your previous version of postgresql and reload
> +it in the new version or use the @command{pg_upgrade} application.  See
> +@url{https://www.postgresql.org/docs/current/upgrading.html} for more
> +info.")

Would be nice if this could be automated, although automation for this
kind of thing is a double-edge sword…

I find the instructions clear enough though, +1!

Ludo’.