From: Mario Weilguni <mweilguni@sime.com>
To: pgsql-performance@postgresql.org
Subject: Re: Optimization of this SQL sentence
Date: Tue, 17 Oct 2006 17:29:19 +0200
User-Agent: KMail/1.9.4
Cc: Alexander Staubo <alex@purefiction.net>, Ruben Rubio <ruben@rentalia.com>
References: <45349CDF.3090002@rentalia.com> <4534A35E.9030909@rentalia.com>
	<181E6D21-8326-4ED6-A9AE-6F9917C1C319@purefiction.net>
In-Reply-To: <181E6D21-8326-4ED6-A9AE-6F9917C1C319@purefiction.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200610171729.19596.mweilguni@sime.com>

Am Dienstag, 17. Oktober 2006 11:52 schrieb Alexander Staubo:
> Lastly, note that in PostgreSQL these length declarations are not =C2=A0
> necessary:
>
> =C2=A0 =C2=A0contacto varchar(255),
> =C2=A0 =C2=A0fuente varchar(512),
> =C2=A0 =C2=A0prefijopais varchar(10)
>
> Instead, use:
>
> =C2=A0 =C2=A0contacto text,
> =C2=A0 =C2=A0fuente text,
> =C2=A0 =C2=A0prefijopais text
>
> See the PostgreSQL manual for an explanation of varchar vs. text.

Enforcing length constraints with varchar(xyz) is good database design, not=
 a=20
bad one. Using text everywhere might be tempting because it works, but it's=
=20
not a good idea.