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

From Joel Jacobson
Subject Re: New "single" COPY format
Date
Msg-id a2097a88-5a28-4f4d-975e-0894382390a5@app.fastmail.com
Whole thread Raw
In response to Re: New "single" COPY format  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: New "single" COPY format
List pgsql-hackers
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.

I have no idea how useful such file format would be, but some googling suggest
it's a trick that's used out there, so I won't exclude the idea entirely, just
feels like a type of hack where it's difficult to foresee the consequences
of allowing it.

/Joel



pgsql-hackers by date:

Previous
From: Rishu Bagga
Date:
Subject: Re: Proposal to add page headers to SLRU pages
Next
From: "David G. Johnston"
Date:
Subject: Re: New "single" COPY format