| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Anjan Dave" <adave(at)vantage(dot)com> |
| Cc: | aspire420(at)hotpop(dot)com, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_restore data block error |
| Date: | 2004-02-27 22:24:21 |
| Message-ID: | 23636.1077920661@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Anjan Dave" <adave(at)vantage(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anjan Dave | 2004-02-27 22:28:52 | Re: pg_restore data block error |
| Previous Message | Anjan Dave | 2004-02-27 19:46:05 | Re: pg_restore data block error |