Re: [GENERAL] pg_restore
- From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Niederland <niederland(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org
- Subject: Re: [GENERAL] pg_restore
- Date: Sun, 23 Jan 2005 11:08:01 -0500 (EST)
- Message-id: <200501231608(dot)j0NG81h01779(at)candle(dot)pha(dot)pa(dot)us>
Tom Lane wrote:
> "Niederland" <niederland(at)gmail(dot)com> writes:
> > System: the released Postgres 8.0, winXP
>
> > Using:
> > pg_dump --format=t --blobs myDB > DBFile
> > pg_restore --create -dbname=crm DBFile
>
> > Resulted in:
> > pg_restore: [archiver] unsupported version (1.13) in file header
>
> Come to think of it, I'll bet that you cannot use "> DBFile" on Windows
> because it ends up opening the archive file in text instead of binary
> mode. SetOutput() in pg_backup_archiver.c tries to work around this by
> doing
>
> fn = fileno(stdout);
> AH->OF = fdopen(dup(fn), PG_BINARY_W);
>
> but it wouldn't surprise me in the least to learn that that doesn't work
> on Windows.
>
> Does it work if you use
> pg_dump --format=t --blobs -f DBFile myDB
> ? Can anyone on pgsql-hackers-win32 think of a way around this?
I never considered the distinction of binary/text mode on ">" but I can
see it could certainly be an issue.
Do we have to start suggesting "-f" for all scripts just so Win32 is OK?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Home |
Main Index |
Thread Index