Message-ID: <54BEA73D.7070605@gmail.com>
Date: Tue, 20 Jan 2015 14:06:37 -0500
From: John Scalia <jayknowsunix@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Glyn Astill <glynastill@yahoo.co.uk>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: cannot drop an extension
References: 
 <798882007.4385422.1421779369077.JavaMail.yahoo@jws11176.mail.ir2.yahoo.com>
 <700714443.4469265.1421780123878.JavaMail.yahoo@jws11131.mail.ir2.yahoo.com>
In-Reply-To: 
 <700714443.4469265.1421780123878.JavaMail.yahoo@jws11131.mail.ir2.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


On 1/20/2015 1:55 PM, Glyn Astill wrote:
>
>
>
> ----- 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.
>
Will try that, as soon my daily standup (agile) call is done today.


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