Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f17GEix71130; Wed, 7 Feb 2001 11:14:44 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f17GEX928520; Wed, 7 Feb 2001 11:14:33 -0500 (EST) To: Brice Ruth cc: Michael Fork , Ian Harding , pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] Re: SQL Join - MySQL/PostgreSQL difference? In-reply-to: <3A8172DD.C91DDCF2@webprojkt.com> References: <3A816921.FEB47B80@webprojkt.com> <28366.981560901@sss.pgh.pa.us> <3A8172DD.C91DDCF2@webprojkt.com> Comments: In-reply-to Brice Ruth message dated "Wed, 07 Feb 2001 10:07:55 -0600" Date: Wed, 07 Feb 2001 11:14:32 -0500 Message-ID: <28516.981562472@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/338 X-Sequence-Number: 4211 Brice Ruth writes: > Here's my latest tactic: I'm guessing that the data 'corruption' has > something to do with the way the data was exported from the original > database by the third party ... probably something with the cr/lf > linebreaks or something to that effect (the data field in question > happens to be the last field in a line in the data file). Ooooh ... the queries you were showing us made it look like the column was not the last one, so I hadn't thought of that. Almost certainly, your extra character is a CR. Postgres expects plain LF as newline in COPY data files; if the newlines are actually CR/LF then the CRs will be taken as part of the last data field. regards, tom lane