Re: pg_restore [archiver] file offset in dump file is too - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_restore [archiver] file offset in dump file is too
Date
Msg-id 43933C3F.1080000@dunslane.net
Whole thread Raw
In response to Re: pg_restore [archiver] file offset in dump file is too  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_restore [archiver] file offset in dump file is too  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] snprintf() argument reordering not working
Next
From: Paul Lindner
Date:
Subject: MIN() performance regression 8.0 -> 8.1