From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thom Brown <thombrown(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Varchar vs text |
Date: | 2009-01-27 15:09:08 |
Message-ID: | 14484.1233068948@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thom Brown <thombrown(at)gmail(dot)com> writes:
> The reason I ask is because the documentation says "If character varying is
> used without length specifier, the type accepts strings of any size. The
> latter is a PostgreSQL extension." I wasn't sure if such an extension meant
> there was a level of over-head involved, or reduced its indexability.
"Extension" means "it's not in the SQL standard". It's not meant to imply
anything about performance.
There is some potential overhead from using varchar instead of text
because of the extra dummy cast nodes that are likely to be present in
your query expressions (since all the native functions are declared to
take/return text, not varchar). In most cases I'd think you'd be
hard-put to measure any difference though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tommy Gildseth | 2009-01-27 15:37:19 | Re: Text search with ispell |
Previous Message | Oleg Bartunov | 2009-01-27 14:49:06 | Re: Text search with ispell |