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

2015-03-02 23:21 GMT+08:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:

> On 03/02/2015 02:49 AM, hailong Li wrote:
>
>>
>>
>> Hi, dear pgsql-general
>>
>>
>> The details are as follows:
>>
>> *1. environment*
>>
>> *DB Master*
>>
>> $ cat /etc/issue
>> CentOS release 6.5 (Final)
>> Kernel \r on an \m
>>
>> $ uname -av
>> Linux l-xxxxx1.xx.cnx 3.14.29-3.centos6.x86_64 #1 SMP Tue Jan 20
>> 17:48:32 CST 2015 x86_64 x86_64 x86_64 GNU/Linux
>>
>> $ psql -U postgres
>> psql (9.3.5)
>> Type "help" for help.
>>
>> postgres=# select version();
>> version
>> ------------------------------------------------------------
>> --------------------------------------------------
>> PostgreSQL 9.3.5 on x86_64-unknown-linux-gnu, compiled by gcc (GCC)
>> 4.4.7 20120313 (Red Hat 4.4.7-3), 64-bit
>> (1 row)
>>
>>
>
>> *DB Slave
>>
>> *$ cat /etc/issue
>> CentOS release 6.5 (Final)
>> Kernel \r on an \m
>>
>> $ uname -av
>> Linux l-xxxx2.xx.cnx 3.14.31-3.centos6.x86_64 #1 SMP Mon Feb 2 15:26:04
>> CST 2015 x86_64 x86_64 x86_64 GNU/Linux*
>> *
>> $ psql -U postgres
>> psql (9.3.5)
>> Type "help" for help.
>>
>> postgres=# select version();
>> version
>> ------------------------------------------------------------
>> --------------------------------------------------
>> PostgreSQL 9.3.5 on x86_64-unknown-linux-gnu, compiled by gcc (GCC)
>> 4.4.7 20120313 (Red Hat 4.4.7-3), 64-bit
>> (1 row)
>>
>>
>
>> *The salve was running, but stopped suddenly , and I never start it !
>>
>> Anyone encounter the same problem? Could tell me why and how to avoid it?
>>
>> If you need some more detailed information, please tell me and I'll give
>> it to you.
>>
>
> So what sort of replication(streaming, archiving, synchronous,etc) where
> you doing?
>

streaminig

>
> Was the streaming happening across a local network or a remote network?
>

local network

>
> Was there a hardware issue on either of the machines?
>

I did not find anything wrong with a hardware issue on either of the
machines at that time, but there is some data on the tablespace which is
located on the SSD of the master machine .

psql -U postgres
psql (9.3.5)
Type "help" for help.

postgres=# \db+
List of tablespaces
Name | Owner | Location | Access privileges | Description
------------+----------+---------------+-------------------+-------------
pg_default | postgres | | |
pg_global | postgres | | |
pgtblspc | laser | /ssd/pgtblspc | |
(3 rows)

Finally , I made a new slave instance on the slave server and it works
fine until now.

>
>>
>> Thanks
>>
>> Best Regards!
>>
>>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>