Hi, Andrea,
if you aren't using prepared statements, it doesn't know that the data is
binary and it will "kick back" to the standard encoding (with a lot of
"\001"-like in the text). It will work, but you are at approximately 300%
overhead.
As mentioned, above, I believe it works for PostgreSQL
On Tue, May 30, 2017 at 7:01 PM, Dave Blasby
wrote:
> Hi, Andrea,
>
> Only updating the driver version.
>
> I can work with the PostGIS maintainer to get it in - it's fairly easy
> (just need to ensure that you are using prepared statements).
>
Maintainer eh? It used to be me and Justin.
When yo
Hi, Andrea,
Only updating the driver version.
I can work with the PostGIS maintainer to get it in - it's fairly easy
(just need to ensure that you are using prepared statements). The
difficulty is in verifying it's working - you don't really have any access
to what's happening in the driver. Fo
So, are you proposing just an upgrade of the driver, or are you also going
to change the postgis store code to leverage the
binary transfer?
Cheers
Andrea
On Mon, May 29, 2017 at 11:22 PM, Dave Blasby
wrote:
> Hi,
>
> For GeoGig, we noticed that the latest Postgresql JDBC driver (42.1.1) now
>
