| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | db(at)zigo(dot)dhs(dot)org |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, thhal(at)mailblocks(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: charset/collation in values |
| Date: | 2004-11-01 22:26:31 |
| Message-ID: | 20041102.072631.62373551.t-ishii@sra.co.jp |
| 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.
Right. AFAIK nobody has proposed charsets/collations onto disk.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hallgren | 2004-11-01 22:30:49 | Re: charset/collation in values |
| Previous Message | Andrew Dunstan | 2004-11-01 22:04:15 | Re: '\0' characters in procedural languages. |