From: Tom Lane <tgl@sss.pgh.pa.us>
To: girish R G peetle <giri.anamika0@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: PostgreSQL Dump based backup using pipe
In-reply-to: 
 <CAKKd066yz3GeEg9D_8KDPGz38YX=rzFAcGd5paUWaOtOqkNsPA@mail.gmail.com>
References: 
 <CAKKd066yz3GeEg9D_8KDPGz38YX=rzFAcGd5paUWaOtOqkNsPA@mail.gmail.com>
Comments: In-reply-to girish R G peetle <giri.anamika0@gmail.com>
 message dated "Wed, 27 May 2015 16:49:37 +0530"
Date: Wed, 27 May 2015 10:24:44 -0400
Message-ID: <31650.1432736684@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

girish R G peetle <giri.anamika0@gmail.com> writes:
> We were using named pipe to read dump data from 'pg_dump -Fc' (compressed
> format) on Windows.
> Restore was failing with 'corrupt dump data' error.
> Later found that pg_dump was performing 'illegal seek' on pipe to write the
> data, which was causing corrupt dump.

That should work.  What PG version are you using exactly, and can we see a
full example of what you were trying to do?

There are unsupported cases --- I recall in particular that you can't do
a parallel restore from a pipe --- but you should not be getting "corrupt
file" errors.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin