Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Attached is a patch that errors for \r and \n in delimiter and
> > null.
>
> I am not convinced that this is a bug. Can you prove that there is no
> use-case for asking COPY to emit data in this style? Sure, COPY itself
> couldn't read it, but people sometimes feed COPY output to other
> programs...
FYI, Tom, old email from Feb 1, 2006, from your server:
Received: from sss.pgh.pa.us (root@sss.pgh.pa.us [66.207.139.130])
by momjian.us (8.11.6/8.11.6) with ESMTP id l14HX7l21306
for <pgman@candle.pha.pa.us>; Sun, 4 Feb 2007 12:33:08 -0500 (EST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l14HWWoj020066;
Sun, 4 Feb 2007 12:32:32 -0500 (EST)
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: David Fetter <david@fetter.org>, Andrew Dunstan <andrew@dunslane.net>,
neilc@samurai.com, PostgreSQL-patches <pgsql-patches@postgresql.org>
Subject: Re: [PATCHES] [BUGS] BUG #2221: Bad delimiters allowed in COPY ...
In-Reply-To: <200602011410.k11EApH14839@candle.pha.pa.us>
References: <200602011410.k11EApH14839@candle.pha.pa.us>
Comments: In-reply-to Bruce Momjian <pgman@candle.pha.pa.us>
message dated "Wed, 01 Feb 2006 09:10:51 -0500"
----------------
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
