| From: | newtglobal postgresql_contributors <postgresql_contributors(at)newtglobalcorp(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org> |
| Subject: | Re: New "raw" COPY format |
| Date: | 2025-02-27 11:09:49 |
| Message-ID: | 174065458978.656.10476821263158522635.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The following review has been posted through the commitfest application:
make installcheck-world: tested, failed
Implements feature: tested, failed
Spec compliant: tested, failed
Documentation: tested, failed
Hi Joel,
After testing the patch, I observed that for single-column tables, the format evolved from SINGLE to RAW and finally to LIST to handle diverse data more flexibly. For example, the command: \COPY test.foo2 FROM '/home/newtdba/postgres-cf-5300/testfiles/testname.txt' WITH (FORMAT LIST); works with CSV, TXT, and RAW files without specifying column names. This LIST format is effective for copying data to/from single-column tables but requires specifying the correct format.
The new status of this patch is: Needs review
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-02-27 11:18:51 | Re: NOT ENFORCED constraint feature |
| Previous Message | newtglobal postgresql_contributors | 2025-02-27 11:09:02 | Re: Replace IN VALUES with ANY in WHERE clauses during optimization |