RE: Index (primary key) corrupt?
| От | Wim Rouquart |
|---|---|
| Тема | RE: Index (primary key) corrupt? |
| Дата | |
| Msg-id | AS2PR05MB107548809A37E7DCC694EC7C2EF11A@AS2PR05MB10754.eurprd05.prod.outlook.com обсуждение исходный текст |
| Ответ на | Re: Index (primary key) corrupt? (Ron Johnson <ronljohnsonjr@gmail.com>) |
| Ответы |
Re: Index (primary key) corrupt?
Re: Index (primary key) corrupt? |
| Список | 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?
>> Does this problem keep happening, or has it only happened once?
It is consistent on this database/index, haven’t noticed it anywhere else yet luckily. Seems to be a one-off.
Are there any other ways to doublecheck for corruption (without enabling checksum upfront)?
>> pg_checksums is available in PG 15.
It is indeed, so to test I enabled checksums, and did a checksum test, no errors, and yes, the file containing the index is mentioned in the checks…
This concerns a PostgreSQL version 15 btw.
>> Are you at the current patch level?
Yes.
Disclaimer
В списке pgsql-general по дате отправления: