Re: visibility map corruption - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: visibility map corruption
Date
Msg-id CAH2-Wzmm=zjQpO1JM7RCc3SwknBBcg60b-9-1c8u98Fu+NPnXA@mail.gmail.com
Whole thread Raw
In response to visibility map corruption  (Floris Van Nee <florisvannee@Optiver.com>)
Responses RE: visibility map corruption  (Floris Van Nee <florisvannee@Optiver.com>)
List pgsql-hackers
On Sun, Jul 4, 2021 at 1:44 PM Floris Van Nee <florisvannee@optiver.com> wrote:
> We recently ran into an issue where the visibility map of a relation was corrupt, running Postgres 12.4. The error
we'dget when running a SELECT * from this table is:
 
>
> could not access status of transaction 3704450152
> DETAIL:  Could not open file "pg_xact/0DCC": No such file or directory.

Have you ever used pg_upgrade on this database?

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Floris Van Nee
Date:
Subject: visibility map corruption
Next
From: Noah Misch
Date:
Subject: Re: "debug_invalidate_system_caches_always" is too long