Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YDdlc-0007sX-ED for pgsql-admin@arkaria.postgresql.org; Tue, 20 Jan 2015 18:43:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YDdlb-00034h-UB for pgsql-admin@arkaria.postgresql.org; Tue, 20 Jan 2015 18:43:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YDdla-00033K-1l for pgsql-admin@postgresql.org; Tue, 20 Jan 2015 18:43:06 +0000 Received: from nm31-vm1.bullet.mail.ir2.yahoo.com ([212.82.97.88]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YDdlV-0007Oq-Ol for pgsql-admin@postgresql.org; Tue, 20 Jan 2015 18:43:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1421779374; bh=mIjqfmPTv6RlYvAJ5kzMl1/AG4lOT315+dbFYEamIEk=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=rSNEp3cXaPjeTiAUZXl5bzwBvkweV853GVYRC6Y7UY2FeGIVlSbX/OQHxxIAxerSfY30VsV4v8/APU81Lh0EcQop63XHYboz6kEPr1Ph69IkV1iSoXcHsxqP6s0op/RG5OAUAhfUmjBsjtBkMXdNPARzZd5xyxrNMaBQgU/YMoksazSqCRNlEGgDlrA2SkQN5nfddrm0kTZMb58/i+3TnMzTa9Vq9qo++p/vqjMWj9C6sBAMQIeDPXKcHqipU0XTh2EFWzao5Mn31Ec3ewxzI4jlIeT1DYKG7Zvw+m0XqnctHu15CFW7SVFAgfw41tv2n//mS3uln3NPr/bfbzmxjw== Received: from [212.82.98.52] by nm31.bullet.mail.ir2.yahoo.com with NNFMP; 20 Jan 2015 18:42:54 -0000 Received: from [212.82.98.80] by tm5.bullet.mail.ir2.yahoo.com with NNFMP; 20 Jan 2015 18:42:52 -0000 Received: from [127.0.0.1] by omp1017.mail.ir2.yahoo.com with NNFMP; 20 Jan 2015 18:42:52 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 77542.857.bm@omp1017.mail.ir2.yahoo.com X-YMail-OSG: GpbEvzUVM1l1wCvBw5ikUm4Xz6_AFP2N8JKcicW0sdYyA0uGsDav2GnW2FQzKeZ Hfz5c4VDQyoDHRLX_1Gls0HeK8PZ5M0cOPOMObEEYH49GToLbyKkJ717Dtt1ef4fc6qJhSFESnkB mvz9axMpEhcxKIRhF5MWDKzesKSz4NCC0QPfJSdhzcV13l5VVPIJ5CN8oocgGrgB8Sdq.hNQ09cD rXRRaoxN.F04S8E8i9daJuOQAaaJj87KPENBwx1BwqN1mvEh2YE6yd4hhxCa0YUZkheB5Ch2SDu1 mdS8aOh1BNiEDQBz6qi5E5i3cmE283ZL95zlmon_AFh_G8H4sZKywMg3IEkg2FlSLX4PtrG_tK14 vr.eAfqgjTgj9giaD2NvRy0Vwbq021EAfR2KuABALbSaQj.MCTJCk6ujNocUvcBHRNADhu5p6IHy za.33piZh8dB7vp1VBlsmobL1Jgukg54prMbOQXBkfeIpGLz8XO3lWQW917q6uBZKT5s1fHZQBfx 9hzSFh.c- Received: by 212.82.98.114; Tue, 20 Jan 2015 18:42:51 +0000 Date: Tue, 20 Jan 2015 18:42:49 +0000 (UTC) From: Glyn Astill Reply-To: Glyn Astill To: John Scalia , "pgsql-admin@postgresql.org" Message-ID: <798882007.4385422.1421779369077.JavaMail.yahoo@jws11176.mail.ir2.yahoo.com> In-Reply-To: <54BE9AA9.8040608@gmail.com> References: <54BE9AA9.8040608@gmail.com> Subject: Re: cannot drop an extension MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Length: 1437 X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org ----- Original Message ----- > From: John Scalia > To: "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