Date: Fri, 10 Dec 2021 20:55:21 +0100 (CET)
From: Eric Meygret <eric.meygret@free.fr>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Message-ID: 
 <1269280643.359125664.1639166121205.JavaMail.root@zimbra62-e11.priv.proxad.net>
In-Reply-To: 
 <CAKFQuwb=dp3ycnRHF3P1YktOeQ=9HURvcpnwwZz2ZY_WOAMWqw@mail.gmail.com>
Subject: Re: BUG #17333: pgdg postgresql-common pg_upgradecluster duplicate
 data_directory in configuration file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/1269280643.359125664.1639166121205.JavaMail.root%40zimbra62-e11.priv.proxad.net>
Precedence: bulk

>> That script isn=E2=80=99t part of the core project so this list may not =
be the best place to report complaints.=20
sorry I was thinking that you mange also pgdg repository, where I can repor=
t that, I am afraid that to have same answer by the Debian team?=20

>> Doing testing on in a test environment first is another useful exercise.=
=20
That was on a test environnement :)=20

>> If you are going to go do customizations the fact that the scripts that =
are built without those customizations in mind fail to work properly isn=E2=
=80=99t a bug. I=E2=80=99d suggest you simply use the pg_upgrade tool direc=
tly if you don=E2=80=99t like (or adhere to) the assumptions built into the=
 distro-specific scripts.=20
I like this tools, but I don't think that it is a choice to not follow "you=
r" assumptions(I mean ignore first value), especially if it could lead to t=
he deletion of data, but maybe I wrong.=20

thanks for your answer.
Eric