Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfXPC-0001TZ-BC for pgsql-admin@arkaria.postgresql.org; Wed, 30 Apr 2014 16:30:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WfXPB-00063W-EZ for pgsql-admin@arkaria.postgresql.org; Wed, 30 Apr 2014 16:30:45 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfXP7-0005xr-L8 for pgsql-admin@postgresql.org; Wed, 30 Apr 2014 16:30:41 +0000 Received: from mail-pd0-x230.google.com ([2607:f8b0:400e:c02::230]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WfXP4-0007ys-14 for pgsql-admin@postgresql.org; Wed, 30 Apr 2014 16:30:41 +0000 Received: by mail-pd0-f176.google.com with SMTP id y10so1956166pdj.21 for ; Wed, 30 Apr 2014 09:30:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type; bh=xZ8ZW5fVBrs9lhd971j4J8rajyjk/Nweg8Dp3Zib8fQ=; b=Ua7JvkQXPg2BM22eBDlE1UaB25chcjT9ahKnxf1JfVf4ZJ1MRHUrA0X9ZwdT8JW3Vp 91wWLGmz2sqs0Sw0yAH9KGzZxYBnhVSKGrCBz3+SI8gD3eDe7ylLpFpsJgEq9gvFvMtz 5TkWMZ0NCpNw/GcoK6f7cu64tEVYKtkBerB2c38DwR/V8CajrRl97PziKYVfhAjxV9qZ fd/fp/ihD6BNZ3AUu7IfL2FIIJp1hkfvKbh08LAVBEwmUWAdflGK537yM2ej51IaUVz5 S1rXRvUo7QYD4w+SVKTJZYUlwhOjjXq397uYX7wYrYrrpah+I78vDW02ROKSSygSn3Jb OVhw== X-Received: by 10.66.66.108 with SMTP id e12mr10357136pat.35.1398875432303; Wed, 30 Apr 2014 09:30:32 -0700 (PDT) Received: from [10.252.27.62] (corp.mtv2.mozilla.com. [63.245.221.32]) by mx.google.com with ESMTPSA id f5sm138612310pat.11.2014.04.30.09.30.30 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 30 Apr 2014 09:30:31 -0700 (PDT) Date: Wed, 30 Apr 2014 09:30:17 -0700 From: Peter Bengtsson To: David G Johnston Cc: pgsql-admin@postgresql.org Message-ID: <4850AF4C2BA944B7A50A13877EB7C44C@gmail.com> In-Reply-To: <1398835199020-5801938.post@n5.nabble.com> References: <63B458542C454ED3A5F58A2323EC9E29@gmail.com> <1398835199020-5801938.post@n5.nabble.com> Subject: Re: Re: Missing loadable libraries when running pg_upgrade 9.2 -> 9.3 due to json_enhancements X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="53612519_2ae8944a_3019" X-Pg-Spam-Score: -0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --53612519_2ae8944a_3019 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I figured it out. Thanks Selena Deckelmann =20 http://www.peterbe.com/plog/pg-9.2-to-9.3-json=5Fenhancement -- =20 Peter Bengtsson home www.peterbe.com work www.mozilla.org fun aroundtheworldgame.com On Tuesday, April 29, 2014 at 10:19 PM, David G Johnston wrote: > Peter Bengtsson wrote > > In on OSX and I upgraded homebrew which upgraded me to postgres 9.3. = =20 > > Now postgres won=E2=80=99t start because the old database is no longe= r compatible. =20 > > I found some promising instructions here: > > http://blog.55minutes.com/2013/09/postgresql-93-brew-upgrade/ > > =20 > > But I get stuck on running this: > > pg=5Fupgrade -d /usr/local/var/postgres -D /usr/local/var/postgres9.3= -b > > /usr/local/Cellar/postgresql/9.2.2/bin/ -B > > /usr/local/Cellar/postgresql/9.3.4/bin/ -v > > =20 > > ( > > output here: http://www.peterbe.com/pg=5Fupgrade.log > > log here: http://www.peterbe.com/pg=5Fupgrade=5Fserver.log > > ) > > =20 > > The content of loadable=5Flibraries.txt is this:: > > Could not load library =22=24libdir/json=5Fenhancements=22 > > ERROR: could not access file =22=24libdir/json=5Fenhancements=22: No = such file or > > directory > > =20 > > =20 > > Yes, I had json=5Fenhancement installed when I was using postgres 9.2= . But I > > don=E2=80=99t need that any more in 9.3 because json=5Fenhancements w= as a backport > > for 9.2. =20 > > The file is still there: > > /usr/local/Cellar/postgresql/9.2.2/lib/json=5Fenhancements.so > > =20 > > So, I can=E2=80=99t upgrade because I don=E2=80=99t have json=5Fenhan= cements installed in > > 9.3. Which is not possible. =20 > > And I can=E2=80=99t upgrade by deleting ./lib/json=5Fenhancements.so > > ./share/postgresql/extension/json=5Fenhancements--1.0.0.sql and > > ./share/postgresql/extension/json=5Fenhancements.control > > =20 > > How to get out of this pickle=3F > > =20 > > By the way, the database that I think I have it installed on is a dat= abase > > I can do without. But I can=E2=80=99t simply =60dropdb > > a=5Fdatabase=5Fwith=5Fjson=5Fenhancements=5Finstalled=60 because drop= db doesn=E2=80=99t work > > any more of course. =20 > > =20 > =20 > =20 > http://www.pgxn.org/dist/json=5Fenhancements/doc/json=5Fenhancements.ht= ml > =20 > =22This module might make using pg=5Fupgrade difficult or even impossib= le. This > use has not been tested. I=46 YOU ARE PLANNING TO USE pg=5Fupgrade THEN= DO NOT > USE THIS EXTENSION WITHOUT UPGRADE TESTING. If you ignore this warning = and > it breaks you get to keep all the pieces.=22 > =20 > Doesn't say anything about how to go about a dump/restore style > upgrade...maybe rebuild the schema in 9.3 manually (more-or-less) then = do a > data-only dump/restore=3F > =20 > Seems you, in theory, should be able to drop the database and extension= from > 9.2 then re-do the upgrade without them. > =20 > Good Luck... > =20 > David J. > =20 > =20 > =20 > =20 > -- > View this message in context: http://postgresql.1045698.n5.nabble.com/M= issing-loadable-libraries-when-running-pg-upgrade-9-2-9-3-due-to-json-enh= ancements-tp5801937p5801938.html > Sent from the PostgreSQL - admin mailing list archive at Nabble.com (ht= tp://Nabble.com). > =20 > =20 > -- =20 > Sent via pgsql-admin mailing list (pgsql-admin=40postgresql.org (mailto= :pgsql-admin=40postgresql.org)) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > =20 > =20 --53612519_2ae8944a_3019 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I figured it out. Thanks Selena Deckelmann
http://www.peterbe.com/plog/pg-9.2-to-9.3-json= =5Fenhancement

-- 
Peter Bengtss= on
home www.peterbe.com
work www.mozilla.org
fun aroundtheworldgame.com

=20

On Tuesday, April 29, = 2014 at 10:19 PM, David G Johnston wrote:

Peter Bengtsson wrote
In on OSX and I upgraded homebrew whic= h upgraded me to postgres 9.3.
Now postgres won=E2=80=99t st= art because the old database is no longer compatible.
I found= some promising instructions here:

But I= get stuck on running this:
pg=5Fupgrade -d /usr/local/var/post= gres -D /usr/local/var/postgres9.3 -b
/usr/local/Cellar/postgre= sql/9.2.2/bin/ -B

The content of loadable=5Flibraries.txt is= this::
Could not load library =22=24libdir/json=5Fenhancements= =22
ERROR: could not access file =22=24libdir/json=5Fenhanceme= nts=22: No such file or
directory


=
Yes, I had json=5Fenhancement installed when I was using postg= res 9.2. But I
don=E2=80=99t need that any more in 9.3 because = json=5Fenhancements was a backport
for 9.2.
The fil= e is still there:
/usr/local/Cellar/postgresql/9.2.2/lib/json=5F= enhancements.so

So, I can=E2=80=99t upgrade beca= use I don=E2=80=99t have json=5Fenhancements installed in
9.3. = Which is not possible.
And I can=E2=80=99t upgrade by deletin= g ./lib/json=5Fenhancements.so
./share/postgresql/extension/jso= n=5Fenhancements--1.0.0.sql and
./share/postgresql/extension/js= on=5Fenhancements.control

How to get out of this= pickle=3F

By the way, the database that I think= I have it installed on is a database
I can do without. But I c= an=E2=80=99t simply =60dropdb
a=5Fdatabase=5Fwith=5Fjson=5Fenha= ncements=5Finstalled=60 because dropdb doesn=E2=80=99t work
any= more of course.


=22This module might make using pg=5F= upgrade difficult or even impossible. This
use has not been tes= ted. I=46 YOU ARE PLANNING TO USE pg=5Fupgrade THEN DO NOT
USE = THIS EXTENSION WITHOUT UPGRADE TESTING. If you ignore this warning and
it breaks you get to keep all the pieces.=22

=
Doesn't say anything about how to go about a dump/restore style
upgrade...maybe rebuild the schema in 9.3 manually (more-or-less) t= hen do a
data-only dump/restore=3F

See= ms you, in theory, should be able to drop the database and extension from=
9.2 then re-do the upgrade without them.

<= div>Good Luck...

David J.




--
Sent from the PostgreSQ= L - admin mailing list archive at Nabbl= e.com.


--
Sent via= pgsql-admin mailing list (pgsql-admin=40postgresql.org)
To make changes to your= subscription:
=20 =20 =20 =20 =20

--53612519_2ae8944a_3019--