| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sutou Kouhei <kou(at)clear-code(dot)com> |
| Cc: | bruce(at)momjian(dot)us, daniel(at)manitou-mail(dot)org, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Fixing backslash dot for COPY FROM...CSV |
| Date: | 2024-07-24 17:36:45 |
| Message-ID: | 1250577.1721842605@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sutou Kouhei <kou(at)clear-code(dot)com> writes:
> I read through this thread. It seems that this thread
> discuss 2 things:
> 1. \. in CSV mode
> 2. \. in non-CSV mode
> Recent messages discussed mainly 2. but how about create a
> separated thread for 2.? Because the original mail focused
> on 1. and it seems that we can handle them separately.
Well, we don't want to paint ourselves into a corner by considering
only part of the problem.
What I'm currently thinking is that we can't remove the special
treatment of \. in text mode. It's not arguably a bug, because
it's been part of the specification since day one; and there
are too many compatibility risks in pg_dump and elsewhere.
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.
> How about introducing a new COPY option that controls
> whether "\." is ignored or not instead of this approach?
No thanks. Once we create such an option we'll never be
able to get rid of it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-07-24 17:41:13 | Re: warning: dereferencing type-punned pointer |
| Previous Message | Jeff Davis | 2024-07-24 17:35:38 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |