Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Because that would corrupt indexes on shared tables. (It might be
>> possible to finesse that, but it's not a no-brainer.)
> Oh, I hadn't thought of that. The problem isn't encoding, because we
> handle that already, but differen representations of time and stuff?
No, the problem is sort ordering of indexes on textual columns.
regards, tom lane
---------------------------(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
