| From: | Rodrigo E(dot) De León Plicet <rdeleonp(at)gmail(dot)com> |
|---|---|
| To: | "Don Mies (NIM)" <dmies(at)networksinmotion(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Disadvantages to using "text" |
| Date: | 2008-05-07 16:01:09 |
| Message-ID: | a55915760805070901t7223f9f0r92404b1b1dbe475@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Wed, May 7, 2008 at 10:52 AM, Don Mies (NIM)
<dmies(at)networksinmotion(dot)com> wrote:
> Are there any reasons for not using the "text" type whenever a variable
> length string field is needed? Are there penalties in disk usage, memory
> usage or performance?
>
> What are the differences between declaring something "varchar" or
> "varchar(n)" or "text"? (I realize that the middle one has an upper limit
> while the others do not.)
Reading The Fine Manual reveals all that is asked:
http://www.postgresql.org/docs/8.3/static/datatype-character.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aurynn Shaw | 2008-05-07 16:02:10 | Re: Disadvantages to using "text" |
| Previous Message | Don Mies (NIM) | 2008-05-07 15:52:27 | Disadvantages to using "text" |