Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects
| От | Kevin Houle |
|---|---|
| Тема | Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects |
| Дата | |
| Msg-id | 3F3EE6F5.107@cert.org обсуждение исходный текст |
| Ответ на | Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects
Re: DBD::Pg 'lo_read' fails on >= 32768 byte large objects |
| Список | 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 по дате отправления: