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 1qeKpG-006WJq-Du for pgsql-general@arkaria.postgresql.org; Thu, 07 Sep 2023 19:38:02 +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 1qeKpF-004HWQ-7z for pgsql-general@arkaria.postgresql.org; Thu, 07 Sep 2023 19:38:01 +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 1qeKpE-004HWC-Pk for pgsql-general@lists.postgresql.org; Thu, 07 Sep 2023 19:38:00 +0000 Received: from mout-u-107.mailbox.org ([80.241.59.207]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qeKpA-003jeR-9s for pgsql-general@lists.postgresql.org; Thu, 07 Sep 2023 19:37:59 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4RhTzh0fWTz9sTq; Thu, 7 Sep 2023 21:37:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1694115472; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TsWnzHqjPhExyHtWMVAWjpNLnZVp9LZslT/cZX8hGxc=; b=H6PUYf7w6wuyeb7tTa6C4oaUnNsB3qx9xeOreP5Xvmt0VRIe1TwIU5EpoTAF4tRlmhoRVX +buNs+9dlbeA1qPAKhdBNCOqHSJ4BN1AdREeXqpGYVoD0miuMlRQYnmCogSDrf7cpisAS9 +oSiAQwXUBt9skIxaOWwXBcHGfLxsQ4ClJoxGDjhuGgRcK5qbE5c3s26NZLKYWRx8vX1CL FXxeFAg6TdBonacxG9cVQyqsWQrE9kYqRh1M/nIYfcMc/VtA7qUbs6tqZ3L7F1fuPhNbQR GAq5TEpUR1T9ZyOHzgkGhekCnLtQXu7xJM7LGlG3dW9K0YA+et7JzWKhJWl0OQ== Date: Thu, 7 Sep 2023 21:37:50 +0200 (CEST) From: Erik Wienhold To: Tom Lane , Sai Teja Cc: pgsql-general@lists.postgresql.org Message-ID: <87357840.138645.1694115470979@office.mailbox.org> In-Reply-To: <1736511.1694113781@sss.pgh.pa.us> References: <1736511.1694113781@sss.pgh.pa.us> Subject: Re: Huge input lookup exception when trying to create the index for XML data type column in postgreSQL MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Priority: 3 Importance: Normal List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 07/09/2023 21:09 CEST Tom Lane wrote: > Sai Teja writes: > > We have one table which is storing XML data with 30k records and stores > > huge amount of data. > > We are trying to create the index for this column in the table. But, we= =E2=80=99re > > getting =E2=80=9CHuge input Lookup error=E2=80=9D during creation of In= dex. >=20 > There is no such string anywhere in the Postgres source code; > furthermore, if someone tried to add such an error, it'd get rejected > (I hope) as not conforming to our style guidelines. I thought maybe > it's coming from libxml or the xpath code, but I couldn't get a match > for it anywhere in Debian Code Search either. Is that the *exact* > spelling of the message? Are you sure it's not coming from your > client-side code? Looks like "Huge input lookup" as reported in [1] (also from Sai) and that error is from libxml. [1] https://www.postgresql.org/message-id/CADBXDMV_D3pBaSA5ZfUWnQP42ZO1YsbP= 9GZv8t1FncdGTiLMug%40mail.gmail.com -- Erik