Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC) - Mailing list pgsql-bugs

From Greg Sabino Mullane
Subject Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
Date
Msg-id CAKAnmmKJ23WVRXQLgpK1ososBd-LAmLp33yidUJUG_w2vTXXXw@mail.gmail.com
Whole thread Raw
In response to [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)  ("第108次明天" <87326549@qq.com>)
List pgsql-bugs
  • PostgreSQL Version: 14.5

That is way too old. Upgrade to 14.20

or guide further troubleshooting?

Run the pg_checksums program to get a handle on the extent of the corruption

https://www.postgresql.org/docs/14/app-pgchecksums.html

Database backups are affected by corrupted data.

I assume you are not using a good backup system then. pgBackRest, for example, will not only check for corrupted pages during the backup, but report on it and allow the backup to proceed.

 

pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
Next
From: PG Bug reporting form
Date:
Subject: BUG #19359: Row level security: Upserts require insert policies in the update path