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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Magnus Hagander <mha(at)sollentuna(dot)net>, 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-12-04 18:58:07
Message-ID: 43933C3F.1080000@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>> While Win32 supports 64-bit files, the MinGW API does not,
>> meaning we have to build an fseeko replacement on top of the
>> Win32 API, and we have to make sure MinGW handles it.
>>
>>
>
>Wouldn't it be better to lobby the MinGW folk to fix their problem?
>Or even help them with it? I can't see the rationale for implementing
>a workaround that helps only us.
>
>
>
>

There is a library available from the gnuwin32 project that advertises
fseeko and fseeko64. So we probably have a choice of requiring this
library or doing it ourselves.

see http://gnuwin32.sourceforge.net/packages/libgw32c.htm

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-12-04 19:17:28 Er ... does port/snprintf.c actually work?
Previous Message Tom Lane 2005-12-04 18:57:44 Re: [PATCHES] snprintf() argument reordering not working