Kevin Houle <[EMAIL PROTECTED]> writes:The nature of the bug is that an 'lo_read' operation performed with DBD::Pg caused a segfault with postgresql-libs-7.3.2 and "hangs" on files >= 32768 bytes with postgresql-libs-7.3.4. The hang is actually a read() loop on the socket generating EAGAIN error on each read().
Can you get us a gdb stack trace from the segfault cases? (And from the loop cases too; a stack trace back from the repeated read() call would be useful.)
The attached gdb-7.3.2.log is from the segfault case using postgresql-libs-7.3.2 and the gdb-7.3.4.log is the loop case from postgresql-libs-7.3.4. I had to SIGINT the loop case to get the stack trace.
Also, does adding/removing SSL encryption affect your results?
Yes. It works flawlessly without SSL. I thought I had tested that previously but in fact did not correctly; I re-tested and it works without SSL and fails with SSL. The stack traces seem to point to pqsecure_read().
Let me know if I can provide anything else.
Kevin
gdb-7.3.2.log
Description: Binary data
Description: Binary data---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
