Horton
Menu

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

lakshmi <lakshmigcdac@gmail.com>

View thread
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-24T07:18:41Z
Lists: pgsql-hackers 
Hi,

Thanks for the detailed explanation.

On Fri, Apr 24, 2026 at 10:24 AM Hayato Kuroda (Fujitsu) <
kuroda.hayato@fujitsu.com> wrote:

> Dear Kamura-san,
>
> > For the reasons above, I would like to proceed with the policy of
> treating
> > this as a syntax error.
>
> Make sense, so the v1 patch is usable as-is. It looks good to me.
>
>
> Handling this as a syntax error seems like a reasonable and consistent
approach, especially given the undefined behavior and alignment with other
systems like Pro*C.

The proposed patch looks good to me.

Regards,
Lakshmi G

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