References: <bf801eb082936b7671c4f7dfb26beec3@mail.gmail.com>
 <1407159008.1433.YahooMailNeo@web122302.mail.ne1.yahoo.com>
 e2a3414f118ca2958923c69c0abecc45@mail.gmail.com
 <aa7e0dcc7e1aba50789a3661b6d67bb6@mail.gmail.com>
Message-ID: <1407176358.38816.YahooMailNeo@web122301.mail.ne1.yahoo.com>
Date: Mon, 4 Aug 2014 11:19:18 -0700
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: upgrading postgres 7.3.4 to 9.1.9
To: Khangelani Gama <kgama@argility.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <aa7e0dcc7e1aba50789a3661b6d67bb6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Khangelani Gama <kgama@argility.com> wrote:

> in psql I keep getting the following errors: I saw what it is
> explained in
> http://stackoverflow.com/questions/12136033/install-pl-perl-in-postgresql
> But I am not sure if this installation command "yum install
> perl-devel" will
> work without affecting other special setups.

Hard to say.=C2=A0 I'm not even sure what OS this is or what you mean by
"other special setups".

> template1=3D#=C2=A0 CREATE EXTENSION plperl;
> ERROR:=C2=A0 could not open extension control file
> "/usr/local/pgsql9/share/extension/plperl.control": No such file or direc=
tory
> template1=3D#=C2=A0 CREATE EXTENSION plperlu;
> ERROR:=C2=A0 could not open extension control file
> "/usr/local/pgsql9/share/extension/plperlu.control": No such file or dire=
ctory

/usr/local/pgsql9/ does not seem likely to be a location that a
packaged build would use, since 9.0, 9.1, etc. are different major
releases and packagers would normally want to make it easy to
install different major releases on the same system.=C2=A0 This looks
like it was probably a build and install from source code.=C2=A0 It
would help to know how the build was configured.=C2=A0 Please run
/usr/local/pgsql9/bin/pg_config to and post the output.

Most likely your best course will be to download the source code
for 9.1.14 to get bug fixes from the last year and a quarter, and
make a new build to a new export location (specific to at least
9.1; personally I like to use a separate directory for each minor
release to make the next minor upgrade take only a few seconds of
down time, but most people don't do it that way).=C2=A0 Make sure when
you configure for the new build you configure it to be compatible
with the old, but make sure that --with-perl is specified.If you
are not familiar with this sort of build and install process, you
should probably find someone to help you who is.

> Can I try the following , I just don=E2=80=99t want to break other
> databases already running on postgres9
>
> Stop all instances from running
>
> ./configure=C2=A0 --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.=C2=A0 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.=C2=A0 (I have
found that restart does not work for a minor upgrade -- a separate
stop -w and start -w is needed.)

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin