Re: charset/collation in values

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Hallgren <thhal(at)mailblocks(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: charset/collation in values
Date: 2004-11-01 15:41:30
Message-ID: 13961.1099323690@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Hallgren <thhal(at)mailblocks(dot)com> writes:
> 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.

I'm not sure if 1 byte is enough or not --- there might be more than 256
charsets/collations to support. 2 ought to be plenty though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dennis Bjorklund 2004-11-01 16:08:21 Re: charset/collation in values
Previous Message Andrew Dunstan 2004-11-01 15:30:44 Re: make check error on -HEAD