From: Jeff Davis <jdavis@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix multibyte issue in ltree_strncasecmp().
Date: Tue, 16 Dec 2025 18:49:27 +0000
Message-ID: <E1vVa6w-0016vm-1v@gemulon.postgresql.org> (raw)
Fix multibyte issue in ltree_strncasecmp().
Previously, the API for ltree_strncasecmp() took two inputs but only
one length (that of the smaller input). It truncated the larger input
to that length, but that could break a multibyte sequence.
Change the API to be a check for prefix equality (possibly
case-insensitive) instead, which is all that's needed by the
callers. Also, provide the lengths of both inputs.
Reviewed-by: Chao Li <li.evan.chao@gmail.com>
Reviewed-by: Peter Eisentraut <peter@eisentraut.org>
Discussion: https://postgr.es/m/5f65b85740197ba6249ea507cddf609f84a6188b.camel%40j-davis.com
Backpatch-through: 14
Branch
------
REL_18_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/f79e239e0bc6e4d5fe91e1a0e573ecf0715d6c8c
Modified Files
--------------
contrib/ltree/lquery_op.c | 40 ++++++++++++++++++++++++++++------------
contrib/ltree/ltree.h | 7 +++++--
contrib/ltree/ltxtquery_op.c | 8 ++++----
3 files changed, 37 insertions(+), 18 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: jdavis@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix multibyte issue in ltree_strncasecmp().
In-Reply-To: <E1vVa6w-0016vm-1v@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox