| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | andreas(dot)zeugswetter(at)telecom(dot)at (Zeugswetter Andreas) |
| Cc: | lockhart(at)alumni(dot)caltech(dot)edu, pgsql-hackers(at)hub(dot)org |
| Subject: | Re: AW: [HACKERS] varchar() vs char16 performance |
| Date: | 1998-03-11 18:50:13 |
| Message-ID: | 199803111850.NAA21384@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> so the current char2-16 code behaves more like varchar. I don't know if anybody does
> rely on this behavior. If not, I would vote to change the char-char16 with the char()
> type and remove the varhdr from char(). I like getting a simple char * into my C function.
> (see point 1)
Removing the header from char() types is possible now that we have
atttypmod, but I doubt atttypmod is available in all places that the
length of the type is needed. varlena is supported all over the place
in the backend.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-03-11 19:05:17 | Re: [HACKERS] indexing words slow |
| Previous Message | Hal Snyder | 1998-03-11 17:15:34 | Re: [HACKERS] varchar() vs char16 performance |