Re: The slave suddenly stopped with such DB log : "will not overwrite a used ItemId" and "heap_insert_redo: failed to add tuple"

From: hailong Li <shuhujiaolong(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: The slave suddenly stopped with such DB log : "will not overwrite a used ItemId" and "heap_insert_redo: failed to add tuple"
Date: 2015-03-10 11:17:22
Message-ID: CAELgjyBjZE96sy7EoxvyC0O9Kn1j3+jCZy9Os2fNyh_vQgmrTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2015-03-05 16:34 GMT+08:00 Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>:

> On 3/3/15 6:52 AM, hailong Li wrote:
>
>>
>> Finally , I made a new slave instance on the slave server and it works
>> fine until now.
>>
>
> Just so you're aware, that error means there was page level corruption
> either on the replica or possibly on the master, or the replication stream
> or WAL files got corrupted. You probably have either a hardware or a
> configuration problem somewhere.
>

Actually there were 3 slave nodes of the same master， and they stopped
nearly at the same time. So, I prefer page level corruption on the master
to the slaves, and SSD hardware to configuration problem somewhere.

> --
> Jim Nasby, Data Architect, Blue Treble Consulting
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message PT 2015-03-10 12:18:40 Re: Strange security issue with Superuser access
Previous Message Andrzej Pilacik 2015-03-09 21:00:14 Strange security issue with Superuser access