Re: Corrupted Data ? - Mailing list pgsql-general

From Francisco Olarte
Subject Re: Corrupted Data ?
Date
Msg-id CA+bJJbyVijaC1C_-fSqpjc-GU_f=kc5ei_dg5SiqDkT3Vnvthw@mail.gmail.com
Whole thread Raw
In response to Re: Corrupted Data ?  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Hi Adrian:

On Fri, Aug 12, 2016 at 9:01 PM, Adrian Klaver
<adrian.klaver@aklaver.com> wrote:
> "Specially if this happens, you may have some slightly bad disks/ram/
> leading to this kind of problems."
>
> Trying to reconcile that with all the physical machine 1 VMs sharing the
> same RAM and physical disk, but the error only occurring on db3.
>
> Is the VM hosting db3 setup different from the VMs 1 & 2?

They probably share the disk, bus, ram and disk controllers, but they
surely do not share the disk SECTORS. "Weak" ( nearly failing ) tracks
can give this kind of problems ( although the disk CRC should catch
all odd number of bit errors , but with VMs in the mix who knows where
the messages could end up ).

Francisco Olarte.


pgsql-general by date:

Previous
From: Patrick B
Date:
Subject: Re: PK Index - Removal
Next
From: Francisco Olarte
Date:
Subject: Re: Any reasons for 'DO' statement not returning result?