On Tue, Apr 10, 2018 at 4:31 AM, Alexandre Arruda <adald...@gmail.com> wrote:
> Actualy, I first notice the problem in logs by autovacuum:
> 2018-04-10 08:22:15.385 -03  CONTEXT: automatic vacuum of
> table "production.public.fn06t"
> 2018-04-10 08:22:16.815 -03  ERROR: found multixact 68834765
> from before relminmxid 73262006
> production=# vacuum analyze verbose fn06t;
> INFO: vacuuming "public.fn06t"
> ERROR: found multixact 76440919 from before relminmxid 122128619
Do you think that CLUSTER was run before regular VACUUM/autovacuum
showed this error, though?
Have you noticed any data loss? Things look okay when you do your dump
+ restore, right? The problem, as far as you know, is strictly that
CLUSTER + VACUUM refuse to finish/raise these multixactid errors?