binary protocol was Performance problem with timestamps in result sets

As Oliver points out the timestamp is not a 64bit integer, or even a
floatingpoint number. It is a textual representation of the timestamp
which needs to be parsed. I looked at the parsing and I was unable to
see anything that could be significantly optimized.

So the option of going to the binary protocol exists. There are a
number of challenges with this. As Oliver points out this is an all
or nothing proposition. In other words you can't ask for just
timestamps to be returned in binary. The entire row comes back as
binary. Additionally, there are two possible representations of
timestamps in postgresql. One is a 64 bit integer, the other is
floating point. Added to this there may be endian issues ( do we know
the answer to this question ?)

Significant performance improvement exists for dates, times,
timestamps, however the advantages for the rest of the types is
questionable given the above assertions.

Comments ?

Dave