From: =?iso-2022-jp?B?GyRCMiYhIUduGyhC?= <bo.wang@infortech.co.jp>
To: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
CC: =?iso-2022-jp?B?GyRCTXshITlAGyhC?= <hao.li@infortech.co.jp>
Subject: Request for official clarification on SQL parameter parsing changes
 in PostgreSQL 15 and 16
Thread-Topic: Request for official clarification on SQL parameter parsing
 changes in PostgreSQL 15 and 16
Thread-Index: AduvVvNQyjDJcbPmTwmwOC/31ImN8w==
Date: Thu, 17 Apr 2025 05:17:18 +0000
Message-ID:
 <TYCP286MB3620D4D19E3793CFA106CCBFB6BC2@TYCP286MB3620.JPNP286.PROD.OUTLOOK.COM>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0:
 =?iso-2022-jp?B?OEJFT0hRaUJiTnMvUEpWZmg2cTJFdk82VXRNR094MDJkQ2JIZGJzR0Fz?=
 =?iso-2022-jp?B?Z1RlUndTOW5uLzk3YUJ4VitmVUR2NTk0TE56dmJJSEJTWU9YbjBhM3R4?=
 =?iso-2022-jp?B?ZHhUakNuREE5MFlycHZacm0rc3ZqOExKV0NiQU9XSW9nWVdaVXVpK1Y3?=
 =?iso-2022-jp?B?dlA0VHFvWFVWcm5zU2JQeW9sUmdjT0pmMSt3dTJXdVhNWkZpZlU0eEQ4?=
 =?iso-2022-jp?B?OUZKVmpUVlFBaTFiUUpmeUZoUStHYkIyZlAzaW0wN1NvR2FmRnRMMjli?=
 =?iso-2022-jp?B?eUlkVFVGVGIrM1NEUVpRWlA0NGFrMVVHUGp5SmdLQlN3bVhTVUFjSVJD?=
 =?iso-2022-jp?B?dVFicjQ5YnZkNWdma3pwbFM2UGNvVWZRc3pRWitza0ZLcEhDb2ZONytw?=
 =?iso-2022-jp?B?NnFVdWZrVlNEMWpZVWJvVk93NzE1SFJPdWkyVHJTRFRMQ0FDa1lITENH?=
 =?iso-2022-jp?B?eVNiOThnNzVNT3VNeUpncUJHS2ZtT1JxY3JJK0JyamRkR2ZSMGxycGE3?=
 =?iso-2022-jp?B?MEhBMlJRNndwZVNtV2F5WkY2MGdWbWZkLzN2T3Nwb2Q3dXBYNHlLNFpR?=
 =?iso-2022-jp?B?a1BmRmdPaDNndkttVmxldkhrMUJ6ZC8xaGlOWE1xNG4wU1l6MnRjUnp1?=
 =?iso-2022-jp?B?RjVnQlJ0NGFzNXJveE9aNGJXNU9MZW9CRzA5U1NldDVGRUdzeFR1Q2k0?=
 =?iso-2022-jp?B?Z2NZcGNWcWtmaE5PSWtUcURYSThCRzhtNHpDWE1zSTNIUjJuVkpWSG51?=
 =?iso-2022-jp?B?bVl6Nm5wbUpxNFJoRy92OXpUZ3lXTmwxdk5FMkx3eHpjejBKeGo5RmEr?=
 =?iso-2022-jp?B?N2pud29HNEliQXRSUklQVHJ3NTN0d0szTTF6TWxWNGxidmV3UzRUV3U3?=
 =?iso-2022-jp?B?eWlkU3hUWjAvVWFoTnNqZUJjL2tQVWttbXpoMkRFN2x2ZStjNjRlMzdl?=
 =?iso-2022-jp?B?RS94WEV5WEtGOW9OSi9qZncxNVErVU51SkFvdUhjMS9CTE5GUnNJdGht?=
 =?iso-2022-jp?B?bVF6bmNlK3g3UERWQzZYMDQxUHErYXBQL1Vtd3NDVkswRkkrS3hBb0tB?=
 =?iso-2022-jp?B?bVVEZkpVSDhHY3lOaEFBSXpnSFJPdGx0N29XdFNRYVpqTVNyTmxqTTZO?=
 =?iso-2022-jp?B?aFo4NmRFZmFuRFBBQ2ZENEU4L0Z3L29oOW9hQktScHZ5bE9uRzloeU1P?=
 =?iso-2022-jp?B?Z0puSUZxTm00eWtIYXFjY0pmcTR5clhNNEFjMDZNYVQ4MEJnajBwa1VK?=
 =?iso-2022-jp?B?UXRMeVFTaVc4QnJUbTQycUYzbnI4ZFFCRmhjV1BEZlhVc3E2YXduWkJa?=
 =?iso-2022-jp?B?bnRuTWg0N2hJRjdteGpQWElVa3VRSU16NVJQcGRhbm1idUwwYmZ6S1Rw?=
 =?iso-2022-jp?B?dXZMRkU3aFExNHRBMGFZOGkvSGNuZHF4OVRHajg1Rm1MaDZZNXZyRnYv?=
 =?iso-2022-jp?B?RVNSdUx1Y0IvRlVYem5NRVliK0wyTmk5eXFqNDEvYWlTa1BoWVd6NEwr?=
 =?iso-2022-jp?B?UUtId1J3QUlxdC92MFJLOE1YekQrVStmQkszKzJWeVRtLy82aW1VcXZX?=
 =?iso-2022-jp?B?dEk3QUE4cFgvZ2w5YWE3Yzl4b3dLdUNWRC9CelBENnlIbzNtNCszU3E2?=
 =?iso-2022-jp?B?ZnRHbzBYVWpFWkViME1EZE9oTHVMcmlDZjRMQnhyVmxDZXhvWUFlV0lW?=
 =?iso-2022-jp?B?RUJPWkRyREVTTW5TTUhWTzQvczFORUpHQXVaSktNOWhVclNmVjcvU0pY?=
 =?iso-2022-jp?B?WVAxNjgvRU1oRE9BUHFodnpQMEV6UFVFWmJjSTc1bTFoMXZZb1NxcFp6?=
 =?iso-2022-jp?B?cTU1OVVxMldEbmdWdDUwcFJ2MjNybC81RmRDcFhsREQ5c2Qrc2xGaW1i?=
 =?iso-2022-jp?B?R2pLekNVdDZqQnNWTzZjY2R4K241bU9qOUJPcC9RVFdLd2hhdlowQlVM?=
 =?iso-2022-jp?B?d0RCL2hQTUMzQnQxaEkxalBJcE5jNXVldXRqdEdsZTlwQ2hvQmxpN2NL?=
 =?iso-2022-jp?B?N2tHa1hXVmlNWjdvZUxKanZjU21STEZHUy9nQXFpWW8yZ1l6cDE3bEht?=
 =?iso-2022-jp?B?THN0dmxqOEdGWDBydVl4OWlxQmhTbU1ZZkU1U2pTUkRHVW11RGl1ejJS?=
 =?iso-2022-jp?B?ZEFsc1dhZDdzUkNzM3o3QkJPSzJqNmVHRVJyTnZWck1zQnhXazRJLzB6?=
 =?iso-2022-jp?B?RjZXRDNkMHI5WUFIcVlkNnlFendDd052cUVXOFIrckFYYXRXWGJleWZI?=
 =?iso-2022-jp?B?QlI5SENwWUlRTHBpSkM0Mm9OcXk5UzltYXZ6M2R4bHh3MGV4blhsanUr?=
 =?iso-2022-jp?B?VlRUbg==?=
Content-Type: multipart/alternative;
	boundary="_000_TYCP286MB3620D4D19E3793CFA106CCBFB6BC2TYCP286MB3620JPNP_"
MIME-Version: 1.0
X-OriginatorOrg: infortech.co.jp
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: TYCP286MB3620.JPNP286.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 8a215b06-7e6d-413d-cb9f-08dd7d6f1ff0
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2025 05:17:18.6882
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cc1bbf89-9cf9-42a6-93f2-da6406d0b117
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: dpsDhHhDbmUXcaoDUjQRPGLgDqr4y2PEx7vrGD6lluFgoVT2Lfz6mwgHxBL/vcbVTQ2rG0myeEJxPTGBgCIFHg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYWP286MB2511
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/TYCP286MB3620D4D19E3793CFA106CCBFB6BC2%40TYCP286MB3620.JPNP286.PROD.OUTLOOK.COM>
Precedence: bulk

--_000_TYCP286MB3620D4D19E3793CFA106CCBFB6BC2TYCP286MB3620JPNP_
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

Hello PostgreSQL Community,

We have encountered unexpected SQL parsing errors during application upgrad=
es from PostgreSQL 14 to 15 and 16, related to the use of JDBC-style parame=
ter placeholders (`?`) in our legacy applications.

Specifically:

1. In PostgreSQL 15 and later:
   The following SQL causes a syntax error unless a space is added after th=
e `?`:
     SELECT * FROM table WHERE a =3D ?AND b =3D 123;
   =1B$B"*=1B(B Adding a space (`? AND`) resolves the issue.
   This did not cause an error in PostgreSQL 14.

2. In PostgreSQL 16:
   The following SQL causes a syntax error:
     SELECT * FROM table WHERE a =3D ?ORDER BY b;
   =1B$B"*=1B(B This query runs in PostgreSQL 15, but causes an error in 16=
 unless a space is added after `?`.

We understand that this behavior may stem from changes to the parser to mak=
e it more strict and SQL-compliant. However, we were unable to find any exp=
licit mention of these changes in the official release notes of PostgreSQL =
15 or 16.

Our client is asking for official documentation or a statement confirming w=
hether this behavior change was intentional and when it was introduced.

Could anyone kindly point us to:
- Relevant release note sections, commits, or discussions on this change
- Confirmation that these are intentional parser changes (and not regressio=
ns)

Any help or references would be greatly appreciated.

Best regards,
Wang Bo

--_000_TYCP286MB3620D4D19E3793CFA106CCBFB6BC2TYCP286MB3620JPNP_
Content-Type: text/html; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-2022-=
jp">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:=1B$B^b%4%7%C%/=1B(B;
	panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@=1B$B^b%4%7%C%/=1B(B";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0mm;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:=1B$B^b%4%7%C%/=1B(B;
	mso-ligatures:standardcontextual;}
span.17
	{mso-style-type:personal-compose;
	font-family:=1B$B^b%4%7%C%/=1B(B;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:99.25pt 30.0mm 30.0mm 30.0mm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026">
<v:textbox inset=3D"5.85pt,.7pt,5.85pt,.7pt" />
</o:shapedefaults></xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"JA" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:bre=
ak-word;text-justify-trim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Hell=
o PostgreSQL Community,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">We h=
ave encountered unexpected SQL parsing errors during application upgrades f=
rom PostgreSQL 14 to 15 and 16, related to the use of JDBC-style parameter =
placeholders (`?`) in our legacy applications.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Spec=
ifically:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">1. I=
n PostgreSQL 15 and later:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs=
p;&nbsp; The following SQL causes a syntax error unless a space is added af=
ter the `?`:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs=
p;&nbsp;&nbsp;&nbsp; SELECT * FROM table WHERE a =3D ?AND b =3D 123;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs=
p;&nbsp; =1B$B"*=1B(B Adding a space (`? AND`) resolves the issue.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs=
p;&nbsp; This did not cause an error in PostgreSQL 14.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">2. I=
n PostgreSQL 16:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs=
p;&nbsp; The following SQL causes a syntax error:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs=
p;&nbsp;&nbsp;&nbsp; SELECT * FROM table WHERE a =3D ?ORDER BY b;<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&nbs=
p;&nbsp; =1B$B"*=1B(B This query runs in PostgreSQL 15, but causes an error=
 in 16 unless a space is added after `?`.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">We u=
nderstand that this behavior may stem from changes to the parser to make it=
 more strict and SQL-compliant. However, we were unable to find any explici=
t mention of these changes in the official
 release notes of PostgreSQL 15 or 16.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Our =
client is asking for official documentation or a statement confirming wheth=
er this behavior change was intentional and when it was introduced.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Coul=
d anyone kindly point us to:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">- Re=
levant release note sections, commits, or discussions on this change<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">- Co=
nfirmation that these are intentional parser changes (and not regressions)<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Any =
help or references would be greatly appreciated.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt"><o:p=
>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Best=
 regards,&nbsp; </span>
<span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-fareast-language:ZH-CN">=
<br>
Wang Bo<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_TYCP286MB3620D4D19E3793CFA106CCBFB6BC2TYCP286MB3620JPNP_--