From: | "Bryan Encina" <bryan(dot)encina(at)valleypres(dot)org> |
---|---|
To: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | |
Date: | 2003-11-20 20:43:44 |
Message-ID: | 000701c3afa6$fde808a0$931f10ac@AT10111 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Sorry if this is a duplicate, I think I sent the first one out to the wrong
address.
Hello all,
Upgraded from 7.1.3 to 7.4 (been waiting on this for a while thanks for all
the hard work guys) and am having problems restoring from a pg_dumpall.
Here's what I've done to dump the info:
pg_dumpall -c > alldump.sql
and I'm restoring with
psql -e -d template1 -f alldump.sql
which gives me these types of errors in the log:
COPY "emp_skill" FROM stdin;
psql:alldump.sql:12724: ERROR: literal carriage return found in data
HINT: Use "\r" to represent carriage return.
CONTEXT: COPY emp_skill, line 10145: "1149 V933280 NOTREQ GÎÆ
<strong>FirstName LastName</strong>, 03/21/2003 - 03:41PM<br>\
NOT IN LVN SKIL..."
Are there any other options I should've used to escape the carriage returns?
Luckily I'm still just testing and this is on a VMWare partition with the
snapshot right before the upgrade, or am I going to have to get something to
parse the dump file and replace all the carriage returns with \n . This is
all on RH 7.2.
Thanks,
Bryan Encina
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-11-20 21:16:53 | Re: |
Previous Message | Ireneusz Kramarz | 2003-11-20 15:20:01 | error while trying to connect... |