| From: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18274: Error 'invalid XML content' |
| Date: | 2024-01-25 12:12:07 |
| Message-ID: | 99aae616-db97-4632-8934-4f39e7105631@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> he security team has discussed 2197d06224a1 after a report from
> coverity regarding the effects that issues like [1] would create in
> the backend, and concluded that this patch should be reverted because
> this could cause the backend to waste plently of CPU and/or memory
> even if the application applied checks on the size of the data given
> in input, and libxml2 does not offer guarantees that input limits are
> respected under XML_PARSE_HUGE.
Thanks for info!
I agree that reverting a patch is a good idea if there are concerns
about server resources (XML is used by few users and there are even
fewer users who need to parse elements larger than 10Mb).
For such users it is better to create custom PostgreSQL build.
--
With best regards,
Dmitry Koval
Postgres Professional: http://postgrespro.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-01-25 14:06:27 | Re: 回复: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment |
| Previous Message | PG Bug reporting form | 2024-01-25 09:24:37 | BUG #18311: python3-psycopg2 packaged for wrong python version |