Joshua D. Drake wrote: > I am not suggestion variant capitalization. I am suggestion a simple > document patch to help eliminate what may not be obvious.
Perhaps it would be more effective to clarify the error message? Right now it just says something to the effect of "invalid integer". I'd imagine "invalid memory unit: TB" would be less confusing. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(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
