| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alexandre Arruda <adaldeia(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: ERROR: found multixact from before relminmxid |
| Date: | 2018-04-10 22:09:21 |
| Message-ID: | CAH2-WzmQ1cQviL=LD9HoSw3gD+5EPQLmh7fjUTCQxkDHoGSaRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 10, 2018 at 4:31 AM, Alexandre Arruda <adaldeia(at)gmail(dot)com> wrote:
> Actualy, I first notice the problem in logs by autovacuum:
>
> 2018-04-10 08:22:15.385 -03 [55477] CONTEXT: automatic vacuum of
> table "production.public.fn06t"
> 2018-04-10 08:22:16.815 -03 [55477] 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?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PT | 2018-04-10 22:48:58 | Re: Using enum instead of join tables |
| Previous Message | Jehan-Guillaume (ioguix) de Rorthais | 2018-04-10 19:19:30 | Re: Postgresql Split Brain: Which one is latest |