On 13 September 2016 at 06:03, Petr Jelinek <p...@2ndquadrant.com> wrote:
> Oh sure, I don't see that as big problem, the TupleData already contains > type of the data it sends (to distinguish between nulls and text data) so > that's mostly about adding some different type there and we'll also need > type info in the column part of the Relation message but that should be easy > to fence with one if for different protocol version. The missing piece seems to be negotiation. If a binary-aware client connects to a non-binary aware server, the non-binary-aware server needs a way to say "you requested this option I don't understand, go away" or "you asked for binary but I don't support that". -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
