| From: | Floris Van Nee <florisvannee(at)Optiver(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: visibility map corruption |
| Date: | 2021-07-04 21:26:00 |
| Message-ID: | 679a6e4661fa436388f71168ad3154b4@opammb0562.comp.optiver.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?
>
Yes. The last time (from v11 to v12) was in October 2020. The transaction id in the tuples (the one PG is trying to check in the tx log) dated from February 2021. I do believe (but am not 100% certain) that the affected table already existed at the time of the last pg_upgrade though.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-07-04 21:52:07 | Re: visibility map corruption |
| Previous Message | Noah Misch | 2021-07-04 21:12:34 | Re: "debug_invalidate_system_caches_always" is too long |