Re: Index (primary key) corrupt?
Ron Johnson <ronljohnsonjr@gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
To: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2025-09-18T15:50:18Z
Lists: pgsql-general
On Thu, Sep 18, 2025 at 10:58 AM Wim Rouquart <wim.rouquart@kbc.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!