summaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2025-07-28 16:50:42 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2025-07-28 16:50:42 -0400
commit589d6e6408b4f2fd4e7ac6941cd3bc2c16893b47 (patch)
tree1b00c31d2b8b14cea95ffa0cd7155d4407e1e28b /src/backend/access/gist
parentf32a471612c9e6adc87254239299024ff3b487ec (diff)
Avoid regression in the size of XML input that we will accept.
This mostly reverts commit 6082b3d5d, "Use xmlParseInNodeContext not xmlParseBalancedChunkMemory". It turns out that xmlParseInNodeContext will reject text chunks exceeding 10MB, while (in most libxml2 versions) xmlParseBalancedChunkMemory will not. The bleeding-edge libxml2 bug that we needed to work around a year ago is presumably no longer a factor, and the argument that xmlParseBalancedChunkMemory is semi-deprecated is not enough to justify a functionality regression. Hence, go back to doing it the old way. Reported-by: Michael Paquier <michael@paquier.xyz> Author: Michael Paquier <michael@paquier.xyz> Co-authored-by: Erik Wienhold <ewie@ewie.name> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/aIGknLuc8b8ega2X@paquier.xyz Backpatch-through: 13
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions