From: Glyn Astill <glynastill@yahoo.co.uk>
To: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: cannot drop an extension
Date: Tue, 20 Jan 2015 18:42:49 +0000 (UTC)
Message-ID: <798882007.4385422.1421779369077.JavaMail.yahoo@jws11176.mail.ir2.yahoo.com> (raw)
In-Reply-To: <54BE9AA9.8040608@gmail.com>
References: <54BE9AA9.8040608@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
----- Original Message -----
> From: John Scalia <jayknowsunix@gmail.com>
> To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
> Cc:
> Sent: Tuesday, 20 January 2015, 18:12
> Subject: [ADMIN] cannot drop an extension
>
> Hi all,
>
> My pg_upgrade woes continue... The primary server, V9.3.3, was originally used
> as a testbed for pgpool-II, although we ended up chosing pacemaker and corosync
> instead. When pgpool
> was installed, the instructions have you add a pgpool-regclass extension.
> Naturally, trying to upgrade to V9.4.0 fails and pg_upgrade writes a
> loadable_libraries.txt saying that
> $libdir/pgpool-regclass cannot be found. So, I restarted the original database,
> and connected to both my csg_db instance and to the template1 instance, then
> tried issuing a "drop
> extension pgpool-reglass", but the both the db's say it does not exist.
> I also tried dropping it by enclosing the extension name in quotes, both single
> and double with no joy.
> Then, I tried looking in pg_extensions, but I didn't see any similar entry
> there either. How can I get rid of this extension so that pg_upgrade will
> complete successfully? I've
> asked on the pgpool admin list, but as it's the middle of the night in
> Japan, I'm not expecting an immediate answer, if any.
Sounds like you need to remove the pgpool-regclass entry from the shared_preload_libraries entry in your postgresql.conf
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: glynastill@yahoo.co.uk, jayknowsunix@gmail.com
Subject: Re: cannot drop an extension
In-Reply-To: <798882007.4385422.1421779369077.JavaMail.yahoo@jws11176.mail.ir2.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox