Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.”

lakshmi <lakshmigcdac@gmail.com>

From: lakshmi <lakshmigcdac@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: "Masashi Kamura (Fujitsu)" <kamura.masashi@fujitsu.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2026-04-21T11:58:19Z
Lists: pgsql-hackers
Hi,
Thanks for the clarification.
from my testing, the current implementation generates invalid code when
multiple header assignments are used, so rejecting the syntax avoids the
issue for now.

That said, supporting multiple COUNT assignments could be useful, but it
would need changes in the code generation. It might be worth checking how
this is handled in the SQL standard or other precompilers.

Regards,
Lakshmi G

On Tue, Apr 21, 2026 at 1:20 PM Hayato Kuroda (Fujitsu) <
kuroda.hayato@fujitsu.com> wrote:

> Dear Lakshmi,
>
> > After applying the patch and rebuilding ecpg, the same statement is now
> rejected
> > during preprocessing with a syntax error. So the patch works as expected.
>
> His patch may work well, but I'm unclear whether it's the correct way to
> fix.
> See my question [1]:
>
> ```
> IIUC, there is another approach, allowing to specify multiple COUNT clause
> in the SET/GET DESCRIPTOR. E.g.,
> ```
>
> We may have to follow SQL standard or other precompilers like Pro*C.
> (Not sure we should spend the effort for the investigation though)
>
> [1]:
> https://www.postgresql.org/message-id/OS9PR01MB12149D090EDD1D8D70770DED7F5232%40OS9PR01MB12149.jpnprd01.prod.outlook.com
>
> Best regards,
> Hayato Kuroda
> FUJITSU LIMITED
>
>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. ecpg: Reject multiple header items in GET/SET DESCRIPTOR