Re: Tracking down log segment corruption

I just got ran into the same problem. Both servers are running 8.4.3, and
the standby server had been running for 2 days, processing many thousands of
logs successfully. Here's my error:

4158 2010-05-02 11:12:09 EDT [26445]LOG: restored log file
"0000000100003C77000000C3" from archive
4158 2010-05-02 11:12:09 EDT [26446]LOG: restored log file
"0000000100003C77000000C4" from archive
4158 2010-05-02 11:12:09 EDT [26447]WARNING: specified item offset is too
large
4158 2010-05-02 11:12:09 EDT [26448]CONTEXT: xlog redo insert: rel
48777166/22362/48778276; tid 2/2
4158 2010-05-02 11:12:09 EDT [26449]PANIC: btree_insert_redo: failed to
add item
4158 2010-05-02 11:12:09 EDT [26450]CONTEXT: xlog redo insert: rel
48777166/22362/48778276; tid 2/2
4151 2010-05-02 11:12:09 EDT [1]LOG: startup process (PID 4158) was
terminated by signal 6: Aborted
4151 2010-05-02 11:12:09 EDT [2]LOG: terminating any other active server
processes

Any suggestions?

Charles Duffy-5 wrote:
>
>
> [14-1] LOG: restored log file "000000010000001400000010" from archive
> [15-1] WARNING: specified item offset is too large
> [15-2] CONTEXT: xlog redo insert_upper: rel 1663/16384/17763; tid 2960/89
> [16-1] PANIC: btree_insert_redo: failed to add item
> [16-2] CONTEXT: xlog redo insert_upper: rel 1663/16384/17763; tid 2960/89
> [1-1] LOG: startup process (PID 17310) was terminated by signal 6:
> Aborted
> [2-1] LOG: aborting startup due to startup process failure
>
>

--
View this message in context: http://old.nabble.com/Tracking-down-log-segment-corruption-tp21121136p28427922.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.