| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New "single" COPY format |
| Date: | 2024-11-09 14:28:18 |
| Message-ID: | CAKFQuwa3G3WZ+1CB+epYjQpOXZxkQBMrbVJ=ekoWa7cZqSx4xQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Saturday, November 9, 2024, Joel Jacobson <joel(at)compiler(dot)org> wrote:
> On Fri, Nov 8, 2024, at 22:47, David G. Johnston wrote:
> > On Fri, Nov 8, 2024 at 2:20 PM Joel Jacobson <joel(at)compiler(dot)org> wrote:
> >>
> >> 1. Text files containing \. in the middle of the file
> >> % cat /tmp/test.txt
> >> foo
> >> \.
> >> bar
> >>
> >> Or another option to turn off the special meaning of \.?
> >
> > This does seem like an orthogonal option worth considering.
>
> I agree; if we want to integrate this into 'text', it's an option worth
> considering.
PostgreSQL cannot store the NUL byte. Would that be an option for the
record separator. Default to new line but accept NUL if one needs to
input/output lists containing newlines. Or whatever character the user
believes is not part of their data - tab probably being a popular option.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2024-11-09 14:45:10 | Re: general purpose array_sort |
| Previous Message | David G. Johnston | 2024-11-09 14:13:47 | Re: New "single" COPY format |