slave restarts with kill -9 coming from somewhere, or nowhere

Hello,

I'm running the latest postgres version (9.2.3), and today for the first
time I encountered this:

12774 2013-04-02 18:13:10 CEST LOG: server process (PID 28463) was
terminated by signal 9: Killed
12774 2013-04-02 18:13:10 CEST DETAIL: Failed process was running:
BEGIN;declare "SQL_CUR0xff25e80" cursor for select distinct .... as
"Reservation_date___time" , "C_4F_TRANSACTION"."FTRA_PRICE_VAL
12774 2013-04-02 18:13:10 CEST LOG: terminating any other active server
processes
12774 2013-04-02 18:13:12 CEST LOG: all server processes terminated;
reinitializing
29113 2013-04-02 18:13:15 CEST LOG: database system was interrupted while
in recovery at log time 2013-04-02 18:02:21 CEST
29113 2013-04-02 18:13:15 CEST HINT: If this has occurred more than once
some data might be corrupted and you might need to choose an earlier
recovery target.
29113 2013-04-02 18:13:15 CEST LOG: entering standby mode
29113 2013-04-02 18:13:15 CEST LOG: redo starts at 6B0/DD0928A0
29113 2013-04-02 18:13:22 CEST LOG: consistent recovery state reached at
6B0/DE3831E8
12774 2013-04-02 18:13:22 CEST LOG: database system is ready to accept
read only connections
29113 2013-04-02 18:13:22 CEST LOG: invalid record length at 6B0/DE3859B8
29117 2013-04-02 18:13:22 CEST LOG: streaming replication successfully
connected to primary

for as far as I know it happened twice today. I have no idea where these
kills are coming from. I only know thse are not nice :)

Does anyone has an idea what happened exactly?

wkr,
Bert

--
Bert Desmet
0477/305361