Re: BUG #7590: Data corruption using pg_dump only with -Z parameter

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: hrtlik(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7590: Data corruption using pg_dump only with -Z parameter
Date: 2012-10-09 18:38:15
Message-ID: 2464.1349807895@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

hrtlik(at)gmail(dot)com writes:
> The following bug has been logged on the website:
> Bug reference: 7590
> Logged by: Jan Vodika
> Email address: hrtlik(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ryan Kelly 2012-10-09 19:02:33 Re: BUG #7590: Data corruption using pg_dump only with -Z parameter
Previous Message Tom Lane 2012-10-09 18:34:27 Re: BUG #7591: Large query string has limit