From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | phil(dot)hildebrand(at)moz(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
Date: | 2019-01-01 00:43:43 |
Message-ID: | 201901010043.hecfwnmygqlh@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2018-Dec-31, PG Bug reporting form wrote:
> Both selects against and pg_dumps of the table fail with the same error.
>
> We were able narrow down the selects to at least one row / page that seems
> to have problems:
>
> select ctid,id from reviews_2018 where ctid = '(382604,16)'::tid;
> ctid | id
> -------------+----------------------------------
> (382604,16) | 00ec91e42d21ce0b818fe8f63ab94c66
>
> select ctid,id from reviews_2018 where id =
> '00ec91e42d21ce0b818fe8f63ab94c66';
> ERROR: MultiXactId 1483293027 has not been created yet -- apparent
> wraparound
Can you please send
select lp, lp_flags, t_xmin, t_xmax, t_field3, t_ctid,
to_hex(t_infomask) as infomask, to_hex(t_infomask2) as infomask2
from heap_page_items(get_raw_page('reviews_2018', 382604)) h;
Also, please send the output of pg_controldata.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Phil Hildebrand | 2019-01-01 01:09:25 | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
Previous Message | PG Bug reporting form | 2018-12-31 21:37:54 | BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |