Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qiMMK-006Cld-AG for pgsql-admin@arkaria.postgresql.org; Mon, 18 Sep 2023 22:04:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qiMMI-003x1k-8i for pgsql-admin@arkaria.postgresql.org; Mon, 18 Sep 2023 22:04:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qiMMG-003x0t-Bu for pgsql-admin@lists.postgresql.org; Mon, 18 Sep 2023 22:04:45 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qiMMC-005KTR-TN for pgsql-admin@lists.postgresql.org; Mon, 18 Sep 2023 22:04:42 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3C2A55C01E7 for ; Mon, 18 Sep 2023 18:04:39 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 18 Sep 2023 18:04:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com.au; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:message-id:mime-version:reply-to :sender:subject:subject:to:to; s=fm2; t=1695074679; x= 1695161079; bh=oXhWv1vIltwgOYv6EEhA7FQk9scmU1//9DgjzEkA+gM=; b=K wCn71CDC24DxOKMSPOzz0EHZLKotyo5A2/IzIhD1HVMz0X6URCTe4u6vFpPzj350 lt8zIFR8zE+76VA06AmStTTVPeR2Ds60361VgaP3+yubtBLop42UJO8qWpAicpsU IIJkSsN3zfu0Fxx1YQ0b+g2nmJHoGZgvvjcv80JgI+7Ggq5lqUAGP9HpBgWqLHZs XkbYekWkxjhnD+21l65t6w350w5KWIQBKaSw+Nyaz8Mrhv3QAGxfrbyDebZ36FXg Gp4n43ijOfgNIhRxeXUbE3Z5cc6CnxzH32Qkroq7EDkeCIVasH1CMuqTsArrPrSN WN+MCB8ikwaavtCvBsksw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1695074679; x=1695161079; bh=oXhWv1vIltwgO Yv6EEhA7FQk9scmU1//9DgjzEkA+gM=; b=Es5f4OPaqB/FVAK8MYZtwkjw4egMY 5WkRy/khrAalHO4HY9VI7iluqzIZfX7tlqnYgNgmbFhWAkizX2hZQdGZ3a97dt/Z 5m6EP0a+37ZB8Y2IHssNaz+Hvg2Hrk84HmM8oigEisWXtJVSCFKCEmbvOPDTfpTx TCX29MI2hswTOGlZUnVCOiIkTuKoSVhcqKLjujXn/BtSkgH2Np4nCF07bV3ri7YJ /HcYBDGthjb7r3MpFWipo8rUtNWihkhwIJVFa0U+FHM353giloMn8MrhpgIMPGqk T3kYV1Dyj8T/tth5uguSlrk361hEWEbCGFbHmGdEVRrFDzXYbJ8Lc874Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudejledgtdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfhvffutgfgsehtkeertd dtvdejnecuhfhrohhmpeforghtthcuifhisggsihhnshcuoehmrghtthgpghhisggsihhn shesfhgrshhtmhgrihhlrdgtohhmrdgruheqnecuggftrfgrthhtvghrnhepgedvieduke ektdffvedtffdtteetleelffegffelgedtgefggfekgeelffeugeegnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhgrthhtpghgihgssghinh hssehfrghsthhmrghilhdrtghomhdrrghu X-ME-Proxy: Feedback-ID: i6d194797:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 18 Sep 2023 18:04:37 -0400 (EDT) Message-ID: <07dbf1c4-4871-4348-b41a-d0a800da7465@fastmail.com.au> Date: Tue, 19 Sep 2023 08:04:33 +1000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-AU From: Matt Gibbins To: pgsql-admin@lists.postgresql.org Subject: Unable to drop extension dblink Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk In the process of removing extensions not required on the database I was in the process of removing the dblink extension from the postgres database. First attempt to drop the extension failed with 'ERROR: schema "ag_catalog" does not exist'. Created the extension and then received the 'ERROR: table "ag_label" does not exist'. In response I created the table with a dummy colum 'label'. Dropping the extension resulted in "ERROR: index "pgsql-admin@lists.postgresql.org"'. So I created the index. Next attempt resulted in 'ERROR:  column is not in index'. Now I appear to be stuck in a loop with 'ERROR:  column is not in index' regardless of any attempt to remove these tables and the original extension. Any assistance appreciated. Regards Matt.