| From: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
|---|---|
| To: | Radoslaw Smogura <rsmogura(at)softperience(dot)eu> |
| Cc: | Florian Weimer <fweimer(at)bfk(dot)de>, Andreas Schmitz <schmitz(at)occamlabs(dot)de>, Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: bytea performance tweak |
| Date: | 2011-06-27 19:33:33 |
| Message-ID: | BANLkTike_g56WHUxF7yEndaji_Dj+gFphA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-06-27 22:20:01 | Re: Connecting over UNIX domain sockets |
| Previous Message | Hannu Krosing | 2011-06-27 19:06:58 | Re: Connecting over UNIX domain sockets |