Jeff, Bill:

> No.  The user docs state that the performance is equal for char, varchar
> and text.

Actually, CHAR is slightly *slower* than VARCHAR or TEXT for SELECTs in many 
applications.   This is becuase of the field padding, and the frequent 
necessity of casting CHAR::TEXT and back.

For INSERT and UPDATE, TEXT is the fastest becuase it's not checking a length 
constraint (takes time) or padding the field out to the required CHAR length 
(even more time).

Frankly, the only reason to use anything other than TEXT is compatibility with 
other databases and applications.

-Josh Berkus
 Aglio Database Solutions
 San Francisco

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?


Reply via email to