From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PROTOCOL TODO] Permit streaming of unknown-length lob/clob (bytea,text,etc) |
Date: | 2014-12-01 14:54:08 |
Message-ID: | 547C8110.305@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/01/2014 10:38 PM, David Fetter wrote:
> On Mon, Dec 01, 2014 at 02:55:22PM +0800, Craig Ringer wrote:
>> Hi all
>>
>> Currently the client must know the size of a large lob/clob field, like
>> a 'bytea' or 'text' field, in order to send it to the server. This can
>> force the client to buffer all the data before sending it to the server.
>
> Yes, this is not good.
>
>> It would be helpful if the v4 protocol permitted the client to specify
>> the field length as unknown / TBD, then stream data until an end marker
>> is read.
>
> What's wrong with specifying its length in advance instead? Are you
> thinking of a one or more use cases where it's both large and unknown?
I am - specifically, the JDBC setBlob(...) and setClob(...) APIs that
accept streams without a specified length:
There are variants that do take a length, so PgJDBC can (and now does)
implement the no-length variants by internally buffering the stream
until EOF. It'd be nice to get rid of that though.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-12-01 14:57:01 | Re: [PROTOCOL TODO] Permit streaming of unknown-length lob/clob (bytea, text, etc) |
Previous Message | David Fetter | 2014-12-01 14:38:11 | Re: [PROTOCOL TODO] Permit streaming of unknown-length lob/clob (bytea,text,etc) |