Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 8198D16108B4 for ; Fri, 23 Dec 2011 10:59:23 -0400 (AST) Received: from gwmta.wicourts.gov ([165.219.244.99] helo=gw.wicourts.gov) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Re6ac-0003TL-B6 for pgsql-admin@postgresql.org; Fri, 23 Dec 2011 14:59:22 +0000 Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 23 Dec 2011 08:59:04 -0600 Message-Id: <4EF442CF020000250004408A@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 23 Dec 2011 08:58:55 -0600 From: "Kevin Grittner" To: "mirrorx" , "Karuna Karpe" Cc: "Jerry Sievers" , Subject: Re: error during PITR References: <87wr9oyboo.fsf@comcast.net> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Pg-Spam-Score: -6.8 (------) X-Archive-Number: 201112/139 X-Sequence-Number: 38897 Karuna Karpe wrote: > 2011-12-23 11:44:18 ISTLOG: restored log file > "00000001000000000000000F" from archive > 2011-12-23 11:44:18 ISTLOG: record with incorrect prev-link > 0/E000094 at 0/F000020 > 2011-12-23 11:44:18 ISTLOG: redo done at 0/E0000C0 > 2011-12-23 11:44:18 ISTLOG: restored log file > "00000001000000000000000E" from archive > 2011-12-23 11:44:18 ISTFATAL: WAL ends before consistent recovery > point > 2011-12-23 11:44:18 ISTLOG: startup process (PID 4435) exited > with exit code 1 > 2011-12-23 11:44:18 ISTLOG: terminating any other active server > processes > > Can please any one give me solution for that as soon as possible? It looks like you don't have a good copy of the 00000001000000000000000F WAL file. If you can retrieve a good copy from somewhere, you should be able to proceed. If not, you should go to an earlier base backup -- that will let you restore a consistent version of the database for as far as you have good WAL files. You should also review your procedure for copying WAL files. We had occasional problems like this when we were using samba shares; we've had none since we copied the files to a directory on the database server and used rsync to copy them off. -Kevin