Re: Patch for binary receive of basic array types - Mailing list pgsql-jdbc

From Kevin Grittner
Subject Re: Patch for binary receive of basic array types
Date
Msg-id 4E7DA6D802000025000416A9@gw.wicourts.gov
Whole thread Raw
In response to Patch for binary receive of basic array types  (Mikko Tiihonen <mikko.tiihonen@nitorcreations.com>)
Responses Patch for allowing explicit enable/disable of binary transfer for each OID type  (Mikko Tiihonen <mikko.tiihonen@nitorcreations.com>)
List pgsql-jdbc
> Mikko Tiihonen  wrote:

> In general could add a mechanism to add/remove specific oids from
> the binary transfer mode as a configuration option to the jdbc
> driver.
>
> The same mechanism could be used for by application code that uses
> custom types inside PostgreSQL to take advantage of binary
> transfers.
>
> There will always be trade-offs between txt and bin encoding and
> sometimes the differences are large enough to change from driver
> defaults.

Yeah, all I'm saying is that when there are such large trade-offs
between CPU usage and network traffic requirements, it might be a
good idea to allow a user to choose with some connection option.  For
perspective, just within our organization we have cases where we're
communicating between busy machines on the same 1Gbps switch, and
cases where we're communicating between nearly-idle machines over a
sometimes-saturated 3Mbps WAN connection.  This change would be a big
win for one and could potentially be a big problem in the other.

-Kevin

pgsql-jdbc by date:

Previous
From: Mikko Tiihonen
Date:
Subject: Patch for binary transfer of point and box geometric types
Next
From: alexbruy
Date:
Subject: Re: Prepared statement with function as argument: how to bind values?