RE: ecpg command does not warn COPY ... FROM STDIN; - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: ecpg command does not warn COPY ... FROM STDIN;
Date
Msg-id OSCPR01MB14966060B76E328E491D39F1EF5132@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: ecpg command does not warn COPY ... FROM STDIN;  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Dear Tom, Fujii-san,

> > ISTM that ecpg supports COPY TO STDOUT and includes the regression test
> "copystdout" for it. No?
>
> Oh right.  (Pokes at it...)  It looks like the backend accepts
> "FROM STDOUT" as a synonym for "FROM STDIN", so that's why this
> is checking for both spellings.  But I agree it'd be better
> for the error message to only use the standard spelling.
>
> Also I tried
>
> regression=# copy int4_tbl from program stdin;
> ERROR:  STDIN/STDOUT not allowed with PROGRAM
>
> So we probably don't need to bother with adjusting the check
> to allow that.

To confirm - I have no objections for the decision. I'm also think it is not
an usual grammar. I checked the doc [1] and I could not find "COPY FROM STDOUT".
I.e., first version is enough.

[1]: https://www.postgresql.org/docs/devel/sql-copy.html

Best regards,
Hayato Kuroda
FUJITSU LIMITED




pgsql-hackers by date:

Previous
From: Robins Tharakan
Date:
Subject: Re: Several buildfarm animals fail tests because of shared memory error
Next
From: Mats Kindahl
Date:
Subject: Re: Coccinelle for PostgreSQL development [4/N]: correcting palloc() use