Error Postgresql 9.3.4 - Mailing list pgsql-admin

From ALEXANDER JOSE
Subject Error Postgresql 9.3.4
Date
Msg-id BAY180-W1323A376B767CEEDD86BD8A5390@phx.gbl
Whole thread Raw
List pgsql-admin
Hi, I'm DBA postgresql, I have a platform to cluster in Debian OS 7.4, postgresql 9.3.4 pgpool2 with streaming replication, I need to know if alquien community have experience with the following error;

2015-02-07 00:00:29.600 VET [31946] LOCATION:  log_disconnections, postgres.c:4434
2015-02-07 00:00:31.573 VET [19316] <:@>FATAL:  XX000: unexpected data beyond EOF in block 0 of relation base/16495/23997
2015-02-07 00:00:31.573 VET [19316] <:@>HINT:  This has been seen to occur with buggy kernels; consider updating your system.
2015-02-07 00:00:31.573 VET [19316] <:@>CONTEXT:  xlog redo insert(init): rel 1663/16495/23997; tid 0/1
2015-02-07 00:00:31.573 VET [19316] <:@>LOCATION:  ReadBuffer_common, bufmgr.c:387
2015-02-07 00:00:32.669 VET [19314] <:@>LOG:  00000: startup process (PID 19316) exited with exit code 1
2015-02-07 00:00:32.669 VET [19314] <:@>LOCATION:  LogChildExit, postmaster.c:3220
2015-02-07 00:00:32.669 VET [19314] <:@>LOG:  00000: terminating any other active server processes
2015-02-07 00:00:32.669 VET [19314] <:@>LOCATION:  HandleChildCrash, postmaster.c:2973
2015-02-07 00:00:32.669 VET [24464] WARNING:  57P02: terminating connection because of crash of another server process
2015-02-07 00:00:32.669 VET [24464] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2015-02-07 00:00:32.669 VET [24464] HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2015-02-07 00:00:32.669 VET [24464] LOCATION:  quickdie, postgres.c:2555
2015-02-07 00:00:32.669 VET [31898] WARNING:  57P02: terminating connection because of crash of another server process
2015-02-07 00:00:32.669 VET [31898] DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.


Raise the fallen database node, select the pgpool2 and a recovery pcp reestablished the replication.

Thank You.

Alexander
DAB Postgresql

pgsql-admin by date:

Previous
From: Jerry Sievers
Date:
Subject: Re: Hourly backup using pg_basebackup
Next
From: Nino Arsov
Date:
Subject: Fwd: Estimating the execution cost of a query in a partitioned schema: Weird execution plans and totally wrong execution costs (pg_class and pg_statistic)