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 3F3EE6F5.107@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>)
Responses Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects  (Kevin Houle <kjh@cert.org>)
Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects  (Kevin Houle <kjh@cert.org>)
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?

One more data point. The DBD::Pg 'lo_extract' function works
fine across SSL. There is no issue with large objects >= 32K
using 'lo_extract'. So that casts doubt on it being an OpenSSL
issue. Is there a different code path within libpq.so to move
data from the server to the client via SSL for lo_extract than
for lo_read that we can learn from? I'm looking at the code,
but for the first time.

Kevin

pgsql-bugs by date:

Previous
From: Joe Conway
Date:
Subject: Re: error in docs
Next
From: Kevin Houle
Date:
Subject: Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects