From: Tom Lane <tgl@sss.pgh.pa.us>
To: Anjan Dave <adave@vantage.com>
Cc: aspire420@hotpop.com
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_restore data block error
Date: Fri, 27 Feb 2004 17:24:21 -0500
Message-ID: <23636.1077920661@sss.pgh.pa.us> (raw)
In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78508C8AF@vt-pe2550-001.vantage.vantage.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78508C8AF@vt-pe2550-001.vantage.vantage.com>
"Anjan Dave" <adave@vantage.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, adave@vantage.com, aspire420@hotpop.com
Subject: Re: pg_restore data block error
In-Reply-To: <23636.1077920661@sss.pgh.pa.us>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78508C8AF@vt-pe2550-001.vantage.vantage.com> <23636.1077920661@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox