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

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: 第108次明天 <87326549(at)qq(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
Date: 2025-12-18 13:30:51
Message-ID: CAKAnmmKJ23WVRXQLgpK1ososBd-LAmLp33yidUJUG_w2vTXXXw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-bugs by date

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