Kevin Houle <kjh(at)cert(dot)org> 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.)
Also, does adding/removing SSL encryption affect your results?
regards, tom lane