[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] tweak request to gm-adjust_db_settings.sh
From: |
Busser, Jim |
Subject: |
Re: [Gnumed-bugs] tweak request to gm-adjust_db_settings.sh |
Date: |
Sat, 24 Jan 2015 20:36:31 +0000 |
On 2015-01-24, at 11:13 AM, Karsten Hilbert <address@hidden> wrote:
> On Sat, Jan 24, 2015 at 07:11:50AM +0000, Jim Busser wrote:
>
>> which results from the fact that I have
>>
>> PostgreSQL 9.1 running on port 5432
>> PostgreSQL 9.4 running on 5433
>
> Why not run just one of the two ?
Well, yes, eventually. However, overlap two versions can often happen for good
reasons:
1. because at the time that the legacy version is known to work, there can be a
delay before the new PostgreSQL (with migrated databases) can be confirmed to
be working satisfactorily, and
2. because a side-by-side install can be essential to direct (not-via-archive)
migration of databases.
Moreover, some upgrades to GNUmed will be unable to be achieved except after
first upgrading PostgreSQL, and so it can easily happen that the new psql, even
despite that it has become the default binary, risks to to the legacy port
instead of the needed alternate port.
That's why -- even if there is insufficient grounds to modify the script to
*handle* non-default ports -- it feels IMHO entirely reasonable to point out,
within the script comments, that this scenario will need manual tweaking of the
script.
-- Jim