| From: | Garick Hamlin <ghamlin(at)isc(dot)upenn(dot)edu> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, Simon Muller <samullers(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Allow COPY's 'text' format to output a header |
| Date: | 2018-05-14 18:44:59 |
| Message-ID: | 20180514184459.GA1272@isc.upenn.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 14, 2018 at 09:37:07AM +0900, Michael Paquier wrote:
> On Sun, May 13, 2018 at 07:01:00PM -0400, David Steele wrote:
> > This patch makes sense to me and looks reasonable.
>
> One "potential" problem is if a relation has a full set of column which
> allows the input of text-like data: if the header has been added with
> COPY TO, and that the user forgets to add again the header option with
> COPY FROM, then an extra row will be generated but there is the same
> problem with CSV format :)
Yeah, I wonder if that can be addressed.
I wonder if there was a way to let COPY FROM detect or ignore headers
as appropriate and rather than cause silently result in headers being
added as data.
Maybe a blank line after the header line could prevent this confusion?
Garick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-05-14 18:45:01 | Re: explain (verbose off, normalized) vs query planid |
| Previous Message | Tom Lane | 2018-05-14 18:01:43 | Re: SPI/backend equivalent of extended-query Describe(statement)? |