Re: charset/collation in values
От
Tatsuo Ishii
Тема
Re: charset/collation in values
Дата
Msg-id
20041102.072631.62373551.t-ishii@sra.co.jp
Ответ на
Re: charset/collation in values (Dennis Bjorklund)
Список
Дерево обсуждения
charset/collation in values Dennis Bjorklund <db@zigo.dhs.org>
Re: charset/collation in values Peter Eisentraut <peter_e@gmx.net>
Re: charset/collation in values Tatsuo Ishii <t-ishii@sra.co.jp>
Re: charset/collation in values Peter Eisentraut <peter_e@gmx.net>
Re: charset/collation in values Dennis Bjorklund <db@zigo.dhs.org>
Re: charset/collation in values Peter Eisentraut <peter_e@gmx.net>
Re: charset/collation in values Dennis Bjorklund <db@zigo.dhs.org>
Re: charset/collation in values Peter Eisentraut <peter_e@gmx.net>
Re: charset/collation in values Tatsuo Ishii <t-ishii@sra.co.jp>
Re: charset/collation in values Thomas Hallgren <thhal@mailblocks.com>
Re: charset/collation in values Tom Lane <tgl@sss.pgh.pa.us>
Re: charset/collation in values Dennis Bjorklund <db@zigo.dhs.org>
Re: charset/collation in values Tatsuo Ishii <t-ishii@sra.co.jp>
Re: charset/collation in values Tom Lane <tgl@sss.pgh.pa.us>
Re: charset/collation in values Thomas Hallgren <thhal@mailblocks.com>
> 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
В списке pgsql-hackers по дате отправления