Re: pg_restore [archiver] file offset in dump file is too

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <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 13:25:46
Message-ID: 4255.24.211.165.134.1130937946.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane said:
> 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?

Meanwhile, the answer seems to be to use text dumps if you run into this
problem.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2005-11-02 13:50:07 Limit usage of tcop/dest.h
Previous Message Andrew Dunstan 2005-11-02 13:22:19 Re: Limit usage of tcop/dest.h