Skip site navigation (1) Skip section navigation (2)

Re: Opening stdin/stdout in binary mode on Windows

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: Opening stdin/stdout in binary mode on Windows
Date: 2005-01-26 19:20:43
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A75E9@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)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

Responses

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2005-01-26 19:47:16
Subject: Re: Opening stdin/stdout in binary mode on Windows
Previous:From: Tom LaneDate: 2005-01-26 18:52:57
Subject: Re: Opening stdin/stdout in binary mode on Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group