Re: Wire protocol: type-specific opt-in to binary format

* Florian Pflug:

>>> If you use the extended query protocol, the client can already choose
>>> text vs. binary representation on a per-column basis. You can query
>>> the result's column types by issuing a Describe message after the
>>> Parse message. For each column you can then decide whether you want
>>> textual or binary representation, and include that choice in the
>>> subsequent Bind message.
>>
>> Interesting. Doesn't this introduce another roundtrip?
>
> Yes. Maybe that's also something that should go on the next protocol version
> todo list.

Okay.

> In any case, this is something that solely concerns the client library
> (libpq, JDBC, ...), not users of that library, and should thus be handled
> on the protocol level, not via a GUC.

How is this different from the bytea_output GUC? libpq doesn't hide
that at all, but the JDBC driver does---similar to the text/binary
distinction.

--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99