Re: corruption issue after server crash - ERROR: unexpected chunk number 0

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Date: 2013-11-21 23:14:30
Message-ID: 528E93D6.9050901@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/21/2013 2:51 PM, Kevin Grittner wrote:
> That leaves three possibilities:
> (1) fsync doesn't actually guarantee persistence in your stack.

I'll put my $5 on (1).... virtualization stacks add way too much
ooga-booga to the storage stack, and tend to play fast and loose with
write buffering to maintain some semblence of performance.

--
john r pierce 37N 122W
somewhere on the middle of the left coast

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ken Tanzer 2013-11-22 00:29:53 Re: Getting non_NULL right-side values on a non-matching join?
Previous Message Kevin Grittner 2013-11-21 23:09:55 Re: corruption issue after server crash - ERROR: unexpected chunk number 0