Gabriel Sánchez Martínez wrote:
> Any suggestions on what sanity checks I should run? For now I am
> doing reindex and vacuum. I think that forces everything to be read. I
> am assuming that if vacuum completes without error then the table is
> fine.
The main sanity check is to make sure the di
> On Nov 17, 2014, at 8:10, Gabriel Sánchez Martínez
> wrote:
>
>
>
>> On Nov 17, 2014, at 3:28, Raghu Ram wrote:
>>
>>> On Mon, Nov 17, 2014 at 10:20 AM, Gabriel Sánchez Martínez
>>> wrote:
>>>
>>> The situation appears to be stable now, but upon running REINDEX and VACUUM
>>> on one
> On Nov 17, 2014, at 3:28, Raghu Ram wrote:
>
>> On Mon, Nov 17, 2014 at 10:20 AM, Gabriel Sánchez Martínez
>> wrote:
>>
>> The situation appears to be stable now, but upon running REINDEX and VACUUM
>> on one of the databases, I get the following:
>>
>> WARNING: relation "pg_attrdef" TI
On Mon, Nov 17, 2014 at 10:20 AM, Gabriel Sánchez Martínez <
gabrielesanc...@gmail.com> wrote:
>
> The situation appears to be stable now, but upon running REINDEX and
> VACUUM on one of the databases, I get the following:
>
> WARNING: relation "pg_attrdef" TID 1/1: OID is invalid
> WARNING: rel
I'm running PostgreSQL 9.3.5 on Ubuntu 14.04 on x86_64. The database
directory is on linux mdadm RAID10, using 4 4TB disks and a far=2
layout. While the RAID tolerates 1 drive failure nicely, I had the
misfortune of 2 drives failing consecutively, one of which had many
sectors reallocated and
