Re: BUG #18274: Error 'invalid XML content'
От | Dmitry Koval |
---|---|
Тема | Re: BUG #18274: Error 'invalid XML content' |
Дата | |
Msg-id | 35ef78f9-8958-4225-ae7e-aead71b0feed@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: BUG #18274: Error 'invalid XML content' (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: BUG #18274: Error 'invalid XML content'
|
Список | pgsql-bugs |
Hi! > Knowing that we have full control of the memory contexts for the XML > nodes, just enforcing the huge flag does not seem like there's any > downside for us. (Right?) I think that's right (flag XML_PARSE_HUGE shouldn't cause any problems). My main doubts are related to the replacement of the xmlParseBalancedChunkMemory() function (that haven't argument for pass XML_PARSE_HUGE flag) with xmlNewNode() + xmlParseInNodeContext() functions (create a fake node and pass the XML_PARSE_HUGE flag to xmlParseInNodeContext function). I'm not sure if this replacement is 100% equivalent (although simple tests work the same). -- With best regards, Dmitry Koval Postgres Professional: http://postgrespro.com
В списке pgsql-bugs по дате отправления: