Robert Haas escribió:
> char(n) is kind of a wierd case because you could also compress by
> storing a count of the trailing spaces, without applying a
> general-purpose compression algorithm. But either way the field is no
> longer fixed-width, and therefore field access can't be done as a
> simple byte offset from the start of the tuple.
That's not the case anyway (fixed byte width) due to possible multibyte
chars.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
