Re: Index (primary key) corrupt?

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
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" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Index (primary key) corrupt?
Date: 2026-03-09 17:53:39
Message-ID: CAKAnmmJzw9TeOd=_VtJ430_AhS+asfRLuOg=mgL0yT_K+7X-yQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Mar 9, 2026 at 11:37 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> This post in answer:
>
>
> https://www.postgresql.org/message-id/AS2PR05MB107549DDE42DC0B8E31CB52BFEF90A%40AS2PR05MB10754.eurprd05.prod.outlook.com
>
> would seem to indicate that is not the issue.
>

Ah, but those are doing the lookup by the index (via indexrelid) but I am
curious about looking up by the table (indrelid), as that is how pg_dump is
going to get at it.

Cheers,
Greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2026-03-09 19:52:59 Re: Index (primary key) corrupt?
Previous Message Shaheed Haque 2026-03-09 17:21:43 Re: Unexpected deadlock across two separate rows, using Postgres 17 and Django's select_for_update()