Re: visibility map corruption

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Floris Van Nee <florisvannee(at)optiver(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: visibility map corruption
Date: 2021-07-04 20:51:39
Message-ID: CAH2-Wzmm=zjQpO1JM7RCc3SwknBBcg60b-9-1c8u98Fu+NPnXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 4, 2021 at 1:44 PM Floris Van Nee <florisvannee(at)optiver(dot)com> wrote:
> We recently ran into an issue where the visibility map of a relation was corrupt, running Postgres 12.4. The error we'd get 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2021-07-04 21:12:34 Re: "debug_invalidate_system_caches_always" is too long
Previous Message Floris Van Nee 2021-07-04 20:43:50 visibility map corruption