| From: | Alexandre Arruda <adaldeia(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Cc: | Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: ERROR: found multixact from before relminmxid |
| Date: | 2018-06-06 01:42:02 |
| Message-ID: | CAGewt-v-5x-MLDObako+QkkZs83uR9DzXHvz5H2=6=XGYcw+ZA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Em seg, 28 de mai de 2018 às 16:44, Andres Freund <andres(at)anarazel(dot)de> escreveu:
>
> Hi,
>
> I think I found the bug, and am about to post a fix for it belo
> https://postgr.es/m/20180525203736.crkbg36muzxrjj5e@alap3.anarazel.de.
>
> Greetings,
>
> Andres Freund
Hi Andres,
In end of April we did a complete dump/reload in database to version 10.3.
Today, the problem returns:
production=# vacuum verbose co27t;
INFO: vacuuming "public.co27t"
ERROR: found multixact 81704071 from before relminmxid 107665371
production=# vacuum full verbose co27t;
INFO: vacuuming "public.co27t"
ERROR: found multixact 105476076 from before relminmxid 107665371
production=# cluster co27t;
ERROR: found multixact 105476076 from before relminmxid 107665371
But this time, regular vacuum versus full/cluster are different in
multixact number.
Your patch is applicable to this issue and is in 10.4 ?
Best regards,
Alexandre
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2018-06-06 01:49:40 | Re: Code of Conduct plan |
| Previous Message | David G. Johnston | 2018-06-06 01:04:39 | Re: pg_stats avg_width and null_frac |