Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qsqXw-009kAR-64 for pgsql-general@arkaria.postgresql.org; Tue, 17 Oct 2023 20:20:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qsqXu-00E1MI-2H for pgsql-general@arkaria.postgresql.org; Tue, 17 Oct 2023 20:20:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qsqXs-00E1KA-BW for pgsql-general@lists.postgresql.org; Tue, 17 Oct 2023 20:20:06 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qsqXp-000ySX-Uk for pgsql-general@lists.postgresql.org; Tue, 17 Oct 2023 20:20:03 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 638E75C03D7; Tue, 17 Oct 2023 16:20:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 17 Oct 2023 16:20:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1697574000; x=1697660400; bh=4rtdkk1YUePo4pxRjEH19ir8y3rGua6e/wD OJZ1FDEc=; b=VLFEiC2XvTIM0q9MxRxXiBRoFoiMmHbYqLjCgPE9dJxAGvlQzwE ZMODl89M5U4O0eoQBjBYp2L62oBqb7Z1qrIc9axXJpNYvpn9tuYe80sEvud12qmA ecuJuX1lQ0vGF14OOadfOTZFyRaksUAvxeJiTRS2ZxeUxO6SMKJlUEhI2TBQR5XI DkEYSnSxL/oD47cGQgxl2MnWXQLSUhHrWVzJvLiSxKlTjT4u3JAVaSZIXfGyozgz koub476ZH72rq9ICRKPNAJh+5WmcSb6atHgnDz9+Qb8aqCZdCceqBZZD9F34BF5z sZfzVjk/KwyrRIeOoV2rO9HAGah/Z3XkyMQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1697574000; x= 1697660400; bh=4rtdkk1YUePo4pxRjEH19ir8y3rGua6e/wDOJZ1FDEc=; b=n PCCQf09XEqRdeLV2sX8y9svms5ebrjrmW/zG0AM5OKCl8+G5i+92iBIqtEmwG7oE 3F7rIcdqwq2vcjlwD6rHcXg0QA9b+CtdhuMGT1l5p46DOPtDg3X71K3UBbSYy0Ce sjQMj0oYalRkuPtJPh5ACgKw46GnR/493/bmoqJRoHIVQnqoRntwJ13e1z4J/Jiy bdH32NSIbDXDcD2MmDRmnpCLMsgrCwmrX5b3r083XrDB2jIQEpBB67Dso/6ORfpT Sj6bF6gQBlLqRBruwFvGWn0EH3aAC4oWi1IDPjH3jsVkUjsD7DI10mr3Y1/vdhIg ouhCE6oxgp2iTkZuKsctA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrjedvgddugeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeelgeevkeekkeeuiefgtdevieeluefhfedufeetkeej ffekjeeujeehgeehgeektdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 17 Oct 2023 16:19:59 -0400 (EDT) Message-ID: Date: Tue, 17 Oct 2023 13:19:58 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Index based search have issues with 11.20 To: Hafeez Rahim , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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