Обсуждение: cannot drop an extension

Поиск
Список
Период
Сортировка

cannot drop an extension

От
John Scalia
Дата:
Hi all,

My pg_upgrade woes continue... The primary server, V9.3.3, was originally used as a testbed for pgpool-II, although we
endedup 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
andpg_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
instanceand 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
extensionname 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
extensionso 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.
--
Jay


Re: cannot drop an extension

От
Glyn Astill
Дата:



----- 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

Re: cannot drop an extension

От
John Scalia
Дата:
On 1/20/2015 1:42 PM, Glyn Astill wrote:
>
>
>
> ----- 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
>
Well, I just checked the server's postgresql.conf file, and the shared_preload_libraries parameter only has
'pg_stat_statements'in it, and local_preload_libraries is commented  
out. I further searched for anything with "pgpool" in the file, and nothing came back.


Re: cannot drop an extension

От
Devrim Gündüz
Дата:
Hi,

<snip>

On Tue, 2015-01-20 at 13:12 -0500, John Scalia wrote:
> then tried issuing a "drop  extension pgpool-reglass", but the both
> the db's say it does not exist.

If there is not a typo in the email, it should be underscore:

DROP EXTENSION pgpool_regclass;

Regards,

--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR


Вложения

Re: cannot drop an extension

От
Glyn Astill
Дата:



----- 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
todrop the relevent objects; take a look in the contrib directory. 

Re: cannot drop an extension

От
John Scalia
Дата:
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
needto drop the relevent objects; take a look in the contrib directory. 
>
Will try that, as soon my daily standup (agile) call is done today.


Re: cannot drop an extension

От
Glyn Astill
Дата:



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

Make sure you read the reply from Devrim stating that you might just be using the wrong extension name first.