From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | marc(dot)morad(at)gmail(dot)com |
Subject: | BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM |
Date: | 2023-05-17 09:42:26 |
Message-ID: | 17937-c93266adaef384ff@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17937
Logged by: Marc Morad
Email address: marc(dot)morad(at)gmail(dot)com
PostgreSQL version: 13.8
Operating system: Alma 8
Description:
This problem occured on PostgreSQL version 13.8 and 14.7.
After we migrated the VM from CentOS 7 to AlmaLinux 8, we had a few issues
with broken/corrupt indexes. This problem occured a total of 3 times. Each
time the procedure of the migration was exactly the same.
We are using a DRBD device to store our database redundantly, which we
reused when we migrated to AlmaLinux 8.
The error messages all looked very similar to the following:
Database error: [S]ERROR#012[V]ERROR#012[C]XX002#012[M]table tid from new
index tuple (3346213,70) cannot find insert offset between offsets 2 and 4
of block 5485 in index
Have you ever heard of a similiar problem ?
Any leads what might cause these problems would be very helpful.
Thank you and kind regards,
Marc
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-05-17 12:41:00 | Re: AW: BUG #17923: Excessive warnings of collation version mismatch in logs |
Previous Message | Richard Guo | 2023-05-17 08:29:54 | Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware) |