Re: Unable to drop extension dblink

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Matt Gibbins <matt_gibbins(at)fastmail(dot)com(dot)au>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Unable to drop extension dblink
Date: 2023-09-19 01:14:20
Message-ID: CAKFQuwZx2cLxSy+FXxMiLbRSM5PAVipaXRoDStLaK0Lbrpk1oA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Monday, September 18, 2023, Matt Gibbins <matt_gibbins(at)fastmail(dot)com(dot)au>
wrote:

> 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(at)lists(dot)postgresql(dot)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.
>

Is the output really that corrupted or is your writing of the email
introducing typos and whatnot that aren’t actually being shown by the
system?

I’d probably hope my backup isn’t corrupted and restore into a newly
created instance where the extension manipulation just works.

David J.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2023-09-19 01:16:05 Re: Unable to drop extension dblink
Previous Message Matt Gibbins 2023-09-18 22:04:33 Unable to drop extension dblink