Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YDdIY-0006oU-Si for pgsql-admin@arkaria.postgresql.org; Tue, 20 Jan 2015 18:13:07 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YDdIY-0005X0-D9 for pgsql-admin@arkaria.postgresql.org; Tue, 20 Jan 2015 18:13:06 +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 1YDdIX-0005Wm-LU for pgsql-admin@postgresql.org; Tue, 20 Jan 2015 18:13:05 +0000 Received: from mail-yh0-x234.google.com ([2607:f8b0:4002:c01::234]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YDdIU-0006pq-6r for pgsql-admin@postgresql.org; Tue, 20 Jan 2015 18:13:04 +0000 Received: by mail-yh0-f52.google.com with SMTP id b6so7831865yha.11 for ; Tue, 20 Jan 2015 10:12:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=2H/phaP4bnHpcQ3F6D4ra5Y/DP3FBSiFBmzcIJu8bEM=; b=L9UIkTizCkLftAwRYiYhtkX5cm5FPhY0EVmEgZiMCH7PnXfSP8Qfy1oSaAhKTYPKTi OcjCuf2FNMU1rkykhl0LoxAw0nArdmIEijtAEzjCIuAKcjv5nTXovJ9CBT7xcAP+TAHW X//hDLS2r9e7D6WrAVaTSi4Rd6Yf82RGKgOfo1Komrp5pnMpWLsTd4AnXyEzvVj3EGp0 2olA1vUf8Sx0GbDKnCg1PYXE7wL6vVWPWRqQwOkk1XWMrcJmlVXulHgjhCr8t9t7A7QN lQKRVmeTLG1U44M2b9/wlnVHLtNiL3vkGCZrVSTJ+H5ylpXL+Ke+EfT0LKEAGZrsm7yz iNmA== X-Received: by 10.170.37.198 with SMTP id 189mr9027441ykf.106.1421777578822; Tue, 20 Jan 2015 10:12:58 -0800 (PST) Received: from [192.168.254.3] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id x46sm5482905yhx.49.2015.01.20.10.12.57 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Jan 2015 10:12:58 -0800 (PST) Message-ID: <54BE9AA9.8040608@gmail.com> Date: Tue, 20 Jan 2015 13:12:57 -0500 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: cannot drop an extension Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 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