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

From Scott Marlowe
Subject Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Date
Msg-id CAOR=d=1R9Wk_LSG0aY+VB9+oMKY7mgbDxJ5KoU5uQ48e2b0nPw@mail.gmail.com
Whole thread Raw
In response to Re: corruption issue after server crash - ERROR: unexpected chunk number 0  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
On Thu, Nov 21, 2013 at 4:14 PM, John R Pierce <pierce@hogranch.com> wrote:
> 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.

If you really hate your database, be sure and include an NFS mount at
the vm image level in there somewhere.


pgsql-general by date:

Previous
From: Joe Van Dyk
Date:
Subject: Re: Changing function from SECURITY DEFINER to SECURITY INVOKER changes query plan?
Next
From: Peter Eisentraut
Date:
Subject: Re: Does LC_CTYPE affect performance, index use?