9.2.4 specified item offset is too large, now what? - Mailing list pgsql-performance

From Tory M Blue
Subject 9.2.4 specified item offset is too large, now what?
Date
Msg-id CAEaSS0afNB6YKSB-W-GNhVWpOFTTONs25ibzoaXBoNwh3pW8sw@mail.gmail.com
Whole thread Raw
List pgsql-performance
So I recently had some corruption, that forced a rebuild. At that time i upgraded to my current release of 9.2.4 (stable in production for a time and I know it's not the latest greatest).

So reloaded data, started loading more, things were good, several reboots etc no issues.

This morning the system crashed again (so there may be some hardware issues). But for now I need again ask if there is something in code I can do vs a complete rebuild again.

014-02-26 07:09:16 PST    LOG:  database system was interrupted while in recovery at 2014-02-26 07:05:09 PST
2014-02-26 07:09:16 PST    HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.
2014-02-26 07:09:16 PST    LOG:  database system was not properly shut down; automatic recovery in progress
2014-02-26 07:09:16 PST    LOG:  redo starts at 9A/89505268
2014-02-26 07:09:16 PST    WARNING:  specified item offset is too large
2014-02-26 07:09:16 PST    CONTEXT:  xlog redo insert: rel 16398/16384/12765884; tid 9943/137
2014-02-26 07:09:16 PST    PANIC:  btree_insert_redo: failed to add item
2014-02-26 07:09:16 PST    CONTEXT:  xlog redo insert: rel 16398/16384/12765884; tid 9943/137
2014-02-26 07:09:16 PST    LOG:  startup process (PID 2391) was terminated by signal 6: Aborted
2014-02-26 07:09:16 PST    LOG:  aborting startup due to startup process failure
thanks again
Tory

pgsql-performance by date:

Previous
From: Бородин Владимир
Date:
Subject: Re: Problem with ExclusiveLock on inserts
Next
From: "acanada"
Date:
Subject: Query taking long time