Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TBnsC-0004bD-RO for pgsql-admin@postgresql.org; Wed, 12 Sep 2012 14:25:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TBns8-0004yS-Gw for pgsql-admin@postgresql.org; Wed, 12 Sep 2012 14:24:59 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q8CEOrXE024834; Wed, 12 Sep 2012 10:24:53 -0400 (EDT) From: Tom Lane To: "ramana.pls" cc: pgsql-admin@postgresql.org Subject: Re: pg_restore problem "Found unexpected Block id" In-reply-to: <1347367004895-5723501.post@n5.nabble.com> References: <1347367004895-5723501.post@n5.nabble.com> Comments: In-reply-to "ramana.pls" message dated "Tue, 11 Sep 2012 05:36:45 -0700" Date: Wed, 12 Sep 2012 10:24:53 -0400 Message-ID: <24833.1347459893@sss.pgh.pa.us> X-Pg-Spam-Score: -2.3 (--) X-Archive-Number: 201209/54 X-Sequence-Number: 39995 "ramana.pls" writes: > I am getting an error while restoring the Database Backup. I am postgre sql > 8.0 with Windows XP O.S. 8.0? You do know that's been out of support for several years now, right? > while restoring the data i am getting > pg_restore: [custom archiver] found unexpected block ID (0) when reading > data -- > expected 4034 This looks somewhat like a pg_restore bug we fixed awhile back. I'd suggest updating to a more modern Postgres version and seeing if it works any better. regards, tom lane