pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM 2+ messages / 2 participants [nested] [flat]
* BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM @ 2023-05-17 09:42 PG Bug reporting form <noreply@postgresql.org> 2023-05-17 13:27 ` Re: BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM Joe Conway <mail@joeconway.com> 0 siblings, 1 reply; 2+ messages in thread From: PG Bug reporting form @ 2023-05-17 09:42 UTC (permalink / raw) To: pgsql-bugs@lists.postgresql.org; +Cc: marc.morad@gmail.com The following bug has been logged on the website: Bug reference: 17937 Logged by: Marc Morad Email address: marc.morad@gmail.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 ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM 2023-05-17 09:42 BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM PG Bug reporting form <noreply@postgresql.org> @ 2023-05-17 13:27 ` Joe Conway <mail@joeconway.com> 0 siblings, 0 replies; 2+ messages in thread From: Joe Conway @ 2023-05-17 13:27 UTC (permalink / raw) To: marc.morad@gmail.com; pgsql-bugs@lists.postgresql.org On 5/17/23 05:42, PG Bug reporting form wrote: > 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 > 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. CentOS 7 is glibc 2.17 AlmaLinux 8 is glibc 2.28 There are known issues with glibc upgrades (in particular 2.28, but also in general) causing collation changes which break all indexes which use glibc collations (basically text, varchar, char). You need to rebuild them, preferably before allowing *any* write activity (inserts or updates). -- Joe Conway PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2023-05-17 13:27 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2023-05-17 09:42 BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM PG Bug reporting form <noreply@postgresql.org> 2023-05-17 13:27 ` Joe Conway <mail@joeconway.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox