| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | zakkr(at)zf(dot)jcu(dot)cz, pgman(at)candle(dot)pha(dot)pa(dot)us, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: OCTET_LENGTH is wrong |
| Date: | 2001-11-20 19:57:00 |
| Message-ID: | 3BFAB58C.8020604@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii 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
>>>
>> Very nice is possibility of choice... What add everything:
>>
>> octet_length_storage()
>> octet_length_server()
>> octet_length_client()
>>
>
>We only need one of octet_length_server() or octet_length_client().
>
And i guess that octet_length_server() is cheaper as it does not do a
convert()
when not needed.
>
>We could emulate the rest using convert() etc.
>--
>Tatsuo Ishii
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://archives.postgresql.org
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2001-11-20 20:19:00 | Re: Further open item (Was: Status of 7.2) |
| Previous Message | Hannu Krosing | 2001-11-20 19:54:30 | Re: Btree doesn't work with ">" condition |