Skip site navigation (1) Skip section navigation (2)

Re: size of varchar

From: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
To: Andreas <maps(dot)on(at)gmx(dot)net>, pgsql-novice(at)postgresql(dot)org
Subject: Re: size of varchar
Date: 2007-03-23 04:55:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
> Therefore I have never figured out the really necessary size for 
> zip-codes, names, phone numbers and what not.
> Can I stay with size 255 in PG without getting a space- or speed-penalty ?
> I'll use ODBC. Is the size 255 relevant in network transfers ?

you probably can, I don't see how it would hurt. However, in postgres you don't even need to
specify a size for your varchar field.


If you desire to store long strings with no specific upper limit, use text or character varying
without a length specifier, rather than making up an arbitrary length limit.) 

Tip: There are no performance differences between these three types, apart from the increased
storage size when using the blank-padded type. While character(n) has performance advantages in
some other database systems, it has no such advantages in PostgreSQL. In most situations text or
character varying should be used instead. 

However, I do not recommend for programs like access or crystal reports.  They cast the types as a
MEMO field.  Reports can groupby these unbounded varchar field.  So it is better to put limits on
them. However, of you never intend to do anything other than store text, it probably would hurt.

Richard  Broersma Jr.

In response to

pgsql-novice by date

Next:From: Richard Broersma JrDate: 2007-03-23 05:21:27
Subject: default_transaction_isolation
Previous:From: AndreasDate: 2007-03-23 01:39:10
Subject: size of varchar

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group