Re: New "single" COPY format - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: New "single" COPY format
Date
Msg-id CAKFQuwYPi9gFaE=eukotMf9Ohs+1gTY3ZGGkaYV76SrP81zQvg@mail.gmail.com
Whole thread Raw
In response to Re: New "single" COPY format  ("Joel Jacobson" <joel@compiler.org>)
List pgsql-hackers
On Sat, Nov 9, 2024 at 1:48 PM Joel Jacobson <joel@compiler.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.

pgsql-hackers by date:

Previous
From: "Joel Jacobson"
Date:
Subject: Re: New "single" COPY format
Next
From: Amit Kapila
Date:
Subject: Re: Virtual generated columns