Re: corruption issue after server crash - ERROR: unexpected chunk number 0 - Mailing list pgsql-general

From John R Pierce
Subject Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Date
Msg-id 528E93D6.9050901@hogranch.com
Whole thread Raw
In response to Re: corruption issue after server crash - ERROR: unexpected chunk number 0  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: corruption issue after server crash - ERROR: unexpected chunk number 0
List 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



pgsql-general by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Next
From: Ken Tanzer
Date:
Subject: Re: Getting non_NULL right-side values on a non-matching join?