Re: Restore Data Encountered the ERROR: literal carriage return found in data Error

Rich - Thanks for explanation for ctrl+M = ascii 13 = CR. Yes. I've been using a very old version of Postgres and trying to migrate to Postgres 8.3.8.
Wow! Thanks Tom! Yes. It took a long time to restore but it was worth it. Using -inserts option of pg_dump were able to restore lots of data. Now, I just need to find out why some rows of some tables weren't able to be restored (I'm sure they had some kind of errors). Happy Friday!

Mary

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, March 05, 2010 5:36 AM
To: Richard Huxton
Cc: Wang, Mary Y; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Restore Data Encountered the ERROR: literal carriage return found in data Error

Richard Huxton <dev(at)archonet(dot)com> writes:
> On 04/03/10 23:52, Wang, Mary Y wrote:
>> I'm getting lots errors like this one: "psql:21.bak:340557: ERROR:
>> literal carriage return found in data HINT: Use "\r" to represent
>> carriage return."

> I'd only expect this if an old pg_dumpall was being used.

Mary's dealing with a version so old that the behavior of COPY itself was different. One possible workaround is to use the --inserts option of pg_dump. That will mean slower dump and restore, though.

regards, tom lane