Re: VARCHAR vs TEXT

From: Frank Bax <fbax(at)sympatico(dot)ca>
To: pgsql-sql(at)postgresql(dot)org
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: VARCHAR vs TEXT
Date: 2001-10-16 15:46:43
Message-ID: 3.0.6.32.20011016114643.01e80c00@pop6.sympatico.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Perhaps 'limits' should be part of FAQ, not separate entity?

Also a reference (or link) to 'limits' from other sections such as
mentioned below may be more appropriate than duplicating the information.

Frank

At 08:56 AM 10/16/01 -0400, you wrote:
>> >>>>> "BM" == Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>>
>> BM> <P>CHAR() is best when storing strings that are usually the
>> BM> same length. VARCHAR() is best when storing variable-length
strings,
>> BM> but you want to limit how long a string can be. TEXT is for
strings
>> BM> of unlimited length, maximum 1 gigabyte. BYTEA is for storing
>> BM> binary data, particularly values that include NULL bytes.</P>
>>
>> Could you add the length limitation for TEXT to the reference manual?
>> I searched high and low for that limit, but never found it. Also,
>> what's the max VARCHAR() or CHAR() I can create? Is that also 1Gb?
>
>TEXT limit is 1GB, as shown on the 'limits' FAQ item. Is it worth
>mentioning here? CHAR()/VARCHAR() also 1GB limit.
>
>--
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Bruce Momjian 2001-10-16 15:55:21 Re: VARCHAR vs TEXT
Previous Message Vivek Khera 2001-10-16 14:08:11 Re: VARCHAR vs TEXT