Re: text .vs. varchar

From: Bill Moran <wmoran(at)collaborativefusion(dot)com>
To: Joao Ferreira <jmcferreira(at)critical-links(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: text .vs. varchar
Date: 2008-08-13 12:45:19
Message-ID: 20080813084519.7ef002ab.wmoran@collaborativefusion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In response to Joao Ferreira <jmcferreira(at)critical-links(dot)com>:

> Hello all,
>
> I have a big database in which much information is stored in TEXT type
> columns (I did this initially because I did not want to limit the
> maximum size of the string to be stored)... but...
>
> .. let's say I choose an upper limit (p.ex. 200) for the string sizes
> and I start a fresh database with VARCHAR(200).
>
> What tradeoffs can I expect ? disk usage ? query execution times ?

See the "Tip" on this page, it answers your questions:
http://www.postgresql.org/docs/8.3/static/datatype-character.html

--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martin Gainty 2008-08-13 12:54:00 Re: text .vs. varchar
Previous Message Bill Moran 2008-08-13 12:43:30 Re: Postgres eats all memory