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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Houle <kjh(at)cert(dot)org>
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-22 22:04:44
Message-ID: 7603.1061589884@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Creager 2003-08-23 04:31:26 contrib-global.mk and sql.in question
Previous Message Tom Lane 2003-08-22 22:02:51 Re: 7.3.4 patch for libpq SSL_read() problems?