| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | v(dot)badalyan(at)open-bs(dot)ru, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17444: ERROR: found xmin 215633 from before relfrozenxid 1280585 |
| Date: | 2022-03-24 09:05:24 |
| Message-ID: | E64456F5-A481-4E34-97BC-41FF757F2BA8@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi!
> 21 марта 2022 г., в 18:08, PG Bug reporting form <noreply(at)postgresql(dot)org> написал(а):
>
>
> If i try vacum
> STATEMENT: VACUUM (VERBOSE) public.projects_tables_values;
> ERROR: found xmin 215633 from before relfrozenxid 1280585
> CONTEXT: while scanning block 63286 offset 11 of relation
> "public.projects_tables_values"
This seems like a data corruption.
Do you have data_checksums enabled? Did you have and HW failures you your block storage device?
I'd recommend making a physical backup of a database and trying your luck with pg_surgery\pg_dirty_hands.
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2022-03-24 11:55:41 | Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join |
| Previous Message | Masahiko Sawada | 2022-03-23 08:48:43 | Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end |