On 2026/07/08 14:02, Olivier Cherrier wrote:
> Hello Stuart,
>
> On 7/8/26 12:15 PM, Stuart Henderson wrote:
> > On 2026/07/08 10:26, Olivier Cherrier wrote:
> > > Hello,
> > >
> > > While upgrading using method 1 (dump / restore),
> > > the 'postgresql-pg_upgrade' pkg is not installed.
> > >
> > > Please see attached patch.
> > > @@ -120,7 +120,7 @@ Examine your old file for local changes
> > > (/var/postgresql/data/postgresql.conf). The following command may help
> > > identify them:
> > > -# diff -wu
> > > ${LOCALBASE}/share/postgresql-${PREV_MAJOR}/postgresql.conf.sample \
> > > +# diff -wu ${LOCALBASE}/share/postgresql/postgresql.conf.sample \
> > > /var/postgresql/data-${PREV_MAJOR}/postgresql.conf
> > It's probably better to install postgresql-pg_upgrade. This will allow
> > comparing the live config file against a default one with fewer
> > differences as it's from a more similar version. e.g.
>
> Yes, we could do it this way too.
>
> Ideally the user has to merge its postgresql.conf file with the more recent
> version.
> The "postgresql-pg_upgrade" package does provide an old version.
I don't think you understand what the diff is for.
It shows the differences between the "as close as is still available to
the unmodified old file" and the installed file. The user should look
through those changes and apply them to the postgresql.conf that was
generated by initdb.
