Re: Index (primary key) corrupt?

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Index (primary key) corrupt?
Date: 2025-09-18 15:50:18
Message-ID: CANzqJaBSwogwtOjLz+UVnxn286G7xcnWjYvOYdeos2Je7uVHWw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 18, 2025 at 10:58 AM Wim Rouquart <wim(dot)rouquart(at)kbc(dot)be> wrote:

> Hello,
>
>
> When doing a pg_dump of one of our databases one of the tables primary
> keys doesn’t get exported. Pg_dump just skips this index, without any
> warning whatsoever (verbose mode was used to doublecheck).
>
>
>
> When doing a REINDEX the issue is fixed.
>
>
>
> As this seems to me to be some form of index corruption, I tried using
> amcheck (bt_index_check and bt_index_parent_check) to verify for corruption
> but both resulted with no issues (the index is a btree).
>
>
>
> I would expect the corruption to show up when using amcheck, am I hitting
> some kind of bug here?
>

Does this problem keep happening, or has it only happened once?

> Are there any other ways to doublecheck for corruption (without enabling
> checksum upfront)?
>

pg_checksums is available in PG 15.

> This concerns a PostgreSQL version 15 btw.
>

Are you at the current patch level?

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2025-09-18 15:54:32 Re: pg_restore scan
Previous Message Ron Johnson 2025-09-18 14:09:13 Re: pg_restore scan