Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects

From: Kevin Houle <kjh(at)cert(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org, dbdpg-general(at)svr3(dot)postgresql(dot)org
Subject: Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects
Date: 2003-08-24 01:15:22
Message-ID: 3F4811AA.6080400@cert.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:

> 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().
>
> I finally realized what's going on here. 7.3 branch CVS tip should fix
> it.

Good news. I'll test as soon as I'm able and report back
only if I still see an issue. No news is good news.

Thanks for the effort, Tom.

Kevin

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2003-08-24 04:35:35 "VIRUS found in:" Re: That movie
Previous Message Peter Eisentraut 2003-08-23 19:21:02 Re: contrib-global.mk and sql.in question