Tom Lane wrote:
> Bruce Momjian <[email protected]> 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 ([EMAIL PROTECTED] [66.207.139.130])
by momjian.us (8.11.6/8.11.6) with ESMTP id l14HX7l21306
for <[email protected]>; Sun, 4 Feb 2007 12:33:08 -0500
(EST)
Received: from sss2.sss.pgh.pa.us ([EMAIL PROTECTED] [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 <[email protected]>
cc: David Fetter <[EMAIL PROTECTED]>, Andrew Dunstan <[EMAIL
PROTECTED]>,
[EMAIL PROTECTED], PostgreSQL-patches <[email protected]>
Subject: Re: [PATCHES] [BUGS] BUG #2221: Bad delimiters allowed in COPY
...
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Comments: In-reply-to Bruce Momjian <[email protected]>
message dated "Wed, 01 Feb 2006 09:10:51 -0500"
----------------
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
