| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: contrib/xml2 pfree bug |
| Date: | 2009-07-24 22:30:42 |
| Message-ID: | 4A6A3612.1090403@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Didn't we just clean up a mess in our XML handling to do with memory
>> handlers? It looks like contrib/xml2 might have similar problems.
>>
>
> Yeah, it's using xmlMemSetup(), and being even less careful than the
> core code was :-(.
>
> Do we feel like fixing it, or is it time to rip it out?
>
>
>
Well, we don't have an XSLT processor in core code. If we get one, we
should rip this module out from HEAD. But this is a bug in released code
- we don't want to rip that out, right? It works OK in some
circumstances, but crashing it was trivially easy.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2009-07-24 22:35:31 | Re: SE-PostgreSQL Specifications |
| Previous Message | KaiGai Kohei | 2009-07-24 22:23:22 | Re: SE-PostgreSQL Specifications |