X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D548AD1DD5D for ; Fri, 27 Feb 2004 22:24:23 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 47983-06 for ; Fri, 27 Feb 2004 18:24:23 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id C793CD1DD00 for ; Fri, 27 Feb 2004 18:24:20 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1RMOLQB023637; Fri, 27 Feb 2004 17:24:21 -0500 (EST) To: "Anjan Dave" Cc: aspire420@hotpop.com, pgsql-admin@postgresql.org Subject: Re: pg_restore data block error In-reply-to: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78508C8AF@vt-pe2550-001.vantage.vantage.com> References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78508C8AF@vt-pe2550-001.vantage.vantage.com> Comments: In-reply-to "Anjan Dave" message dated "Fri, 27 Feb 2004 14:46:05 -0500" Date: Fri, 27 Feb 2004 17:24:21 -0500 Message-ID: <23636.1077920661@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/388 X-Sequence-Number: 12561 "Anjan Dave" writes: > Same error again. > -bash-2.05b$ pg_restore -a -d access > backups/access/data.pg > pg_restore: [custom archiver] could not read data block > -- expected 4096, got 3608 You said the dump file was over 4Gb, right? I'm wondering if you are running into some file-offset-size bug. In particular this recent bug fix might be relevant: 2004-01-03 23:02 tgl * src/bin/pg_dump/pg_backup_archiver.c (REL7_4_STABLE): Fix ReadOffset() to work correctly when off_t is wider than int. although offhand I'm not sure how that would translate into what sounds to be an unexpected-EOF failure. regards, tom lane