| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | molofeev <molofeev3(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, 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-05 12:11:29 |
| Message-ID: | baa2c00a-6be2-f909-1a4f-9d7a6495b615@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 4/5/18 1:46 PM, molofeev wrote:
>
>> 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)?
Honestly, if you've disabled fsync and it crashed, then all bets are off
and the best thing you can do is rebuilding the database. This is hardly
the only corrupted block.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | molofeev | 2018-04-05 12:16:23 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |
| Previous Message | molofeev | 2018-04-05 11:48:11 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |