From: | molofeev <molofeev3(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |
Date: | 2018-04-04 10:42:21 |
Message-ID: | 8d5c7a24-183e-552c-ee3e-d9c18c6c63a9@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thank you for reply.
> The bigger question is how
> many other such cases are there.
I can get data from table only before tuple #162, after that all queries
(for example getting tuple 163, 164 ... etc) return error.
Table contain openstreatmap data, maybe errors occurs because when i was
creating necessary indexes for table, happened server crash and I
relaunch indexes creation.
From | Date | Subject | |
---|---|---|---|
Next Message | molofeev | 2018-04-04 11:31:59 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |
Previous Message | Tomas Vondra | 2018-04-04 09:22:26 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |