| From: | Bruce Badger <bruce_badger(at)badgerse(dot)com> |
|---|---|
| To: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Text format protocol representation |
| Date: | 2003-05-14 00:54:13 |
| Message-ID: | 1052873653.31993.11.camel@wally |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2003-05-14 at 08:47, Peter Eisentraut wrote:
> What's the rationale for not including the trailing zero byte in the
> protocol representation of the text format? The output functions of data
> types generate one, and the client most likely wants one, so it seems
> unreasonable that the protocol cuts it out and the client has to put it
> back. Is the bandwidth saved worth the extra computation?
I maintain the Smalltalk PostgreSQL driver. Smalltalk does not require
special terminator characters in Strings, so for me, if the extra
character gets added to the end, I have to strip it off.
So, why expend badwidth *and* computation on this? :-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-14 03:48:58 | Re: Text format protocol representation |
| Previous Message | Sean Chittenden | 2003-05-14 00:01:38 | Re: LISTEN/NOTIFY benchmarks? |