Greg Stark <[EMAIL PROTECTED]> writes: > And indeed in pg_type the typalign column says "i" for this data type. My > question is just, why? What would be the problem with an alignment of 1 for > "name"?
Probably none, but that's how it's been defined since day one, and there doesn't seem any good reason to change. (Looking at the system catalog definitions, it doesn't appear that we'd save anything on alignment.) It's possible that back when that decision was taken, there was something in the bootstrap code that wouldn't work with non-int-aligned columns? Just a guess. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match