Re: [postgis-devel] JDBC & WKB - 400% overhead

From: dblasby(at)openplans(dot)org
To: Markus Schaber <schabios(at)logi-track(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, PostGIS Development Discussion <postgis-devel(at)postgis(dot)refractions(dot)net>
Subject: Re: [postgis-devel] JDBC & WKB - 400% overhead
Date: 2005-02-23 17:25:01
Message-ID: 1109179501.421cbc6d4bd9e@webmail.limegroup.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Markus,

>Maybe your postgresql driver only uses text transfer up to now.
>asBinary() returns a byte array, so this should be transferred more
>efficiently.

I'm using the JDBC3 build 310 drivers (latest from jdbc.postgresql.org).

>Can you try the following query:
>
>select 5::float8,asBinary('POINT(0 0)')::bytea
>
asBinary() already returns a bytea:

#\df asbinary
List of functions
Schema | Name | Result data type | Argument data types
--------+----------+------------------+---------------------
public | asbinary | bytea | geometry
public | asbinary | bytea | geometry, text
(2 rows)

But, I tried your query and it, also, sends 84 bytes.

dave

----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message peter royal 2005-02-23 17:35:14 Re: DatabaseMetaData.getIndexInfo and function-based indexes
Previous Message Guillaume Cottenceau 2005-02-23 16:24:56 PGStatement#setUseServerPrepare breaking PreparedStatement#executeUpdate return value?