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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: "Masashi Kamura (Fujitsu)" <kamura(dot)masashi(at)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, lakshmi <lakshmigcdac(at)gmail(dot)com>
Subject: Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.”
Date: 2026-06-03 08:13:37
Message-ID: CAHGQGwEtLCMPJ21vqVFCO82KbC7dMA0zzNThV8dyf=0yY7DtWQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 29, 2026 at 12:44 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> Oh, I didn't recognized that we had TAP tests to detect error/warnings by the pre compiler.
> I do not have strong opinions for it.

IMO it feels a bit odd to add a test specifically for multiple items in
GET/SET DESCRIPTOR causing a syntax error, given that there are many
other unsupported syntax cases that we do not test. So I'm thinking not
to include that test.

Masashi-san,

Do you think this fix should be backpatched to all supported versions?
If so, could you prepare patches for the older branches?

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message yangboyu 2026-06-03 08:13:44 Optimize RelfilenumberMapInvalidateCallback for logical decoding performance
Previous Message Zsolt Parragi 2026-06-03 08:12:31 Re: Fix bug of CHECK constraint enforceability recursion