Re: How to continue streaming replication after this error?

On 22/02/14 03:21, Torsten Förtsch wrote:
>> 2014-02-21 05:17:10 UTC PANIC:  heap2_redo: unknown op code 32
>> > 2014-02-21 05:17:10 UTC CONTEXT:  xlog redo UNKNOWN
>> > 2014-02-21 05:17:11 UTC LOG:  startup process (PID 1060) was terminated
>> > by signal 6: Aborted
>> > 2014-02-21 05:17:11 UTC LOG:  terminating any other active server processes
>> > 2014-02-21 05:17:11 UTC WARNING:  terminating connection because of
>> > crash of another server process
>> > 2014-02-21 05:17:11 UTC 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.
>> > 2014-02-21 05:17:11 UTC HINT:  In a moment you should be able to
>> > reconnect to the database and repeat your command.

> Any idea what that means?

Updating the replica to 9.3.3 cured it. The master was already on 9.3.3.

Torsten