Date: Tue, 20 Jan 2015 18:55:23 +0000 (UTC)
From: Glyn Astill <glynastill@yahoo.co.uk>
Reply-To: Glyn Astill <glynastill@yahoo.co.uk>
To: Glyn Astill <glynastill@yahoo.co.uk>,
 John Scalia <jayknowsunix@gmail.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Message-ID: 
 <700714443.4469265.1421780123878.JavaMail.yahoo@jws11131.mail.ir2.yahoo.com>
In-Reply-To: 
 <798882007.4385422.1421779369077.JavaMail.yahoo@jws11176.mail.ir2.yahoo.com>
References: 
 <798882007.4385422.1421779369077.JavaMail.yahoo@jws11176.mail.ir2.yahoo.com>
Subject: Re: cannot drop an extension
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Length: 2117
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


----- Original Message -----
> From: Glyn Astill <glynastill@yahoo.co.uk>
> To: John Scalia <jayknowsunix@gmail.com>; "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
> Cc: 
> Sent: Tuesday, 20 January 2015, 18:42
> Subject: Re: [ADMIN] cannot drop an extension
> 
> 
> 
> 
> 
> ----- 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
> 


Actually after looking at the pgpool website, it looks like this isn't a shared preload library, but just a function.

Is it possible you installed the extension via the sql script rather than using create extension?  IF so you just need to drop the relevent objects; take a look in the contrib directory.


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