From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Smitha Pamujula <smitha(dot)pamujula(at)iovation(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Grant Holly <grant(dot)holly(at)iovation(dot)com> |
Subject: | Re: pg_upgrade + Extensions |
Date: | 2015-08-31 22:18:25 |
Message-ID: | 20150831221825.GE17858@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 14, 2015 at 09:48:59AM -0700, Smitha Pamujula wrote:
> This error will go away only if I install the new json_build94.
> ........................................................................
> I was under the impression that we dont need to get the json_build
> libraries for 94. But the upgrade wont go forward without that. Are we
> missing doing something here or is it necessarty to get json_build94
> before upgrade.
I am coming very late to this discussion, but I do have some
information. Basically, pg_upgrade is trying to predict if the
dump/restore will fail by checking references to shared objects in the
old cluster. It sees a reference to json_build in the old cluster and
assumes this is needed in the new cluster, when in fact it isn't.
We could have hard-coded this knowledge into 9.4 pg_upgrade if we had
known it. The simple solution is to install json_build94 as you did,
run pg_upgrade, then just uninstall json_build94 as nothing depends on
it. Not sure if this should be in the pg_upgrade docs or not.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2015-08-31 22:20:52 | Re: WIP: Access method extendability |
Previous Message | Robert Haas | 2015-08-31 21:47:12 | Re: Horizontal scalability/sharding |