Horton

Re: Fixing backslash dot for COPY FROM...CSV

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Verite" <daniel@manitou-mail.org>
Cc: Artur Zakirov <zaartur@gmail.com>, Sutou Kouhei <kou@clear-code.com>, bruce@momjian.us, robertmhaas@gmail.com, pgsql-hackers@postgresql.org
Date: 2024-10-01T20:17:19Z
Lists: pgsql-hackers 
"Daniel Verite" <daniel@manitou-mail.org> writes:
> Tom Lane wrote:
>> Returning to my upthread thought that
>>> I think we should fix it so that \. that's not alone on a line
>>> throws an error, but I wouldn't go further than that.
>> here's a quick follow-on patch to make that happen.  It could
>> probably do with a test case to demonstrate the error, but
>> I didn't bother yet pending approval that we want to do this.

> +1 for fixing.

It's been on the thread for awhile now without objections,
so I'll go ahead and make that happen.

			regards, tom lane

Commits

  1. Reject a copy EOF marker that has data ahead of it on the same line.

  2. Do not treat \. as an EOF marker in CSV mode for COPY IN.

  3. doc: \copy can get data values \. and end-of-input confused