From: Khangelani Gama <kgama@argility.com>
References: <bf801eb082936b7671c4f7dfb26beec3@mail.gmail.com>
 <1407159008.1433.YahooMailNeo@web122302.mail.ne1.yahoo.com>
 e2a3414f118ca2958923c69c0abecc45@mail.gmail.com
 <aa7e0dcc7e1aba50789a3661b6d67bb6@mail.gmail.com>
 <1407176358.38816.YahooMailNeo@web122301.mail.ne1.yahoo.com>
In-Reply-To: <1407176358.38816.YahooMailNeo@web122301.mail.ne1.yahoo.com>
MIME-Version: 1.0
Thread-Index: AQLAo3AD0SI8NySoocndshO8R1ykkQFN/yMxALIoQkEDV4/i3Zm0w3VQ
Date: Tue, 5 Aug 2014 06:23:46 +0200
Message-ID: <ec3c2eb760f4c84c503ef779b8c9f8d0@mail.gmail.com>
Subject: Re: upgrading postgres 7.3.4 to 9.1.9
To: Kevin Grittner <kgrittn@ymail.com>, pgsql-admin@postgresql.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

> Can I try the following , I just don=E2=80=99t want to break other databa=
ses
> already running on postgres9
>
> Stop all instances from running
>
> ./configure  --with-perl --prefix=3D$PATH Gmake Gmake install
>
> And then create an instance, and then pg_restore.

Personally, I would get that new build in a new directory, make sure that it
works with a PITR restore (or directory tree copy while the database is
stopped) of one of the other 9.1 clusters, and make sure you can CREATE
EXTENSION plperl before trying to convert this 7.3 database.  Then you can
move all the old clusters over to the new executable by updating your
service script to point to the new executable running stop and then running
start.  (I have found that restart does not work for a minor upgrade -- a
separate stop -w and start -w is needed.)


Thanks Kevin,