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

From: "Masashi Kamura (Fujitsu)" <kamura(dot)masashi(at)fujitsu(dot)com>
To: 'lakshmi' <lakshmigcdac(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.”
Date: 2026-04-24 03:08:36
Message-ID: OS9PR01MB131740CE3324CB59E6C22F1F2942B2@OS9PR01MB13174.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Syntax rules in the SQL standard do not appear to include any restrictions on specifying COUNT multiple times.
However, since the behavior when COUNT is specified multiple times in SET DESCRIPTOR is not also defined, I consider this to be undefined behavior.

In Oracle's Pro*C, COUNT can be specified only once.

Specifying it multiple times results in a syntax error.

This issue has been occurring from PG14 to PG18, but no one has pointed it out until now.

For the reasons above, I would like to proceed with the policy of treating this as a syntax error.

Regards,
Masashi Kamura
Fujitsu Limited

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-04-24 03:10:03 Re: Redundant/mis-use of _(x) gettext macro?
Previous Message jian he 2026-04-24 02:59:49 Re: [PATCH] Fix null pointer dereference in PG19