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 1qeKNw-006URY-UP for pgsql-general@arkaria.postgresql.org; Thu, 07 Sep 2023 19:09:48 +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 1qeKNv-0043FO-MX for pgsql-general@arkaria.postgresql.org; Thu, 07 Sep 2023 19:09:47 +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 1qeKNv-0043F3-5F for pgsql-general@lists.postgresql.org; Thu, 07 Sep 2023 19:09:46 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qeKNr-003Ie0-Hc for pgsql-general@lists.postgresql.org; Thu, 07 Sep 2023 19:09:45 +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 387J9fBg1736512; Thu, 7 Sep 2023 15:09:41 -0400 From: Tom Lane To: Sai Teja cc: pgsql-general@lists.postgresql.org Subject: Re: Huge input lookup exception when trying to create the index for XML data type column in postgreSQL In-reply-to: References: Comments: In-reply-to Sai Teja message dated "Thu, 07 Sep 2023 22:58:30 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1736510.1694113781.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 07 Sep 2023 15:09:41 -0400 Message-ID: <1736511.1694113781@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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’re > getting “Huge input Lookup error” during creation of Index. 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? regards, tom lane