From the manual:
Tip: There are no performance differences between these
three types, apart from the increased storage size when using
the blank-padded type. While character(n) has performance
advantages in some other database systems, it has no such
advantages in PostgreSQL. In most situations text or
character varying should be used instead.
Note that varchar(n) will have a performance effect, because on
insert or update you have to check to make sure the input doesn't
exceed the specified length.
A
--
Andrew Sullivan | a...@crankycanuck.ca
I remember when computers were frustrating because they *did* exactly what
you told them to. That actually seems sort of quaint now.
--J.D. Baldwin
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
Nothing, if you don't use a limit for varchar.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majo...@postgresql.org so that your
message can get through to the mailing list cleanly
See also Peter Koczan's reply in the '"_" in a serach pattern' thread.
--
Lew