From: | molofeev <molofeev3(at)gmail(dot)com> |
---|---|
To: | 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-03 13:36:45 |
Message-ID: | 8883c05f-a737-5a14-301b-06d469ff9853@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The last query that working is - select * from TABLE_NAME limit 1 offset
160;
the next query
select * from TABLE_NAME limit 1 offset 162;
return - ERROR: MultiXactId 1048586 has not been created yet -- apparent
wraparound
SQL state: XX000
On 04/03/2018 04:23 PM, Alvaro Herrera wrote:
> molofeev wrote:
>> Thank you for reply.
>> Output of pg_controldata:
>>
>> Latest checkpoint's NextMultiXactId: 1
>> Latest checkpoint's NextMultiOffset: 0
> Uh, this says that this cluster has never used any multixacts.
>
>> Output of [select datminmxid from pg_database where datname =
>> current_database();]:
>>
>> datminmxid
>> ------------
>> 1
> ... and this confirms.
>
> I think the easiest way forward is to identify the problem page and see
> what's there. Please find what command was being run that caused the
> error, which might help narrow down which table it is; then scan the
> table to see on which page you can see the error.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Sergei Kornilov | 2018-04-03 14:07:01 | Re: autovacuum can not remove dead tuples |
Previous Message | Alvaro Herrera | 2018-04-03 13:23:19 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |