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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Wed, 26 Jan 2005 14:20:43 -0500
  • Message-id: <6EE64EF3AB31D5448D0007DD34EEB3412A75E9(at)Herge(dot)rcsinc(dot)local>

> "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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group