RE: Index (primary key) corrupt?

Internal

Let me get this straight, are you still contesting that the index is actually not part of the dumpfile and I somehow just keep on ‘missing it’?

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Sent: dinsdag 10 maart 2026 15:15
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Wim Rouquart <wim(dot)rouquart(at)kbc(dot)be>; pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Index (primary key) corrupt?

The real sender of this external email is htamfids(at)gmail(dot)com<mailto:htamfids(at)gmail(dot)com>

On Mon, Mar 9, 2026 at 3:53 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com<mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
Yeah, but the indrelid did not change after the the REINDEX.

Agreed, but none of this makes sense. pg_dump grabs pks via a bulk pg_index scan based on table oids, so I wanted to rule out some problem there.

I'm chalking this one up to user error, not database corruption, as the OP has not actually shown us the output of how they are determining the missing index, and then how the reindex fixes it (although I appreciate the pg_index query results). To put another way, user error is a much more likely explanation than anything else given the lack of specific data.

Cheers,
Greg

Disclaimer <https://www.kbc.com/KBCmailDisclaimer>