From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Sokolov Yura <funny(dot)falcon(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: BUG #3860: xpath crashes backend when is querying xmlagg result |
Date: | 2008-01-09 23:01:42 |
Message-ID: | 20080109230142.GB22548@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-patches |
Alvaro Herrera escribió:
> 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.
>
> We call it *after* the context has been reset -- or at least that's what
> gdb is showing me.
>
> Hardware watchpoint 3: handlers[0]
I forgot to mention that I had a breakpoint on xmlCleanupParser that
didn't fire.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2008-01-09 23:44:07 | Re: BUG #3866: Segfault during table update when using convert_from() |
Previous Message | Alvaro Herrera | 2008-01-09 22:42:19 | Re: BUG #3860: xpath crashes backend when is querying xmlagg result |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-09 23:28:00 | Revised patch for fixing archiver shutdown behavior |
Previous Message | Alvaro Herrera | 2008-01-09 22:42:19 | Re: BUG #3860: xpath crashes backend when is querying xmlagg result |