| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | molofeev <molofeev3(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, 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 14:57:08 |
| Message-ID: | 87fu49k8k1.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>>>>> "molofeev" == molofeev <molofeev3(at)gmail(dot)com> writes:
>> You said a server crash occurred while you were creating indexes. Was
>> that a hard crash (power failure, etc.) and is it possible that you had
>> fsync disabled in postgresql.conf, or hardware or filesystems that don't
>> respect fsync properly?
molofeev> That was not hard crash, and fsync was disabled.
molofeev> I was disconnected form remote terminal, which was performing
molofeev> creating indexes from sql file.
Just being disconnected remotely (for some reason other than a server
crash) isn't enough to account for the corruption; fsync=off only results
in corrupt data if there is an actual OS-level crash or unclean shutdown.
So I wouldn't rule out the possibility of hardware or storage subsystem
problems.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2018-04-05 20:29:38 | Re: BUG #14941: Vacuum crashes |
| Previous Message | molofeev | 2018-04-05 12:16:23 | Re: BUG #15142: ERROR: MultiXactId nnnnn has not been created yet -- apparent wraparound in v9.5 |