pgsql: Fix crash introduced by incorrect backport 806555e300. - Mailing list pgsql-committers

From Jeff Davis
Subject pgsql: Fix crash introduced by incorrect backport 806555e300.
Date
Msg-id E1vkljt-002zO6-1Q@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Fix crash introduced by incorrect backport 806555e300.
List pgsql-committers
Fix crash introduced by incorrect backport 806555e300.

Commit 7f007e4a04 in master depends on 1476028225, but the latter was
not backported. Therefore 806555e300 (the backport of commit
7f007e4a04) incorrectly used pg_strfold() in a locale where
ctype_is_c.

The fix is to simply have the callers check for ctype_is_c.

Because 7f007e4a04 was only backported to version 18, and because the
commit in master is fine, this fix only exists in version 18.

Reported-by: Александр Кожемякин <a.kozhemyakin@postgrespro.ru>
Discussion: https://postgr.es/m/456f7143-51ea-4342-b4a1-85f0d9b6c79f@postgrespro.ru

Branch
------
REL_18_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/8993bf0991d876c878fe3739d6d4e200a1e122f3

Modified Files
--------------
contrib/ltree/crc32.c     | 34 ++++++++++++++++++++++++----------
contrib/ltree/lquery_op.c | 21 +++++++++++++++++++--
2 files changed, 43 insertions(+), 12 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: pg_waldump: Remove file-level global WalSegSz.
Next
From: Jeff Davis
Date:
Subject: Re: pgsql: Fix crash introduced by incorrect backport 806555e300.