Re: COPY manual is ambiguous about column list - Mailing list pgsql-docs

From Bruce Momjian
Subject Re: COPY manual is ambiguous about column list
Date
Msg-id 20191219165340.GP30116@momjian.us
Whole thread Raw
In response to Re: COPY manual is ambiguous about column list  (Pavlo Golub <pavlo.golub@gmail.com>)
Responses Re: COPY manual is ambiguous about column list  (Pavlo Golub <pavlo.golub@gmail.com>)
Re: COPY manual is ambiguous about column list  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On Thu, Nov 28, 2019 at 02:53:03PM +0100, Pavlo Golub wrote:
> On Thu, 28 Nov 2019 at 10:47, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> >
> > On Wed, 2019-11-27 at 17:54 +0000, PG Doc comments form wrote:
> > > "If a list of columns is specified, COPY will only copy the data in the
> > > specified columns to or from the file. If there are any columns in the table
> > > that are not in the column list, COPY FROM will insert the default values
> > > for those columns."
> > >
> > > I clearly see "to or from" file here. But if one tries to COPY FROM filename
> > > with more columns than list specified, the process fails:
> >
> > I think you misunderstood the documentation.
> 
> Yeap, I did. Even two of us. Laetitia was helping me :)
> 
> >
> > Nowhere in that sentence is the documentation talking about columns in
> > the file, only columns in the table.
> >
> > But if you got it wrong, maybe a clarification would be a good idea.
> 
> I think it better to have more details to avoid confusion.

How is the attached patch?

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

Attachment

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: document effect of USAGE on foreign server to dblink
Next
From: Pavlo Golub
Date:
Subject: Re: COPY manual is ambiguous about column list