| From: | Johannes Graën <johannes(at)selfnet(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | found xmin x from before relfrozenxid y |
| Date: | 2018-10-21 09:27:20 |
| Message-ID: | 0662ea90-5249-4b8d-faa3-4abe4c88135a@selfnet.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Colson | 2018-10-21 13:52:50 | Re: Postgres 10, slave not catching up with master |
| Previous Message | Boris Sagadin | 2018-10-21 07:06:31 | Postgres 10, slave not catching up with master |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-10-21 13:42:06 | More issues with pg_verify_checksums and checksum verification in base backups |
| Previous Message | David Rowley | 2018-10-20 21:15:31 | Re: Multi-insert into a partitioned table with before insert row trigger causes server crash on latest HEAD |