Re: pg_upgrade + Extensions

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
Cc: Smitha Pamujula <smitha(dot)pamujula(at)iovation(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-07-10 23:26:39
Message-ID: CAD5tBcLwmrSMt7nWOtuB_8TS+Z5uDRABik--X9fzbwJaH6rtSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 10, 2015 at 5:05 PM, David E. Wheeler <david(at)justatheory(dot)com>
wrote:

> On Jul 10, 2015, at 11:32 AM, Smitha Pamujula <
> smitha(dot)pamujula(at)iovation(dot)com> wrote:
>
>
> > Your installation references loadable libraries that are missing from the
> > new installation. You can add these libraries to the new installation,
> > or remove the functions using them from the old installation. A list of
> > problem libraries is in the file:
> > loadable_libraries.txt
> >
> > Failure, exiting
> > [postgres(at)pdxdvrptsrd04 ~]$ cat loadable_libraries.txt
> > Could not load library "json_build"
> > ERROR: could not access file "json_build": No such file or directory
>
> So you drop the json_build extension before upgrading, but pg_upgrade
> still complains that it’s missing? That seems odd.
>
>
>

Are you sure the extension was uninstalled from every database in the
cluster? This seems likely to occur when you forgot to uninstall it from
some database (e.g. template1)

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-07-10 23:32:04 Re: Freeze avoidance of very large table.
Previous Message Joe Conway 2015-07-10 22:08:53 Re: more RLS oversights