Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: David Fetter <david(at)fetter(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, neilc(at)samurai(dot)com, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #2221: Bad delimiters allowed in COPY ...
Date: 2007-02-04 17:32:32
Message-ID: 20065.1170610352@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2007-02-04 18:11:18 Re: BUG #2967: BUG #2881: FATAL: could not reattach to shared memory (Win32)
Previous Message Magnus Hagander 2007-02-04 15:45:06 Re: BUG #2967: BUG #2881: FATAL: could not reattach to shared memory (Win32)

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-04 17:38:40 Re: [HACKERS] \copy (query) delimiter syntax error
Previous Message David Fetter 2007-02-04 15:45:28 Re: [HACKERS] writing new regexp functions