Re: Opening stdin/stdout in binary mode on Windows - Mailing list pgsql-hackers-win32

From Merlin Moncure
Subject Re: Opening stdin/stdout in binary mode on Windows
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB3412A75E9@Herge.rcsinc.local
Whole thread Raw
In response to Opening stdin/stdout in binary mode on Windows  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Opening stdin/stdout in binary mode on Windows  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers-win32
> "Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> > I'll test...is there a quick way to reproduce the error?
>
> Try
>     pg_dump -Fc mydb >mydb.dump
>     pg_restore -l mydb.dump
> and see if pg_restore complains.  I'd suggest checking
> all four combinations of writing to stdout or a named file and
> having pg_restore read from stdin or a named file.

We are good to go. The old version of pg_dump gave numerous ftell errors
and wouldn't restore and the new one gives no errors (and restore works
properly).

Also, text version runs fine (and should, by the code).

Merlin

pgsql-hackers-win32 by date:

Previous
From: Tom Lane
Date:
Subject: Re: Opening stdin/stdout in binary mode on Windows
Next
From: Tom Lane
Date:
Subject: Re: Opening stdin/stdout in binary mode on Windows