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

Поиск
Список
Период
Сортировка
От John R Pierce
Тема Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Дата
Msg-id 528E93D6.9050901@hogranch.com
обсуждение исходный текст
Ответ на Re: corruption issue after server crash - ERROR: unexpected chunk number 0  (Kevin Grittner <kgrittn@ymail.com>)
Ответы Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Список 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 по дате отправления:

Предыдущее
От: Kevin Grittner
Дата:
Сообщение: Re: corruption issue after server crash - ERROR: unexpected chunk number 0
Следующее
От: Ken Tanzer
Дата:
Сообщение: Re: Getting non_NULL right-side values on a non-matching join?