From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | 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-07 18:18:49 |
Message-ID: | 1616257.1704651529@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> The problem is in the libxml2 library (in xmlParseBalancedChunkMemory
> function), which is used in PostgreSQL and does not support the
> XML_PARSE_HUGE flag.
> There have been attempts to correct this problem [1].
> Apparently they were unsuccessful because libxml2 technical support refused
> to fix the xmlParseBalancedChunkMemory function.
> I'd like to know what the community's opinion is regarding this error:
> 1) the error is correct and does not need to be corrected;
> 2) corrections should be made in the libxml2 library;
> 3) corrections should be made in PostgreSQL (maybe need to stop using the
> xmlParseBalancedChunkMemory function or make other corrections);
> 4) ...?
libxml2 seems to be a little moribund, so I'm not sure that waiting
for #2 to happen will yield results. On the other hand, XML is
pretty much a development backwater in Postgres too, so if you are
hoping for somebody else to do #3 you are unlikely to get anywhere.
If you want to work on #3 yourself, have at it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey M. Borodin | 2024-01-07 18:33:56 | Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum |
Previous Message | Andrey M. Borodin | 2024-01-07 18:04:35 | Re: [BUG] false positive in bt_index_check in case of short 4B varlena datum |