Re: BUG #3860: xpath crashes backend when is querying xmlagg result
От | Alvaro Herrera |
---|---|
Тема | Re: BUG #3860: xpath crashes backend when is querying xmlagg result |
Дата | |
Msg-id | 20080110004114.GD22548@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: BUG #3860: xpath crashes backend when is querying xmlagg result (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #3860: xpath crashes backend when is querying xmlagg result
Re: BUG #3860: xpath crashes backend when is querying xmlagg result |
Список | pgsql-bugs |
Tom Lane escribió: > We might be able to compromise by only resetting the context after > an error, but this is still only possible if we have a way to make > libxml let go of *all* pointers to alloc'd objects. I don't understand > your comment that xmlCleanupParser solves it --- we call that already, > and it doesn't seem to be preventing the problem. With the attached patch, it doesn't crash, but I see the added WARNING four times in the log, which is proof that the cleanup thing is not called as the code seems to think. I wonder -- is this thing supposed to be reentrant? I think that's the whole problem with it. (I think what I'm doing in xml_init in the non-first case is bogus anyway -- but I post the patch to show my point.) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Вложения
В списке pgsql-bugs по дате отправления: