Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D9E9A476E40 for ; Tue, 28 Jan 2003 10:34:59 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 62159476070 for ; Tue, 28 Jan 2003 10:32:35 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0SFWZ5u013298; Tue, 28 Jan 2003 10:32:36 -0500 (EST) To: Oliver Vecernik Cc: pgsql-sql Subject: Re: CR/LF conversion (was: import error) In-reply-to: <3E368EE5.8080501@aon.at> References: <3E368509.9050200@aon.at> <3E368EE5.8080501@aon.at> Comments: In-reply-to Oliver Vecernik message dated "Tue, 28 Jan 2003 15:08:37 +0100" Date: Tue, 28 Jan 2003 10:32:35 -0500 Message-ID: <13297.1043767955@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/439 X-Sequence-Number: 11304 Oliver Vecernik writes: > It's always the same problem with CR/LF conversions ... Ah, you figured it out. (Didn't see your followup right away because of the changed subject line.) > After changing it to just LFs, everthing worked like a charm. Is there > an elegant way to handle this automatically? There are plans to make COPY treat all common styles of newline alike. We had to wait a release or two after taking the first step, though, since it's an incompatible change. regards, tom lane