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.96) (envelope-from ) id 1vt5Kg-001qCH-1M for pgsql-general@arkaria.postgresql.org; Thu, 19 Feb 2026 14:48:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vt5Ke-003nvA-39 for pgsql-general@arkaria.postgresql.org; Thu, 19 Feb 2026 14:48:44 +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.96) (envelope-from ) id 1vt5Ke-003nuz-00 for pgsql-general@lists.postgresql.org; Thu, 19 Feb 2026 14:48:44 +0000 Received: from fout-a8-smtp.messagingengine.com ([103.168.172.151]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vt5KY-000000009V8-1pJI for pgsql-general@postgresql.org; Thu, 19 Feb 2026 14:48:42 +0000 Received: from phl-compute-07.internal (phl-compute-07.internal [10.202.2.47]) by mailfout.phl.internal (Postfix) with ESMTP id 4426EEC053B; Thu, 19 Feb 2026 09:48:36 -0500 (EST) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-07.internal (MEProxy); Thu, 19 Feb 2026 09:48:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; 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:subject:subject:to:to; s=fm2; t=1771512516; x=1771598916; bh=XnzuVQUxWsuUiswSuKmlLPSVbkz3q1cUFtETm+vB2z4=; b= dHKgcibvZLtUMbGD0ctLopJVkim5exVuywEdbOX+1/B7z1Lycm1gAuUNZR3c5U9k Pe0EMY124fXiCNwB3mHAe89VK241gUDSwyGYxz+twtCKvbwr3nfYpdHL7REG4Vzc ZRLZDkRSJvJpuVGvzHEwwakxJj+J9mellZeSNn6GizIqCXAPIanvCef2uWGzwkRJ 5EOWB4nInMPXTgK9xztMOhgwDM9CDXmyA4JVGnSpyviAPqyAU0X9snXBDnRZpB0X xW0Uy5yOMnG8cH8SuoF9hg5s9K0e6q/ktzgnqMQSsGByk+RwbTXVarpAp+cAebO+ wROBtZMOuzDxyPtd+GxZQw== 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:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1771512516; x=1771598916; bh=X nzuVQUxWsuUiswSuKmlLPSVbkz3q1cUFtETm+vB2z4=; b=a0nv9HWEP4+wYDiua 4M97RLhczlwXpKkhIvl0NUZCp2pAFaipiUEOypdkFrUv3Jzqyh3jFbBHY3ThFsi6 c6MiHOormr1zMFGC1cMqcQPVqncj0AE4KaQ+7R7i4widT2pm1ozVJbPTVYBdH3gL xoSKVXMuO6vTLZmoO7gPOwgvV6ue1EFqI7WUrmEZQADFh96bQWwhgVB6LGO9SBdW 7I/DtmbxKKVio7XLG3E7Ax7/nRh18JepeL0nNepSQCNWg85CPrZZWSD8H3zAATg5 EFG6jDtdgPQoF+RQCGyBo87xubw+N8VBmGRhOMYYJ2D29RUtX3npqvChHxpmLxEg GVNZg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddvvdehkeduucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgvthgvrhcu gfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhgqeenuc ggtffrrghtthgvrhhnpeehiedvhfeuhfeugefgfeehgeejtdevuefhtefhueefvddugfdt ueehgfefudfhffenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrghdpnhgspghrtghpthhtohep vddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepuggvphgvshiiseguvghpvghsii drtghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehpohhsthhgrhgvshhq lhdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Feb 2026 09:48:35 -0500 (EST) Message-ID: <3dbae091-6168-4b4b-91dc-4bf1a3a51136@eisentraut.org> Date: Thu, 19 Feb 2026 15:48:33 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Can we get sha* function over text, that could be used in index? To: depesz@depesz.com, pgsql-general mailing list 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 18.02.26 15:58, hubert depesz lubaczewski wrote: > And while I kinda undestand, create-conversion, server-encoding, I don't > really*grok* why we can't have immutable conversion to bytea. And/or > versions of sha* functions that simply work on text. Hash functions fundamentally work on a sequence of bytes, so bytea is the right type. The encoding of text into bytes is complicated, so it seems better if you handle that yourself depending on the local requirements.