Re: BUG #18367: Cannot drop schema

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: charles(at)twenty(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18367: Cannot drop schema
Date: 2024-02-27 18:19:36
Message-ID: 202402271819.uxvcer73hf2f@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2024-Feb-27, Tom Lane wrote:

> I would try to pg_dump the database, and if you can do that and
> reload successfully then discard the original. If you've found
> one bit of catalog corruption there's likely more.

I second that recommendation. However, there's also pg_catcheck which
could help diagnose and fix things, in case a dump/restore of the whole
database is impractical. If you operate it wrong enough, you can
corrupt your whole database though.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Voy a acabar con todos los humanos / con los humanos yo acabaré
voy a acabar con todos (bis) / con todos los humanos acabaré ¡acabaré! (Bender)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-02-27 20:12:42 Re: Feature bug dumpall CREATE ROLE postgres
Previous Message Tom Lane 2024-02-27 18:14:43 Re: BUG #18367: Cannot drop schema