Re: charset/collation in values - Mailing list pgsql-hackers

From Tom Lane
Subject Re: charset/collation in values
Date
Msg-id 13961.1099323690@sss.pgh.pa.us
Whole thread Raw
In response to Re: charset/collation in values  (Thomas Hallgren <thhal@mailblocks.com>)
Responses Re: charset/collation in values  (Dennis Bjorklund <db@zigo.dhs.org>)
List pgsql-hackers
Thomas Hallgren <thhal@mailblocks.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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: make check error on -HEAD
Next
From: Dennis Bjorklund
Date:
Subject: Re: charset/collation in values