| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | lockhart(at)fourpalms(dot)org, Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: OCTET_LENGTH is wrong |
| Date: | 2001-11-20 21:55:38 |
| Message-ID: | 3BFAD15A.5040507@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>>>>There have been three ideas of what octet_length() sould return:
>>>> 1) compressed on-disk storage length
>>>> 2) byte length in server-side encoding
>>>> 3) byte length in client-side encoding
>>>>
>>...
>>
>>>>The open question is whether we should be doing #3.
>>>>
>>There is no question in my mind that (3) must be the result of
>>octet_length(). Any of the other options may give an interesting result,
>>but of no practical use to a client trying to retrieve data. And
>>everything is a client!
>>
>
>Also added to TODO:
>
> * Make octet_length_client the same as octet_length()
>
Will this break backward compatibility ?
-------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-20 22:41:03 | SPI and CommandCounterIncrement, redux |
| Previous Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-11-20 21:44:54 | Re: beta3 |