On 10/17/23 11:24, Hafeez Rahim wrote:
>
> Hi
>
> This is to check regarding an issue we came across on postgreSQL
> community version 11 with minor patch 11.20 along with few other changes
> change details mention on end part of this mail
>
> The issue is notice after the minor patching from postgreSQL 11.16 to 11.20
> The particular database runs on a dockerized platform
>
> Issue :
>
> One of the table query not woks when string values are filtered with =
> clause
> where as the query works with like clause using '%' flag or using
> trim(column)
> below are query examples describes the problem
>
> not working
>
> select * from atlas_order.gdp_ship_logistic_food cgslf where
> shipping_group_id = '2VxFRCOG9tc7SjQ2Ogg0bveve96';
>
> working
>
> select * from atlas_order.gdp_ship_logistic_food cgslf where
> shipping_group_id like '%2VxFRCOG9tc7SjQ2Ogg0bveve96%';
> select * from atlas_order.gdp_ship_logistic_food cgslf where
> shipping_group_id like '2VxFR%COG9tc7SjQ2Ogg0bveve96';
> select * from atlas_order.gdp_ship_logistic_food cgslf where
> trim(shipping_group_id) = '2VxFR%COG9tc7SjQ2Ogg0bveve96';
>
> Later as per the feedback from dev we have dropped and recreated the
> constraints and rebuild the indexes of the affected tables
> and the data is accessibleafter on
I would say the above is due to the distro change below.
> 2. Change docker container base image from Debian to Alpine (Debian
> Bookworm - alpine3.18)
My guess something along lines of:
https://wiki.postgresql.org/wiki/Locale_data_changes
Changing distro's mid stream increases the likely hood there will be issues.
--
Adrian Klaver
adrian.klaver@aklaver.com
