Re: BUG #17333: pgdg postgresql-common pg_upgradecluster duplicate data_directory in configuration file - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #17333: pgdg postgresql-common pg_upgradecluster duplicate data_directory in configuration file
Date
Msg-id CAKFQuwZJ_mnr7CDfD7cQ=HQgQ=BCbAK0mVCKzodO8tqzD7NZcQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17333: pgdg postgresql-common pg_upgradecluster duplicate data_directory in configuration file  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
On Fri, Dec 10, 2021 at 12:55 PM Eric Meygret <eric.meygret@free.fr> wrote:
>> 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’t a bug. I’d suggest you simply use the pg_upgrade tool directly if you don’t like (or adhere to) the assumptions built into the distro-specific scripts.
I like this tools, but I don't think that it is a choice to not follow "your" assumptions(I mean ignore first value), especially if it could lead to the deletion of data, but maybe I wrong.


It assumes that the directory configuration only appears once (I suspect this violation is the true cause) and, I'm assuming here, that its choice for where to place the various files (i.e., /var, not /postgres) is maintained.  I agree that the script is seemingly not as robust as it could be.

As for working toward improvement - the main Apt page on the PostgreSQL Wiki has the relevant information:


David J.

pgsql-bugs by date:

Previous
From: Eric Meygret
Date:
Subject: Re: BUG #17333: pgdg postgresql-common pg_upgradecluster duplicate data_directory in configuration file
Next
From: Alexander Korotkov
Date:
Subject: Re: BUG #17300: Server crashes on deserializing text multirange