Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5

From: molofeev <molofeev3(at)gmail(dot)com>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, 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-05 11:46:57
Message-ID: 6e589f1d-851e-790b-b9d0-fcbf9835154c@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> 4. Obviously the data in the corrupted block is not easily recoverable.
> If you need to recover the remaining data in the table, it could
> probably best be done by zeroing only this specific block. Whether this
> is worth doing will depend on whether it would be easier to just
> recreate the data.
If fsync was disabled when I work with table, can I restore block
3220146 (by zeroing or maybe remove it)?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message molofeev 2018-04-05 11:48:11 Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5
Previous Message molofeev 2018-04-05 07:02:35 Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5