Re: pg_restore [archiver] file offset in dump file is too
От | Tom Lane |
---|---|
Тема | Re: pg_restore [archiver] file offset in dump file is too |
Дата | |
Msg-id | 8220.1130963773@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pg_restore [archiver] file offset in dump file is too (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: pg_restore [archiver] file offset in dump file is too
|
Список | pgsql-hackers |
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 :-( regards, tom lane
В списке pgsql-hackers по дате отправления: