While developing a Python program I encountered a situation that makes
on of the PostgreSQL 8.3b4's processes crash badly with a segfault.
Let me explain.
After enabling "debug5" as log level I was able to locate and
reproduce the exact sequence of SQL queries made against my test
database
and cra
Here it is:
postgres$ gdb /usr/local/pgsql/bin/postgres core.1600
(gdb) bt
#0 0x082c101c in pfree (pointer=0x8472f00) at mcxt.c:591
#1 0xb7e46513 in xmlCleanupCharEncodingHandlers () from /usr/lib/libxml2.so.2
#2 0xb7e4f091 in xmlCleanupParser () from /usr/lib/libxml2.so.2
#3 0x082940e4 in xpa
On Dec 12, 2007 1:29 PM, Pavel Stehule <[EMAIL PROTECTED]> wrote:
> I cannot repeat this bug on my test date. Can you send some small set
> that reproduce the bug?
I dumped the entire table here: http://www.oluyede.org/temp/instrument.txt
Let me know if you need anything else
--
Lawrence, oluy
> I think we finally found the problem. Please see if things are more
> stable with 8.3RC1 plus this patch:
>
> http://archives.postgresql.org/pgsql-committers/2008-01/msg00190.php
Sorry for being so late. I'm currently using PostgreSQL RC2 at work
and I notice no crashes.
Thanks!
--
Lawrence,
As specified in the W3C Recommendation for XML the DOCTYPE element is
perfectly valid in a document.
I have a bunch of XML files generated by the boost library which
contains a doctype like this:
which lies within the bound of the recommendation
(http://www.w3.org/TR/xml/#sec-prolog-dtd):
"Note
