| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, Sheikh Amjad <sheikhamjad(at)gmail(dot)com> |
| Subject: | Re: Postgresql 8.3 beta crash |
| Date: | 2007-11-01 18:09:08 |
| Message-ID: | 9385.1193940548@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane wrote:
>> The note
>> at line 27ff of xml.c implies that libxml keeps static pointers to
>> allocated things that it thinks will survive indefinitely, so we
>> may have to have these. I'm suspicious whether xmlelement doesn't
>> have a problem if the called expressions error out ...
> Hmm. That could also be fixed if we separated xml_init() and
> xmlInitParser().
Do we know that only xmlInitParser() sets up such static pointers?
If we do, I wonder whether we could call xmlInitParser once in
TopMemoryContext (or before changing the memory function pointers
at all) and then never do xmlCleanupParser?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-01 18:30:24 | Re: beta2, I can't set UTF-8 for czech locales on win |
| Previous Message | Tom Lane | 2007-11-01 17:48:13 | Re: Calculation of a shared memory |