[BUGS] executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error
e 1 LOG: record with zero length at 0/367B04B0 LOG: redo is not required DEBUG: transaction ID wrap limit is 2147484025, limited by database "template1" DEBUG: proc_exit(0) DEBUG: shmem_exit(0) DEBUG: exit(0) DEBUG: reaping dead processes LOG: autovacuum launcher started LOG: database system is ready to accept connections The server appeared as crashed and got restarted. Seek your help to have this issue fixed. Thanks, Sushil 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.begin:vcard fn:Sushil Dive n:;Sushilchandra Dive org:Vertex Software Pvt Ltd;Delivery adr:;;;Pune;MH;;IN email;internet:[EMAIL PROTECTED] tel;work:+91 20 6604 1500 Ex. 554 x-mozilla-html:TRUE version:2.1 end:vcard -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error
I tried installing following RPMs postgresql-8.3.5-1PGDG.rhel5.x86_64.rpm postgresql-libs-8.3.5-1PGDG.rhel5.x86_64.rpm postgresql-server-8.3.5-1PGDG.rhel5.x86_64.rpm still this issue is appearing. is there any thing i am missing? Please advise. Thanks, Peter Eisentraut wrote: > Sushil wrote: >> I am trying to exploit XML features of PostgreSQL 8.3.0 DB. > > You should upgrade to the latest 8.3 release, currently 8.3.5. There > were some fixes in this area (and other areas). > > 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.begin:vcard fn:Sushil Dive n:;Sushilchandra Dive org:Vertex Software Pvt Ltd;Delivery adr:;;;Pune;MH;;IN email;internet:[EMAIL PROTECTED] tel;work:+91 20 6604 1500 Ex. 554 x-mozilla-html:TRUE version:2.1 end:vcard -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error
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 libxml2 istalled libxml2-2.6.26-2.1.2 libxml2-python-2.6.26-2.1.2 libxml2-2.6.26-2.1.2 its a Centos 5.1 environment. the system on which this issue is appearing has following libxml2 RPMs installed libxml2-2.6.26-2.1.2.1 libxml2-python-2.6.26-2.1.2.1 libxml2-2.6.26-2.1.2.1 please note that system where the issue is has libxml2 library with higher version. 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 worked. Peter Eisentraut wrote: > 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. > > 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.begin:vcard fn:Sushil Dive n:;Sushilchandra Dive org:Vertex Software Pvt Ltd;Delivery adr:;;;Pune;MH;;IN email;internet:[EMAIL PROTECTED] tel;work:+91 20 6604 1500 Ex. 554 x-mozilla-html:TRUE version:2.1 end:vcard -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] 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 <[EMAIL PROTECTED]> 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.begin:vcard fn:Sushil Dive n:;Sushilchandra Dive org:Vertex Software Pvt Ltd;Delivery adr:;;;Pune;MH;;IN email;internet:[EMAIL PROTECTED] tel;work:+91 20 6604 1500 Ex. 554 x-mozilla-html:TRUE version:2.1 end:vcard -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
