Re: [postgis-devel] JDBC & WKB - 400% overhead - Mailing list pgsql-jdbc

From Markus Schaber
Subject Re: [postgis-devel] JDBC & WKB - 400% overhead
Date
Msg-id 421DA0C2.10407@logi-track.com
Whole thread Raw
In response to Re: [postgis-devel] JDBC & WKB - 400% overhead  (Kris Jurka <books@ejurka.com>)
Responses Re: [postgis-devel] JDBC & WKB - 400% overhead
List pgsql-jdbc
Hi, Kris,

Kris Jurka schrieb:

>>Maybe your postgresql driver only uses text transfer up to now.
>>asBinary() returns a byte array, so this should be transferred more
>>efficiently.
>
> The driver receives all data as text.  To be able to receive binary data
> we must support binary data for all types because we do not know what type
> we will be getting back from the SELECT before it is run.  Getting that
> information would require an extra network round trip so we don't want to
> do that.  Doing all binary transfer is on the 8.1 todo list, but I've yet
> to really get started on it.

Oh, I thought that binary transmit was implemented in 8.0 :-(

Then, currently, the better way to receive geometries may be to use the
new canonical text rep for geometries (hex-encoded extended WKB) which
is only two times as large compared to pure binary rep.

As there are at least plans to use caching of prepared statements, it
also should be possible to cache this information together with the
prepared statement. This would reduce the number of roundtrips.

Markus

--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com


Attachment

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Socket timeouts (probably)
Next
From: Kris Jurka
Date:
Subject: Re: [postgis-devel] JDBC & WKB - 400% overhead