Re: forcing returned values to be binary - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: forcing returned values to be binary
Date
Msg-id 511212AF-9F32-43A2-BE95-C7C3DBE835E6@fastcrypt.com
Whole thread Raw
In response to Re: forcing returned values to be binary  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: forcing returned values to be binary  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Yeah,

I finally read it through and found it. There's some anecdotal  
evidence of up to 2x performance, so I'm interested in how to  
implement this in the jdbc driver. ( I'm a little skeptical about 2x)

I was thinking that it may be necessary to issue a describe before  
the execute, but I'm thinking now that the driver can only handle  
specific types, so anything outside of what it knows about would be  
an error anyway.

I gather it's not possible to mix the return format? For example all  
known types would be binary, others would be text ? At this point I'm  
not even sure it would help.

Thx,

Dave

On 13-Nov-05, at 10:21 PM, Tom Lane wrote:

> Dave Cramer <pg@fastcrypt.com> writes:
>> Is there a way to force select * from foo to use binary values ?
>
> In what context?
>
> There is a provision for that in the V3 extended-query protocol.
>
>             regards, tom lane
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 6: explain analyze is your friend
>



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: forcing returned values to be binary
Next
From: Tom Lane
Date:
Subject: Re: forcing returned values to be binary