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 1s2We5-003kX0-3O for pgsql-hackers@arkaria.postgresql.org; Thu, 02 May 2024 13:38:45 +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 1s2We2-000ePN-By for pgsql-hackers@arkaria.postgresql.org; Thu, 02 May 2024 13:38:43 +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 1s2We0-000eNy-Fk for pgsql-hackers@lists.postgresql.org; Thu, 02 May 2024 13:38:42 +0000 Received: from wfhigh4-smtp.messagingengine.com ([64.147.123.155]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s2Wdy-0015aK-7u for pgsql-hackers@postgresql.org; Thu, 02 May 2024 13:38:40 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.west.internal (Postfix) with ESMTP id 881DC1800172; Thu, 2 May 2024 09:38:35 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 02 May 2024 09:38:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc: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:subject:subject:to:to; s=fm2; t=1714657115; x=1714743515; bh=YMrvWvZ30QBe+VtzR4nM9ViOd/gf/3pv 3JpbkPhS8Iw=; b=XuQAoMpMCcwnz0HRim9aAQ56b+3j4LQaWLMIm9GzcjIykMwq FvLinzeD0Rx0fiFA9F5/mDJzwnIJ7Rvje8Wz55pmEno8qAB+cJyaXoPSA0AFnJMG T2vuwXtmPpBt2zagshS65Tg11a3zU+xumlZvnifi9yp3Qg60iDMmGkuliKpztJaG AVQtkMTY9vZtdTeib+uxWGWLXN400bCKiy0NhLIYZYY1wxg8l8UAOv0edS3ATqdf T59xEl+qnYhvfSIzFDOeMyRJw73nuqaRYYzgofhL8w/m+n//vw4V1YlZUF9xt7GO f+rTtXiPdF/mzVwbACZozuroCJu2tXFSQKAOQg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1714657115; x= 1714743515; bh=YMrvWvZ30QBe+VtzR4nM9ViOd/gf/3pv3JpbkPhS8Iw=; b=c XocaSUQc2T6xmlnZM2gnGMXCDKMvwOQEo/WNQcba+tW8JnX4kZCPh0apJRI/IPno n2vO9mEHTTdNHbmS2qwSZYaT9Z03Gv97YQWbC7ZYvOC0PQgiDclpOScpk2T8zOqM +/0Pq71m85DzR4weOvIb4RqKAPvuUrE7Rawr2yrZirTUOheU7oE37T+jOsYE/jZP uwX7HrQpbRLr4f2NuqfGiVux0Q4Yvhcc11fogs5BQMVDT2IbGIWgrz3/NuIAOIMk /zk1dFNRgKA28ckwdBiKdm1URsAXmC6VGONwYsqAQvILcWo6FsjssEE5lm+12y3d WGz1ukdE1Wj9KQFAxGpJQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvddukedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepgfejtdfhkeeftdeugfeileehteeljeeghfeuledthfeu tedvffdukeefjefhgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 2 May 2024 09:38:34 -0400 (EDT) Message-ID: Date: Thu, 2 May 2024 15:38:32 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Support LIKE with nondeterministic collations To: Daniel Verite Cc: pgsql-hackers References: Content-Language: en-US From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 30.04.24 14:39, Daniel Verite wrote: > postgres=# SELECT '.foo.' like '_oo' COLLATE ign_punct; > ?column? > ---------- > f > (1 row) > > The first two results look fine, but the next one is inconsistent. This is correct, because '_' means "any single character". This is independent of the collation. I think with nondeterministic collations, the single-character wildcard is often not going to be all that useful.