Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 37B0C475451 for ; Fri, 26 Apr 2002 12:11:59 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3QGBaF26749; Fri, 26 Apr 2002 12:11:36 -0400 (EDT) To: "Josh Berkus" Cc: pgsql-sql@postgresql.org Subject: Re: Wierd error for COPY command In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Fri, 26 Apr 2002 08:42:34 -0700" Date: Fri, 26 Apr 2002 12:11:36 -0400 Message-ID: <26746.1019837496@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/326 X-Sequence-Number: 7590 "Josh Berkus" writes: > I'm getting the following error: > jwnet=# copy elbs_udf from '/home/jwnet/testtransfer/udf.txt' > jwnet-# using delimiters '|' with null as ''; > ": can't parse "ne 1, pg_atoi: error in "1 > jwnet=# I'll bet your file contains \r\n newlines not \n. The weird look of the error comes from copy echoing the \r as part of the "data item" it's unhappy about. Try examining the log entry using od -c if you want to see exactly what's there. regards, tom lane