Re: executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error

Here is an update.

the 8.3 version is now working after i reinstalled the OS.

most probably the issue was due to corrupt libxml2.

Thank you so much for all the help to get rid off the issue.

Regards,
Sushil

Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>
>> Sushil wrote:
>>
>>> *postgres: postgres testdb [local] SELECT: symbol lookup error:
>>> postgres: postgres testdb [local] SELECT: undefined symbol:
>>> xmlNewTextWriterMemory*
>>>
>
>
>> Your problem appears to be here. Check you libxml installation. Maybe
>> someone forgot to export this symbol.
>>
>
> I think it most likely is a corrupted download. Red Hat's normal
> release process includes checks for ABI breakage such as disappearing
> symbols, so it's hard to believe there's really a problem of that ilk.
>
> The annoying thing about this from a Postgres standpoint is that the
> missing symbol results in a runtime crash; a failure at server startup
> would be a lot better IMHO. Ideally, shared libraries would be
> processed with the equivalent of dlopen(RTLD_NOW). But as far as I
> can find we can't easily force that on Linux --- the only available
> way to determine it is to set a magic environment variable that the
> linker consults.
>
> I could fix this in the RPM distribution by putting export LD_BIND_NOW=1
> into the postmaster start script, but I wonder whether there's a better
> way.
>
> regards, tom lane
>
>

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.