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

From Jacob Champion
Subject Re: New "raw" COPY format
Date
Msg-id CAOYmi+mp1Ty-kPY9xG0U2TJKEHP=vHn+RzG_DXPcRfuxJ1nB9Q@mail.gmail.com
Whole thread Raw
In response to Re: New "raw" COPY format  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: New "raw" COPY format
List pgsql-hackers
Hi,

Idle thoughts from a design perspective -- feel free to ignore, since
I'm not the target audience for the feature:

- If the column data stored in Postgres contains newlines, it seems
like COPY TO won't work "correctly". Is that acceptable?
- RAW seems like an okay-ish label, but for something that's doing as
much magic end-of-line detection as this patch is, I'd personally
prefer SINGLE (as in, "single column").
- Speaking of magic end-of-line detection, can there be a way to turn
that off? Say, via DELIMITER?
- Generic DELIMITER support, for any single-byte separator at all,
might make a "single-column" format more generally applicable. But I
might be over-architecting. And it would make the COPY TO issue even
worse...

Thanks,
--Jacob



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Detailed release notes
Next
From: Alexander Lakhin
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER