| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Hallgren <thhal(at)mailblocks(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: charset/collation in values |
| Date: | 2004-11-01 16:08:21 |
| Message-ID: | Pine.LNX.4.44.0411011703340.2015-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 1 Nov 2004, Tom Lane wrote:
> > I think the number of charset/collation combinations will be relatively
> > few so perhaps it would be space efficient to maintain a table where
> > each combination is given an oid and have string values store that
> > rather than two separate oid's?
>
> In fact, we should do our best to get the overhead down to 1 or 2 bytes.
> Two OIDs (8 bytes) is ridiculous.
Just to be clear, we don't want to store it on disk no matter what since
it should be enough to store it once for each column. As a first solution
we could store it just to keep it simple until we have tried it out.
--
/Dennis Björklund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-11-01 16:52:00 | Re: make check error on -HEAD |
| Previous Message | Tom Lane | 2004-11-01 15:41:30 | Re: charset/collation in values |