found xmin x from before relfrozenxid y - Mailing list pgsql-general

From Johannes Graën
Subject found xmin x from before relfrozenxid y
Date
Msg-id 0662ea90-5249-4b8d-faa3-4abe4c88135a@selfnet.de
Whole thread Raw
Responses Re: found xmin x from before relfrozenxid y  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: found xmin x from before relfrozenxid y  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi,

after upgrading to version 11, I see the error pattern "found xmin x
from before relfrozenxid y" in different databases on different hosts.

From https://www.postgresql.org/docs/10/static/release-10-3.html, I
learned that this was an error caused by pg_upgrade, which apparently
had been fixed in 10.3. This page also states that refreshing the
affected materialized view non-concurrently would fix the problem.

My question is now how to infer the affected materialized view from the
error message. Is there a way to tell which one to refresh from the xmin
or relfrozenxid value?

Best
  Johannes


Attachment

pgsql-general by date:

Previous
From: Boris Sagadin
Date:
Subject: Postgres 10, slave not catching up with master
Next
From: Andy Colson
Date:
Subject: Re: Postgres 10, slave not catching up with master