Skip site navigation (1)
Skip section navigation (2)
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
Peripheral Links
Header And Logo
|
Site Navigation
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: Sun, 27 May 2007 00:49:17 -0500
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
- Prev by Date: Re: backup strategies
- Next by Date: Re: why postgresql over other RDBMS
- Previous by thread: How to create trigger if it does not exist
- Next by thread: Problems with "anyelement" after upgrading from 8.1.4 to 8.1.9
- Indexes: