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 1reOPW-00B7ve-GI for pgsql-bugs@arkaria.postgresql.org; Sun, 25 Feb 2024 23:59:58 +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 1reOPU-009Twq-IQ for pgsql-bugs@arkaria.postgresql.org; Sun, 25 Feb 2024 23:59:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1reOPU-009Twh-9w for pgsql-bugs@lists.postgresql.org; Sun, 25 Feb 2024 23:59:56 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1reOPN-000zVo-On for pgsql-bugs@lists.postgresql.org; Sun, 25 Feb 2024 23:59:56 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 41PNxbi61667236; Sun, 25 Feb 2024 18:59:37 -0500 From: Tom Lane To: Michael Paquier cc: Thomas Munro , cees.van.zeeland@freedom.nl, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18362: unaccent rules and Old Greek text In-reply-to: References: <18362-be6d0cfe122b6354@postgresql.org> Comments: In-reply-to Michael Paquier message dated "Mon, 26 Feb 2024 08:25:36 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1667234.1708905577.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sun, 25 Feb 2024 18:59:37 -0500 Message-ID: <1667235.1708905577@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Mon, Feb 26, 2024 at 12:15:57PM +1300, Thomas Munro wrote: >> That has a normal looking sequence that we can understand (α + an >> accent). If I tell the script to follow such "simple" redirections, I >> get over a thousand new mappings, including those. See attached. >> There is probably more correct terminology that I'm using here... > Ah, you've beaten me to it. Yes, that's pretty much the impression I > was getting while looking at the set of characters in Unicode.txt. I > am not entirely sure if what you are doing is the best way to do it, > but the set of characters generated in unaccent.rules makes sense > here. I am surprised to see that many, TBH. There are only about 1650 lines in our standard unaccent.rules file today. Are we concerned about adding so many more? I don't think the trie lookup logic would be slowed any, but the time to load the rules file might take a hit. regards, tom lane