| 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 |
| Subject: | Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects |
| Date: | 2003-08-17 22:48:19 |
| Message-ID: | 3205.1061160499@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kevin Houle <kjh(at)cert(dot)org> writes:
>> 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.
No, it does not, because lo_export writes the data to a file on the
server side --- the data does not pass across the encrypted connection.
It still appears that there's an issue with moving a large chunk of
data across the link.
Whether this is OpenSSL's fault or libpq's is not clear. I'm prepared
to believe that we are not using SSL_read correctly, but if so, what
is the correct way? The OpenSSL docs are not very clear on how one
does asynchronous reads.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2003-08-18 01:55:16 | Re: [JDBC] Bug #926: if old postgresql.jar in CLASSPATH, |
| Previous Message | Palle Girgensohn | 2003-08-17 13:57:16 | Re: Bug #926: if old postgresql.jar in CLASSPATH, ant fails |