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

From Tom Lane
Subject Re: ecpg command does not warn COPY ... FROM STDIN;
Date
Msg-id 1661748.1736353870@sss.pgh.pa.us
Whole thread Raw
In response to Re: ecpg command does not warn COPY ... FROM STDIN;  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses RE: ecpg command does not warn COPY ... FROM STDIN;
List pgsql-hackers
Fujii Masao <masao.fujii@oss.nttdata.com> writes:
> On 2025/01/09 0:42, Tom Lane wrote:
>> There's another problem: the correct syntax is COPY TO STDOUT,
>> and that won't trigger this warning either.

> 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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Virtual generated columns
Next
From: Tom Lane
Date:
Subject: Re: Virtual generated columns