SOLVED: Corrupted index file after restoring WAL on warm spare server

From: "Michael Nolan" <htfoot(at)gmail(dot)com>
To: "pgsql general" <pgsql-general(at)postgresql(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: SOLVED: Corrupted index file after restoring WAL on warm spare server
Date: 2007-05-27 05:49:17
Message-ID: 4abad0eb0705262249v1c8492f2wb7da2f27a55204ca@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Problem solved! It turns out the warm spare server wasn't the same release
of Linux, though that wasn't quite the problem. However, it also an older
version of the tar utility.

When I restored the index file with the problem, it came out as 32768 bytes
long rather than 40960 bytes long.

Upgrading to the current version of the GNU tar utility program fixed the
problem.
--
Mike Nolan

Browse pgsql-general by date

  From Date Subject
Next Message Rafael Martinez 2007-05-27 10:02:35 Problems with "anyelement" after upgrading from 8.1.4 to 8.1.9
Previous Message Francisco Reyes 2007-05-27 02:06:11 Re: backup strategies