| From: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18274: Error 'invalid XML content' |
| Date: | 2024-01-14 18:28:50 |
| Message-ID: | 5588db01-45be-48ff-b158-85f789bc502c@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi!
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.
Using libxml2 library functions with support of XML_PARSE_HUGE flag
increases maximum size allowed for a single text node from 10.000.000 to
1.000.000.000 (see XML_MAX_TEXT_LENGTH macro,
libxml2/include/libxml/parserInternals.h) which in most cases solves the
problem with insufficient memory.
What do you think about the patch?
Maybe it would be a good idea to add a GUC-variable for using of the
XML_PARSE_HUGE flag? (The current behavior without XML_PARSE_HUGE flag
is default).
--
With best regards,
Dmitry Koval
Postgres Professional: http://postgrespro.com
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Added-support-of-XML_PARSE_HUGE-flag-for-XML-docu.patch | text/plain | 5.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Tom Lane | 2024-01-14 17:39:26 | Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger |