From: | J T <jorge(dot)torralba(at)gmail(dot)com> |
---|---|
To: | "[ADMIN]" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Found xmin before relfrozenxid and logical replication |
Date: | 2021-08-18 14:57:05 |
Message-ID: | CACut7uTcGDM7XZKSkaiLTV7O=6BVehMEn4c0xyDSqmDm_Mbqzg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I am running into an issue on Postgres 13.3 on Centos 7.5
I have done some reading on the web and almost everything points to a bug
back in the 9.x days. However, here is my scenario.
Primary server is PG 10.17
Target server is PG 13.3
On the primary, for testing purposes, the DB is restored from a pg_dump and
just for the heck of it, I vacuumed every table in the primary db manually.
The secondary server i create the schema with a pg_dump using the -c
option. No other databases are on the target since it's a fresh build and
new install. I create a subscription to the publisher on the primary and
all is fine while data is initialized. Eventually all is caught up.
Everything looks normal. But, as I look at my log file for errors on the
replica, I see hundreds of entries for.
2021-08-16 23:58:14.496 CDT [32191] ERROR: found xmin 387485 from before
relfrozenxid 531040
2021-08-16 23:58:31.632 CDT [32204] ERROR: MultiXactId 537919489 has not
been created yet -- apparent wraparound
I cannot vacuum the table on the replica without it erroring out due to the
xmin condition.
Any clues?
--
Thanks,
Jorge Torralba
----------------------------
Note: This communication may contain privileged or other confidential
information. If you are not the intended recipient, please do not print,
copy, retransmit, disseminate or otherwise use the information. Please
indicate to the sender that you have received this email in error and
delete the copy you received. Thank You.
From | Date | Subject | |
---|---|---|---|
Next Message | Vijaykumar Jain | 2021-08-18 15:56:40 | Re: Found xmin before relfrozenxid and logical replication |
Previous Message | Ian Dauncey | 2021-08-18 13:47:35 | Postgres Vacuum failed on space |