| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Daniel Verite <daniel(at)manitou-mail(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: backslash-dot quoting in COPY CSV |
| Date: | 2019-01-31 00:39:35 |
| Message-ID: | 20190131003935.GD16781@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 30, 2019 at 01:20:59PM -0500, Tom Lane wrote:
> Given how long we've had COPY CSV support, and the tiny number of
> complaints to date, I do not think it's something to panic over.
> Disallowing the functionality altogether is surely an overreaction.
>
> A documentation warning might be the appropriate response. I don't
> see any plausible way for psql to actually fix the problem, short
> of a protocol change to allow the backend to tell it how the data
> stream is going to be parsed.
Yes, agreed. I looked at this problem a couple of months (year(s)?)
ago and gave up on designing a clear portable solution after a couple
of hours over it, and that's quite a corner case.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-01-31 00:44:51 | Re: [PATCH] Pass COPT and PROFILE to CXXFLAGS as well |
| Previous Message | Michael Paquier | 2019-01-31 00:35:50 | Re: Unused parameters & co in code |