Re: BUG #18274: Error 'invalid XML content'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18274: Error 'invalid XML content'
Date: 2024-01-14 19:17:28
Message-ID: 1314313.1705259848@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> writes:
> Attached a patch that adds the use of XML_PARSE_HUGE flag for libxml2
> functions and replaces some functions (that do not support this flag)
> with their equivalents.

Thanks for doing this work! Please add an entry to the upcoming
commitfest[1] to ensure we don't forget about it.

> Maybe it would be a good idea to add a GUC-variable for using of the
> XML_PARSE_HUGE flag?

That strikes me as a completely awful idea. Is there some downside
to XML_PARSE_HUGE?

regards, tom lane

[1] https://commitfest.postgresql.org/47/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Koval 2024-01-14 20:58:07 Re: BUG #18274: Error 'invalid XML content'
Previous Message PG Bug reporting form 2024-01-14 18:48:13 BUG #18292: Unexpected error: "relation "hobbies_r" does not exist" caused by user-defined functions