Horton

Re: ecpg command does not warn COPY ... FROM STDIN;

Ryo Kanbayashi <kanbayashi.dev@gmail.com>

View thread View on postgr.es
From: Ryo Kanbayashi <kanbayashi.dev@gmail.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2025-01-09T12:27:47Z
Lists: pgsql-hackers

Attachments

> On 2025/01/09 20:34, Ryo Kanbayashi wrote:
> > Dear Tom, Fujii-san, Kuroda-san,
> >
> > I saw comments of yours and recognized that better fix is below.
> >
> > - Fix of first attached patch which does not change warning message
> >
> > And I created patch entry of commitfest :)
> > https://commitfest.postgresql.org/52/5497/
> >
> > What should I do additionally?
> > Do I need to write patches for current supporting versions? (12.x - 17.x)
>
> Testing the patch across all supported versions would be helpful.
> If adjustments are needed for specific versions, creating separate
> patches for those would also be appreciated. Since v12 is no longer
> supported, back-patching to it isn't necessary.

thanks.
I try these :)

> BTW, regarding the discussion on the list, please avoid top-posting;
> bottom-posting is the preferred style on this mailing list.

I understand.
I'll be careful from now on :)

(Please Ignore: I attach renamed patch file for updating patch file on
commitfest system)

--
Best regards,
Ryo Kanbayashi
https://github.com/ryogrid

Commits

  1. ecpg: Restore detection of unsupported COPY FROM STDIN.

  2. plpgsql: pure parser and reentrant scanner

  3. Add support for piping COPY to/from an external program.