Nop, this is problem with information passed by encoding to binary format . Currently driver sends timestamp and
offsetas text unknown.
However in binary mode you may only send Julian local date or Julian UTC date, this means when
youcall set timestamp you need to know what is target type of field.
Sending timestamps as text unknown resolves this,
butmay add problems like in post you has referenced.
Regards,
Radek
-----Original Message-----
From: Maciek Sakrejda
Sent: 27 czerwca 2011 21:33
To: Radoslaw Smogura
Cc: Florian Weimer; Andreas Schmitz; Oliver Jowett; pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] bytea performance tweak
> I started with different assumption - encode everything in binary, eventually fix server.
I didn't realize the server lacked binary support for some types. I
guess the driver can disclose this as a caveat emptor when documenting
the binary flag. If you know your particular query workload will not
use certain types, it's not really an issue. If you can't be sure,
that's pretty much a show-stopper unless there's some kind of
automatic fallback to text mode at the driver level, which sounds much
too crazy to be useful.
> Problems are with timestamp encoding , here you can't send unknown, and I don't think it will be fixed in any way.
What issue are you talking about here? Is it related to this:
http://archives.postgresql.org/pgsql-jdbc/2006-12/msg00037.php ? If
so, we don't necessarily need to implement binary parameter input to
support binary result output.
---
Maciek Sakrejda | System Architect | Truviso
1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com
