| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
| Cc: | hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] TODO addition |
| Date: | 1998-01-11 20:49:57 |
| Message-ID: | 199801112049.PAA08814@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> > * allow varchar() to only store used bytes, not maximum
>
> Hmm. Some file managers might make use of the fact that a column is of
> fixed storage size, which I would think varchar() should be. Also, it
> would possibly allow rows to be updated in place with predictable
> performance. The text type (or varchar w/o maximum specified) are
> available for truely variable length fields. I'll bet that others DBs
> make these assumptions too...
Char() is now fixed, varchar() is not, hence the varchar name. text is
unchanged.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-01-11 20:53:54 | Re: [PATCHES] Patches for getting version 6.2/6.2.1 running on |
| Previous Message | Bruce Momjian | 1998-01-11 20:48:39 | Re: [HACKERS] Alternate locations for databases |