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 43692EF1.1060303@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>)
List pgsql-hackers

Tom Lane wrote:

>Andrew Dunstan <andrew@dunslane.net> writes:
>  
>
>>There is no fseeko in the Windows libraries, nor any provision in the 
>>mingw headers that I can see for a 64 bit off_t. So we would need to 
>>roll our own to some extent - I think we need more than just a bit of 
>>configure cleverness.
>>    
>>
>
>  
>
>>However, there is a Windows library routine to do a 64bit seek and 
>>return the file position, so we could fairly easily implement fseeko and 
>>ftello based on that. See
>>http://msdn.microsoft.com/library/en-us/vclib/html/_crt__lseek.2c_._lseeki64.asp
>>    
>>
>
>Is there any risk that the mingw libraries would fail when manipulating
>a file whose current offset exceeds 32 bits?  I'm wondering if we'd have
>to roll our own stdio in toto, not just fseeko/ftello :-(
>
>
>  
>

AFAIK all this is coming straight from the base Windows libraries. I 
guess we'll have to test it when we get around to it.

cheers

andrew


pgsql-hackers by date:

Previous
From: Robert Creager
Date:
Subject: Re: Assert failure found in 8.1RC1
Next
From: Bruce Momjian
Date:
Subject: Re: pg_restore [archiver] file offset in dump file is too