Message-ID: <1181993709.4673caedd6fe8@imp.free.fr>
Date: Sat, 16 Jun 2007 13:35:09 +0200
From: okparanoid@free.fr
To: pgsql-performance@postgresql.org
Subject: Re: determining maxsize for character varying
References: <1181987590.4673b306d4baf@imp.free.fr>
	<20070616105525.GA13754@KanotixBox>
In-Reply-To: <20070616105525.GA13754@KanotixBox>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.5

Thanks

if i understand well that means that if i choose character varying(3) or
character varying(8) or character varying(32) or character varying with no max
length the fields will take the same place in the disk (8kb) except for fields
too long to take place in the 8kb whose are stored in another place ?

Is that correct ?

So for small strings it's better to choose character(n) when it's possible ?


Best regards,

Loic

Selon Andreas Kretschmer <akretschmer@spamfence.net>:

> okparanoid@free.fr <okparanoid@free.fr> schrieb:
>
> > Hello i would like to know if not determining a max size value for a
> character
> > varying's fields decrease the perfomance (perhaps size of stockage ? or
> > something else ?)
>
> No problem because of the TOAST-technology:
> http://www.postgresql.org/docs/current/static/storage-toast.html
>
>
> Andreas
> --
> Really, I'm not out to destroy Microsoft. That will just be a completely
> unintentional side effect.                              (Linus Torvalds)
> "If I was god, I would recompile penguin with --enable-fly."    (unknow)
> Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
>                 http://www.postgresql.org/about/donate
>