This could happen if some tuples were locked (but not deleted). While queries would still function correctly, vacuum would normally ignore such pages, with the long-term effect that the tuples were never frozen. In recent releases this would eventually result in errors such as "found multixact nnnnn from before relminmxid nnnnn".
So basically, he just need to upgrade in order to fix it ? Or there is something else that need to be done?
בתאריך יום ד׳, 23 בינו׳ 2019 ב-21:51 מאת Jerry Sievers <gsievers19@comcast.net>:
> Hey, > I'm trying to help a guy that is using pg9.6 but I'm not so familiar > with the error message : > ERROR: found xmin 16804535 from before relfrozenxid 90126924 > CONTEXT: automatic vacuum of table db1.public.table_1"
9.6.?...
That error or a very similar one was fixed in a recent point release.