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

From Tom Lane
Subject Re: pg_restore [archiver] file offset in dump file is too
Date
Msg-id 5202.1133671080@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_restore [archiver] file offset in dump file is too  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pg_restore [archiver] file offset in dump file is too  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Added to TODO:

>         o Add long file support for binary pg_dump output

>           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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_restore [archiver] file offset in dump file is too
Next
From: Jan Wieck
Date:
Subject: Re: SERIAL type feature request