From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <Kevin(dot)Grittner(at)wicourts(dot)gov>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_restore [archiver] file offset in dump file is too |
Date: | 2005-11-02 14:37:18 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C7B4D@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Andrew Dunstan <andrew(at)dunslane(dot)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?
Windows certainly supports large files. I don't see why we wouldn't pick
this up in autoconf, perhaps the mingw libraries don't?
Definitly worth investigating, no time for 8.1, so putting it on TODO
seems very good :-)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-02 15:16:56 | Re: 8.1RC1 fails to build on OS X (10.4) |
Previous Message | Tom Lane | 2005-11-02 14:20:15 | Re: Limit usage of tcop/dest.h |