| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "John R Pierce *EXTERN*" <pierce(at)hogranch(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "Raimon Fernandez" <coder(at)montx(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Implementing Frontend/Backend Protocol TCP/IP |
| Date: | 2009-10-27 08:55:13 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C203937FD2@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces |
John R Pierce wrote:
> yah, seriously. the binary protocol is not considered stable, it can
> change in subtle ways in each version. libpq handles the current
> version and all previous versions, and exposes all methods.
That's probably not the problem in the original message, but there
are things you can do with the frontend/backend protocol that libpq
does not expose: for example, with the extended query protocol you can
send a "Bind" call that requests that some of the results should be
returned in text format, others in binary.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Sergio Borgonovo | 2009-10-27 09:05:18 | design, ref integrity and performance |
| Previous Message | Raimon Fernandez | 2009-10-27 08:02:47 | Re: Implementing Frontend/Backend Protocol TCP/IP |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2009-10-27 10:10:43 | Re: Implementing Frontend/Backend Protocol TCP/IP |
| Previous Message | Raimon Fernandez | 2009-10-27 08:02:47 | Re: Implementing Frontend/Backend Protocol TCP/IP |