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 1s78OS-003rkk-5E for pgsql-bugs@arkaria.postgresql.org; Wed, 15 May 2024 06:45:41 +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 1s78OR-00Ad9t-LR for pgsql-bugs@arkaria.postgresql.org; Wed, 15 May 2024 06:45:39 +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 1s78OQ-00Ad9k-MC for pgsql-bugs@lists.postgresql.org; Wed, 15 May 2024 06:45:39 +0000 Received: from fhigh2-smtp.messagingengine.com ([103.168.172.153]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s78OK-000Jyu-EH for pgsql-bugs@lists.postgresql.org; Wed, 15 May 2024 06:45:38 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 294F811400F6; Wed, 15 May 2024 02:45:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 15 May 2024 02:45:31 -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=1715755531; x=1715841931; bh=PEY9BBIypzJUQSKF/M1JVoQN0hjTCXqQ opZ8npgx4JY=; b=zuYWx1JnwvID/Kfpb4OxoC026M2AFVTBo7XowjKYCi/+f97e BDdzOoe1NMUtP+Od9QpHzJLwD+p7m2SEQ59XZcPz52s3YazQ8/1UNONezKMH3Luw 4zXfD3UWcVJ+jan7gz8U/9eyUj3xWUblSNVhI+hb09ZDB9S1JO5QN3yFJAiV2iU4 p6igtzmqwPZXwrMm1x4MpHC3Kv5P/jZx/79Dlt8q2x2oeUlSMt4HBHabK8zbmI8u 1DyW3XAMYT78fnQVeuCOX6Ue4Qw4ckRqaOexqJGHczIsUIqkN5FgwAiEqu/XGH5P 8ynrNu+UZAhiB0UD2rDls2Gpg9JEfi4Es8Fwyg== 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=1715755531; x= 1715841931; bh=PEY9BBIypzJUQSKF/M1JVoQN0hjTCXqQopZ8npgx4JY=; b=J HxpaGF4lBptj7rZi+mjA9svv66SSsgvVlkEa5C9mIjMUif+R2W8u2LNlt+8x8mOY 2OWT9e07AhSqQpwO6B4QchjYCzHIzzprm7vwcND+p8gl+mtlo6J4moDUDESPzWAV ZTcbK3XOdJYVHcelTrGgmbt6l5eeTUD3/y2WJSYJGeTh1i4f1HxZtqWzTZOMcUOL 9pL/vcPNkXF72r3Doheh3IH2/3pv8YvkBOky3MQcBddnkWA0RPsCmTIKuxHwhms9 Xv9UpShyeiFVH4UqA2YVvuoSnfSUP0Sj5v+7HOYhOhbytAWo/1eUvk2TRLr1FX2r 0ExreReOKpIDL75EwRH5Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdegjedguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorh hgqeenucggtffrrghtthgvrhhnpefgjedthfekfedtuefgieelheetleejgefhueeltdfh ueetvdffudekfeejhfegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 May 2024 02:45:29 -0400 (EDT) Message-ID: Date: Wed, 15 May 2024 08:45:27 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18362: unaccent rules and Old Greek text To: Robert Haas , Thomas Munro Cc: Cees van Zeeland , Michael Paquier , Tom Lane , pgsql-bugs@lists.postgresql.org References: <18362-be6d0cfe122b6354@postgresql.org> 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 14.05.24 16:51, Robert Haas wrote: > 1. The question of rule file load times seems like something that > anyone who could compile PostgreSQL with and without a patch applied > could test in under an hour. They could then report the results that > they got, and people here could judge whether the resulting numbers > are totally cool or very sad or something in between. Anyone willing > to do that? The rules are only loaded once on first use, right? I tested with date; for x in $(seq 1 1000); do psql -X -c "select unaccent('foobar')" -o /dev/null; done; date and this had the same runtime (about 8 seconds here) with and without the patch. Btw., with the patch I get WARNING: duplicate source strings, first one will be used so it will need to adjustments in how the rules are produced.