Re: pg_restore data block error
От | Anjan Dave |
---|---|
Тема | Re: pg_restore data block error |
Дата | |
Msg-id | 4BAFBB6B9CC46F41B2AD7D9F4BBAF78508C8B7@vt-pe2550-001.vantage.vantage.com обсуждение исходный текст |
Ответ на | pg_restore data block error ("Anjan Dave" <adave@vantage.com>) |
Список | pgsql-admin |
Yes, it's about 7GB. I installed it from RPMs...Do I just copy over the pg_backup_archiver.c file? Is there any easy way to dump individual tables (dealing with 73 tables)? Thanks for your response, Anjan -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Friday, February 27, 2004 5:24 PM To: Anjan Dave Cc: aspire420@hotpop.com; pgsql-admin@postgresql.org Subject: Re: [ADMIN] pg_restore data block error "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
В списке pgsql-admin по дате отправления: