pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedcannot drop an extension
7+ messages / 3 participants
[nested] [flat]
* cannot drop an extension
@ 2015-01-20 18:12 John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:42 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 18:54 ` Re: cannot drop an extension Devrim Gündüz <devrim@gunduz.org>
0 siblings, 2 replies; 7+ messages in thread
From: John Scalia @ 2015-01-20 18:12 UTC (permalink / raw)
To: pgsql-admin
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.
--
Jay
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: cannot drop an extension
2015-01-20 18:12 cannot drop an extension John Scalia <jayknowsunix@gmail.com>
@ 2015-01-20 18:42 ` Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 18:48 ` Re: cannot drop an extension John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:55 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
1 sibling, 2 replies; 7+ messages in thread
From: Glyn Astill @ 2015-01-20 18:42 UTC (permalink / raw)
To: John Scalia <jayknowsunix@gmail.com>; pgsql-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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: cannot drop an extension
2015-01-20 18:12 cannot drop an extension John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:42 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
@ 2015-01-20 18:48 ` John Scalia <jayknowsunix@gmail.com>
1 sibling, 0 replies; 7+ messages in thread
From: John Scalia @ 2015-01-20 18:48 UTC (permalink / raw)
To: Glyn Astill <glynastill@yahoo.co.uk>; pgsql-admin
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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: cannot drop an extension
2015-01-20 18:12 cannot drop an extension John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:42 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
@ 2015-01-20 18:55 ` Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 19:06 ` Re: cannot drop an extension John Scalia <jayknowsunix@gmail.com>
1 sibling, 1 reply; 7+ messages in thread
From: Glyn Astill @ 2015-01-20 18:55 UTC (permalink / raw)
To: Glyn Astill <glynastill@yahoo.co.uk>; John Scalia <jayknowsunix@gmail.com>; pgsql-admin
----- 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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: cannot drop an extension
2015-01-20 18:12 cannot drop an extension John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:42 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 18:55 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
@ 2015-01-20 19:06 ` John Scalia <jayknowsunix@gmail.com>
2015-01-20 19:28 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
0 siblings, 1 reply; 7+ messages in thread
From: John Scalia @ 2015-01-20 19:06 UTC (permalink / raw)
To: Glyn Astill <glynastill@yahoo.co.uk>; pgsql-admin
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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: cannot drop an extension
2015-01-20 18:12 cannot drop an extension John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:42 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 18:55 ` Re: cannot drop an extension Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 19:06 ` Re: cannot drop an extension John Scalia <jayknowsunix@gmail.com>
@ 2015-01-20 19:28 ` Glyn Astill <glynastill@yahoo.co.uk>
0 siblings, 0 replies; 7+ messages in thread
From: Glyn Astill @ 2015-01-20 19:28 UTC (permalink / raw)
To: John Scalia <jayknowsunix@gmail.com>; pgsql-admin
----- 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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: cannot drop an extension
2015-01-20 18:12 cannot drop an extension John Scalia <jayknowsunix@gmail.com>
@ 2015-01-20 18:54 ` Devrim Gündüz <devrim@gunduz.org>
1 sibling, 0 replies; 7+ messages in thread
From: Devrim Gündüz @ 2015-01-20 18:54 UTC (permalink / raw)
To: John Scalia <jayknowsunix@gmail.com>; +Cc: pgsql-admin
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
Attachments:
signature.asc (application/pgp-signature, 818B) download
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2015-01-20 19:28 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-01-20 18:12 cannot drop an extension John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:42 ` Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 18:48 ` John Scalia <jayknowsunix@gmail.com>
2015-01-20 18:55 ` Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 19:06 ` John Scalia <jayknowsunix@gmail.com>
2015-01-20 19:28 ` Glyn Astill <glynastill@yahoo.co.uk>
2015-01-20 18:54 ` Devrim Gündüz <devrim@gunduz.org>
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