Re: BUG #7590: Data corruption using pg_dump only with -Z parameter - Mailing list pgsql-bugs

From Jan Vodička
Subject Re: BUG #7590: Data corruption using pg_dump only with -Z parameter
Date
Msg-id CA+8ZZiKZpOgCnivbK_KpDxPC-9Wqwq7R=sQGARwAQLXTzK+4og@mail.gmail.com
Whole thread Raw
In response to Re: BUG #7590: Data corruption using pg_dump only with -Z parameter  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
So is there any way how to get plain sql from this "corrupted" backup?
It would be nice to mention this behavior in manual.


2012/10/9 Tom Lane <tgl@sss.pgh.pa.us>
hrtlik@gmail.com writes:
> The following bug has been logged on the website:
> Bug reference:      7590
> Logged by:          Jan Vodička
> Email address:      hrtlik@gmail.com
> PostgreSQL version: 9.2.1
> Operating system:   Windows 8
> Description:

> "pg_dump -Z1 my_db > backup" always make corrupted package.

On Windows, that doesn't seem terribly surprising: Windows will probably
do newline munging on the process's stdout, which will corrupt
compressed data since it's not plain text.  There's not a lot we can do
to prevent that.  Try it like this instead:

        pg_dump -Z1 -f backup.gz my_db

to keep the data away from Windows' interference.

                        regards, tom lane



--
Jan Vodička

pgsql-bugs by date:

Previous
From: Ryan Kelly
Date:
Subject: Re: BUG #7590: Data corruption using pg_dump only with -Z parameter
Next
From: Jan Vodička
Date:
Subject: Re: BUG #7590: Data corruption using pg_dump only with -Z parameter