xmlNewTextWriterMemory might be causing this issue.
I have following details in this regard.
the query works on postgres 8.3 installation on a system with following
its a Centos 5.1 environment.
the system on which this issue is appearing has following libxml2 RPMs
please note that system where the issue is has libxml2 library with
to see if this higher version is causing the issue, i installed these
RPMs on earlier system (where the select query works). the query still
Peter Eisentraut wrote:
> Sushil wrote:
>> *postgres: postgres testdb [local] SELECT: symbol lookup error:
>> postgres: postgres testdb [local] SELECT: undefined symbol:
> Your problem appears to be here. Check you libxml installation.
> Maybe someone forgot to export this symbol.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy the original message all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
Please do not print this email unless it is absolutely necessary.
Description: text/x-vcard (216 bytes)
In response to
pgsql-bugs by date
|Next:||From: Alexandra Nitzschke||Date: 2008-11-21 14:49:39|
|Subject: Re: could not read block 77 of relation 1663/16385/388818775|
|Previous:||From: Peter Eisentraut||Date: 2008-11-21 10:12:45|
|Subject: Re: executing SELECT xmlelement(name foo); causes "server
closed the connection unexpectedly" Error|