| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New "single" COPY format |
| Date: | 2024-11-09 20:52:06 |
| Message-ID: | CAKFQuwYPi9gFaE=eukotMf9Ohs+1gTY3ZGGkaYV76SrP81zQvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 9, 2024 at 1:48 PM Joel Jacobson <joel(at)compiler(dot)org> wrote:
> On Sat, Nov 9, 2024, at 15:28, David G. Johnston wrote:
> > 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.
>
> Clever idea, could work, but using NUL bytes in text files feels a bit
> unorthodox, and I can imagine surprising results in other systems having
> to deal
> with such files.
>
>
Yeah. I was inspired by xargs and find but for a permanent file it is a
bit different.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-11-10 03:16:37 | Re: Virtual generated columns |
| Previous Message | Joel Jacobson | 2024-11-09 20:48:07 | Re: New "single" COPY format |