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

From Joel Jacobson
Subject Re: New "single" COPY format
Date
Msg-id ce2cb85f-fa4d-47a5-944e-0ac1c541d7d5@app.fastmail.com
Whole thread Raw
In response to Re: New "single" COPY format  ("Joel Jacobson" <joel@compiler.org>)
Responses Re: New "single" COPY format
Re: New "single" COPY format
List pgsql-hackers
Hi hackers,

After further consideration, I'm withdrawing the patch.
Some fundamental questions remain unresolved:

- Should round-trip fidelity be a strict goal? By "round-trip fidelity",
  I mean that data exported and then re-imported should yield exactly
  the original values, including the distinction between NULL and empty strings.
- If round-trip fidelity is a requirement, how do we distinguish NULL from empty
  strings without delimiters or escapes?
- Is automatic newline detection (as in "csv" and "text") more valuable than
  the ability to embed \r (CR) characters?
- Would it be better to extend the existing COPY options rather than introducing
  a new format?
- Or should we consider a JSONL format instead, one that avoids the NULL/empty
  string problem entirely?

No clear solution or consensus has emerged. For now, I'll step back from the
proposal. If someone wants to revisit this later, I'd be happy to contribute.

Thanks again for all the feedback and consideration.

/Joel



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: FileFallocate misbehaving on XFS
Next
From: "Joel Jacobson"
Date:
Subject: Re: Add pg_ownerships and pg_privileges system views