Fw: TEXT vs VARCHAR - Mailing list pgsql-general

From Adam Lang
Subject Fw: TEXT vs VARCHAR
Date
Msg-id 02b601c032ee$212bd5a0$330a0a0a@6014cwpza006
Whole thread Raw
List pgsql-general

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Adam Lang" <aalang@rutgersinsurance.com>
To: <cmarkiew@commnav.com>
Sent: Tuesday, October 10, 2000 3:13 PM
Subject: Re: [GENERAL] TEXT vs VARCHAR


> If from what I understand correctly, text has an upper limit between 8K
and
> 32K (dependent upon the compiled configuration).  In the next release the
> limit is being removed.
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> ----- Original Message -----
> From: "chris markiewicz" <cmarkiew@commnav.com>
> To: <pgsql-general@postgresql.org>
> Sent: Tuesday, October 10, 2000 2:45 PM
> Subject: [GENERAL] TEXT vs VARCHAR
>
>
> > hello.
> >
> > i am faced with a situation where i must store a potentially large ascii
> > string (several thousand characters?).  i am looking for some insight
> beyond
> > what the documentation offers...
> >
> > is there a limit on the upper limit of a VARCHAR?  i cannot find one in
> the
> > documentation.
> >
> > is it true that a TEXT field can be any size?
> >
> > what is the best way to manage memory?  for example, if i declare it as
> > VARCHAR(10000), does that mean that memory for 10,000 characters will be
> > allocated whether i use it or not, or is it dynamic?  how about the TEXT
> > type.
> >
> > thanks
> > chris
>


pgsql-general by date:

Previous
From: "Adam Ruth"
Date:
Subject: Re: Some advanced database features, are they present in PostgreSQL
Next
From: Michael Meskes
Date:
Subject: Re: Re: [HACKERS] My new job