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
Subject: Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects
Date: 2003-08-17 02:25:30
Message-ID: 3F3EE79A.8070509@cert.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Kevin Houle wrote:

> Tom Lane wrote:
>
>> Kevin Houle <kjh(at)cert(dot)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.

s/lo_extract/lo_export/

Must work less.

Kevin

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Houle 2003-08-17 02:58:58 Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects
Previous Message Kevin Houle 2003-08-17 02:22:45 Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects