Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects - Mailing list pgsql-bugs

From Tom Lane
Subject Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects
Date
Msg-id 12847.1060951403@sss.pgh.pa.us
Whole thread Raw
In response to DBD::Pg 'lo_read' fails on >= 32768 byte large objects  (Kevin Houle <kjh@cert.org>)
Responses Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects  (Kevin Houle <kjh@cert.org>)
List pgsql-bugs
Kevin Houle <kjh@cert.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: two minor issues with date time types
Next
From: Tom Lane
Date:
Subject: Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects