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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Restore Data Encountered the ERROR: literal carriage return found in data Error
Date: 2010-03-05 13:36:13
Message-ID: 29629.1267796173@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Cyril Scetbon 2010-03-05 14:09:16 kernel version impact on PostgreSQL performance
Previous Message Tom Lane 2010-03-05 13:33:54 Re: need some advanced books on Postgres