Latin-9 5 bytes UTF-8 6 bytes UTF-16 10 bytes
But it should still fit in a char(5), wouldn't you agree?
Got you.
In postgresql there is no difference in storage method between text, varchar(n) and char(n).
Learn something new every day. Thanks!
So that would say the previous statements are not accurate? That is, there's no problem with using a varchar?
-- Until later, Geoffrey
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
