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

From Fujii Masao
Subject Re: ecpg command does not warn COPY ... FROM STDIN;
Date
Msg-id 20e81fe2-cc30-4d15-882f-253f7fa2b2d3@oss.nttdata.com
Whole thread Raw
In response to Re: ecpg command does not warn COPY ... FROM STDIN;  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ecpg command does not warn COPY ... FROM STDIN;
List pgsql-hackers

On 2025/01/09 0:42, Tom Lane wrote:
> Fujii Masao <masao.fujii@oss.nttdata.com> writes:
>> On 2025/01/08 23:04, Ryo Kanbayashi wrote:
>> But it is not working.
>> ecpg command fails to notice though code like above exits on pgc code.
> 
>> This issue seems to have been introduced in commit 3d009e45bd.
> 
> Indeed :-(
> 
>> As for COPY FROM STDOUT, while it's possible, mentioning it might be
>> confusing since it's not official syntax. So I'm not sure if this is
>> good idea.
> 
> 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?

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION




pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Enhancing Memory Context Statistics Reporting
Next
From: Andrew Dunstan
Date:
Subject: Re: pgindent exit status if a file encounters an error