Horton
Menu

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

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

View thread
From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: 'lakshmi' <lakshmigcdac@gmail.com>
Cc: "Masashi Kamura (Fujitsu)" <kamura.masashi@fujitsu.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2026-04-21T07:50:17Z
Lists: pgsql-hackers 
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