From: | Wim Rouquart <wim(dot)rouquart(at)kbc(dot)be> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Index (primary key) corrupt? |
Date: | 2025-09-18 12:25:38 |
Message-ID: | AS2PR05MB1075477BA334D4DA262AD75BFEF16A@AS2PR05MB10754.eurprd05.prod.outlook.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Internal
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?
Are there any other ways to doublecheck for corruption (without enabling checksum upfront)?
This concerns a PostgreSQL version 15 btw.
Thanks!
Disclaimer <https://www.kbc.com/KBCmailDisclaimer>
From | Date | Subject | |
---|---|---|---|
Next Message | R Wahyudi | 2025-09-18 12:58:42 | Re: pg_restore scan |
Previous Message | HORDER Philip | 2025-09-18 09:58:11 | How do I specify the NetworkService user to the postgres installer. |