From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: charles@twenty.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18367: Cannot drop schema
Date: Tue, 27 Feb 2024 19:19:36 +0100
Message-ID: <202402271819.uxvcer73hf2f@alvherre.pgsql> (raw)
In-Reply-To: <2135024.1709057683@sss.pgh.pa.us>
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, charles@twenty.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18367: Cannot drop schema
In-Reply-To: <202402271819.uxvcer73hf2f@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox