Thanks for all the answers.
Tom:
FWIW, I'd go with text results, especially if you already have code to
deal with that. PG's on-the-wire binary formats are more efficient to
process in some absolute sense, but they're hardly free: you need to
consider byte endianness for integers and
[ too tired to respond to the other points, but: ]
Shay Rojansky r...@roji.org writes:
It's also possible for a type not to have send/recv functions, i.e. to
support text-only use.
In that case, what would be the behavior of selecting such a type with an
extended query that specifies all
On 09/30/2014 01:09 PM, Shay Rojansky wrote:
The idea of using extended query protocol for non-prepared queries
raised another best practices question, which I'm hoping you can help
with. To get rid of text encoding (which is locale-dependent,
inefficient etc.) for certain fields, it seems
