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

From Kevin Houle
Subject Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects
Date
Msg-id 3F3E3B48.9040000@cert.org
Whole thread Raw
In response to Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:
> Kevin Houle <kjh@cert.org> writes:
>
>>Is it just me, or are both sides reading waiting for the other
>>side to send data?
>
> Sure looks like it.  Could it be an OpenSSL bug?

Well, redhat-9 ships with openssl-0.9.7a so I tried it
with openssl-0.9.7b and lo_read still caused a read()
loop after 32768 bytes. Then I used a Debian sid machine
for testing using the same test case. It uses

   postgresql 7.3.3
   openssl 0.9.7b

The lo_read worked flawlessly on the Debian box. So I grabbed
the postgresql 7.3.3 packages from the PGDG website and tried
those on redhat-9. Still experienced the loop after 32768 bytes.

I'm at a bit of a loss here. It would be nice if someone else
could run the test script (see original message in this thread)
on a redhat-9 box to eliminate my environment from the equation.

Kevin

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Bug #926: if old postgresql.jar in CLASSPATH, ant fails
Next
From: Gonzalo Paniagua Javier
Date:
Subject: Reading from a read-only BLOB is allowed