X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 01FA2476BF3 for ; Sun, 2 Feb 2003 04:44:57 -0500 (EST) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id 0DB1A47931F for ; Sun, 2 Feb 2003 03:14:50 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id h128EfB07898; Sun, 2 Feb 2003 03:14:41 -0500 (EST) From: Bruce Momjian Message-Id: <200302020814.h128EfB07898@candle.pha.pa.us> Subject: Re: CR/LF conversion (was: import error) In-Reply-To: <13297.1043767955@sss.pgh.pa.us> To: Tom Lane Date: Sun, 2 Feb 2003 03:14:41 -0500 (EST) Cc: Oliver Vecernik , pgsql-sql X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/29 X-Sequence-Number: 11427 We are supporting Win32 in 7.4, so it is very likely COPY will support carriage returns the next release. --------------------------------------------------------------------------- Tom Lane wrote: > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073