Re: Huge input lookup exception when trying to create the index for XML data type column in postgreSQL - Mailing list pgsql-general

From Dominique Devienne
Subject Re: Huge input lookup exception when trying to create the index for XML data type column in postgreSQL
Date
Msg-id CAFCRh-83y136owqFsC6YYAbeR8utEFAur4ELMs8C2AEY_iEA2A@mail.gmail.com
Whole thread Raw
In response to Re: Huge input lookup exception when trying to create the index for XML data type column in postgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Thu, Sep 7, 2023 at 10:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Erik Wienhold <ewie@ewie.name> writes:
> Looks like "Huge input lookup" as reported in [1] (also from Sai) and that
> error is from libxml.

Ah, thanks for the pointer.  It looks like for the DOCUMENT case,
we could maybe relax this restriction by passing the XML_PARSE_HUGE
option to xmlCtxtReadDoc().  However, there are things to worry about:

Just a remark from the sidelines, from someone having done a fair bit of XML in years past.

That XPath is simple, and a streaming parser (SAX or StAX) could handle it. While that
XML_PARSE_HUGE option probably applies to a DOM parser. So is there a work-around
to somehow force using a streaming parser instead of one that must produce the whole Document,
just so a few elements are picked out of it? FWIW. --DD

pgsql-general by date:

Previous
From: Matthias Apitz
Date:
Subject: Re: Will PostgreSQL 16 supports native transparent data encryption ?
Next
From: Dominique Devienne
Date:
Subject: Re: Huge input lookup exception when trying to create the index for XML data type column in postgreSQL