Thread: pg_restore [archiver] file offset in dump file is too large
Posting here because it may be a 8.1 pre-release problem. I'll take it to the admin list if it looks like it's not. File dumped from 8.1beta3 using pg_dump -Fc on Linux box. This dump restored successfully onto 8.1RC1 on Linux box. File FTP'd to Windows box; attempt to restore onto 8.1RC1 fails with: pg_restore [archiver] file offset in dump file is too large This happens even wilth pg_restore -l <filename> All instanced init'd with --locale=C Both Linux and Windows 8.1RC1 instances give: dtr=> \l List of databases Name | Owner | Encoding -----------+----------+-----------dtr | dtr | SQL_ASCIIpostgres | postgres | SQL_ASCIItemplate0 | postgres |SQL_ASCIItemplate1 | postgres | SQL_ASCII (4 rows) (Source database was also SQL_ASCII.) On the Linux box: ; Archive created at Mon Oct 31 20:00:01 2005 ; dbname: dtr ; TOC Entries: 166 ; Compression: -1 ; Dump Version: 1.10-0 ; Format: CUSTOM ; Integer: 4 bytes ; Offset: 8 bytes ; Dumped from database version: 8.1beta3 ; Dumped by pg_dump version: 8.1beta3 -rw-r--r-- 1 postgres users 40874747876 Nov 1 05:27 dtr.dump On Windows, the file size and md5sum -b result is identical. Any suggestions on things to check or try? -Kevin
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> File dumped from 8.1beta3 using pg_dump -Fc on Linux box.
> This dump restored successfully onto 8.1RC1 on Linux box.
> File FTP'd to Windows box; attempt to restore onto 8.1RC1 fails with:
> pg_restore [archiver] file offset in dump file is too large
[ itch... ] This sure as heck sounds like the file was corrupted during
the FTP transfer. Did you remember to select binary transfer mode?
> On Windows, the file size and md5sum -b result is identical.
That observation does seem like evidence against my theory, but ...
regards, tom lane
Hmm. Windows reports an offset size of 4 bytes on a dump I just made ... is that relevant? What governs it? cheers andrew Kevin Grittner wrote: >Posting here because it may be a 8.1 pre-release problem. I'll take >it to the admin list if it looks like it's not. > >File dumped from 8.1beta3 using pg_dump -Fc on Linux box. >This dump restored successfully onto 8.1RC1 on Linux box. >File FTP'd to Windows box; attempt to restore onto 8.1RC1 fails with: > >pg_restore [archiver] file offset in dump file is too large > >This happens even wilth pg_restore -l <filename> > >All instanced init'd with --locale=C > >Both Linux and Windows 8.1RC1 instances give: > >dtr=> \l > List of databases > Name | Owner | Encoding >-----------+----------+----------- > dtr | dtr | SQL_ASCII > postgres | postgres | SQL_ASCII > template0 | postgres | SQL_ASCII > template1 | postgres | SQL_ASCII >(4 rows) > >(Source database was also SQL_ASCII.) > >On the Linux box: > >; Archive created at Mon Oct 31 20:00:01 2005 >; dbname: dtr >; TOC Entries: 166 >; Compression: -1 >; Dump Version: 1.10-0 >; Format: CUSTOM >; Integer: 4 bytes >; Offset: 8 bytes >; Dumped from database version: 8.1beta3 >; Dumped by pg_dump version: 8.1beta3 > >-rw-r--r-- 1 postgres users 40874747876 Nov 1 05:27 dtr.dump > >On Windows, the file size and md5sum -b result is identical. > >Any suggestions on things to check or try? > >-Kevin > > > >---------------------------(end of broadcast)--------------------------- >TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > >
Andrew Dunstan <andrew@dunslane.net> writes:
> Hmm. Windows reports an offset size of 4 bytes on a dump I just made ...
> is that relevant? What governs it?
[ looks again... ] Hm, that is a 40Gb dump Kevin is complaining of,
isn't it. Do our Windows builds have LARGEFILE support?
regards, tom lane
Tom Lane said: > Andrew Dunstan <andrew@dunslane.net> writes: >> Hmm. Windows reports an offset size of 4 bytes on a dump I just made >> ... is that relevant? What governs it? > > [ looks again... ] Hm, that is a 40Gb dump Kevin is complaining of, > isn't it. Do our Windows builds have LARGEFILE support? > I think from a cursory investigation the short answer is no, but they probably could. If so, that should definitely go on the TODO list. Windows gurus, any thoughts? Meanwhile, the answer seems to be to use text dumps if you run into this problem. cheers andrew